RFC-0025 · Design Q&A
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.
Q: Does a path modifier require or forbid a matching path token?
Status: Open
Source: RFC-0025 §§2.2–2.3, 4; M25514–M25515
Issue: The canonical createIssue example marks owner and repo as path and also includes {owner} and {repo} in path:. The rules classify that combination as M25514 conflict. They then say a missing token is auto-synthesized, but no insertion point or resulting URL is defined.
Recommendation: Require each path-modified field to match exactly one existing {fieldName} token; treat that token as the target of the modifier, not a conflicting assignment. Reject missing or duplicate tokens rather than synthesizing an unspecified path.
Q: Which slot controls request-body encoding?
Status: Open
Source: RFC-0025 §§2, 4 step 3, 5
Issue: responseAs: is defined as response decoding, but §4 changes request-body serialization to octet-stream when responseAs: binary. A client can need a binary request with JSON response or the reverse.
Recommendation: Keep responseAs solely for response decoding and add a separate request encoding/body media-type slot to the HTTP binding.
Q: Can a static header override the declared authentication scheme?
Status: Open
Source: RFC-0025 §3; RFC-0024 §4
Issue: An operation-level or client-level Authorization entry wins over auth: bearer-token or auth: basic, so the runtime can silently use an authored static header instead of the credential store. That weakens the meaning of the declared auth: scheme and can leak a literal credential into a compiled bundle.
Recommendation: Reject collisions with auth-owned headers at compile time, or require an explicit auth: none and a separately reviewed custom-header credential mechanism.
Q: Can M25510 be both an error and a warning?
Status: Open
Source: RFC-0025 §4.1; §7 Issue: Implicit body collection emits M25510 at warning severity, while the diagnostic table defines M25510 as an error for an unplaced input field. A single code then has two distinct conditions and severities. Recommendation: Allocate a separate warning code for implicit body collection, keeping M25510 as the unplaced-field error.
Q: Does an absolute path: bypass the client’s registry of permitted outbound origins?
Status: Open
Source: RFC-0025 §6; RFC-0024 §4; RFC-0009 permission model
Issue: An operation can ignore baseUrl: by supplying an absolute URL while retaining the client’s authentication headers. The RFC warns but does not require that the alternate origin be authorized or that credentials be withheld across origins.
Recommendation: Require the absolute origin to be declared and authorized at compile and runtime, and never forward client credentials to an undeclared origin.