You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no documentation for the "controller" property that is used in a very large number of examples in the security vocab. It is given a namespace in the v3 namespace json-ld giving it the URLhttps://w3id.org/security#controller.
My guess is that it relates key material to the agent that knows the private key of the published public key.
We have a use for this in Solid, and I have written up here how I propose we use it: JWK in Access Control. So I wanted to check here if the interpretation of the relation I was guessing at was correct, and of course it would help if that were specified in writing in the spec.
The text was updated successfully, but these errors were encountered:
Mhh: I see that the did namespace document assigns "controller" to <https://w3id.org/security#controller> so they are the same. So the problem is that by following one's nose one does not end up at the did specification.
There is no documentation for the "controller" property that is used in a very large number of examples in the security vocab. It is given a namespace in the v3 namespace json-ld giving it the URL
https://w3id.org/security#controller
.My guess is that it relates key material to the agent that knows the private key of the published public key.
We have a use for this in Solid, and I have written up here how I propose we use it: JWK in Access Control. So I wanted to check here if the interpretation of the relation I was guessing at was correct, and of course it would help if that were specified in writing in the spec.
The text was updated successfully, but these errors were encountered: