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

Profile is not permitted to define failure sub-property #300

Open
nitmws opened this issue Mar 5, 2018 · 9 comments
Open

Profile is not permitted to define failure sub-property #300

nitmws opened this issue Mar 5, 2018 · 9 comments
Assignees

Comments

@nitmws
Copy link
Contributor

nitmws commented Mar 5, 2018

The section about Rule Class in the Information Model (IM) defines for the failure property:

A Rule MAY have none, one or many failure sub-property values of type Rule.

The IM currently defines two failure sub-properties: remedy, consequence.

But the ODRL Profile Mechanism does not permit to define a sub-property of failure (by not listing creating failure sub-properties this section).
This appears to be an overly strict constraint in particular as for the semantically quite similar function property of the Rule Class sub-properties may be defined by a profile.

@vroddon
Copy link
Contributor

vroddon commented Mar 6, 2018 via email

@nitmws
Copy link
Contributor Author

nitmws commented Mar 6, 2018

@vroddon at the call on 5 March it was agreed that I should write this down as an official issue.
Then it will be reviewed and either accepted or added to a list of "pending next ODRL version issues".

@simonstey
Copy link
Contributor

simonstey commented Mar 13, 2018

The IM currently defines two failure sub-properties: remedy, consequence.

+ duty

@riannella
Copy link
Contributor

The first para before the Table should have read:

"To create an ODRL Profile, direct extensions to the ODRL Core Vocabulary classes, properties, and instances are defined. The table below shows some of of the typical extensions:"

@nitmws
Copy link
Contributor Author

nitmws commented Mar 16, 2018

@riannella what exactly is a "direct extension"? This must be explained in this para. Could it be:

"To create an ODRL Profile, the ODRL Core Vocabulary classes are extended by sub-classes, the properties are extended by sub-properties, and instances of both are defined. The table below shows some typical extensions:"

This leaves open: may new non-sub-property properties be added?

And another question: may a new (sub-)property be defined in the ODRL namespace? A quick check did not show any prohibition of that.

@riannella
Copy link
Contributor

Given the IM is based on the open-world RDF/OWL model, anyone can define a property with domain and range from ODRL and use it in a Profile.

No, only W3C can now add terms to the https://www.w3.org/ns/odrl/2/ namespace

@nitmws
Copy link
Contributor Author

nitmws commented Mar 19, 2018

Ok, then I suggest this definition of the Profile Mechanism using a more verbose but as I think also clearer wording:

To create an ODRL Profile, the ODRL Core Vocabulary classes can be extended by sub-classes with optional additional properties, the Core Vocabulary properties can be extended by sub-properties, further instances of classes and properties defined by the Core Vocabulary or this Profile can be defined. The table below shows some typical extensions, a new Profile is not limited to them:

What about these phrases in the Profile Definition examples:

  • ... and define it as disjoint with all other Policy subclasses (except Set).
  • ... and define it as disjoint with all other Rule subclasses.

Is that only a hint or a normative requirement?

@riannella
Copy link
Contributor

In section 2.6 we do say:
" A Rule MAY have none, one or many failure sub-property values of type Rule"

So, it would be reasonably expected that you could define your own failure sub-property.

@riannella
Copy link
Contributor

Summary: The first para of Section 3.3 should be more clearer as "To create an ODRL Profile, the ODRL Core Vocabulary classes can be extended by sub-classes with optional additional properties, the Core Vocabulary properties can be extended by sub-properties, further instances of classes and properties defined by the Core Vocabulary or this Profile can be defined. The table below shows some typical extensions, a new Profile is not limited to them:"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants