rdfs:comment"""OWL T-Box. Six layers (Ownership, Business, Logical, Delivery, Physical, Consumption) crossed with a provenance axis (Curated vs Observed). Curated objects are asserted by governance and reviewed; Observed objects are harvested from Snowflake, Tableau and Looker and are rebuilt, never edited. Bridge annotation properties are declared for future alignment with domain ontologies.""" .
# ---- Bridge to conceptual (domain) ontologies -----------------
# A meta model instance is a DOCUMENTATION RECORD about a concept.
# A domain ontology holds the CONCEPT ITSELF, axiomatised.
# "Customer Invoice" is an INSTANCE of pr:BusinessObject here,
# and a CLASS (fin:Invoice) there. These three properties join the two.
# Annotation properties (not object properties) so that pointing an
# individual at a class stays inside OWL 2 DL without punning.
pr:denotes a owl:AnnotationProperty ;
rdfs:label "denotes" ;
rdfs:comment "Links a documentation record (Business Object, Business Concept, Data Object) to the CLASS it describes in a domain ontology. Example: ex:BO_16_03_001 pr:denotes fin:Invoice ." .
pr:denotesProperty a owl:AnnotationProperty ;
rdfs:label "denotes property" ;
rdfs:comment "Links a Data Element or Business Concept to the PROPERTY it describes in a domain ontology. Example: ex:DE_16_03_0001 pr:denotesProperty fin:netAmount ." .
pr:denotesActivity a owl:AnnotationProperty ;
rdfs:label "denotes activity" ;
rdfs:comment "Links a Metric or Business Object to the PROCESS or EVENT it describes, typically a prov:Activity subclass. Example: ex:M_16_03_001 pr:denotesActivity fin:InvoiceIssuance ." .
rdfs:comment "Anything the meta model describes. Actors are deliberately NOT Meta Model Objects." .
pr:CuratedObject a owl:Class ; rdfs:subClassOf pr:MetaModelObject ;
rdfs:label "Curated Object" ;
pr:curationMode "ASSERTED" ;
rdfs:comment "Asserted by governance, edited through pull request on the domain TTL file, subject to the full ownership and lifecycle shape (identifier, name, owner, owning Data Domain, status, version)." .
pr:ObservedObject a owl:Class ; rdfs:subClassOf pr:MetaModelObject ;
rdfs:label "Observed Object" ;
pr:curationMode "HARVESTED" ;
rdfs:comment "Harvested from a running system and rebuilt on every run. Never hand-edited. Carries sourceIdentifier, fullyQualifiedName and harvestedOn instead of curated ownership: attribution is INFERRED through the Data Element it is mapped to, not asserted on the node." .
pr:OwnershipLayerObject a owl:Class ; rdfs:subClassOf pr:CuratedObject ;
pr:DeliveryLayerObject a owl:Class ; rdfs:subClassOf pr:CuratedObject ;
rdfs:label "Delivery Layer Object" ;
rdfs:comment "What we promise, to whom, until when. A different question from how the data is structured, hence a layer of its own: version, owner, changelog, support channel, consumers to warn." .
pr:PhysicalLayerObject a owl:Class ; rdfs:subClassOf pr:ObservedObject ;
rdfs:label "Physical Layer Object" .
pr:ConsumptionLayerObject a owl:Class ; rdfs:subClassOf pr:ObservedObject ;
rdfs:label "Consumption Layer Object" ;
rdfs:comment "The BI estate. Separate from Physical because BI assets have their own lifecycle and their own owner: a dashboard belongs to its author, not to the Data Domain that owns the underlying data." .
rdfs:comment "The single anchor of accountability, which is why it stays in the Ownership layer: it is the one object where a steward is declared, and Data Objects and Data Elements inherit from it. It carries NO business definition of its own -- its meaning comes from its aboutConcept. What it does carry is a perimeter: the subject it is about, and the notions needed to read it." .
pr:BusinessConcept a owl:Class ; rdfs:subClassOf pr:BusinessLayerObject ;
rdfs:label "Business Concept" ;
rdfs:comment "A shared business notion WITHOUT a formula. The presence of a formula is the sole discriminator against Metric (rule BR-003)." .
pr:Metric a owl:Class ; rdfs:subClassOf pr:BusinessLayerObject ;
rdfs:label "Metric" ;
rdfs:comment "A quantifiable measurement WITH a formula, a unit and a grain. Under BR-013 a Metric carries the harmonised CALCULATION RULE; variants that differ only by analysis context are Data Elements linked back via computedBy." .
pr:KPI a owl:Class ; rdfs:subClassOf pr:Metric ;
rdfs:label "Key Performance Indicator" ;
rdfs:comment "An elevated Metric. Use this class rather than the deprecated isKPI flag." .
rdfs:comment "The pivot: represents exactly one Business Object, is composed of Data Elements, and is materialized as one or more Physical Relations. The single junction between governance and technology." .
pr:DataElement a owl:Class ; rdfs:subClassOf pr:LogicalLayerObject ;
rdfs:label "Data Element" ;
pr:curationMode "PROPOSED_CONFIRMED" ;
rdfs:comment "The finest curated unit. Its mapping to a physical Field is the ONLY place where the curated graph and the observed graph meet: proposed automatically by name and type matching, confirmed by a Data Steward." .
pr:DataAsset a owl:Class ; rdfs:subClassOf pr:LogicalLayerObject ;
rdfs:comment "v1.0 term, defined as 'directly consumable by a business user' -- a judgement, not a structural test, which is why it collected zero instances in a year. Use DataInterface." .
rdfs:comment "The unit of delivery: what carries a version number, an owner, a changelog, a support channel and a list of consumers to warn. It has no single technical counterpart, and should not: physically it often lands on a Snowflake schema or a dbt project, but that is not what defines it. Operated by exactly one Sub-Domain -- it is a consumable, and there must be no ambiguity about who runs it. Candidate alignment: dcat:Dataset / DPROD." .
pr:DataInterface a owl:Class ; rdfs:subClassOf pr:DeliveryLayerObject ;
rdfs:label "Data Interface" ;
rdfs:comment "The channel through which a consumer actually gets the data: a Snowflake secure share or listing, a consumption schema with its grants, a file extract to a panel partner, an API or reverse-ETL feed. Not a Data Object (that is structure) and not a BI Data Source (that is one consumer among others). Verifiable: a grant, a share or an endpoint either exists or it does not. The output port in data-mesh terms." .
pr:DataContract a owl:Class ; rdfs:subClassOf pr:DeliveryLayerObject ;
rdfs:comment "The service commitment attached to a Data Product: schema, freshness, quality thresholds, support, breaking-change notice period. Candidate alignment: ODCS (Bitol)." .
pr:System a owl:Class ; rdfs:subClassOf pr:PhysicalLayerObject ;
rdfs:label "System" ;
pr:harvestSource "Manually seeded once, then referenced. Replaces the free-text hasSourceSystem." ;
rdfs:comment "A real system: Snowflake, MDM Product, MDM Customer, a panel provider feed, Tableau Server, Looker. Making this a node rather than a string is what makes 'what depends on MDM Product?' answerable." .
pr:Database a owl:Class ; rdfs:subClassOf pr:PhysicalLayerObject ;
rdfs:comment "Abstract parent of everything with columns. Specialised because impact traversal differs by kind: a View propagates impact to whatever it reads." .
pr:BaseTable a owl:Class ; rdfs:subClassOf pr:PhysicalRelation ;
rdfs:label "Base Table" .
pr:View a owl:Class ; rdfs:subClassOf pr:PhysicalRelation ;
rdfs:label "View" ;
rdfs:comment "Depends on other relations through dependsOn, so impact is transitive." .
pr:MaterializedView a owl:Class ; rdfs:subClassOf pr:PhysicalRelation ;
rdfs:label "Materialized View" .
pr:ExternalTable a owl:Class ; rdfs:subClassOf pr:PhysicalRelation ;
rdfs:label "External Table" ;
rdfs:comment "Backed by files outside the warehouse. Marks the boundary where lineage leaves Snowflake." .
pr:Table a owl:Class ; rdfs:subClassOf pr:PhysicalRelation ;
rdfs:label "Table (deprecated)" ;
owl:deprecated true ;
dcterms:isReplacedBy pr:BaseTable ;
rdfs:comment "v0.9 term. Kept so that existing assertions still classify. Use BaseTable." .
pr:Field a owl:Class ; rdfs:subClassOf pr:PhysicalLayerObject ;
rdfs:comment "Gives foreign keys a home. Rule OW-006 says an FK is not a Data Element - true, but it still needs somewhere to live, and it lets the asserted DataObject-references-DataObject edge be checked against reality." .
pr:PrimaryKey a owl:Class ; rdfs:subClassOf pr:KeyConstraint ;
rdfs:label "Primary Key" .
pr:ForeignKeyConstraint a owl:Class ; rdfs:subClassOf pr:KeyConstraint ;
rdfs:label "Foreign Key Constraint" .
pr:Transformation a owl:Class ; rdfs:subClassOf pr:PhysicalLayerObject , prov:Activity ;
rdfs:label "Transformation" ;
pr:harvestSource "dbt manifest.json, Snowflake TASKS, Azure Data Factory pipelines" ;
rdfs:comment "The code that turns inputs into outputs: a dbt model, a Snowflake task, an ADF pipeline. Subclass of prov:Activity so that lineage is expressed in a standard vocabulary rather than a private one." .
pr:BIWorkspace a owl:Class ; rdfs:subClassOf pr:ConsumptionLayerObject ;
rdfs:label "BI Workspace" ;
pr:harvestSource "Tableau Metadata API (Project/Site) ; Looker API (Model)" .
pr:BIDataSource a owl:Class ; rdfs:subClassOf pr:ConsumptionLayerObject ;
rdfs:label "BI Data Source" ;
pr:harvestSource "Tableau Published Datasource ; Looker Explore" ;
rdfs:comment "The semantic surface a report is built on. This is where BI meets the warehouse." .
pr:BIField a owl:Class ; rdfs:subClassOf pr:ConsumptionLayerObject ;
rdfs:label "BI Field" ;
pr:harvestSource "Tableau calculated fields ; LookML measures and dimensions" ;
rdfs:comment "A field as a business user sees it. realizesMetric is what turns a certified Metric from a definition on paper into something measurable against the real BI estate." .
pr:BIReport a owl:Class ; rdfs:subClassOf pr:ConsumptionLayerObject ;
rdfs:comment "What a Data Governance Lead actually cares about in an impact analysis: not that a column changed, but which reports break and who to warn." .
pr:DataDomainOwner a owl:Class ; rdfs:subClassOf pr:Actor ;
rdfs:label "Data Domain Owner" ;
rdfs:comment "Accountable for a Data Domain. Exactly one per domain." .
pr:SubDomainOwner a owl:Class ; rdfs:subClassOf pr:Actor ;
rdfs:label "Sub-Domain Owner" ;
rdfs:comment "Accountable for a Sub-Domain. Exactly one per sub-domain." .
pr:DataGovernanceLead a owl:Class ; rdfs:subClassOf pr:Actor ;
rdfs:label "Data Governance Lead" ;
pr:hasAcronym "DGL" ;
rdfs:comment "Runs governance for a Data Domain. The acronym belongs in hasAcronym, not in the label (rule NR-005)." .
pr:DataProductOwner a owl:Class ; rdfs:subClassOf pr:Actor ;
rdfs:label "Data Product Owner" ;
rdfs:comment "Runs a Data Product day to day: releases, changelog, support, consumer communication. Belongs to the Sub-Domain that operates the product." .
pr:DataSteward a owl:Class ; rdfs:subClassOf pr:Actor ;
rdfs:label "Data Steward" ;
rdfs:comment "Monitors a Business Object. Declared there and nowhere else: Data Objects and Data Elements inherit their steward, so that no column can ever have two answers to 'who watches this'." .
pr:ActivationStatus a owl:Class ; rdfs:label "Activation Status" .
pr:NotActivated a pr:ActivationStatus ; rdfs:label "Not Activated" .
pr:LightActivation a pr:ActivationStatus ; rdfs:label "Light Activation" .
pr:FullActivation a pr:ActivationStatus ; rdfs:label "Full Activation" .
pr:Environment a owl:Class ; rdfs:label "Environment" ;
rdfs:comment "Same logical object, several physical incarnations. Kept as a vocabulary rather than folded into the name so that DEV drift never pollutes PROD lineage." .
pr:Development a pr:Environment ; rdfs:label "Development" .
pr:UserAcceptance a pr:Environment ; rdfs:label "User Acceptance" .
pr:Production a pr:Environment ; rdfs:label "Production" .
pr:SystemType a owl:Class ; rdfs:label "System Type" .
pr:SourceApplication a pr:SystemType ; rdfs:label "Source Application" .
pr:MasterDataSystem a pr:SystemType ; rdfs:label "Master Data System" .
pr:DataPlatform a pr:SystemType ; rdfs:label "Data Platform" .
pr:BITool a pr:SystemType ; rdfs:label "BI Tool" .
pr:ExternalProvider a pr:SystemType ; rdfs:label "External Provider" .
pr:belongsTo a owl:ObjectProperty , owl:FunctionalProperty ;
rdfs:label "belongs to" ;
rdfs:comment "Position in the categorization tree. One property for the whole tree: SubDomain belongs to DataDomain, BusinessObject belongs to SubDomain. Scope is enforced per class by SHACL rather than by two near-identical properties, and the same relation will serve if a domain family ever appears. Deliberately NOT transitive: entailment would produce two values and break the maxCount 1 shape. To walk the ancestry, use the property path belongsTo+ in the query." .
rdfs:comment "The single subject of this Business Object, and where its meaning comes from -- a Business Object carries no definition of its own. Exactly one. If the subject cannot be named, the object is not scoped, and that is the most useful thing the rule can tell you. Replaces the 3..10 minimum of BR-004, which was satisfied in v0.6 by attaching unrelated concepts." .
rdfs:comment "Carried three different meanings depending on the object: dependency (Sell Out Volume), subject (Retailer Stock), part-whole (Calendar). One word for three relations is what allowed the v0.6 padding. Split into aboutConcept and usesConcept." .
rdfs:comment "The elements whose combination makes a row unique. Grain belongs to a DATASET, not to a calculation rule: a Metric has no rows, so it cannot have a grain of its own -- its grain is derivable from the Data Objects it lands in. Stated at element level rather than object level because it is then CHECKABLE against the harvested PrimaryKey: a declared grain that does not match the real key is an automatic finding." .
rdfs:comment "BR-013. Links a mother Metric to the granular Data Elements that implement it in a given analysis context (period, promo status, scope, unit, currency)." .
rdfs:comment """The business notion a logical artefact is the data-side counterpart of. One relation at two granularities:
DataObject represents BusinessObject (exactly one -- the pivot, BR-006)
DataElement represents BusinessConcept (at most one)
Renamed from 'implements', which carried software-engineering baggage: a Data Object does not implement a Business Object the way a class implements an interface.
Range is deliberately left open and scoped by SHACL per class, because the two uses have different targets.
A Data Element uses this ONLY when it is dimensional. A measure element reaches meaning through Metric -> computedBy, which says more: it names WHICH metric the meaning travels through. Never both routes on one element.
Functional at DataObject level only -- not declared owl:FunctionalProperty here, since a single global cardinality would be wrong for one of the two uses.""" .
rdfs:comment "The scope of the product. Through these Data Objects and their represents, the Business Objects a product makes available are derivable -- which is why a product needs no direct link to a Business Object." .
rdfs:comment "The single Sub-Domain that runs this product. A Data Product spans several Business Objects and therefore cannot inherit accountability the way a Data Object does -- so it declares its own, and exactly one. It is a consumable: there must be no ambiguity about who runs it." .
pr:hasProductOwner a owl:ObjectProperty , owl:FunctionalProperty ;
rdfs:comment "Data Object to physical relation. Not functional: the same Data Object exists in DEV, UAT and PROD, and sometimes across several tables." .
rdfs:comment "Data Element to physical column, 1..n. Proposed by the reconciliation job on fullyQualifiedName and type, confirmed by a Data Steward. This single edge is what makes end-to-end impact analysis possible." .
rdfs:comment "Replaces the free-text hasSourceSystem. Domain deliberately omitted: applies to Data Elements, Physical Relations and BI Data Sources alike." .
pr:hasSystemType a owl:ObjectProperty , owl:FunctionalProperty ;
rdfs:comment "Domain widened from Table to PhysicalRelation so that views and external tables carry columns too. Inverse now declared - in v0.9 hasField and livesIn were inverses in fact but not in the model, so they were free to diverge." .
pr:livesIn a owl:ObjectProperty , owl:FunctionalProperty ;
rdfs:comment "Relation-level dependency, view to table. Transitive by nature; in practice compute the closure at query time in Snowflake rather than materialising it with a reasoner." .
pr:derivedFrom a owl:ObjectProperty , owl:TransitiveProperty ;
rdfs:comment """The harmonisation measure: how many distinct BI Fields realize one certified Metric, and do their expressions agree. Turns 'we harmonised the definitions' from a claim into a count over the real BI estate.
In principle this is derivable from the lineage chain Metric -> DataElement -> Field -> BIField, since lineage carries semantic inheritance. In practice that chain will have holes -- four hops, one of them PROPOSED_CONFIRMED, another harvested from an API that does not resolve custom SQL, extracts or cascaded calculated fields -- and the question it answers is too important to depend on them.
So: TRANSITIONAL CONTROL. Asserted directly, and that is all. No rule is written against the lineage chain: making the assertion conditional on intermediate mappings would create confusion and discourage people from filling it in.
Retirement criterion, to be measured rather than debated: when the lineage chain reproduces the asserted link for more than 95% of certified BI fields across three consecutive reconciliation cycles, the direct link is derivable and can go.""" .
rdfs:comment """The single Data Domain with authority to define the object's rule. Absent on Observed Objects: a Snowflake column is attributed through the Data Element mapped to it, never asserted directly.
Unlike the steward, this one is RE-DECLARABLE on a Data Element. It is inherited by default from the parent chain, but OW-002 attributes an element to the domain that defines its RULE, and a borrowed element -- Brand Code sitting in a Sell Out fact object -- has its rule elsewhere. A Data Element whose owningDomain differs from its parent's is a borrowed element: a signal to check against its represents, not an anomaly to fix.""" .
rdfs:comment """Declared on BusinessObject, and on DataProduct, and NOWHERE ELSE. Data Objects inherit through represents, Data Elements through hasElement. Declaring a steward at several levels would allow two answers to 'who watches this column'.
Says what the steward DOES, where the deprecated hasSteward only stated a membership.
DataProduct is the one exception to inheritance: it packages Data Objects belonging to several Business Objects, so it cannot inherit a single steward and declares its own.""" .
rdfs:comment """The meaning of a business notion. Belongs to the BusinessConcept.
MUST NOT be carried by a BusinessObject: an object gets its meaning through aboutConcept. Two definitions for one notion are two definitions free to diverge. Enforced by SHACL rather than by rdfs:domain, because Data Elements legitimately carry one too and a declared domain would make them entail BusinessConcept -- which the disjointness axioms would then reject.
MIGRATION: text currently on a Business Object moves to the Concept named by its aboutConcept.""" .
pr:hasFormula a owl:DatatypeProperty ; rdfs:label "formula" ; rdfs:range xsd:string .
pr:hasUnit a owl:DatatypeProperty ; rdfs:label "unit" ; rdfs:range xsd:string ;
rdfs:comment "From the Units LoV. Note the LoV currently mixes physical units, currencies (ISO 4217) and value types (Index, Rate, Count) - three different concepts that should eventually be split." .
rdfs:comment "Free-text grain label on a Metric, e.g. 'SKU x Customer x Day'. Kept a second, unverifiable copy of something now stated structurally on the Data Object. Grain is a property of a dataset, not of a calculation rule." .
rdfs:comment "Recorded verbatim, never altered (NR-009). Must NOT be carried by a Metric - that is a layer leak; under BR-013 the physical name belongs on the Data Element." .
pr:fullyQualifiedName a owl:DatatypeProperty , owl:FunctionalProperty ;
rdfs:comment "DATABASE.SCHEMA.RELATION[.COLUMN]. The actual join key against INFORMATION_SCHEMA: a bare physical name is ambiguous as soon as the same column name exists in two tables." .
pr:sourceIdentifier a owl:DatatypeProperty , owl:FunctionalProperty ;
rdfs:comment "Native immutable id in the source system (Snowflake object id, Tableau LUID, Looker id). Makes reconciliation idempotent and survives renames, which names do not." .
rdfs:comment "Lets the model say 'documented but unused for eight months'. A rationalisation argument that costs nothing and is denominated in warehouse spend." .
