-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pointing into nodes in surfaces #206
Comments
Of course, we do this with hash URLs such as |
I think this is not an N3 issue, but a VCDM issue. I think you're correct, that the Credential Graph should point to the Credential Proof Graph; i.e., that the I think there are some other issues with this diagram which stem from its original creation, rather early in the VCDM process, combined with later efforts to simplify it (for instance, to include just one claim), which unfortunately removed and/or distorted elements which may have been more correct in the earlier version(s), or may never have been quite correct. |
It is an N3 question for the rdf proposed in
I have the following argument about how one can go logically from one to the other. In
|
The Verifiable Credentials Data Model has an interesting diagram of how they see the structure of a Credential,
which I reproduce below from the Figure 6 of §3.2 Credentials
As argued in issue 1248 of the VC repo the JsonLD does not seem to map to that data structure, where the colored surfaces are mapped to N3
{...}
contexts.In issue 1248 I tried to map as closely as I could to N3, but came across these two problems for which I was not sure what the best encoding would be:
:credentialSubject
relation points from theCredential123
node on the pink surface into the yellow Claim surface to its right. But it does not point at the claim, i.e, at the surface border, but into a node in the claim, namely the node named:Pat
.:Signature456
node.I don't think the lower claim must be on its own surface. And I am unsure if there is a need to point to the node on the surface in those two cases. Still, I wonder if and how N3 could represent it.
The text was updated successfully, but these errors were encountered: