- From: Michael Steidl via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Jun 2017 06:39:54 +0000
- To: public-poe-archives@w3.org
@iherman and @simonstey I see the points of your considerations but take the view of an ODRL newbie - the guys we have to convince ODRL is an easy-to-use standard: The restriction code at the top of this thread was not written down by me but by Protege (5.2.) and Protege also shows this restriction clearly in the User Interface. So if a guy investigating the ODRL ontology would see cardinality restrictions s/he could create policies accordingly. If the cardinality check is only done with SHACL such a guy has to be/get familiar with SHACL too, only then s/he would be able to read the cardinality constraints. My conclusion: ODRL should provide both, OWL constraints to reflect a complete Information Model to a user and SHACL rules to check existing policies properly. -- GitHub Notification of comment by nitmws Please view or discuss this issue at https://github.com/w3c/poe/issues/198#issuecomment-309659205 using your GitHub account
Received on Tuesday, 20 June 2017 06:40:00 UTC