Skip to content

docs(core): name ERR_INVALID_NUMBER and fix two stale citations #170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
justinmerrell merged 1 commit into from
Oct 4, 2026
Merged

docs(core): name ERR_INVALID_NUMBER and fix two stale citations #170

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions specifications/core/v1/spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -518,7 +518,8 @@ Musher document and is read identically.
The byte boundary MUST use fatal UTF-8 decoding. Parser/profile errors and
representation depth are checked before conversion to JSON; aliases are never
expanded. Implementations return diagnostics rather than conversion exceptions.
Non-finite numbers and integers outside ±9007199254740991 are rejected.
Non-finite numbers and integers outside ±9007199254740991 are rejected with
`ERR_INVALID_NUMBER`.
Other numbers use finite binary64 representation. Logical values may contain
null when explicitly admitted by their value schema; this is separate from
optional document-field omission.
Expand Down Expand Up @@ -658,7 +659,9 @@ edition ([§8](#conformance)), so the two corpora the claim names both exist and
were tested together. How the edition is recorded, the checks that hold a
family release while this document has unreleased releasable changes, and why
its other unreleased changes only warn, are set out in
[ADR 0023](../../../docs/adr/0023-published-bytes-are-immutable-release-assets.md).
[ADR 0023](../../../docs/adr/0023-published-bytes-are-immutable-release-assets.md),
as [ADR 0037](../../../docs/adr/0037-the-repository-adopts-engineering-conventions-0-7-0.md)
§3 refines it.

**What a release of this document may change.** This paragraph is informative:
it records this repository's release policy. Within v1, a minor release of this
Expand Down Expand Up @@ -749,8 +752,9 @@ reviewed brings in something the review did not cover.

**Schema retrieval.** Every published bundle is self-contained: all `$ref`s
resolve inside `$defs`, and no validator needs a network request to evaluate a
document ([README](../../../README.md)). An implementation SHOULD vendor the
schema at an exact version rather than fetching it, and MUST verify what it
document ([Using the schemas](../../../docs/using-schemas.md#offline)). An
implementation SHOULD vendor the schema at an exact version rather than fetching
it, and MUST verify what it
fetches if it does — the `.sha256` beside each pinned URL and `published.json`
are there for that. A validator that resolves schemas over the network at
validation time is an SSRF primitive and a runtime dependency on an origin it
Expand Down
Loading