Point
Content, References, and Resources have distinct roles
Stable Resource identity, primary Content, and typed References preserve why material is included without claiming ownership or authority.
- Posture
- asserted
- Lifecycle
- active
A Resource gives addressable material a stable Atlas-wide identifier. A Content edge says that the target is primary material for the Atlas, Map, Area, or Point record. A Reference edge says that the target is evidence, support, implementation, history, or an example.
These roles preserve the reason for inclusion without copying the target’s meaning into the source record. A document can participate through several visible context edges and does not inherit one Point’s Map, posture, lifecycle, or authority. Registration and citation also do not grant permission to retrieve, modify, redistribute, or publish the material.
Material and overlapThe three material roles determine whether a source is registered, primary to a container, or merely relevant evidence.
Selection and reader labels must preserve primary, evidence, supporting, implementation, historical, and example roles for each material edge.
A compiler cannot flatten every cited target into one undifferentiated document set. It must preserve why each source record included the target, apply explicit closure rules, and let the reader inspect multiple reasons without duplicating the underlying Resource.
Selection and closureClosure rules need material roles to decide which Resources are primary, supporting, evidentiary, or omittable.
Reader experienceRole labels tell readers why each linked source appears without collapsing every link into undifferentiated content.