Difference between revisions of "ISO5087-1:Agent"
| Line 1: | Line 1: | ||
{{Class Definition | {{Class Definition | ||
| − | |Description=An Agent may | + | |Description=An Agent is a generic concept that may represent a person, software system, organization, or any other object that may be responsible for the occurrence of an 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 40: | Line 40: | ||
|Figure=Agree1.png, | |Figure=Agree1.png, | ||
|Caption=Figure 1: Example use of the Agreement Ontology. | |Caption=Figure 1: Example use of the Agreement Ontology. | ||
| + | }}{{Figure Row | ||
| + | |Figure=Prov1.png, | ||
| + | |Caption=Figure 2: The Provenance Ontology main classes and properties | ||
}} | }} | ||
}} | }} | ||
Revision as of 21:37, 3 July 2021
Pattern
This class has been associated with the following pattern:
Pattern:Agent Pattern, Pattern:Provenance Pattern
Subclass Of
Description
An English description of the definition (what distinguishes this sense of the term?).
An Agent is a generic concept that may represent a person, software system, organization, or any other object that may be responsible for the occurrence of an 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?)
Finding, Reserving, and Paying for Parking
CDM References
What other classes or properties reference this term?
- Organization (← links)
- Post (← links)
- ISO5087-1:Activity (← links)
- Entity (← links)
- Finding, Reserving, and Paying for Parking (← links)
- PersonID (← links)
- Agent (redirect page) (← links)
- 5087-1:Agent (redirect page) (← links)
- Iso5087-1:Agent (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 |
|---|---|---|
| HasName | exactly 1 | xsd:string |
| ResourceOf | only | resource:TerminalResourceState |
| Perform | only | activity:Activity |
| HasClaim | only | AtomicAgreement |
| HasNoClaim | only | AtomicAgreement |
| HasDuty | only | AtomicAgreement |
| HasPrivilege | only | AtomicAgreement |
Supplementary Figures
| Figure | Caption |
|---|---|
| Figure 1: Example use of the Agreement Ontology. | |
| Figure 2: The Provenance Ontology main classes and properties |
