Skip to content

State that one IRI denotes one record and references cross record types - #11

Merged
ANierbeck merged 1 commit into
mainfrom
one-iri-one-record
Oct 25, 2026
Merged

ANierbeck merged 1 commit into
mainfrom
one-iri-one-record

Conversation

@ANierbeck

Copy link
Copy Markdown
Contributor

Title: State that one IRI denotes one record and references cross record types

Summary

Follows the dev@ thread "Resolving references on read, and what one IRI can stand for". Spec text only; the schemas are unchanged.

  • New section "One IRI, one record": an IRI denotes exactly one record, of one type, for the whole life of the record. The id names the record, not the model or dataset it describes.
  • References (custodyChain[].agent, trainingData[].dataset) are by IRI alone and resolve across record types. A Registry reports the referenced record's current state when the referencing record is read: one hop, status only, nothing stored in either record.
  • A custodyChain agent may be the id of any Sourcelume record, including a TrainingProvenanceRecord (a model that rewrote the data is a custodian). Before, the text said "another ProvenanceRecord".
  • CHANGELOG entry.

Compatibility

Data that validated before still validates: an agent is an IRI either way. Registries that resolve custody agents must now look in both stores (sourcelume-registry#25).

Testing

pytest tests (25 passed), tools/validate.py examples/ passes.

Apache-ai: Yes
Generated-by: pi (claude-sonnet-5-5)
Reviewed-by: anierbeck

Settled on dev@ ("Resolving references on read, and what one IRI can
stand for"): an IRI denotes exactly one record, of one type, for its
whole life. The new section "One IRI, one record" says so, says the id
names the record and not the model or dataset it describes, and
states that references resolve across record types, with the
referenced record's current state reported when the referencing record
is read (one hop, status only, nothing stored).

A custodyChain agent may now be the id of any Sourcelume record,
including a TrainingProvenanceRecord. The schemas are unchanged: an
agent is an IRI either way, and data that validated still does.

Apache-ai: Yes
Generated-by: pi (claude-sonnet-5-5)
Reviewed-by: anierbeck
@ANierbeck
ANierbeck merged commit 69492ce into main Oct 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant