Orie Steele

@brianorwhatever it knows what a hash is supposed to look like, and how to encode base64url... but sadly its not secure in the random oracle model.... the syntax it proposes...

There were updates related to this in data integrity, see: - https://w3c.github.io/vc-data-integrity/#retrieve-verification-method

We decided to move this issue to vc-jwt, I believe this is already solved for in data integrity. @brentzundel @Sakurann can we close this now?

If only this came with a regex https://ijmacd.github.io/rfc3339-iso8601/

I don't understand the proposal. Is it to use /2018/ in IRIs for terms defined in 2023? Or is it to use /2018/ for terms defined in v1, and do...

So this should be changed: https://github.com/w3c/vc-data-model/blob/main/contexts/credentials/v2#L4 from: `"@vocab": "https://www.w3.org/ns/credentials/issuer-dependent#",` to `"@vocab": "https://www.w3.org/2018/credentials/issuer-dependent#",` No other changes are implied by the proposal. And this issue can be closed after the above is...

@iherman Ahh ok, I think this thread is pretty massively stale at this point. I suggest we close this issue to avoid future confusion.

I suggest we close this.

I'm happy to answer any questions and to propose additional text, on a dedicated issue.

cc @awoie who just answered a question about this on the ccg list. To make this work with iOS don't you need to use an https link?