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

Consider deprecating this work item #37

Open OR13 opened 3 years ago

OR13 commented 3 years ago

@msporny maybe we can kill this off and use the did spec registries instead? seems like mostly a dupe of that registry.

msporny commented 3 years ago

@msporny maybe we can kill this off and use the did spec registries instead? seems like mostly a dupe of that registry.

DID / Linked Data / RDF turf war in 3... 2... 1. :)

Yes, they are more or less the same thing... if we could mechanize the process of copying one of them into the other, that might be best. The Linked Data Security WG Charter already expects to have control of this cryptosuite registry and I doubt they'd be ok w/ the DID WG having control over it:

https://w3c.github.io/lds-wg-charter/#ig-other-deliverables

I'd like it to result in less work for those maintaining the registries... so, either DID Spec Registries copies the registry out of this one, or the other way around.

I suggest we let this marinate until the LDS WG is up and running... I expect they'll have some thoughts on this.

kdenhartog commented 3 years ago

I just added a reference from the VC spec to point at this document, so if we do decide to please don't forget to update the reference to the new location.

Also, this may end up fitting better in the VCWG from the recent in scope/out of scope discussions I've heard about the LDI charter so I'd think this one is still on hold until then.

OR13 commented 3 years ago

this registry does not belong in a community group... this registry should be moved to the VC WG, like the did did spec registries is for dids.

msporny commented 3 years ago

this registry does not belong in a community group... this registry should be moved to the VC WG, like the did did spec registries is for dids.

We can't do that until the W3C AC approves the VCWG rechartering that puts LDI in scope in it's charter. :(