Having a look at the IM Editor Draft of 11 October, Constraint section:
For the Logical Constraint the values of the operand are defined as "its value is a list of the existing Constraint instances."
Example 15 shows this example of an "existing Constraint instance" as:
{
...
"xone": [ { "@id": "http://example.com/p:88/C1" },
{ "@id": "http://example.com/p:88/C2" } ]
...}
{
"@context": "http://www.w3.org/ns/odrl.jsonld",
"@type": "Constraint",
"uid": "http://example.com/p:88/C1",
"leftOperand": "media",
"operator": "eq",
"rightOperand": "online"
}
By the IM definitions this Constraint instance is invalid as the 2.5.1 Constraint Class does NOT define a uid property. On the other hand a Logical Constraint operand needs identifiers to refer to Constraints.
Conclusion: currently Constraint and Logical Constraint instances can only have an auto-generated blank node id, it is not possible to set an identifier explicitly.
Suggestion: the Constraint class and also the Logical Constraint Class must have a uid property.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3