search

w3c-ccg / ld-cryptosuite-registry

REGISTRY: Linked Data Keys Registry (managed by W3C Credentials Community Group)
https://w3c-ccg.github.io/ld-cryptosuite-registry/
Other
12 stars 4 forks source link

JCS Ed25519 Signature 2020 Suite #31

Closed decentralgabe closed 4 years ago

decentralgabe commented 4 years ago

Hosted on the DIF: https://identity.foundation/JcsEd25519Signature2020/

OR13 commented 4 years ago

This entry looks correct, but I think we need to wait for confirmation that the go, java, and javascript implementations are functioning the same.

And I need to take another pass at reviewing the spec.

decentralgabe commented 4 years ago

Updated name

OR13 commented 4 years ago

@msporny @talltree can you give your thoughts on this?

msporny commented 4 years ago

Its a bit odd to add a suite that doesn't support JSON-LD to a Linked Data Crypto Suite Registry, but it might be helpful for others.

In the early days, I specifically pushed JSON-LD in the direction of rejecting RDF due to it's complexity and, what I viewed to be, a hard headed, uncompromising community of academics. In time, the RDF and JSON-LD communities came together.

http://manu.sporny.org/2014/json-ld-origins-2/

BUT... the Linked Data part of JSON-LD was specifically not RDF. We didn't call it JSON-RDF on purpose, because we didn't want to assert that RDF was the only way to do Linked Data (because, initially, JSON-LD wasn't based on RDF at all).

So, I suggest throwing up the horns :smiling_imp: and merging this :fire: :apple: :shopping_cart: :fire:. Yes, you can only generate the signature in a JSON syntax, but that's not wrong.