docs: strengthen v0 citation to cross-implementation evidence#9
Merged
Conversation
The README citation landed in #8 with the v0 vectors qualified as "Independently reproduced under rfc8785@0.1.4" — single-library evidence. The AP2 discussion #262 thread then escalated to cross-implementation: both @chopmob-cloud and we now have JS canonicalize@3.0.0 (erdtman + Rundgren, RFC 8785 author as contributor) reproducing all 7 vectors byte-for-byte against the Python rfc8785@0.1.4 output. Different authors, different languages, different codebases, same canonical bytes and hashes on every vector, all four pair invariants hold under both impls. Tighten the Background bullet to reflect that strengthened scope. Still qualified as community-seeded and not AP2-spec-blessed. No public API, wire-shape, or protocol-conformance change. Below the AUDIT.md / CHANGELOG.md update thresholds (docs-only pointer).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #8. The v0 conformance vectors citation landed in #8 qualified as "Independently reproduced under
rfc8785@0.1.4" — single-library evidence. The AP2 discussion #262 thread has since escalated to cross-implementation evidence:rfc8785@0.1.4canonicalize@3.0.0Different authors, different languages, entirely different codebases — same canonical bytes, same hashes, same pair behaviour for every vector. The Unicode NFC-vs-NFD pair agrees byte-for-byte under both, which is direct evidence that the no-Unicode-normalisation rule is implementation-independent, not an
rfc8785@0.1.4artefact.One README bullet edited to reflect the strengthened scope. Still qualified as community-seeded, not AP2-spec-blessed.
Why
The single-library wording in #8 was honest at the time but the public AP2 thread now carries the cross-impl validation — keeping the README aligned with the strongest evidence form that's currently in the public record.
Out of scope
AUDIT.mdandCHANGELOG.mdupdate thresholds — no entries added.gowebpki/jcs(Go) as the natural third implementation for an AP2-maintainer-blessed CI matrix remains future work; not in this PR.Test plan
rfc8785@0.1.4+ JScanonicalize@3.0.0against all 7 v0 vectors — 7/7 byte-identical JCS + 7/7 hash match + 4/4 pair invariants under each.canonicalize@3.0.0package.json on npm lists Anders Rundgren (RFC 8785 author) as contributor alongside Samuel Erdtman. Repo:erdtman/canonicalize.