Renato Iannella
Renato Iannella
Summary: Typo fixed in JSON-LD Schema: "neg" to "neq"
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...
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...
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...
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...
@vroddon @simonstey @nitmws Do you have any views on this?
Sorry for such a late response... Is it an "error" that we use transitiveBroader/Narrow for a few properties? Semantically it makes sense right? It is not that useful as there...
@iherman to update "skos:broaderTransitive" to "skos:broader" in https://www.w3.org/ns/odrl/2/ODRL22.ttl (then export to .rdf and .nt and .json using Protege)
Summary: "skos:broaderTransitive" updated to "skos:broader" in the Turtle file
These seem to be added: ``` 66141010000114 20231015 1 11010000107 30051010000102 en 900000000000013009 LOINC code ID 900000000000017005 66151010000111 20231015 1 11010000107 30051010000102 en 900000000000013009 LOINC code identifier 900000000000017005 66161010000113 20231015...