PR Data Meta Model - SHACL Shapes
modified: 2026-07-30
comment: Executable form of the rulebook. Validated by scripts/run_shacl_validation.py.

DefinedObjectShape
type: NodeShape
target class: DefinedObject
comment: Applies to everything governance writes. Captured objects are deliberately exempt: see CapturedObjectShape.
property:
  path: hasIdentifier
  datatype: string
  min count: 1
  max count: 1
  severity: Violation
  message: DQ-001 -- every defined object carries exactly one identifier. NOTE: uniqueness across the graph is NOT tested here; SHACL checks cardinality only. The reconciliation job tests uniqueness.
property:
  path: hasName
  datatype: string
  min count: 1
  max count: 1
  min length: 3
  severity: Violation
  message: Every defined object carries exactly one canonical name.
property:
  path: hasStatus
  min count: 1
  in: DRAFT
  in: UNDER_REVIEW
  in: PUBLISHED
  in: DEPRECATED
  in: RETIRED
  severity: Violation
  message: LC-001 -- status must be one of DRAFT, UNDER_REVIEW, PUBLISHED, DEPRECATED, RETIRED.
property:
  path: owningDomain
  max count: 1
  severity: Violation
  message: OW-001 -- at most one owning Data Domain. On a Data Element this may be re-declared to differ from the parent chain: that marks a borrowed element.
property:
  path: hasVersion
  max count: 1
  severity: Warning
  message: A published object should carry a version.

PublishedShape
type: NodeShape
target class: DefinedObject
comment: Extra demands that only bite once an object claims to be PUBLISHED. Keeping these off the base shape is what lets a domain be documented progressively.
sparql:
  severity: Violation
  message: OW-007 -- an object flagged TO_ARBITRATE cannot be PUBLISHED. Resolve at the Cross-Domain Council first.
  select: PREFIX pr: <https://ontology.pernod-ricard.com/metamodel/> SELECT $this WHERE { $this pr:hasStatus "PUBLISHED" ; pr:arbitrationStatus "TO_ARBITRATE" . }
sparql:
  severity: Violation
  message: OW-003 -- a PUBLISHED object must have an owning Data Domain.
  select: PREFIX pr: <https://ontology.pernod-ricard.com/metamodel/> SELECT $this WHERE { $this pr:hasStatus "PUBLISHED" . FILTER NOT EXISTS { $this pr:owningDomain ?d } }

CapturedObjectShape
type: NodeShape
target class: CapturedObject
comment: No identifier, no name, no owner, no status, no version. A harvested column is attributed through the Data Element mapped to it, never asserted directly. What it must carry is enough to be re-found on the next run.
property:
  path: sourceIdentifier
  datatype: string
  max count: 1
  severity: Warning
  message: A native immutable source id makes reconciliation idempotent and survives renames, which names do not.
property:
  path: harvestedOn
  datatype: dateTime
  min count: 1
  max count: 1
  severity: Violation
  message: Every captured object records when it was harvested. Without it there is no way to tell a current fact from a stale one.
property:
  path: owningDomain
  max count: 0
  severity: Warning
  message: Captured objects are not attributed directly -- ownership flows from the Data Element mapped to them.

DataStructureShape
type: NodeShape
target class: DataStructure
property:
  path: inSchema
  max count: 1
  severity: Info
  message: Optional on purpose: not every engine has a schema level.
property:
  path: sourcedFrom
  max count: 1
  severity: Info

FieldShape
type: NodeShape
target class: Field
property:
  path: fullyQualifiedName
  datatype: string
  min count: 1
  max count: 1
  pattern: ^[A-Za-z0-9_$]+\\.[A-Za-z0-9_$]+\\.[A-Za-z0-9_$]+\\.[A-Za-z0-9_$]+$
  severity: Violation
  message: A Field carries DATABASE.SCHEMA.RELATION.COLUMN. A bare column name is ambiguous as soon as it exists in two tables, so the FQN is the real join key against INFORMATION_SCHEMA.
property:
  path: livesIn
  min count: 1
  max count: 1
  severity: Violation
  message: Every Field lives in exactly one Physical Relation.

SubDomainShape
type: NodeShape
target class: SubDomain
property:
  path: belongsTo
  class: DataDomain
  min count: 1
  max count: 1
  severity: Violation
  message: A Sub-Domain belongs to exactly one Data Domain.
property:
  path: hasSubDomainOwner
  max count: 1
  severity: Warning
  message: A Sub-Domain should name its owner.

DataDomainShape
type: NodeShape
target class: DataDomain
property:
  path: hasDomainOwner
  max count: 1
  severity: Warning
  message: A Data Domain should name its owner.
property:
  path: hasDGL
  max count: 1
  severity: Warning
  message: A Data Domain should name its Data Governance Lead.
property:
  path: hasActivationStatus
  max count: 1
  severity: Info

BusinessObjectShape
type: NodeShape
target class: BusinessObject
property:
  path: belongsTo
  class: SubDomain
  min count: 1
  max count: 1
  severity: Violation
  message: A Business Object belongs to exactly one Sub-Domain.
property:
  path: aboutConcept
  class: BusinessConcept
  min count: 1
  max count: 1
  severity: Violation
  message: BR-004 -- a Business Object is about exactly one Business Concept. Replaces the old 3..10 minimum, which was satisfied in v0.6 by attaching unrelated concepts. If the subject cannot be named, the object is not scoped.
property:
  path: usesConcept
  class: BusinessConcept
  severity: Info
  message: Other notions needed to read this object. Zero is a legitimate answer.
property:
  path: monitoredBy
  class: DataSteward
  min count: 1
  severity: Warning
  message: The Business Object is where a steward is declared -- Data Objects and Data Elements inherit from here.
property:
  path: hasBusinessDefinition
  max count: 0
  severity: Violation
  message: A Business Object carries no definition of its own: meaning belongs to the Business Concept named by aboutConcept. Two definitions for one notion are two definitions free to diverge. MIGRATION: move the text to that Concept.
property:
  path: sourcedFrom
  max count: 0
  severity: Violation
  message: A Business Object has no system of truth. It is a governance grouping, not data: its data lives in the Data Objects that represent it, and those name the system. In v0.6 this property held a grab-bag on the 15 objects -- physical locations, migration notes, arbitration remarks -- all under one name.

BusinessConceptShape
type: NodeShape
target class: BusinessConcept
comment: Note what is NOT here: no requirement that a Concept be realized by any Data Element or measured by any Metric. The business layer is allowed to run ahead of the data. Coverage is a dashboard metric, not a rule.
property:
  path: hasBusinessDefinition
  datatype: string
  min count: 1
  max count: 1
  min length: 20
  severity: Violation
  message: A Business Concept exists to carry meaning: it must hold exactly one business definition of at least 20 characters.
property:
  path: hasFormula
  max count: 0
  severity: Violation
  message: BR-003 -- the presence of a formula is what makes something a Metric. A Concept with a formula is a misclassified Metric.
property:
  path: sourcedFrom
  max count: 0
  severity: Violation
  message: A Business Concept has no system of truth. Its authority is its owning domain and its definition belongs in the glossary. Naming a system here would ask which of the systems that USE the concept defines it -- a question with no answer.

MetricShape
type: NodeShape
target class: Metric
property:
  path: hasFormula
  datatype: string
  min count: 1
  max count: 1
  severity: Violation
  message: BR-003 -- a Metric is a measurement with a calculation rule. No formula, no Metric.
property:
  path: hasUnit
  min count: 1
  severity: Violation
  message: A Metric states every unit its variants are expressed in. NOT capped at one: Sell Out Volume is computed in 9L and in L, Sell Out Value in EUR, USD and local currency. The single-unit rule belongs on the Data Element, where it holds -- see DataElementShape.
property:
  path: measures
  class: BusinessConcept
  min count: 1
  severity: Violation
  message: A Metric measures at least one Business Concept -- this is how a measure element reaches business meaning.
property:
  path: hasGranularity
  max count: 0
  severity: Warning
  message: Grain moved off the Metric in v1.1. A Metric is a calculation rule and has no rows; grain belongs to the Data Object, stated with hasGrainElement and checkable against the real primary key.
property:
  path: physicalName
  max count: 0
  severity: Violation
  message: A Metric must not carry a physical name -- that is a layer leak. Under BR-013 the physical name belongs on the Data Element.

MetricSourceShape
type: NodeShape
target class: Metric
comment: Rewritten in v1.4 to compare System references rather than strings. A string comparison would have called 'SODH Gold' and 'Snowflake (SODH Gold)' two different systems.
sparql:
  severity: Violation
  message: A Metric's system of truth must match that of at least one element computing it. If they disagree, either the metric points at the wrong system or an element has moved.
  select: PREFIX pr: <https://ontology.pernod-ricard.com/metamodel/> SELECT $this WHERE { $this pr:sourcedFrom ?sys ; pr:computedBy ?de . FILTER NOT EXISTS { $this pr:computedBy ?any . ?any pr:sourcedFrom ?sys . } }
sparql:
  severity: Warning
  message: Elements computing one Metric come from several systems. Legitimate for a metric blending sources, worth a look otherwise.
  select: PREFIX pr: <https://ontology.pernod-ricard.com/metamodel/> SELECT $this WHERE { $this pr:computedBy ?a , ?b . ?a pr:sourcedFrom ?sa . ?b pr:sourcedFrom ?sb . FILTER(?sa != ?sb) }

MotherMetricShape
type: NodeShape
target class: Metric
sparql:
  severity: Warning
  message: BR-013 -- a PUBLISHED Metric should be implemented by at least one Data Element through computedBy. A metric no element computes is a definition with nothing behind it.
  select: PREFIX pr: <https://ontology.pernod-ricard.com/metamodel/> SELECT $this WHERE { $this pr:hasStatus "PUBLISHED" . FILTER NOT EXISTS { $this pr:computedBy ?de } }

DataObjectShape
type: NodeShape
target class: DataObject
property:
  path: represents
  class: BusinessObject
  min count: 1
  max count: 1
  severity: Violation
  message: BR-006 -- a Data Object represents exactly one Business Object. This is the pivot: the single junction between governance and technology.
property:
  path: hasElement
  class: DataElement
  min count: 1
  severity: Violation
  message: A Data Object holds at least one Data Element.
property:
  path: hasGrainElement
  class: DataElement
  severity: Warning
  message: State the grain: the elements whose combination makes a row unique. Checkable against the harvested primary key.
property:
  path: monitoredBy
  max count: 0
  severity: Warning
  message: Stewardship is declared on the Business Object and inherited through represents. Declaring it here allows two answers to the same question.
property:
  path: sourcedFrom
  class: System
  max count: 1
  severity: Warning
  message: Name the System holding the authoritative data, as a reference rather than a string. A string could not answer 'what depends on MDM Product'.
property:
  path: storedIn
  class: DataStructure
  severity: Warning
  message: Where the object actually sits: a table, a view, later a node label. The seam between what governance defines and what a harvester captures -- proposed by the reconciliation job, confirmed by a steward.
property:
  path: materializedAs
  max count: 0
  severity: Warning
  message: Deprecated in v1.4: storedIn now serves both granularities.

GrainConsistencyShape
type: NodeShape
target class: DataObject
sparql:
  severity: Violation
  message: A grain element must be one of the object's own Data Elements.
  select: PREFIX pr: <https://ontology.pernod-ricard.com/metamodel/> SELECT $this ?grain WHERE { $this pr:hasGrainElement ?grain . FILTER NOT EXISTS { $this pr:hasElement ?grain } }

DataElementShape
type: NodeShape
target class: DataElement
property:
  path: physicalName
  datatype: string
  max count: 1
  severity: Warning
  message: NR-009 -- the physical name is recorded verbatim and never altered.
property:
  path: fullyQualifiedName
  max count: 1
  severity: Info
property:
  path: hasUnit
  max count: 1
  severity: Violation
  message: A Data Element carries exactly one unit. This is the counterpart of the Metric rule: the mother metric lists the units its variants use, each variant states the single unit it is actually expressed in. An element with two units is two elements.
property:
  path: represents
  class: BusinessConcept
  max count: 1
  severity: Violation
  message: A Data Element represents at most one Business Concept. If a column carries two business notions, it should almost certainly be split -- so the case where a steward cannot choose is exactly the one worth looking at.
property:
  path: monitoredBy
  max count: 0
  severity: Warning
  message: Stewardship is inherited from the Business Object, not declared here.

DataElementMeaningShape
type: NodeShape
target class: DataElement
comment: A Data Element reaches business meaning by exactly one of two routes: it represents a Business Concept (dimensional), or a Metric is computedBy it (measure). sh:xone rejects zero routes and two alike. A measure element must NOT also represent a Concept: the chain Metric -> measures -> Concept already carries the meaning, and carries more, since it names which metric it travels through.
xone:
  property:
    path: represents
    min count: 1
    max count: 1
xone:
  property:
    path:
      inverse path: computedBy
    min count: 1
severity: Violation
message: A Data Element must reach business meaning by exactly one route: represents a Business Concept (dimensional), or be computedBy a Metric (measure). Never both, never neither. A defined column with no business meaning is debt, not an acceptable state.

DataProductShape
type: NodeShape
target class: DataProduct
property:
  path: operatedBy
  class: SubDomain
  min count: 1
  max count: 1
  severity: Violation
  message: A Data Product is operated by exactly one Sub-Domain. It spans several Business Objects and cannot inherit accountability, so it declares its own -- it is a consumable, and there must be no ambiguity about who runs it.
property:
  path: hasProductOwner
  class: DataProductOwner
  max count: 1
  severity: Warning
  message: A Data Product should name exactly one Product Owner. A warning rather than a block: the SODH owner is genuinely not appointed, and a blocking rule that cannot be satisfied truthfully is how BR-004 produced padding.
property:
  path: packages
  class: DataObject
  min count: 1
  severity: Violation
  message: A Data Product packages at least one Data Object. The Business Objects it makes available are derived from these, which is why no direct link to a Business Object is needed.
property:
  path: governedBy
  max count: 1
  severity: Warning
  message: A Data Product should be governed by a Data Contract.
property:
  path: exposes
  class: DataInterface
  severity: Info
  message: The channels through which consumers actually get the data.

DataInterfaceShape
type: NodeShape
target class: DataInterface
property:
  path: servedBy
  min count: 1
  severity: Warning
  message: An interface should name what physically backs it. Unlike the old Data Asset test, this is verifiable: a grant, a share or an endpoint either exists or it does not.

BIFieldShape
type: NodeShape
target class: BIField
comment: realizesMetric is a transitional control: asserted directly, with no rule written against the lineage chain. Making the assertion conditional on intermediate mappings existing would create confusion and discourage people from filling it in at all.
property:
  path: exposesMetric
  class: Metric
  max count: 1
  severity: Info
  message: Which certified Metric this BI field implements. Comparing expressions across fields realizing one Metric is the harmonisation measure.

NamingShape
type: NodeShape
target class: DefinedObject
property:
  path: hasName
  not:
    pattern: _NM$
  severity: Warning
  message: NR-001 -- a canonical name must not end in a physical suffix. Written as sh:not[sh:pattern] rather than a lookbehind: sh:pattern is normatively XPath 2.0 regex, which has no lookbehind, so the v0.1.1 form only worked under pySHACL.
property:
  path: hasName
  not:
    pattern: ^[a-z_]+$
  severity: Warning
  message: NR-002 -- a canonical name is written for humans, not as a snake_case identifier.