A person-level record has a declared shape

Answers Mereology

The joins a person-level record must be able to make are declared as record shapes: a position, an exposure, an attributed conversion, a reading and a consent receipt, each a shape over the kinds and the roads, walking at least one record road. The registry instantiates none of them; the standards export writes each as a SHACL node shape without a target, for a record system to apply. A campaign roll-up, the one record join not made at the person level, is declared the same way.

What goes wrong without it

The vocabulary says what a metric is; only a record says what it read, over which window, in which market, for which segment. The vocabulary says which state a position realises; only a record says who held it and how well they were known. A model that stops at the vocabulary leaves every one of those joins to be invented again by each system that holds the records, and invented differently. Declaring the join as a shape, in the same grammar the questions are declared in, and exporting it in the constraint language a validator already reads, is what lets two record systems agree without either owning the other.

What proves it — 2

Each is a gate the build runs: a check inside a ring, a whole ring, or an eval beside them. A build stops at the first that refuses.

• registry integrityrecord shapes hold
  Every pattern declares its grain. A record shape is a shape, walks at least one record road, and is the registry's declaration of a join a record must make, a person-level record in every case but the campaign roll-up, so the registry instantiates it by nothing and the standards export writes it as a shape without a target. A vocabulary pattern walks no record road, because a record road holds no rows to answer from.
• ring:8the standards ring
  A SHACL validator and a SPARQL engine that are not this build agree with it.

Derived from — 3

• W3CShapes Constraint Language (SHACL)
• Kantara InitiativeConsent Receipt Specification 1.1
• Adobe Experience PlatformXDM Individual Profile Class

Relationships it licenses

read over · read in · read for · held at · occurs within

Where this model stands

Seven record roads are record grain, asserted by nothing here: they join a reading to its window, geography and segment, a position to the level it is held at, an event to the window it occurs within and to the tactic credited with it, and a campaign to its parent.

Six record shapes stand under Shapes, each unrooted and walking at least one record road; FND-036 holds every pattern to declaring its grain, a record shape to being a shape that walks a record road, and a vocabulary pattern to walking none.

The standards export writes each record shape as a SHACL node shape with a property per road it walks and no target, so the shapes graph still conforms and a record system can attach its own targets.

What it does not claim

A record shape says which join a record makes and nothing about the values it carries; a reading’s value, its time and its provenance are the record system’s to hold, and this model neither stores nor validates them.

RUL-052