Agreements, like Creative Commons' Licenses, require Requirements (subclass of skos:Concept) which ask actions of an Agent. Unlike CC Requirements which "may or may not be requested of you", the level of the Requirement (the extent to which it is imparative) is qualified by the value of a RequirementLevel (also subclass of skos:Concept) class instance that is related to the Requirement. The RequirementLevel instances given in this AGR-O match the keywords given in RFC2119.
Every Agreement must have at least one Requirement and every requirement can have one and only one RequirementLevel.
All of these relationships and restrictions are indicated in Figure A.
In order to indicate that a Requirement has been satisfied, an Agent must perform a RequirementResolution action. A RequirementResolution is subclass of both skos:Concept and of prov:Activity therefore it is a thing to be done, by some Agent. In order to know which Requirement a RequirementResolution applies to, the RequirementResolution must have an agr:satisfies predicate indicating a particular Requirement class instance, the inverse of which is agr:satisfiedBy. Different Requirements many be satisfied by different RequirementResolutions (i.e. different Agents may undertake different actions to satisfy a particular Requirement). This is indcated in Figure B.
Figure C in Indicating Agreement / data relationships shows a Requirement to Publish Data being satisfied by a Data Publication Event Activity.
| Prefix | URI |
|---|---|
| agr | http://promsns.org/def/agr# |
| skos | http://www.w3.org/2004/02/skos/core# |
| prov | http://www.w3.org/ns/prov# |