JENA-2155: Add Web Access Control Ontology #1064
Conversation
|
Hi @ebremer, What's the long term situation here? Is the work in Solid a different namespace? Is it compatible with this (up to 2016) vocabulary? |
| public static final Property defaultForNew = Init.defaultForNew(); | ||
| public static final Property owner = Init.owner(); | ||
|
|
||
| public static class Init { |
There was a problem hiding this comment.
This shouldn't need the "Init"
Use of "Init" is needed in RDF.java uniquely to stop class preliminary initialization problems within jena-core. It arises because Jena internally uses RDF constants. Once jena-core initialization (which is the earliest) then everything should be normal.
If you encountered a problem, we need to track it down.
There was a problem hiding this comment.
No problems. Was following the code for RDF. I removed the Init function. Added the final new line.
| public static final Node defaultForNew = Init.defaultForNew().asNode(); | ||
| public static final Node owner = Init.owner().asNode(); | ||
| } | ||
| } |
afs
changed the title
|
Maybe the class name should be |
|
The name space is the same as what is used in Solid: https://solid.github.io/web-access-control-spec/ |
|
Thanks for the updates. How about WebACL? It's just "ACL" just feels a bit weak because this is specific to web operations. Vocabularies don't have to be in jena itself - it does not convey any magic to them - but this is a W3C work. If Solid add something, presumably it will go in a different namespace or get community agreement. |
|
WAC would fine with me. Keeps it short and less ambiguous. What say you? |
|
OK |
|
Done. |
https://www.w3.org/wiki/WebAccessControl