RFC-0025 HTTP domain identity 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.
Evidence
RFC-0025 §3 defines bearer-token, api-key, basic, and none as values of the client’s auth: slot. The domain projection types them NamedDeclaration under declaration/auth-scheme/*, with FQNs auth.*. RFC-0033 uses the same IRIs for inbound API authentication schemes with different FQNs and behavior. These are different protocol directions: outbound credential injection versus inbound credential acceptance.
RFC-0025 §2.2 defines path, query, body, and header as per-field syntax modifiers. The projection types each as a DeclarationKind with class Surface, though no top-level declaration is introduced. Its shared declaration/client node also assigns Surface while RFC-0008 and RFC-0024 assign Operations. The Bytes and Map scalar/type nodes claim definition in RFC-0008, whose authored text does not define either type.
Recommended correction
- Model outbound HTTP auth choices under adapter-scoped value IRIs, distinct from RFC-0033 inbound schemes. Preserve the four values and HTTP header rules; link to a shared scheme taxonomy only if one is explicitly defined.
- Model binding modifiers as syntax modifiers with field scope, not declarations. Keep their exact HTTP placement rules and diagnostic links.
- Use the canonical
Operationsclass on the sharedclientdeclaration IRI. - Give
BytesandMapan explicit normative type definition before assigning adefinedInowner; retain their RFC-0025 use references without inventing definitions.
Acceptance
- Shared-domain identity audit has one class/FQN per reused IRI.
- RDF queries can distinguish outbound auth choice from inbound API scheme and field modifier from declaration.
- The source-domain protobuf, generated Turtle, reference pages, source-bound reviews, and site pin agree.
- Checked-in claim queries and local framework KG consumers are compared before and after subject IRI changes.
Nothing is deployed, so no stored RDF migration is required for the first release.