Difference between revisions of "ISO5087-1:Agent"

From City Data Model Project Collaboratory
Jump to navigation Jump to search
m (Megankatsumi moved page Iso5087-1:Agent to ISO5087-1:Agent: Text replacement - "Iso5087-1:Agent" to "ISO5087-1:Agent")
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
{{Class Definition
 
{{Class Definition
−
|Description=An Agent may be a Person or Organization.  (We do not include Software or Mechanical Device at this time).
+
|Subclass Of=Prov:Agent
 +
|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.
 +
 
 +
Agent: An Agent may be a Person or Organization.  (We do not include Software or Mechanical Device at this time). An Agent has the following core properties:
 +
* hasName: an identifier for the agent
 +
* resourceOf: identifies what State the agent may be a resource of
 +
* perform: identifies activities that the agent performs
 
|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 17: Line 23:
 
|Property=Perform
 
|Property=Perform
 
|Restriction=only
 
|Restriction=only
−
|Value=activity:Activity
+
|Value=ISO5087-1:Activity
 +
}}{{Manchester Row
 +
|Property=HasClaim
 +
|Restriction=only
 +
|Value=5087-1:ISO5087-1:AtomicAgreement
 +
}}{{Manchester Row
 +
|Property=HasNoClaim
 +
|Restriction=only
 +
|Value=5087-1:ISO5087-1:AtomicAgreement
 +
}}{{Manchester Row
 +
|Property=HasDuty
 +
|Restriction=only
 +
|Value=5087-1:ISO5087-1:AtomicAgreement
 +
}}{{Manchester Row
 +
|Property=HasPrivilege
 +
|Restriction=only
 +
|Value=5087-1:ISO5087-1:AtomicAgreement
 
}}
 
}}
 
}}
 
}}
 
{{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.
 +
}}{{Figure Row
 +
|Figure=Prov1.png
 +
|Caption=Figure 2: The Provenance Ontology main classes and properties
 
}}
 
}}
 
}}
 
}}

Latest revision as of 05:34, 16 December 2022


Pattern

This class has been associated with the following pattern:

Pattern:Agent Pattern, Pattern:Provenance Pattern

Subclass Of

Prov:Agent

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.

Agent: An Agent may be a Person or Organization. (We do not include Software or Mechanical Device at this time). An Agent has the following core properties:

  • hasName: an identifier for the agent
  • resourceOf: identifies what State the agent may be a resource of
  • perform: identifies activities that the agent performs

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?

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 ISO5087-1:Activity
HasClaim only 5087-1:ISO5087-1:AtomicAgreement
HasNoClaim only 5087-1:ISO5087-1:AtomicAgreement
HasDuty only 5087-1:ISO5087-1:AtomicAgreement
HasPrivilege only 5087-1:ISO5087-1:AtomicAgreement


Supplementary Figures

Figure Caption
Agree1.png
Figure 1: Example use of the Agreement Ontology.
Prov1.png
Figure 2: The Provenance Ontology main classes and properties
Retrieved from "http://citydatastandard.org/index.php?title=ISO5087-1:Agent&oldid=31734"