-
Notifications
You must be signed in to change notification settings - Fork 9
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
Create asset Action not present in ODRL #35
Comments
Yes, there is no restriction on adding a new "ex:create" action (in your profile). |
But shouldn't we be able to express policies for assets that do not exist yet? |
I don't find the notion "existing" specific enough. An identifier being expressed and discoverable or dereferenceable may be more useful. Technically a policy for a URI that's not dereferenceable is possible. Or possibly even a bnode instead of a URI. Alternative approach is to refer to a container/collection/storage of sorts that will eventually contain the specific asset. (I don't know what a "data vault" is.. is that expressed in a spec / document somewhere or random branding out there?) |
@csarven agreed. I want to be able to say that the target of my policy is some instance of dpv:Data, for instance, as I might not even know where that particular piece of data is. (AFAIK "data vault" is being used as you would use data stores or data wallets, but it is not very important for the point I wanted to make - I don't care very much where the data is stored as long as I can decide who has access to it or what can be done with it) |
@besteves4 |
Included in the Community Vocabulary via this commit. |
In an usage control enforcement project, I am trying to use ODRL as a language as policy language for CRUD decisions.
To the best of my knowledge, it is not possible to state with an ODRL Rule to declare an
odrl:Action
that an entity is allowed to create an asset.In an issue on the aforementioned project, I argue that it is possible however to use
odrl:use
for this purpose.The problem with
odrl:use
, however, is that it allows for way more than just creating an asset.My question thus is, shouldn't it be possible to state with ODRL that an entity is allowed to create an asset? (e.g. by using an action such as
odrl:create
with as description "The act of creating an Asset")The text was updated successfully, but these errors were encountered: