RFC 9880 model assessment inventory

The immutable fine-grained inventory rfc9880.model/1 contains 54 finite model obligations. It covers RFC 9880, including normative Appendices A and C. Appendix B is informative; Appendix D contains examples and Appendix E historical changes. Imported definitions apply only where a clause uses them. Each obligation counts once across the requested model scope, regardless of how many occurrences or supporting citations it has.

The Full request retains assessment and baseline identity rfc9880/base-1. Its area inventory esdieff.full-model/1 has 13 members. Initial retains its eight narrower areas and existing exclusions. Successful Initial assessment always discloses broader partial coverage. These identities follow ADR 0011: Machine-readable report contracts and ADR 0013: Shared workflow and report guarantees.

Completion and applicability

An obligation is assessed only when all applicable occurrences and subdimensions have been assessed, including definite invalidity. Established absence is not applicable. Missing implementation is unassessed; unknown needed meaning, context, knowledge or traversal is undetermined. Joining repeated observations uses undetermined before unassessed, then assessed, then not applicable. One finished occurrence cannot hide an unfinished sibling. Errors, warnings and notices remain independent of completion and of optional detail retention.

Full broader completion describes these54 model obligations. Requested outcome completion describes all13 selected areas, including the separate advisory area. All model work may therefore finish while advice remains incomplete. Assessed errors still constitute completed work; neither completion value certifies validity or universal capability. Full does not emit an optional omitted-areas list whose absence could be mistaken for completion.

Full establishes capability and meaning for the supplied model. Sample admission is a separate operation; a successful sample never completes a model obligation. Device behavior, protocol bindings, conversion, registry administration, operator duties and general satisfiability are outside this model denominator. Unknown extensions are retained without guessing their meaning or universally rejecting them.

Each subclause has one counting owner. The clause ownership table names supporting dependencies separately. The clause-family trace preserves all132 body/grammar/characteristic/process families and the explicit comment obligation with their model owners or excluded roles. These are traceability rows, not another denominator. For example, nullable belongs to M029, special-type selector admission to M025 and Property flags to M031; they do not also earn M022 credit. M022 owns only unit and content-format string shape. Direct-item container shape belongs to M040; Full properties and Choice descendants retain M038 and M030. Grammar family G013 therefore supports M039 for pattern/format/uniqueness shape and M040 for the restricted items container.

Obligations

IDs below expand to rfc9880.model.M001/1 through rfc9880.model.M054/1. The capability column describes current checking and limitations. Runtime status comes from the report, not this table.

The model coverage boundaries collect retained gaps with their current outcomes, reasons and conditions for reconsideration.

Formal CDDL number membership is separate from mathematical decimal decoding. Appendix A imports the RFC 8610 domains: uint 0 through 2^64−1, nint −2^64 through −1, their int union, and binary16/32/64 floating-point values. Full admits every JSON number as number, following RFC 8610 Appendix E’s description of JSON numbers as decimal and RFC 9880’s own Figure 5, which uses 5e-2. Full checks uint as integral values from 0 through 2^64−1, without rounding. Numeric literals, bound parameters and count parameters have distinct owners M035, M036 and M037. Exact lexemes such as 0.1, 10.0, 18446744073709551616 and 1e400 remain inspectable. Colon entries reject established out-of-domain counts. Grouping counts use no-cut fallback and known literal extension alternatives remain framework-admitted, with their unavailable semantics scoped separately. Initial, expanded and selected-sample contracts remain unchanged. See ADR 0032: Formal model admission and the formal admission contract.

Full area membership

The fixed areas are document syntax, model roles, metadata, namespace/reference, composition/requiredness, critical extensions, data grammar, formal numbers, scalar meaning, pattern/format, compound meaning, special type/unit, and the four advisory classes. Their exact IDs are the distinct area entries in the table above plus advisory-four/1. The advisory area counts once in the 13 areas and contributes no extra RFC obligation to the 54 denominator.

Both unit subareas join once into M023. Both content-format subareas join once into M024. Modified metadata joins into M012 and pattern syntax into M047. Each resulting obligation joins once into its Full area. Producing condition IDs remain modified-date-time/1, unit-spelling/1, unit-registry-guidance/1, content-format-syntax/1, content-format-registry/1, pattern-syntax/1, inspection for required relationships, or advisory-four/1. Optional coverage_owner identifies their requested Full area without changing the producing assessment_unit. Generic findings use actual field and role context.

Roles outside model assessment

The following audit identities do not enter model counts. They distinguish standards duties from the model obligations above.

Consumer contract

The mandatory existing request.inventory identifies the immutable area membership. esdieff.full-model/1 also binds the 54-member rfc9880.model/1 inventory, even when every new optional section is absent. Historical Full reports with null inventory and coverage.inventory_unavailable mean unknown membership, never an empty inventory.

The borrowed descriptor and typed status accessors do not render or allocate a report. Full returns all 54 known descriptors and authoritative statuses; an unfamiliar requirement ID is absent. Other operations do not request this inventory. Optional wire aliases, summaries, rows and ownership detail may be omitted under presentation limits. Consumers preserve mandatory aggregates and surviving diagnostic facts, accept unknown additive fields and human wording changes, and validate unique retained identities and linked omission counts. See the report contract.