Skip to content
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

Jump to bottom

Add 'jcs' and 'urdna2015' canonicalization values. #261

Merged
merged 2 commits into from Oct 10, 2022
Merged

Add 'jcs' and 'urdna2015' canonicalization values. #261

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
30da43e
Introduce 'canonhash' tag instead of c14n via multihash.
dmitrizagidulin Mar 8, 2022
f2559ee
Re-add JCS, change tag from canonhash to ipld to match json-dag.
dmitrizagidulin Sep 30, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions table.csv
View file
Open in desktop
Expand Up @@ -483,8 +483,10 @@ skein1024-1016, multihash, 0xb3df, draft,
skein1024-1024, multihash, 0xb3e0, draft,
poseidon-bls12_381-a2-fc1, multihash, 0xb401, permanent, Poseidon using BLS12-381 and arity of 2 with Filecoin parameters
poseidon-bls12_381-a2-fc1-sc, multihash, 0xb402, draft, Poseidon using BLS12-381 and arity of 2 with Filecoin parameters - high-security variant
urdca-2015-canon, ipld, 0xb403, draft, The result of canonicalizing an input according to URDCA-2015 and then expressing its hash value as a multihash value.
Copy link

@gobengo gobengo Mar 31, 2023 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this be urdna-2015-canon with an n not a c

urdna

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a debate raging over what we should call it. Traditionally, we used "n" to mean "normalization"... but it's generally accepted now that we should've said "canonicalization" since it's a more accurate description of what's happening. Thus, the "urdca" vs. "urdna" distinction. This is currently being discussed in the W3C RDF Dataset, Canonicalization, and Hashing Working Group (note that we didn't call it the "normalization" working group).

Copy link

@gobengo gobengo Apr 1, 2023 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@msporny is there a uri for that issue or do I need to file one? I just earlier today noticed meetings are started and I need to get that on my cal.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

w3c/rdf-canon#88

ssz, serialization, 0xb501, draft, SimpleSerialize (SSZ) serialization
ssz-sha2-256-bmt, multihash, 0xb502, draft, SSZ Merkle tree root using SHA2-256 as the hashing function and SSZ serialization for the block binary
json-jcs, ipld, 0xb601, draft, The result of canonicalizing an input according to JCS - JSON Canonicalisation Scheme (RFC 8785)
iscc, softhash, 0xcc01, draft, ISCC (International Standard Content Code) - similarity preserving hash
zeroxcert-imprint-256, zeroxcert, 0xce11, draft, 0xcert Asset Imprint (root hash)
varsig, varsig, 0xd000, draft, Namespace for all not yet standard signature algorithms
Expand Down