A Governed Data Record is one record of your data, validated against a published Semantic Data Charter model and permanently bound to it: its meaning, its constraints, its provenance and its governance. The model can never change after it is published and can never go missing, so what the record means holds wherever the record goes.
Because every record is bound to a model that cannot drift, two things become possible that depend on it: a deterministic decision about what may be done with the record, and a settlement anyone can verify.
What makes a record governed
Bound
The record is permanently bound to one published model: its labels, definitions, constraints and vocabulary bindings, all in one self-contained, computable schema. A receiver resolves what the data means and what it is permitted to be from that model, not from a profile document or a terminology server consulted at run time.
Refused unless valid
A Governed Data Record is refused unless it validates against the published model it names. A recoverable gap is kept and tagged with an ISO 21090 exceptional value, so the record stays valid and the gap is recorded rather than hidden.
Fixed once made
Who made it, under what workflow state, with what attestation: when the model defines governance, the record must hold that governance content, and it is fixed once the record is made. A published model never changes, so a record made years ago still means what it meant.
Open, and yours
The canonical form is XML validated with W3C XSD 1.1. JSON and RDF are projections of the
same record. There is no private format: the records live in your store, on your
infrastructure, and the open-source sdcvalidator
checks them anywhere.
If you think in tables
The difference is what is bound to it. A row means what the application that reads it decides it means, and loses that when it leaves the table. A Governed Data Record is the row with its meaning, its constraints, its provenance and its governance bound to it, kept together wherever it goes. Tables and graphs are still there: they are projections of the records.
Governed
Governance validation is the per-decision check, at the point of action, that a record
and the operation requested on it conform to the constraints and access policies that
govern it. sdcgovernance reads the governance
defined in the record's model (workflow, attestation, party and role, provenance) and
returns a decision in OASIS XACML terms: PERMIT, DENY or INDETERMINATE.
It works because the governance is bound to the record, not kept in a policy engine beside it. The record carries its classification; the engine renders the decision. The same inputs always produce the same decision, and every decision produces a SHA-256 hash-chained receipt in W3C PROV.
In practice
Settled
When a Governed Data Record moves between two parties, one call to the Verifiable
Settlement Layer validates it against its published model, evaluates the governance
decision with sdcgovernance, and binds both
parties and the release condition into a signed Settlement Receipt.
Anyone verifies that Receipt offline, against published keys, with the open-source
sdcreceipt tool. A counterparty can check your
work without trusting you, or us, and the Receipt holds hashes, identifiers and
signatures, never your data.
Why it needs a governed record
A Receipt is only as good as what it was checked against. Because the record is bound to a published model that never changes, any party can fetch the exact schema the Receipt was checked against, re-run the validation and the governance decision, and reproduce the hash. Data whose description sits beside it cannot be settled this way: the description can change, or be gone, after the fact.
Governed Data Records start with a published model. Build one in SDCStudio from the published component libraries, then govern and settle the records made against it.