Semantic Structure Mapping Profile — Rights of Robots
Purpose
The Semantic Structure Mapping Profile defines a minimal set of link relation types for referentially identifying existing web resources that carry persistent entity identity, canonical relational structure, or contextual composition within an integrated semantic system.
The profile does not define, reproduce, or replace the semantic content of referenced resources.
Profile
Version: 0.1
Canonical profile URI:
https://www.rightsofrobots.com/semantic-structure-mapping/
The profile is intended for use with RFC 9264 Link Sets using the application/linkset+json media type.
Link Context
The link context identifies the integrated semantic system to which the resource-role assignments apply.
A conforming mapping must provide an explicit absolute anchor URI for every mapped link context.
The anchor identifies the system within which the relations are interpreted. It does not assert that the anchored web resource is ontologically identical to the persistent semantic entity represented within that system.
Relation Types
persistent-entity-resource
Relation URI:
https://www.rightsofrobots.com/semantic-structure-mapping/#persistent-entity-resource
Identifies an existing web resource that carries the persistent semantic identity of the primary subject within the anchored system.
The relation does not assert ontological identity between the referenced web resource and the semantic entity.
canonical-relation-resource
Relation URI:
https://www.rightsofrobots.com/semantic-structure-mapping/#canonical-relation-resource
Identifies an existing web resource that carries one or more stable relations constitutive of the persistent subject within the anchored system.
The mapping does not enumerate, redefine, or reproduce those canonical relations.
contextual-resource
Relation URI:
https://www.rightsofrobots.com/semantic-structure-mapping/#contextual-resource
Identifies an existing web resource that contextualizes the persistent subject or its canonical relations within the anchored system.
The profile does not prescribe context categories. The semantic nature of the context remains defined by the referenced resource.
Multiple Relations
A target resource may be referenced through more than one relation type.
Multiple relations indicate that an existing resource performs more than one structural function within the anchored system. The profile does not define primary or secondary roles.
Minimal Conformance
A conforming mapping must contain at least one persistent-entity-resource relation.
persistent-entity-resource: one or more targetscanonical-relation-resource: zero or more targetscontextual-resource: zero or more targets
All target href values must use absolute URIs.
Referentiality
A conforming mapping must not reproduce definitions, summaries, keywords, evidence statements, research findings, source descriptions, or other substantive semantic content from referenced resources.
The mapping identifies structural relationships between the anchored system and existing web resources. Semantic authority remains with the referenced resources themselves.
Partiality
A mapping is a partial structural projection. It must not be interpreted as a complete inventory, ontology, sitemap, navigation model, or complete representation of the anchored system.
Absence from a mapping does not imply absence, irrelevance, or exclusion from the underlying website or semantic system.
Mapped relations must not be inferred solely from URL paths, directory names, navigation positions, subdomains, or hosting boundaries.
Scope Boundary
The profile is limited to persistent semantic identity, canonical relational structure, and contextual composition.
Evidence resources, source structures, research publications, legal resources, navigation structures, and other supporting resources are outside the minimal mapping scope defined by version 0.1.
Terms such as “resource” or “role” used within referenced websites for editorial, evidential, navigational, source, document, contributor, or interface purposes are independent of the relation types defined by this profile.
Versioning
The profile URI and relation URIs are stable and do not contain a profile version number.
Adding or removing target resources within a mapping instance does not change the profile version.
Editorial clarification may occur without changing relation identity. An incompatible change to the semantics of a relation must not silently redefine an existing relation URI.
Technical Basis
The representation model follows RFC 9264, Linkset: Media Types and a Link Relation Type for Link Sets, and the Web Linking model defined by RFC 8288.