w3c / did-imp-guide

DID Implementation Guide (Note)
https://w3c.github.io/did-imp-guide/
Other
17 stars 11 forks source link

Add considerations about Data Model and Representations. #8

Closed peacekeeper closed 3 years ago

peacekeeper commented 3 years ago

Adds some guidance about the Data Model and Representations, and describes problems with using representation-foreign entries such as @context in an application/did+json DID document.

As discussed, we can also include alternative / opposing views.

Adresses https://github.com/w3c/did-imp-guide/issues/6.

Also see discussions in https://github.com/w3c/did-imp-guide/issues/5 and https://github.com/w3c/did-imp-guide/pull/3.


Preview | Diff

peacekeeper commented 3 years ago

"representation-foreign entry" seems to have been coined for this PR... and I agree with neither this appellation nor the characterizations in the "advisement" that follows.

@TallTed No, the term was coined in a resolution which the WG accepted on 5 Nov 2020, to describe a situation when a representation-specific entry such as @context shows up in another representation:

https://www.w3.org/2019/did-wg/Meetings/Minutes/2020-11-05-did#resolution5

Strictly speaking, we should have covered this in DID Core. But since we didn't do that, this PR at least adds it to the Implementation Guide.

Most of what follows reads to me as very personally slanted, though written as if it were not.

@TallTed I consider this write-up not a personal opinion, or a proposal, but rather a historical account of why the ADM and the registry were introduced (some people - including myself - wanted JSON-LD, while others wanted non-LD JSON).

-1 to giving advice when there is not consensus on what advice to give.

@dlongley I know that a lot of people disagree with this PR, but the conclusion was that we would allow different viewpoints which can reference each other. I therefore expect the PR to be merged, and then when Orie or others write up their counter-arguments, I will not oppose them either.

msporny commented 3 years ago

Multiple reviews, changes requested and made, concerns raised but non-blocking, merging.