Dave Longley

> I've been trying to inform myself on how issuance works, and it seems like there is a pretty tight connection between Issuers and Holders ... meaning, it seems some...

> I guess, maybe the point that I was trying to make here is that the closed wallet choice is necessary (rather than, as you said, sufficient), and I think...

Side(-ish) note: I recommend adopting a pattern of: `/v1rc` until the spec reaches PR (or perhaps right before it when tests are passing for enough implementations in CR). This makes...

I think this is the only practical model: > User trusts wallet and browser equally to act on it's interests And, therefore, it's a violation of trust for a wallet...

> https://www.w3.org/2025/credentials/vcdi/multikey/context.jsonld While it might be very unlikely that we'd have another context version come out in the year 2025, it might be prudent to include the version number in...

Yes, those look ok to me. Thanks, @iherman!

@iherman, > I seem to be lost in the different changes. The text in [#1560 (review)](https://github.com/w3c/vc-data-model/pull/1560#pullrequestreview-2560505494) is pretty different from [#1560 (comment)](https://github.com/w3c/vc-data-model/pull/1560#discussion_r1921127205) and its related comments. Yeah, I think the...

Trying to help out... If you guys (@msporny and @David-Chadwick) both agree on this text (which includes edits from David's comment [here](https://github.com/w3c/vc-data-model/pull/1560#discussion_r1923432170)), let's use this: > A [=verifiable credential=] is...

I think this is now the default behavior -- we should confirm so we can close this issue.

I would think the kind of guidance we could offer would be like: "Alice can include one or more Verifiable Credentials that express information (such as location, etc.) about the...