Submissions:EEP

From Odp

Revision as of 16:32, 9 July 2018 by IKERESNAOLA-GONZALEZ (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 13498

Graphical representation

General description

Name: EEP
Submitted by: IKERESNAOLA-GONZALEZ
Also Known As:
Intent: To represent executions made by executors that implement procedures. Executions are events like observations or actuations. Executors are systems like sensors or actuators that produce executions. Executors implement procedures to carry out their goals. Executions and executors are taken over features of interest and their intrinsic properties/qualities.
Domains:

Building and Construction, General

Competency Questions:
  • CQ1: What are the observations/actuations performed by a given procedure?
  • CQ2: What are the observations/actuations performed by a given sensor/actuator?
  • CQ3: What are the procedures implemented by a given sensor/actuator?
  • CQ4: What are the features of interest on a given observation/actuation?
  • CQ5: What are the properties/qualities sensed/actuated by a given
  • observations/actuations?
  • CQ6: What are the features of interest of a given sensor/actuator?
  • CQ7: What are the properties/qualities sensed/actuated by a given executor?
Solution description: The Execution-Executor-Procedure (EEP) ODP imports the AffectedBy ODP (https://w3id.org/affectedBy), that involves classes for Features of Interest and their intrinsic Properties/Qualities.

The EEP ODP is an adaptation of the Procedure Execution Ontology (PEP) (https://w3id.org/pep/pep-1.1) from the SEAS ontology which, in turn, is a generalization of the Observation-Sensor-Procedure and Actuation-Actuator-Procedure patterns used in the SOSA (http://www.w3.org/ns/sosa/) and SSN (http://www.w3.org/ns/ssn/) ontologies. From the AffectedBy ODP, the EEP ODP imports the notion that a property/quality is intrinsic to the feature of interest that it belongs to (i.e., according to the definition of the class Quality in the DUL ontology http://www.ontologydesignpatterns.org/ont/dul/DUL.owl). Apart from the two classes imported from the AffectedBy ODP (aff:FeatureOfIntetest and aff:Quality), the EEP ODP consists of three more classes: Execution, Executor, and Procedure. The class Execution and their three functional object properties eep:madeBy, eep:usedProcedure, and eep:onQuality, form the backbone of the ODP. The property eep:madeBy links an execution to its executor, the property eep:usedProcedure links an execution to its procedure, and the property eep:onQuality links an execution to the quality/property concerned by the execution. Therefore, an execution jointly with their three object values of the three aforementioned properties can be considered as a n-ary relationship. Note that every quality belongs to unique feature of interest. Therefore, a feature of interest is involved in the n-ary relationship. The remaining object properties: eep:implements, that links executors to procedures, eep:hasFeatureOfInteres, that links executions to features of interest, eep:forQuality, that links executors to qualities, and eep:forFeatureOfInterest, that links executors to features of interest, are defined in terms of the functional object properties using property chain axioms.

Reusable OWL Building Block: https://w3id.org/eep (0)
Consequences: Axioms included in the EEP ODP provide inferences that allow to answer the competency questions properly. Therefore, solving some weaknesses of the sosa/ssn ontologies.

Note that only triples about the four functional object properties: eep:madeBy, eep:usedProcedure, eep:onQuality, and aff:belongsTo, needs to be asserted, the remaining triples are inferred by the property axioms.

Scenarios:
Known Uses: https://w3id.org/eepsa
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:


Elements

The EEP Content OP locally defines the following ontology elements:

Additional information

Scenarios

Scenarios about EEP

No scenario is added to this Content OP.

Reviews

Reviews about EEP

There is no review about this proposal. This revision (revision ID 13498) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about EEP

There is no Modeling issue related to this proposal.


References

Add a reference


Personal tools
Quality Committee
Content OP publishers