Difference between revisions of "ISO5087-1:AtomicAgreement"

From City Data Model Project Collaboratory
Jump to navigation Jump to search
m (Megankatsumi moved page Iso5087-1:AtomicAgreement to ISO5087-1:AtomicAgreement: Text replacement - "Iso5087-1:AtomicAgreement" to "ISO5087-1:AtomicAgreement")
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Class Definition
 
{{Class Definition
|Subclass Of=Agreement
+
|Subclass Of=ISO5087-1:Agreement
 
|Description=AtomicAgreement is a subclass of Agreement and specifies the “essence” of an agreement.  In particular it identifies how agents participating in the agreement are involved:
 
|Description=AtomicAgreement is a subclass of Agreement and specifies the “essence” of an agreement.  In particular it identifies how agents participating in the agreement are involved:
forActivity: identifies the activity that the atomic agreement is for.
+
* forActivity: identifies the activity that the atomic agreement is for.
inverse hasClaim: links the agreement to any agent that has a claim.
+
* inverse hasClaim: links the agreement to any agent that has a claim.
inverse hasNoClaim: links the agreement to any agent that does not have a claim.
+
* inverse hasNoClaim: links the agreement to any agent that does not have a claim.
inverse hasDuty: links the agreement to any agent that has a duty to perform the activity.
+
* inverse hasDuty: links the agreement to any agent that has a duty to perform the activity.
inverse hasPrivilege: links the agreement to any agent that has the privilege to perform the activity.
+
* inverse hasPrivilege: links the agreement to any agent that has the privilege to perform the activity.
 
|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 15: Line 15:
 
|Property=HasSubAgreement
 
|Property=HasSubAgreement
 
|Restriction=exactly 0
 
|Restriction=exactly 0
|Value=Agreement
+
|Value=ISO5087-1:Agreement
 
}}{{Manchester Row
 
}}{{Manchester Row
 
|Property=ForActivity
 
|Property=ForActivity
 
|Restriction=some
 
|Restriction=some
|Value=Activity
+
|Value=ISO5087-1:Activity
 
}}{{Manchester Row
 
}}{{Manchester Row
 
|Property=disjointWith
 
|Property=disjointWith
 
|Value=ComplexAgreement
 
|Value=ComplexAgreement
 +
}}{{Manchester Row
 +
|Property=inverse hasDuty
 +
|Restriction=only
 +
|Value=iso5087-1:Agent
 +
}}{{Manchester Row
 +
|Property=inverse hasPrivilege
 +
|Restriction=only
 +
|Value=iso5087-1:Agent
 +
}}{{Manchester Row
 +
|Property=inverse hasClaim
 +
|Restriction=only
 +
|Value=iso5087-1:Agent
 +
}}{{Manchester Row
 +
|Property=inverse hasNoClaim
 +
|Restriction=only
 +
|Value=iso5087-1:Agent
 
}}
 
}}
 
}}
 
}}

Latest revision as of 05:11, 16 December 2022


Pattern

This class has been associated with the following pattern:

Pattern:Agreement Pattern

Subclass Of

ISO5087-1:Agreement

Description

An English description of the definition (what distinguishes this sense of the term?).

AtomicAgreement is a subclass of Agreement and specifies the “essence” of an agreement. In particular it identifies how agents participating in the agreement are involved:

  • forActivity: identifies the activity that the atomic agreement is for.
  • inverse hasClaim: links the agreement to any agent that has a claim.
  • inverse hasNoClaim: links the agreement to any agent that does not have a claim.
  • inverse hasDuty: links the agreement to any agent that has a duty to perform the activity.
  • inverse hasPrivilege: links the agreement to any agent that has the privilege to perform the activity.

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?

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 exactly 0 ISO5087-1:Agreement
ForActivity some ISO5087-1:Activity
disjointWith ComplexAgreement
inverse hasDuty only iso5087-1:Agent
inverse hasPrivilege only iso5087-1:Agent
inverse hasClaim only iso5087-1:Agent
inverse hasNoClaim only iso5087-1:Agent


Supplementary Figures

Figure Caption
Agree1.png
Figure 1: Example use of the Agreement Ontology.