<https://w3id.org/pep/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://purl.org/vocommons/voaf#Vocabulary> . <https://w3id.org/pep/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#NamedIndividual> . <https://w3id.org/pep/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#Ontology> . <https://w3id.org/pep/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://xmlns.com/foaf/0.1/Document> . <https://w3id.org/pep/> <http://purl.org/dc/terms/creator> <http://www.maxime-lefrancois.info/me#> . <https://w3id.org/pep/> <http://purl.org/vocab/vann/preferredNamespacePrefix> "pep" . <https://w3id.org/pep/> <http://purl.org/vocab/vann/preferredNamespaceUri> <https://w3id.org/pep/> . <https://w3id.org/pep/> <http://www.w3.org/2002/07/owl#versionIRI> <https://w3id.org/pep/pep-1.0> . <https://w3id.org/pep/> <http://purl.org/dc/terms/modified> "2016-09-12"^^<http://www.w3.org/2001/XMLSchema#date> . <https://w3id.org/pep/> <http://www.w3.org/2002/07/owl#versionInfo> "v1.0" . <https://w3id.org/pep/> <http://creativecommons.org/ns#license> <https://www.apache.org/licenses/LICENSE-2.0> . <https://w3id.org/pep/> <http://purl.org/dc/terms/description> "The process execution ontology is a proposal for a simple extension of both the [W3C Semantic Sensor Network](https://www.w3.org/TR/vocab-ssn/) and the [Semantic Actuator Network](https://www.irit.fr/recherches/MELODI/ontologies/SAN.owl) ontology cores. \n\nSSN describe `ssn:Sensor`s that implement `ssn:Sensing` methods and generate `ssn:Observation`s, which are (soon to be) activities.\n\nIn parallel to this, SAN describes `san:Actuator`s that implement `san:Acting` methods and generate `ssn:Actuation` activities.\n\nIn this ontology, we want to generalize these two parallel conceptual models, and account for a third use case: *Web services exposed on the web may trigger the execution of some processes*. \n\nWe hence propose the following core concepts for the Process Execution ontology:\n\n> `pep:ProcessExecutor`s implement `pep:Process` methods, and generate `pep:ProcessExecution`s activities.\n\n_Note: we call for comments and suggestions about the naming of these concepts [in this project open issue](https://github.com/thesmartenergy/pep/issues/1)_\n\nAs sensing and acting methods in SSN and SAN, processes may describe the necessary inputs and outputs. This is represented using properties `pep:hasInput` and `pep:hasOutput`. These properties may also be used to describe the actual input and output of a specific process execution.\n\nFigure below overviews the PEP ontology, and illustrates it with an example.\n\n[![Overview of the PEP Ontology](https://w3id.org/pep/pep.png)](https://w3id.org/pep/pep.png).\n\nAdditional documents describe alignments with other existing ontologies:\n\n- [the Semantic Sensor Network ontology](https://w3id.org/pep/SSNAlignment);\n- [the RDF Presentation ontology](https://w3id.org/pep/RDFPAlignment).\n\n## Process Execution Platform\n\n[Process execution platforms](https://w3id.org/pep/platform.html) expose process executors on the Web in a RESTful way.\n\n"@en . <https://w3id.org/pep/> <http://purl.org/dc/terms/issued> "2016-07-01"^^<http://www.w3.org/2001/XMLSchema#date> . <https://w3id.org/pep/> <http://purl.org/dc/terms/title> "Process Execution ontology."@en . <https://w3id.org/pep/> <http://purl.org/vocab/vann/preferredNamespaceUri> <https://w3id.org/pep/> . <https://w3id.org/pep/hasInput> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/hasOutput> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/Process> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/ProcessExecution> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/ProcessExecutionContainer> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/ProcessExecutor> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/executed> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/executedBy> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/executor> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/forProcess> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/implements> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/methodUsed> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> . <https://w3id.org/pep/processExecutionContainer> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .

<https://w3id.org/pep/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://purl.org/vocommons/voaf#Vocabulary> .
<https://w3id.org/pep/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#NamedIndividual> .
<https://w3id.org/pep/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#Ontology> .
<https://w3id.org/pep/> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://xmlns.com/foaf/0.1/Document> .
<https://w3id.org/pep/> <http://purl.org/dc/terms/creator> <http://www.maxime-lefrancois.info/me#> .
<https://w3id.org/pep/> <http://purl.org/vocab/vann/preferredNamespacePrefix> "pep" .
<https://w3id.org/pep/> <http://purl.org/vocab/vann/preferredNamespaceUri> <https://w3id.org/pep/> .
<https://w3id.org/pep/> <http://www.w3.org/2002/07/owl#versionIRI> <https://w3id.org/pep/pep-1.0> .
<https://w3id.org/pep/> <http://purl.org/dc/terms/modified> "2016-09-12"^^<http://www.w3.org/2001/XMLSchema#date> .
<https://w3id.org/pep/> <http://www.w3.org/2002/07/owl#versionInfo> "v1.0" .
<https://w3id.org/pep/> <http://creativecommons.org/ns#license> <https://www.apache.org/licenses/LICENSE-2.0> .
<https://w3id.org/pep/> <http://purl.org/dc/terms/description> "The process execution ontology is a proposal for a simple extension of both the [W3C Semantic Sensor Network](https://www.w3.org/TR/vocab-ssn/) and the [Semantic Actuator Network](https://www.irit.fr/recherches/MELODI/ontologies/SAN.owl) ontology cores. \n\nSSN describe `ssn:Sensor`s that implement `ssn:Sensing` methods and generate `ssn:Observation`s, which are (soon to be) activities.\n\nIn parallel to this, SAN describes `san:Actuator`s that implement `san:Acting` methods and generate `ssn:Actuation` activities.\n\nIn this ontology, we want to generalize these two parallel conceptual models, and account for a third use case: *Web services exposed on the web may trigger the execution of some processes*. \n\nWe hence propose the following core concepts for the Process Execution ontology:\n\n> `pep:ProcessExecutor`s implement `pep:Process` methods, and generate `pep:ProcessExecution`s activities.\n\n_Note: we call for comments and suggestions about the naming of these concepts [in this project open issue](https://github.com/thesmartenergy/pep/issues/1)_\n\nAs sensing and acting methods in SSN and SAN, processes may describe the necessary inputs and outputs. This is represented using properties `pep:hasInput` and `pep:hasOutput`. These properties may also be used to describe the actual input and output of a specific process execution.\n\nFigure below overviews the PEP ontology, and illustrates it with an example.\n\n[![Overview of the PEP Ontology](https://w3id.org/pep/pep.png)](https://w3id.org/pep/pep.png).\n\nAdditional documents describe alignments with other existing ontologies:\n\n- [the Semantic Sensor Network ontology](https://w3id.org/pep/SSNAlignment);\n- [the RDF Presentation ontology](https://w3id.org/pep/RDFPAlignment).\n\n## Process Execution Platform\n\n[Process execution platforms](https://w3id.org/pep/platform.html) expose process executors on the Web in a RESTful way.\n\n"@en .
<https://w3id.org/pep/> <http://purl.org/dc/terms/issued> "2016-07-01"^^<http://www.w3.org/2001/XMLSchema#date> .
<https://w3id.org/pep/> <http://purl.org/dc/terms/title> "Process Execution ontology."@en .
<https://w3id.org/pep/> <http://purl.org/vocab/vann/preferredNamespaceUri> <https://w3id.org/pep/> .
<https://w3id.org/pep/hasInput> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/hasOutput> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/Process> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/ProcessExecution> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/ProcessExecutionContainer> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/ProcessExecutor> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/executed> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/executedBy> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/executor> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/forProcess> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/implements> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/methodUsed> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .
<https://w3id.org/pep/processExecutionContainer> <http://www.w3.org/2000/01/rdf-schema#isDefinedBy> <https://w3id.org/pep/> .