Verifiable Credentials 2.0

[kayaelle]

VC 2.0 is inching it's way towards release. It may be a good idea for the group to start reviewing the changes and considering:

https://www.w3.org/TR/vc-data-model-2.0/

One big change is the switch from issuanceDate to validity period: https://www.w3.org/TR/vc-data-model-2.0/#validity-period

[clehner]

As well as validity period (issuanceDate/expirationDate -> validFrom/validUntil),
and the new base context URL (https://www.w3.org/ns/credentials/v2),
id properties now must be URLs (https://www.w3.org/TR/vc-data-model-2.0/#identifiers); I think this invalidates use of UUID URNs (urn:uuid:...) as in the OB3 examples.

[amiller-ims]

It was discussed recently here: w3c/vc-data-model#1160. In particular, see this comment: w3c/vc-data-model#1160 (comment)

Yes, discussed to death at W3C between the years of 2008-2018 or so. Ultimately, that resulted in this specification:

https://url.spec.whatwg.org/

... which is now the normative specification for "URLs" for the Web... where URLs include things like URIs and URNs.

In other words, you can continue to use URNs such as those in the OB3 examples.

[clehner]

@amiller-ims thank you for the correction.
I see now a URN is in the URL spec examples
https://url.spec.whatwg.org/#example-url-components

[ottonomy]

id properties now must be URLs (https://www.w3.org/TR/vc-data-model-2.0/#identifiers); I think this invalidates use of UUID URNs (urn:uuid:...) as in the OB3 examples.

What about our use of data URIs in id properties for things like Image.id. Schema.org has a contentUrl property that we could fall back on if the use of data URIs in id fields is disallowed.

@clehner what's your take on this? Has anybody brought up that data URIs are often used in properties that expect an identifier?