gnomonlearn
Docs/RFC-0026 RDF relationship proposal

RFC-0026 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, gRPC binding, and RDF consumer maintainers. No projection source or generated Turtle is changed by this proposal. The source-bound review in PROJECTION_GAPS.md identified thirteen RFC-0026 claim relationships whose structured subjects omit an operation mode, operation owner, or auth/TLS condition stated in the authored draft.

Candidate mapping

Keep all thirteen claim IRIs, text, kinds, predicates, values, confidence, and section links. Replace only the structured subject or object shown:

Claim slugsCurrent subjectCandidate subjectSource condition
sec-2/rpc-required, sec-2/service-requiredfield/operation/{rpc,service} with is-required-on object module/gnomon.io.grpcKeep the field subject; replace claimObject with operation/grpc.operationRequired on each gRPC operation, not on the registering module.
sec-3/bidi-streaming-input-stream, sec-3/bidi-streaming-returns-streamfield/operation/modeoperation/grpc.bidi-streamingSelected mode is bidi-streaming.
sec-3/client-streaming-input-stream, sec-3/client-streaming-returns-non-streamingfield/operation/modeoperation/grpc.client-streamingSelected mode is client-streaming.
sec-3/server-streaming-returns-streamfield/operation/modeoperation/grpc.server-streamingSelected mode is server-streaming.
sec-3/unary-call-site-execute, sec-3/unary-input-any, sec-3/unary-returns-non-streamingfield/operation/modeoperation/grpc.unarySelected mode is unary.
sec-5/custom-interceptor-fallbackmodule/gnomon.io.grpcinvariant/grpc-nonnative-auth-fallbackAuthor needs api-key or basic auth.
sec-6/tls-none-dev-only, sec-6/tls-none-warningfield/client/tlsconfiguration/grpc.tls.noneConfigured value is tls: none.

The seven candidate domain identities are grpc.operation, four mode-specific operation kinds, grpc.nonnative-auth-fallback, and grpc.tls.none. The five operation identities would use the existing domain#Operation class; the auth fallback would use domain#Invariant; grpc.tls.none needs an agreed configuration class or a generic domain#DomainEntity until such a class is defined. Each identity needs a source-backed FQN, summary, and definedIn link before publication. The module remains the registrar of the slots, and field/operation/mode remains the typed selector field; those current nodes are not deleted.

The first row changes two claimObject triples, not subjects. The remaining eleven rows change claimSubject. A machine patch must follow those columns exactly. This proposal does not change RFC-0026 syntax, diagnostic codes, runtime behavior, or published proto packages.

Measured local query impact

An in-memory counterfactual loaded the current ontology, generated formal catalogs, and all claim/domain Turtle. It replaced the two slot-requirement objects and eleven conditional subjects, then added four minimal triples (rdf:type, fqn, summary, definedIn) for each of seven candidate domain nodes. The resulting graph had 89,117 triples. All sixteen checked-in claim queries executed, and their distinct result sets were unchanged. This result is limited to those local queries; it does not test external queries, cached results, RDF clients that inspect claimSubject or claimObject directly, or the suitability of the proposed domain identities.

Acceptance and migration

  1. Approve the seven domain identities and the class for the TLS configuration value. Check for existing published identities with the same meanings.
  2. Update the thirteen protobuf claim nodes and seven domain nodes, regenerate Turtle, and refresh source-bound review verdicts. Keep all claim IRIs and section links stable.
  3. Run projection drift, section-link, SHACL, semantic-consistency, and all sixteen claim-query gates. Compare exact row sets against the counterfactual and inspect any changed limited query pages.
  4. Inventory external RDF and cached consumers, then publish the corrected graph as a versioned artifact with a rollback path. Repoint the framework duplicate and site only after the released artifact passes their consumer checks.