gnomonlearn
Docs/RFC-0025 HTTP path binding proposal

RFC-0025 HTTP path binding 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 §2.2 says a path modifier interpolates its field into a matching {fieldName} token in the operation’s path: template. The same section and §4 then declare that a modified field appearing in that template is a dual-location error M25514. The normative example marks owner and repo as path and uses both tokens, so it would fail its own rule. The paragraph after the example says modified fields interpolate without tokens and describes automatic token synthesis, but gives no position or ordering rule for synthesized tokens. The current narrative and Lean catalog both assign informational M25515 to synthesis and M25514 to duplicate placement. Their code agreement does not resolve the example conflict or supply a synthesis algorithm.

  • A path modifier claims the field’s location. The path: template must contain exactly one {fieldName} token for that field. The token is a substitution site, not a second location claim.
  • A matching token may also claim an unmodified field in the existing fallback pass. A token that names no input field or appears more than once is a compile error.
  • M25514 applies when a query or body modifier conflicts with a corresponding operation-level location, or when a field is assigned to two distinct locations. The path-modifier plus matching-token pair is valid.
  • Remove implicit path-token synthesis and the M25515 informational behavior. Missing tokens for path-modified fields are compile errors with a dedicated diagnostic code from the RFC-0025 range.
  • URL-encode each substituted field exactly once. Keep the authored example valid.

Acceptance

  • Compile the authored createIssue example and verify /repos/{owner}/{repo}/issues resolves with encoded values.
  • Reject missing, duplicated, or unknown path tokens; reject distinct location conflicts; accept unmodified fields claimed by template tokens.
  • Narrative, Lean diagnostics, source-bound RDF claims, diagnostic inventories, and reference output use one diagnostic mapping.
  • The HTTP adapter’s compiler fixtures and generated module manifest pass; build and site references stay pinned.

Nothing is deployed, so no runtime compatibility migration is required for the first release.