Rule
'The Rule class is the parent of the Permission, Prohibition, and Duty classes. The Rule class represents the common characteristics of these three classes. A Rule class MUST be disjoint with all other Rule subclasses. The Rule class has the following properties: A Rule MUST have one action property value of type Action. A Rule MAY have none or one relation sub-property values of type Asset. A Rule MAY have none, one or many function sub-property values of type Party. A Rule MAY have none, one or many failure sub-property values of type Rule. A Rule MAY have none, one or many constraint property values of type Constraint/LogicalConstraint. A Rule MAY have none or one uid property values (of type IRI [rfc3987]) to identify the Rule so it MAY be referenced by other Rules. Note: The above property cardinalities reflect the normative ODRL Information Model. In some cases, repeat occurrences of some properties are also supported (as described in Policy Rule Composition and Compact Policy) but the normative atomic Policy is consistent with the above property cardinalities. Explicit sub-properties of the abstract relation, relation and failure properties must be used, the choice depending on the subclass of Rule in question.'
Type |
Class |
|---|---|
URI |
Slots
| Name | Type | Description | Inherited from |
|---|---|---|---|
1..* |
The action to be performed |
n/a |
|
0..* |
To express the recipient Party of the Rule. In this context it is recommended to specify the role of the party responsible... |
n/a |
|
0..* |
Description of the rule |
n/a |
|
0..* |
Unique identifier for the duty or rule |
n/a |
assignee
To express the recipient Party of the Rule. In this context it is recommended to specify the role of the party responsible (see also https://docs.internationaldataspaces.org/ids-knowledgebase/idsa-rulebook/idsa-rulebook/2.-guiding-principles/2.5-role_models#core-roles)
URI |
|
|---|---|
Cardinality |
0..* |
Type |