search

w3c-ccg / did-spec

Please see README.md for latest version being developed by W3C DID WG.
https://w3c.github.io/did-core/
Other
124 stars 45 forks source link

Explain the reasoning behind using graph data models and JSON-LD #58

Closed msporny closed 6 years ago

msporny commented 6 years ago

From @rxgrant at RWoT6:

The spec currently doesn't explain why we're depending on graph-based data models and JSON-LD for extensibility. It also doesn't explain when you can and/or shouldn't process the document as pure JSON. We should add a section explaining this architectural decision. Mention the expectation that developers will parse DID Documents with common libraries (e.g. what happens when "owner" doesn't exist).

msporny commented 6 years ago

Resolve this issue by submitting a PR that creates a section on why graph-based data models and JSON-LD were chosen for extensibility, semantic interop, and what happens if we don't have those features.

talltree commented 6 years ago

I am in favor of resolving this exactly as Manu describes. I'm willing to write this or co-write it as we spent a LOT of time working out how DID documents could strike the right balance between supporting the JSON-LD graph model for extensibility and the JSON tree model for simplicity. So I'd really like us to communicate this clearly to developers.

On Thu, Mar 8, 2018 at 2:38 AM, Manu Sporny notifications@github.com wrote:

Resolve this issue by submitting a PR that creates a section on why graph-based data models and JSON-LD were chosen for extensibility, semantic interop, and what happens if we don't have those features.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/w3c-ccg/did-spec/issues/58#issuecomment-371405483, or mute the thread https://github.com/notifications/unsubscribe-auth/ADLkTX6zR1JbEMN0RkcWOpu8_zC-dTfsks5tcN_2gaJpZM4ShDL3 .