{"@context":{"rdf":"http://www.w3.org/1999/02/22-rdf-syntax-ns#","voaf":"http://purl.org/vocommons/voaf#","owl":"http://www.w3.org/2002/07/owl#","foaf":"http://xmlns.com/foaf/0.1/","dct":"http://purl.org/dc/terms/","vann":"http://purl.org/vocab/vann/","ns0":"https://w3id.org/pep/","cc":"http://creativecommons.org/ns#","ns1":"https://www.apache.org/licenses/","rdfs":"http://www.w3.org/2000/01/rdf-schema#"},"@graph":[{"@id":"https://w3id.org/pep/","@type":["voaf:Vocabulary","owl:NamedIndividual","owl:Ontology","foaf:Document"],"dct:creator":{"@id":"http://www.maxime-lefrancois.info/me#"},"vann:preferredNamespacePrefix":"pep","vann:preferredNamespaceUri":{"@id":"https://w3id.org/pep/"},"owl:versionIRI":{"@id":"ns0:pep-1.0"},"dct:modified":{"@type":"http://www.w3.org/2001/XMLSchema#date","@value":"2016-09-12"},"owl:versionInfo":"v1.0","cc:license":{"@id":"ns1:LICENSE-2.0"},"dct:description":{"@language":"en","@value":"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[](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"},"dct:issued":{"@type":"http://www.w3.org/2001/XMLSchema#date","@value":"2016-07-01"},"dct:title":{"@language":"en","@value":"Process Execution ontology."}},{"@id":"ns0:hasInput","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:hasOutput","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:Process","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:ProcessExecution","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:ProcessExecutionContainer","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:ProcessExecutor","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:executed","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:executedBy","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:executor","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:forProcess","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:implements","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:methodUsed","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}},{"@id":"ns0:processExecutionContainer","rdfs:isDefinedBy":{"@id":"https://w3id.org/pep/"}}]}