@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix voaf: <http://purl.org/vocommons/voaf#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix foaf: <http://xmlns.com/foaf/0.1/> . @prefix dct: <http://purl.org/dc/terms/> . @prefix vann: <http://purl.org/vocab/vann/> . @prefix ns0: <https://w3id.org/pep/> . @prefix cc: <http://creativecommons.org/ns#> . @prefix ns1: <https://www.apache.org/licenses/> . @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . <https://w3id.org/pep/> cc:license <https://www.apache.org/licenses/LICENSE-2.0> ; dct:creator <http://www.maxime-lefrancois.info/me#> ; dct: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. SSN describe `ssn:Sensor`s that implement `ssn:Sensing` methods and generate `ssn:Observation`s, which are (soon to be) activities. In parallel to this, SAN describes `san:Actuator`s that implement `san:Acting` methods and generate `ssn:Actuation` activities. In 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*. We hence propose the following core concepts for the Process Execution ontology: > `pep:ProcessExecutor`s implement `pep:Process` methods, and generate `pep:ProcessExecution`s activities. _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)_ As 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. Figure below overviews the PEP ontology, and illustrates it with an example. [](https://w3id.org/pep/pep.png). Additional documents describe alignments with other existing ontologies: - [the Semantic Sensor Network ontology](https://w3id.org/pep/SSNAlignment); - [the RDF Presentation ontology](https://w3id.org/pep/RDFPAlignment). ## Process Execution Platform [Process execution platforms](https://w3id.org/pep/platform.html) expose process executors on the Web in a RESTful way. """@en ; dct:issued "2016-07-01"^^<http://www.w3.org/2001/XMLSchema#date> ; dct:modified "2016-09-12"^^<http://www.w3.org/2001/XMLSchema#date> ; dct:title "Process Execution ontology."@en ; vann:preferredNamespacePrefix "pep" ; vann:preferredNamespaceUri <https://w3id.org/pep/> ; a voaf:Vocabulary, owl:NamedIndividual, owl:Ontology, foaf:Document ; owl:versionIRI <https://w3id.org/pep/pep-1.0> ; owl:versionInfo "v1.0" . ns0:Process rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:ProcessExecution rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:ProcessExecutionContainer rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:ProcessExecutor rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:executed rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:executedBy rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:executor rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:forProcess rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:hasInput rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:hasOutput rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:implements rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:methodUsed rdfs:isDefinedBy <https://w3id.org/pep/> . ns0:processExecutionContainer rdfs:isDefinedBy <https://w3id.org/pep/> .