Ted Thibodeau Jr
Ted Thibodeau Jr
> While investigating the above, I discovered that we have two competing definitions for holder (and several other things) — in [1.2 Ecosystem Overview](https://w3c.github.io/vc-data-model/#ecosystem-overview) (which I think should either point...
The initial comment on this PR should include the specific review comments this PR is meant to address, i.e. -- - [ ] Wordsmith statements to say is that the...
> it makes the specification longer, so we're probably better leaving things as-is. It also makes the specification clearer, and was based on requests from a reviewer with significant experience...
All existing mentions of `issuee` within HTML spec docs can be found with this search (which regrettably gets extra things like `issueEvent`, which I can find no way to exclude)....
@jandrieu [said](https://github.com/w3c/vc-data-model/pull/1468#issuecomment-2034848335) > Jamming two nouns together and pretending its a new noun most likely doesn't help ... We could say "presenter holder" or "recipient holder" I think you're right...
This is a blend of the `issuee` above, and my own earlier straw man. Note that no actions are required of the `issuee`; this is purely a passive role, based...
> Q. Is a holder required to store the VC in its repository? If not, how is it a holder? If it is, since an issuee is a subclass of...
In any case, we should capitalize JAdES (the "[JSON format for AdES Signatures](https://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.01.01_60/ts_11918201v010101p.pdf)") correctly, painful though it may be...
The significant downside of this change is that there's no longer any obvious fallback from `application/vc+ld+json` to `application/ld+json` nor `application/json`, obviating all the work we did to make plain-JSON (or...
@KonradHoeffner -- It appears that the issue described here has been resolved for you, upon correct tuning? Please confirm. Others (@whu2015, @vijayranker, @hanito, @Aklakan) -- Please advise, whether a current...