-
Notifications
You must be signed in to change notification settings - Fork 1
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
Describe how to transform a key id into an actor id #9
Comments
Also, I think the following constraints would be necessary:
For the |
I don't think that's true at all. Also, |
@evanp |
(I expect any conclusion here this to be incorporated in the draft text in #8 (comment).) |
The property isn't defined to be "functional" (single-valued), and generally speaking, an RDF property not explicitly specified to be functional can have multiple values because the functionality is opt-in IIUC. And that seems to actually match the intention of the Security Vocabulary spec, since the spec has a number of examples that use the term with an array value (search the spec for |
Thanks @tesaguri! |
I think the algorithm is roughly:
If the key ID has a fragment...
owner
of that propertyIf the key ID does not have a fragment...
owner
of that resourceThe text was updated successfully, but these errors were encountered: