search

uncefact / spec-untp

UN Transparency Protocol
https://uncefact.github.io/spec-untp/
GNU General Public License v3.0
10 stars 9 forks source link

why use VC 1.1 instead of 2.0? #81

Open VladimirAlexiev opened 2 months ago

VladimirAlexiev commented 2 months ago

Why do you use this context?

  "@context": [
    "https://www.w3.org/2018/credentials/v1",

In https://www.w3.org/TR/vc-data-model-2.0/#example-usage-of-issuer-property a newer version is used:

  "@context": [
    "https://www.w3.org/ns/credentials/v2",

Please also review the other imported contexts for being up to date:

    "https://w3id.org/vc-revocation-list-2020/v1",
    "https://w3id.org/security/suites/jws-2020/v1",
    "https://w3id.org/security/suites/jws-2020/v1",

And remove the duplication of jws-2020/v1

zachzeus commented 1 month ago

The upgrade of our reference implementation from v1 to v2 is in flight we will shortly be updating demos and references to point at v2

VladimirAlexiev commented 1 month ago

Thanks @zachzeus ! Do you expect any issues, or it's just a matter of upgrading the reference URLs? In other words, are VC 2.0 backward compatible in VC 1.1.

onthebreeze commented 1 month ago

We probably should not demand conformance with latest version until it is ubiquitously adopted

PatStLouis commented 3 weeks ago

I think supporting backwards compatibility for verifying is important but issuance should use the 2.0 version moving forward.