RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.w3.org/2012/09/odrl/archive/odrl.net/2.0/issues/issueslist-1_9.html below:

ODRL Requirement 1.9 Issues List

This is the list of issues the ODRL Initiative has considered, when addressing the respective requirement (see above).

issue01 -Shall ODRLv2 allow for a context element to further specify the constraint?

Pro:

OMA uses the context element in their ODRL profile.
Version 1.1 suggests to use uid of context element to further specify user constraints, device constraints, watermark constraint.
Allows to further specify the constraint - also for the human reader

Contra:

Allowing extra information in the context element makes is harder to exactly identify the constraint that has to be evaluated. Constraint might get ambiguous.

Solution Approaches:

As mostly only the UID is required of the context element, a special operator "equals" could be used. For example:
```
<constraint>  
 <individual>
 <equals>sguth </equals>
 </individual>
</constraint>
```

issue02 - Shall ODRLv2 allow for nested constraints?

Pro:

Two constraints can be nested together, i.e. cond. A and cond B have to be met.

Contra:

Nesting gets ambiguous with three constraints.

Solution Approaches:

No, do not allow for neste constraint. Group constraints that belong together (connected by "and", "or", "xor") on the same level. Relate the constraints directly to the respective permission.

issue03 - How do we express "and", "or", "xor" constraints?

For example, the permission is granted if one/all/either one or the other constraint(s) is met.

Solution Approaches:

Creating various permissions with different constraints. Depending on the environmental conditions either the one or the other (or non) Permission will be granted.

issue04 - Do we need type for a meter in the "right operand"?

For example, to indicate a time zone for datetime.

issue05 - Do we need type for a meter in the "constraint"?

For example, to indicate the granularity of the spatial constraint (Country, City, Continent, etc.)

issue06 - Do we keep "count"? What does count exactly mean?

Does count always refer to the parent permission/or parent constraint? (See ODRL example #3 in version 1.1)

issue07 - How does the constraint - duty fulfilled look like? Solution Approaches:

<constraint>  
 <duty>
 <fulfilled>duty01</fulfilled>
 </duty>
</constraint>

issue08 - How does the OMA profile change with ODRLv2?

issue09 - Do we want to allow Unicode Mathematical Operators?

UNICODE-MATH-OPERATORS from u2200 - u22FF will be allowed additionally to common predefined operators, such as equals, less than, etc. With allowing the Unicode Mathematical Operators a large number of mathematical expressions can be formulated in ODRL, allowing for the expression of various constraints.

Examples:

         <constraint>  
          <individual> 
            <Uniode code="003d" label="equals">sguth</Unicode>
          </individual>
         </constraint>

.. means the same as ...

         <constraint>  
          <individual> 
            <equals>sguth</equals>
          </individual>
         </constraint>

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