RELATION MAP ยท SNAPSHOT V1
Data Relations
Relations connect isolated records into reusable knowledge.
CURRENT V1 SEMANTICS
One generic relation, not a finished ontology
The published snapshot contains 114 directed relation entries across 43 records. Every entry is related_to: a navigational association only. It does not assert causality, containment, equivalence or guaranteed symmetry.
Of those directed entries, 84 have a reverse counterpart and 30 are one-way. That asymmetry is preserved as published; consumers must not infer meaning from direction in v1.
Record
related_to
Known target ID
Catalog navigation
No extra inference
Proposed typed vocabulary
The terms below are retained as a roadmap. None is encoded as a relation type in dataset v1.0.0, and records must be reviewed before any migration from related_to.
| Proposed relation | Intended meaning | Illustrative example | v1 status |
|---|---|---|---|
| contains | One data object contains another. | Document contains tokens. | Not encoded |
| derived_from | A record is calculated or extracted from another. | Spectrum is derived from waveform. | Not encoded |
| measures | A value observes a property of an entity. | Temperature measures thermal state. | Not encoded |
| located_at | Data is associated with a spatial position. | Sensor reading located at coordinate. | Not encoded |
| occurs_at | An event is associated with time. | Transaction occurs at timestamp. | Not encoded |
| represents | One form encodes another concept or entity. | Vector represents semantic meaning. | Not encoded |
| processed_by | Data can be consumed by a tool or operation. | IP address processed by subnet calculator. | Not encoded |