Difference between revisions of "ISO5087-1:ComplexAgreement"
Megankatsumi (talk | contribs) m (Megankatsumi moved page ComplexAgreement to ISO5087-1:ComplexAgreement: Text replacement - "ComplexAgreement" to "ISO5087-1:ComplexAgreement") |
|||
(7 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Class Definition | {{Class Definition | ||
− | |Subclass Of=Agreement | + | |Subclass Of=ISO5087-1:Agreement |
− | |Description=A complex agreement may be decomposed into disjunctive or conjunctive sub-agreements. This allows for the representation of both types of agreement composition. | + | |Description=A complex agreement may be decomposed into disjunctive or conjunctive sub-agreements. This allows for the representation of both types of agreement composition. |
+ | ComplexAgreement is a subclass of Agreement and has one additional property: | ||
+ | * hasSubAgreement: identifies two or more agreements that comprise the agreement. | ||
|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 10: | Line 12: | ||
|Property=HasSubAgreement | |Property=HasSubAgreement | ||
|Restriction=min 2 | |Restriction=min 2 | ||
− | |Value=Agreement | + | |Value=ISO5087-1:Agreement |
}} | }} | ||
}} | }} | ||
{{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 11:43, 19 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?).
A complex agreement may be decomposed into disjunctive or conjunctive sub-agreements. This allows for the representation of both types of agreement composition. ComplexAgreement is a subclass of Agreement and has one additional property:
- hasSubAgreement: identifies two or more agreements that comprise the agreement.
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?
- ComplexAgreement (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 |
---|---|---|
HasSubAgreement | min 2 | ISO5087-1:Agreement |
Supplementary Figures
Figure | Caption |
---|---|
Figure 1: Example use of the Agreement Ontology. |