Skip to content
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

Missing documentation for security:contoller #114

Open
bblfish opened this issue Jun 12, 2021 · 1 comment
Open

Missing documentation for security:contoller #114

bblfish opened this issue Jun 12, 2021 · 1 comment
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@bblfish
Copy link

bblfish commented Jun 12, 2021

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.

@bblfish bblfish added bug Something isn't working help wanted Extra attention is needed labels Jun 12, 2021
@bblfish
Copy link
Author

bblfish commented Jun 17, 2021

is security:controller the same as did:controller from the [did specification])(https://www.w3.org/TR/did-core/#dfn-did-controllers)? Is there an equivalent security:subject?

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant