Difference between revisions of "ISO5087-1:Agreement"
Megankatsumi (talk | contribs) m (Megankatsumi moved page Iso5087-1:Agreement to ISO5087-1:Agreement: Text replacement - "Iso5087-1:Agreement" to "ISO5087-1:Agreement") |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Class Definition | {{Class Definition | ||
|Description=An agreement exists between 2 or more agents. It is established at some point in time and it may be considered valid only in some Location and/or for some interval in time. An agreement may be defined at varying levels of detail, this is supported with the introduction of the ComplexAgreement and AtomicAgreement class. | |Description=An agreement exists between 2 or more agents. It is established at some point in time and it may be considered valid only in some Location and/or for some interval in time. An agreement may be defined at varying levels of detail, this is supported with the introduction of the ComplexAgreement and AtomicAgreement class. | ||
| + | |||
| + | The class Agreement has the following properties: | ||
| + | * involvesAgent: identifies the agents that are party to the agreement. | ||
| + | * validIn: identifies the location where the agreement is valid. | ||
| + | * establishedOn: specifies the instant of time that agreement was created. | ||
| + | * validFor: specifies the time interval during which the agreement is in force. | ||
|Class Diagram Description=Figure 1 illustrates the use of the Agreement Ontology to represent agreements at different levels of detail. The example shown captures a complex, disjunctive agreement that can be decomposed into two simple agreements. One option (“agr0012”) describes “alice”’s right to have lawn maintenance be performed by “bob”, (also read “bob”’s duty to perform lawn maintenance for “alice”). | |Class Diagram Description=Figure 1 illustrates the use of the Agreement Ontology to represent agreements at different levels of detail. The example shown captures a complex, disjunctive agreement that can be decomposed into two simple agreements. One option (“agr0012”) describes “alice”’s right to have lawn maintenance be performed by “bob”, (also read “bob”’s duty to perform lawn maintenance for “alice”). | ||
|Definition Status=Pending Approval | |Definition Status=Pending Approval | ||
| Line 9: | Line 15: | ||
|Property=InvolvesAgent | |Property=InvolvesAgent | ||
|Restriction=min 2 | |Restriction=min 2 | ||
| − | |Value=Agent | + | |Value=5087-1:Agent |
}}{{Manchester Row | }}{{Manchester Row | ||
|Property=ValidIn | |Property=ValidIn | ||
| Line 26: | Line 32: | ||
{{Supplementary Figures | {{Supplementary Figures | ||
|Figure Row={{Figure Row | |Figure Row={{Figure Row | ||
| − | |Figure=Agree1.png | + | |Figure=Agree1.png |
|Caption=Figure 1: Example use of the Agreement Ontology. | |Caption=Figure 1: Example use of the Agreement Ontology. | ||
}} | }} | ||
}} | }} | ||
Latest revision as of 04:06, 16 December 2022
Pattern
This class has been associated with the following pattern:
Subclass Of
Description
An English description of the definition (what distinguishes this sense of the term?).
An agreement exists between 2 or more agents. It is established at some point in time and it may be considered valid only in some Location and/or for some interval in time. An agreement may be defined at varying levels of detail, this is supported with the introduction of the ComplexAgreement and AtomicAgreement class.
The class Agreement has the following properties:
- involvesAgent: identifies the agents that are party to the agreement.
- validIn: identifies the location where the agreement is valid.
- establishedOn: specifies the instant of time that agreement was created.
- validFor: specifies the time interval during which the agreement is in force.
Class Diagram Description
Figure 1 illustrates the use of the Agreement Ontology to represent agreements at different levels of detail. The example shown captures a complex, disjunctive agreement that can be decomposed into two simple agreements. One option (“agr0012”) describes “alice”’s right to have lawn maintenance be performed by “bob”, (also read “bob”’s duty to perform lawn maintenance for “alice”).
Required by Use Case(s)
(why is this specialized definition needed?)
CDM References
What other classes or properties reference this term?
- ISO5087-1:ComplexAgreement (← links)
- ISO5087-1:AtomicAgreement (← links)
- Contract (← links)
- ISO5087-2:ContractualCommitment (← links)
- Agreement (redirect page) (← links)
- 5087-1:Agreement (redirect page) (← links)
- Iso5087-1:Agreement (redirect page) (← links)
Interface Specification References
This class has been associated with the following interface specification items:
Sources
Sources considered when developing the class:
Status
Pending Approval
Has Subclass(es)
Annotations
| Annotation | Value |
|---|
Manchester Syntax Specification
| Property | Restriction | Value |
|---|---|---|
| InvolvesAgent | min 2 | 5087-1:Agent |
| ValidIn | only | Feature |
| EstablishedOn | only | Time:Instant |
| ValidFor | only | Time:Interval |
Supplementary Figures
| Figure | Caption |
|---|---|
| Figure 1: Example use of the Agreement Ontology. |
