RFC-0006 scalar representation 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.
Status: proposed for the first release. Owners: Semantic Core, compiler, and serialization. Nothing is deployed, so no stored-value migration is needed.
Source gap
RFC-0006 §4.A lists scalar names but gives no representation contract for five details asserted by the RDF domain projection:
| Scalar | RDF assertion without authored definition |
|---|---|
Currency | A currency code value. |
Decimal | A fixed-precision decimal value. |
Identifier | An opaque identifier value. |
Timestamp | An instant-in-time value. |
USState | A US-state code value. |
These qualifiers can affect accepted values, comparison, storage, JSON/proto
serialization, SQL lowering, and cross-language clients. The Lean RFC-0006
catalog names Value and Reference but does not define these five scalar
representations. A generated RDF summary alone cannot establish them as
first-release guarantees.
Recommended path: define the five scalar value domains in authored RFC clauses, including exact lexical forms, normalization, equality, null and invalid-value behavior, and serialization. Regenerate Lean definitions, references, and RDF from those clauses. If the implementation cannot yet support one, remove that RDF qualifier and publish a scoped gap rather than claiming an undefined representation. The alternative is to keep all five as opaque named scalar categories for the first release and trim RDF to that minimal contract; this delays useful type-level guarantees.
Acceptance
- Choose a canonical source contract for each scalar before normative publication; do not infer an ISO code, decimal scale, identifier format, timestamp timezone policy, or US-state encoding from the name alone.
- Test valid, invalid, boundary, and round-trip cases through
.gnmtype checking, protobuf/JSON boundaries, storage, and Graph clients. - Align authored RFC, Lean catalog, RDF source, reference pages, query consumers, and published implementation evidence; re-run drift and source-bound review gates.