This item from the Did Spec Completion doc did not make it into the latest 0.1 spec.
3: JSON Pointer
Motivation
Enable tree-based processing of DIDs that include DID fragments (which resolve directly within the DID document) to locate metadata contained directly in the DID document or or the service resource given by the target URL without needing to rely on graph-based processing.
Proposal
Specify that DID URLs support the use of JSON Pointer (RFC 6901).
Suggestions from Dave Longley
Perhaps what could be done to deal with mapping the graph to a certain shape prior to using the JSON pointer (frame could be a URL which could be fetched, cached, or there could be some common frames, etc).
did:method:123?query=frame=https://example.com?234234#/json/pointer
TODO: explore further
SUGGESTION: Have the spec say that we should not do anything to prevent the use of JSON Pointer. 11
This item from the Did Spec Completion doc did not make it into the latest 0.1 spec.
3: JSON Pointer
Motivation Enable tree-based processing of DIDs that include DID fragments (which resolve directly within the DID document) to locate metadata contained directly in the DID document or or the service resource given by the target URL without needing to rely on graph-based processing. Proposal Specify that DID URLs support the use of JSON Pointer (RFC 6901). Suggestions from Dave Longley Perhaps what could be done to deal with mapping the graph to a certain shape prior to using the JSON pointer (frame could be a URL which could be fetched, cached, or there could be some common frames, etc). did:method:123?query=frame=https://example.com?234234#/json/pointer TODO: explore further SUGGESTION: Have the spec say that we should not do anything to prevent the use of JSON Pointer. 11