RFC-0034 · 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: How can an HTTP path modifier bind to its matching route token?
Status: Open
Source: RFC-0034 §§5.1, 6–7.1; M34023; RFC-0025 §§2.2–2.3
Issue: The example route uses {enrollmentId} and its input would naturally carry a path modifier, but the rule treats a field appearing in both the modifier and route template as a conflict. This repeats RFC-0025’s path-binding contradiction.
Recommendation: Make a matching route token the target of a path modifier, not a second location assignment; reject missing, duplicate, or mismatched tokens consistently on client and server bindings.
Q: Does inbound null for an optional field mean absence or a zero value?
A: RFC-0006 §4.D is authoritative: inbound null becomes field-absent for an optional field, and an explicit default is then applied if present. RFC-0034 §5.2, its Lean catalog, and its RDF claim text now agree.
Source: RFC-0034 §5.2; RFC-0006 §4.D
Issue: The handler replaces null for an optional field without a default with a type zero value. That can turn an omitted age into 0 or an omitted list into an empty list, changing operation meaning while still appearing valid.
Recommendation: Normalize null to absence for optional fields, apply an explicit default only when declared, and reject null for required fields.
Q: When do the promised server-side protocol extensions become authoritative?
Status: Open
Source: RFC-0034 §§4, 7; RFC-0025–0027, RFC-0029 Issue: RFC-0034 calls its extension tables normative but labels the owning protocol RFC sections “to be authored”. A compiler importing those modules has no matching manifest and no single authoritative owner for server slot definitions. Recommendation: Add the server extension manifests and normative rules to each owning protocol RFC and implementation before marking RFC-0034 or a server binding ready.
Q: What operation can map to a GraphQL subscription root?
Status: Open
Source: RFC-0034 §7.3; RFC-0033 §6.1; RFC-0020 §1
Issue: api.exposes allows only actions, queries, and procedures, while §7.3 says reactive operations may map to GraphQL Subscription. RFC-0020 has no .gnm subscription declaration. No exposed operation kind currently supplies the required stream contract.
Recommendation: Omit subscription mapping until a typed, authored streaming operation is specified, or define that operation and add it to the API exposure grammar.
Q: What happens when a selected protocol cannot enforce api.auth?
Status: Open
Source: RFC-0034 §5, §11 M34021; RFC-0033 §6.3 Issue: M34021 is an error but its summary says the unsupported auth scheme “will be silently ignored at runtime.” A binding that compiles despite unsupported authentication would violate the handler’s mandatory auth step. Recommendation: Make unsupported authentication a compile error that prevents stub and route emission; never publish a binding with a silently ignored auth requirement.