gnomonlearn
Docs/RFC-0020 RDF relationship proposal

RFC-0020 RDF relationship proposal

Versioned draft snapshot

RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.

Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.

This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.

Status: proposed. Owners: specification, subscription API, and RDF consumers. The source-bound review of all 103 RFC-0020 projection nodes found five relationship mismatches. This proposal changes no authored RFC, projection source, or generated Turtle. Nothing is deployed, so it needs no live-object migration; the source contract and local consumers still need to agree before normative publication.

Candidate mapping

Keep all five claim or domain subject IRIs and all claim section links stable.

NodeCurrent relationshipCandidate relationshipSource reason
claim/RFC-0020/sec-3/eventid-is-event-log-canonical-ididentified-by → domain/phase/runtimesourced-from → new domain/type/EventLogEventIdRFC-0020 §3.2 says the identifier comes from the RFC-0010 event log. A runtime phase is not an identifier.
claim/RFC-0020/sec-8/reuses-readscope-from-rfc-0008domain/type/ReadScopeDescriptor derived-from itselfdomain/field/SubscriptionOptions/readScope derived-from rfc/RFC-0008#sec-8RFC-0008 §8 contains the readScope grammar, while RFC-0020 §8 reuses that mechanism at open and delivery.
claim/RFC-0020/sec-10/read-scope-immutabilityfixed-at → subscription open timebounded-by-opened-scope → opened scope intersected with current grantsRFC-0020 §10 fixes the opened envelope, while revocation can narrow effective scope.
domain/type/GnomonQuerydefinedIn RFC-0007definedIn RFC-0020RFC-0020 §3.1 names this runtime API type; RFC-0007 defines the query mechanism but does not define a type named GnomonQuery.
domain/type/ReadScopeDescriptordefinedIn RFC-0008definedIn RFC-0020RFC-0020 §3.3 names this option type; RFC-0008 defines readScope grammar but not a type named ReadScopeDescriptor.

The proposed EventLogEventId node would be a domain#DataType defined in RFC-0020, with a source-backed summary that it is the identifier carried from the RFC-0010 event log by SubscriptionEvent.eventId. RFC-0020 must define its value shape and stability before the new node is published. Similarly, RFC-0020 must define the shape of GnomonQuery and ReadScopeDescriptor as runtime binding types, explicitly mapping them to RFC-0007 queries and RFC-0008 readScope rules. This keeps the two earlier RFCs as the owners of their mechanisms without assigning them types they do not name.

Measured local query impact

An in-memory counterfactual loaded the current ontology, regenerated formal catalogs, and all claim and domain Turtle. It made the eight triple replacements above and added four minimal triples (rdf:type, fqn, summary, definedIn) for EventLogEventId. The resulting graph had 89,120 triples. All 16 checked-in claim queries executed. Fifteen distinct result sets were unchanged; predicate-vocabulary.rq changed the identified-by count from 16 to 15 because the event ID relationship becomes sourced-from. This does not test external RDF queries, persisted results, code that reads these relationships directly, or whether the proposed type contracts are complete.

Acceptance before normative publication

  1. Approve the three relationship replacements and the two type ownership corrections. Define the three runtime type shapes in authored RFC-0020 and its Lean catalog, including event ID value and stability rules.
  2. Update the protobuf projection nodes, add the new domain node, regenerate Turtle, and re-review the five source-bound verdicts. Retain all claim IRIs and emitted section links.
  3. Run the projection, section-link, semantic, and 16-query gates. Compare exact query row sets with the counterfactual and check the site pin and framework duplicate consumers before publishing a versioned spec artifact.