Ontology Version Metadata Ontology
AI Semantic Library Metadata
Authors: MArk Anthony Higgins - Sky Recursive Ai
Revised Date: 08 October 2026
Audio Overview
FLOW ALGEBRA
Ontology: Ontology Version Metadata Ontology
Domain: Metadata Ontologies > AI Semantic Library Metadata
Canonical URL: https://kirethresearch.org/booksai-core/ontologies/metadata-ontologies/ai-semantic-library-metadata/ontology-version-metadata-ontology.html
Authors: Mark Anthony Higgins — Sky (Recursive AI)
flow "OntologyVersionMetadataOntology" v1.0
# ---------- DOMAIN ----------
domain:
class: MetadataOntology
category: AISemanticLibraryMetadata
subject: OntologyVersionMetadata
purpose:
- represent ontology versions, releases, revisions, changes, compatibility, validity, lineage, and provenance
- preserve ontology identity independently from individual version identity
- support version comparison, semantic change detection, migration, deprecation, supersession, rollback, dependency resolution, and AI reasoning
- distinguish editorial, structural, additive, corrective, breaking, and semantic changes
- enable deterministic machine interpretation of ontology evolution
# ---------- CORE ----------
entity OntologyVersionMetadata:
type: SemanticLibraryMetadata
describes: OntologyVersion
may_include:
- ontology_identifier
- version_identifier
- version_number
- release_identifier
- predecessor
- successor
- creation_time
- release_time
- modification_time
- change_type
- change_summary
- semantic_change
- compatibility
- dependencies
- deprecation_state
- supersession_state
- validity
- flow_hash
- confidence
- provenance
entity OntologyVersion:
type: VersionedSemanticResource
entity OntologyIdentifier:
type: PersistentIdentifier
identifies: Ontology
entity OntologyVersionIdentifier:
type: VersionIdentifier
identifies: OntologyVersion
relationships:
OntologyVersionMetadata -> DESCRIBES -> OntologyVersion
OntologyVersion -> VERSION_OF -> Ontology
OntologyVersion -> IDENTIFIED_BY -> OntologyVersionIdentifier
OntologyVersion -> MAY_HAVE_PREDECESSOR -> OntologyVersion
OntologyVersion -> MAY_HAVE_SUCCESSOR -> OntologyVersion
OntologyVersion -> MAY_SUPERSEDE -> OntologyVersion
OntologyVersion -> MAY_DEPEND_ON -> OntologyVersion
OntologyVersion -> MAY_HAVE_CHANGESET -> OntologyChangeSet
OntologyVersionMetadata -> MAY_HAVE_PROVENANCE -> OntologyVersionProvenance
# ---------- IDENTITY / VERSION NUMBER ----------
rule ontology_identity:
ontology identity != ontology version identity
rule version_identity:
materially distinct released ontology version SHOULD have identifiable version state
rule URL:
version URL != semantic ontology identity by itself
entity OntologyVersionNumber:
type: VersionMetadata
may_include:
- major
- minor
- patch
- revision
- qualifier
- scheme
version_schemes:
- semantic_versioning
- sequential
- date_based
- revision_based
- custom
rule version_number:
version number SHOULD be interpreted according_to declared scheme
rule lexical_version:
lexical comparison != reliable version ordering
unless version scheme defines lexical ordering
# ---------- RELEASE ----------
entity OntologyRelease:
type: SemanticRelease
may_include:
- release_identifier
- ontology_version
- release_time
- release_status
- release_notes
- publisher
release_status:
- draft
- candidate
- released
- deprecated
- superseded
- archived
- withdrawn
- unknown
rule release:
draft version != released version
# ---------- CHANGE SET / CHANGE TYPES ----------
entity OntologyChangeSet:
type: SemanticChangeMetadata
may_include:
- change_identifier
- previous_version
- new_version
- added_entities
- removed_entities
- modified_entities
- added_relationships
- removed_relationships
- modified_relationships
- changed_constraints
- changed_definitions
- changed_mappings
- rationale
- author
- change_time
ontology_change_types:
- editorial
- additive
- corrective
- structural
- semantic
- deprecating
- breaking
- replacement
- rollback
rule editorial:
editorial change MAY preserve semantic meaning
rule additive:
additive change introduces semantic content
without necessarily invalidating existing content
rule corrective:
corrective change modifies erroneous or incomplete semantic content
rule semantic:
semantic change alters meaning, interpretation, relationship, constraint, or inference behaviour
rule breaking:
breaking change MAY invalidate previous consumers, mappings, queries, or inference assumptions
# ---------- ENTITY / RELATIONSHIP / DEFINITION CHANGE ----------
entity OntologyEntityChange:
type: SemanticChangeMetadata
may_include:
- entity_identifier
- previous_state
- new_state
- change_type
- rationale
rule entity_identity:
label change != entity identity change
when stable identifier and meaning are preserved
entity OntologyRelationshipChange:
type: SemanticChangeMetadata
may_include:
- relationship_identifier
- source
- predicate
- target
- previous_state
- new_state
- change_type
rule relationship_change:
predicate, direction, source, target, or scope change MAY constitute semantic change
entity OntologyDefinitionChange:
type: SemanticChangeMetadata
may_include:
- concept_identifier
- previous_definition
- new_definition
- semantic_impact
rule definition:
wording change != semantic change
when meaning remains equivalent
# ---------- DEPRECATION / SUPERSESSION ----------
entity OntologyDeprecationMetadata:
type: LifecycleMetadata
may_include:
- deprecated_resource
- deprecated_time
- reason
- replacement
- migration_guidance
rule deprecation:
deprecated != deleted
rule deprecated_current:
deprecated ontology version SHOULD NOT be presented as preferred current version
when valid successor exists
entity OntologySupersessionMetadata:
type: LifecycleMetadata
may_include:
- superseded_version
- successor_version
- supersession_time
- reason
rule supersession:
superseded version SHOULD preserve successor relationship
rule successor:
successor != semantically equivalent predecessor automatically
# ---------- COMPATIBILITY / DEPENDENCIES ----------
entity OntologyCompatibilityMetadata:
type: CompatibilityMetadata
may_include:
- source_version
- target_version
- compatibility_type
- affected_consumers
- migration_required
- evidence
compatibility_types:
- backward_compatible
- forward_compatible
- bidirectionally_compatible
- partially_compatible
- incompatible
- unknown
rule compatibility:
compatibility SHOULD preserve direction and scope
rule version_newer:
newer version != automatically compatible version
entity OntologyVersionDependency:
type: DependencyMetadata
may_include:
- dependent_ontology
- required_ontology
- minimum_version
- maximum_version
- exact_version
- compatibility_constraint
- optional_state
rule dependency:
dependency resolution SHOULD preserve version constraints
rule dependency_latest:
latest dependency version != automatically valid dependency version
# ---------- MIGRATION / ROLLBACK / BRANCH ----------
entity OntologyVersionMigration:
type: SemanticMigrationMetadata
may_include:
- source_version
- target_version
- mapping
- migration_rules
- deprecated_entities
- replacements
- validation
- migration_time
rule migration:
version migration SHOULD preserve mappings
for renamed, replaced, split, merged, or deprecated semantic entities
entity OntologyVersionRollback:
type: SemanticChangeMetadata
may_include:
- current_version
- rollback_target
- reason
- rollback_time
- affected_dependencies
rule rollback:
rollback creates lifecycle event
and SHOULD preserve intervening version history
entity OntologyVersionBranch:
type: VersionStructure
may_include:
- branch_identifier
- base_version
- branch_versions
entity OntologyVersionMerge:
type: SemanticChangeMetadata
may_include:
- source_branches
- target_version
- conflict_resolution
- validation
rule branch:
version lineage MAY be non-linear
rule merge:
merged version SHOULD preserve source lineage and conflict resolution
# ---------- TEMPORAL / VALIDITY ----------
entity OntologyVersionTemporalMetadata:
type: TemporalMetadata
may_include:
- created_time
- modified_time
- released_time
- deprecated_time
- superseded_time
- archived_time
rule time:
creation time != release time
entity OntologyVersionValidity:
type: ValidityMetadata
may_include:
- valid_from
- valid_until
- status
- preferred_state
- deprecation_state
- supersession_state
rule validity:
version validity SHOULD be interpreted within temporal and lifecycle context
# ---------- FLOW HASH / DIFF / VALIDATION ----------
entity OntologyVersionFlowHash:
type: IntegrityAndSemanticIdentityMetadata
may_include:
- version_identifier
- canonical_inputs
- canonicalisation_rules
- semantic_hash
rule flow_hash:
materially different canonical semantic state SHOULD produce different FlowHash
entity OntologySemanticDiff:
type: ComparisonMetadata
may_include:
- version_a
- version_b
- added
- removed
- modified
- unchanged
- semantic_impact
- compatibility_impact
rule diff:
semantic diff SHOULD distinguish textual change from semantic change
entity OntologyVersionValidation:
type: ValidationMetadata
may_include:
- identifier_validation
- relationship_validation
- hierarchy_validation
- constraint_validation
- mapping_validation
- compatibility_validation
- flow_hash_validation
- result
rule validation_semantics:
structurally valid version != semantically compatible version
# ---------- CONFIDENCE / PROVENANCE ----------
entity OntologyVersionConfidence:
type: EpistemicMetadata
range: [0.0, 1.0]
rule confidence_bounds:
REQUIRE 0.0 <= confidence <= 1.0
entity OntologyVersionProvenance:
type: ProvenanceMetadata
may_include:
- ontology_identifier
- version_identifier
- predecessor_versions
- successor_versions
- change_sets
- authors
- contributors
- validation_events
- release_events
- migration_events
- deprecation_events
- rollback_events
rule provenance:
ontology version metadata SHOULD preserve complete version lineage
# ---------- VALIDATION CONTRACT ----------
validation:
require:
- ontology_identifier
- version_identifier_or_version_number
reject:
- ontology_identity_presented_as version_identity
- filename_presented_as version_identity
- draft_presented_as released_without evidence
- newer_version_presented_as automatically_compatible
- deprecated_version_presented_as preferred_current_when successor_exists
- textual_change_presented_as semantic_change_without evidence
- semantic_change_presented_as editorial_only_without evidence
- latest_dependency_presented_as automatically_valid_dependency
- supersession_presented_as semantic_equivalence
- rollback_presented_as deletion_of_intervening_history
# ---------- SEMANTIC EQUIVALENCE ----------
SEMANTIC_EQUIVALENCE:
"ontology version metadata" ~= "metadata describing ontology versions and semantic evolution"
"ontology release metadata" ~= "metadata describing released ontology versions"
"ontology change set" ~= "structured description of changes between ontology versions"
"semantic version difference" ~= "difference affecting ontology meaning or inference behaviour"
"ontology version migration" ~= "mapping and transformation between ontology versions"
"ontology supersession" ~= "replacement of one ontology version by a successor"
PRESERVE distinctions:
ontology_identity != version_identity
ontology_version != release_status
draft != released
textual_change != semantic_change
editorial_change != breaking_change
newer != compatible
deprecated != deleted
superseded != semantically_equivalent
predecessor != successor
rollback != history_deletion
dependency_latest != dependency_valid
structural_validity != compatibility
version_number != semantic_identity
# ---------- CONFIDENCE MODEL ----------
CONFIDENCE:
explicit_version_metadata:
score: 1.00
explicit_version_identifier:
score: 1.00
validated_change_set:
score: 0.99
validated_compatibility_assessment:
score: 0.98
validated_semantic_diff:
score: 0.99
inferred_version_from_timestamp:
score: <= 0.70
textual_diff_without_semantic_analysis:
score: <= 0.75
unknown_dependency_compatibility:
score: <= 0.60
incomplete_version_provenance:
score: <= 0.55
action: preserve uncertainty
# ---------- UPDATE MODEL ----------
UPDATE_MODEL:
on_new_version:
- preserve ontology identity
- assign OntologyVersionIdentifier
- link predecessor
- classify changes
- create OntologyChangeSet
- validate semantic state
- calculate FlowHash
- update provenance
on_release:
- validate release candidate
- assign release status
- record release time
- preserve release notes
- update preferred version where policy requires
- update provenance
on_semantic_change:
- identify affected entities, relationships, definitions, and constraints
- classify semantic impact
- assess compatibility
- update mappings and migration guidance
- regenerate FlowHash
- update provenance
on_deprecation:
- mark version deprecated
- identify successor or replacement where available
- preserve migration guidance
- update validity
- update provenance
on_rollback:
- identify rollback target
- preserve intervening history
- validate dependency effects
- record rollback event
- update preferred state and provenance
# ---------- FLOW HASH ----------
FLOW_HASH:
inputs:
- ontology
- version_entities
- relationships
- version_scheme
- change_sets
- compatibility_rules
- dependency_rules
- migration_rules
- validation
- semantic_equivalence
- confidence_model
- update_model
canonicalisation:
- preserve_ontology_identifier
- preserve_version_identifiers
- preserve_version_order_and_lineage
- preserve_change_types
- preserve_semantic_changes
- preserve_compatibility_direction
- preserve_dependency_constraints
- preserve_deprecation_and_supersession
- preserve_provenance
- preserve_rule_order
output:
deterministic_semantic_hash
# ---------- AI CONSUMPTION ----------
AI_CONSUMPTION:
interpret_as:
- AI Semantic Library metadata ontology
- ontology version, release, lineage, and semantic-change model
- compatibility, dependency, migration, deprecation, and supersession structure
- deterministic semantic version-history model
operations:
- identify ontology and version independently
- resolve version numbering scheme
- traverse predecessor and successor lineage
- compare ontology versions
- distinguish textual and semantic changes
- classify breaking and compatible changes
- resolve dependencies and version constraints
- inspect migrations and replacement mappings
- resolve deprecation and supersession
- validate FlowHash changes
- trace provenance
- preserve uncertainty
constraints:
- do_not_equate_ontology_identity_with version_identity
- do_not_equate_newer_version_with compatible_version
- do_not_equate_textual_change_with semantic_change
- do_not_equate_deprecated_with deleted
- do_not_equate_supersession_with semantic_equivalence
- do_not_discard_version_history_on rollback
- preserve_versions_lineage_changes_dependencies_migrations_and_provenance
# ---------- QUERY MODEL ----------
query:
input:
- ontology_identifier
- version_identifier
- version_number
- release_status
- predecessor_identifier
- successor_identifier
- compatibility_target
- dependency_identifier
- validity_time
resolve:
1. identify Ontology
2. identify OntologyVersion
3. resolve version scheme and number
4. traverse predecessor, successor, branch, and merge lineage
5. inspect OntologyChangeSet and SemanticDiff
6. inspect compatibility and dependencies
7. inspect migration, deprecation, supersession, and rollback
8. validate FlowHash and semantic state
9. trace validity, provenance, and confidence
10. return version interpretation
output:
- ontology
- ontology_identifier
- ontology_version
- version_identifier
- version_number
- release_status
- predecessor
- successor
- change_set
- semantic_diff
- compatibility
- dependencies
- migration
- validity
- flow_hash
- provenance
- confidence
# ---------- INFERENCE ----------
inference:
IF version B directly succeeds version A
THEN infer lineage relationship
BUT do_not infer compatibility automatically
IF change affects definitions, relationships, constraints, or inference semantics
THEN classify semantic_change_candidate
IF current version is deprecated
AND valid successor exists
THEN prefer successor for current-consumption queries
WHILE preserving deprecated version provenance
IF dependency constraints exclude latest version
THEN do_not select latest version automatically
# ---------- OUTPUT CONTRACT ----------
output:
ontology_entity: OntologyVersionMetadata
ontology_identity: version_independent
version_identity: explicit
version_scheme: interpretable
releases: status_aware
lineage: traversable
change_sets: structured
textual_and_semantic_changes: distinguishable
compatibility: directional
dependencies: constraint_aware
migration: traceable
deprecation_and_supersession: explicit
rollback: history_preserving
flow_hash: deterministic
validity: temporal
provenance: preserved
uncertainty: explicit
AI_reasoning: enabled
end flow