62
results
  • IoT-O is a core domain Internet of Things ontology. It is intended to model horizontal knowledge about IoT systems and applications, and to be extended with vertical, application specific knowledge. It is constituted of different modules : - A sensing module, based on W3C's SSN (http://purl.oclc.org/NET/ssnx/ssn) - An acting module, based on SAN (http://www.irit.fr/recherches/MELODI/ontologies/SAN) - A service module, based on MSM (http://iserve.kmi.open.ac.uk/ns/msm/msm-2014-09-03.rdf) and hRest (http://www.wsmo.org/ns/hrests) - A lifecycle module, based on a lifecycle vocabulary (http://vocab.org/lifecycle/schema-20080603.rdf) and an iot-specific extension (http://www.irit.fr/recherches/MELODI/ontologies/IoT-Lifecycle) - An energy module, based on powerOnt (ttp://elite.polito.it/ontologies/poweront.owl) IoT-O developping team also contributes to the oneM2M IoT interoperability standard. @en
  • This ontology is intended to describe Semantic Actuator Networks, as a counterpoint to SSN definition of Semantic Sensor Networks. An actuator is a physical device having an effect on the world (see Actuator for more information). It is worth noticing that some concepts are imported from SSN, but not SSN as a whole. This is a design choice intended to separate as much as possible the definition on actuator from the definition of sensor, which are completely different concept that can be used independantly from each other. This ontology is used as a ontological module in IoT-O ontology. @en
  • The Ontology of units of Measure (OM) 2.0 models concepts and relations important to scientific research. It has a strong focus on units, quantities, measurements, and dimensions. @en
  • This ontology describes sensors, actuators and observations, and related concepts. It does not describe domain concepts, time, locations, etc. these are intended to be included from other ontologies via OWL imports. @en
  • Core module of the suite of ontologies for urban IoT devices. @en
  • Electric Mobility module of the suite of ontologies for urban IoT devices. @en
  • This ontology is based on the SSN Ontology by the W3C Semantic Sensor Networks Incubator Group (SSN-XG), together with considerations from the W3C/OGC Spatial Data on the Web Working Group. @en
  • CASO (Context Aware System Observation) is an ontology for context aware system and observation services. Its goal is to describe all the processing of the context. @en
  • Defines temporal / spatial concepts and general-purpose datastructures @en
  • This ontology models trust recommendation concepts in SIoT to bridge the gap between abstract trust concepts and real-world device concepts. @en
  • Defines concepts related to airport status, including weather, forecasts, and airport operations @en
  • The VAS ontological model enables the semantic integration of the heterogeneous observations used in ASOTVAS project ( https://robotica.uv.es/proyectos/ASOTVAS/ ), including ground measurements, UAV acquisitions and satellite products. Built as an extension of the W3C SOSA ontology (Janowicz et al., 2018), it incorporates a domain-specific vocabulary tailored to the needs of the Valencia Anchor Station as a CEOS LPV supersite. The model provides additional classes and properties to represent, in a homogeneous way, the different observational platforms: field sensors installed at VAS stations, UAVs equipped with multispectral cameras, and satellite missions such as Sentinel-2 and Sentinel-3. All observations follow a common SOSA pattern and share the same structure for results, units and timestamps. By aligning field, UAV and satellite observations under a unified semantic framework, the VAS ontology supports interoperable data access, consistent representation across scales, and integrated analysis of the multi-source measurements collected in ASOTVAS. @en
  • The Smart Appliances REFerence (SAREF) ontology is a shared model of consensus that facilitates the matching of existing assets (standards/protocols/datamodels/etc.) in the smart appliances domain. The SAREF ontology provides building blocks that allow separation and recombination of different parts of the ontology depending on specific needs. @en
  • This ontology extends the SAREF ontology for the Agricultural domain. This work has been developed in the context of the STF 534 (https://portal.etsi.org/STF/STFs/STFHomePages/STF534.aspx), which was established with the goal to create three SAREF extensions, one of them for the Agricultural domain. @en
  • The present document is the technical specification of SAREF4SYST, a generic extension of [ETSI TS 103 264 SAREF](https://www.etsi.org/deliver/etsi_ts/103200_103299/103264/02.01.01_60/ts_103264v020101p.pdf) that defines an ontology pattern which can be instantiated for different domains. SAREF4SYST defines Systems, Connections between systems, and Connection Points at which systems may be connected. These core concepts can be used generically to define the topology of features of interest, and can be specialized for multiple domains. The topology of features of interest is highly important in many use cases. If a room holds a lighting device, and if it is adjacent with an open window to a room whose luminosity is low, then by turning on the lighting device in the former room one may expect that the luminosity in the latter room will rise. The SAREF4SYST ontology pattern can be instantiated for different domains. For example to describe zones inside a building (systems), that share a frontier (connections). Properties of systems are typically state variables (e.g. agent population, temperature), whereas properties of connections are typically flows (e.g. heat flow). SAREF4SYST has two main aims: on the one hand, to extend SAREF with the capability or representing general topology of systems and how they are connected or interact and, on the other hand, to exemplify how ontology patterns may help to ensure an homogeneous structure of the overall SAREF ontology and speed up the development of extensions. SAREF4SYST consists both of a core ontology, and guidelines to create ontologies following the SAREF4SYST ontology pattern. The core ontology is a lightweight OWL-DL ontology that defines 3 classes and 9 object properties. Use cases for ontology patterns are described extensively in [ETSI TR 103 549 Clauses 4.2 and 4.3](https://www.etsi.org/deliver/etsi_tr/103500_103599/103549/01.01.01_60/tr_103549v010101p.pdf). For the Smart Energy domain: - Electric power systems can exchange electricity with other electric power systems. The electric energy can flow both ways in some cases (from the Public Grid to a Prosumer), or in only one way (from the Public Grid to a Load). Electric power systems can be made up of different sub-systems. Generic sub-types of electric power systems include producers, consumers, storage systems, transmission systems. - Electric power systems may be connected one to another through electrical connection points. An Electric power system may have multiple connection points (Multiple Winding Transformer generally have one single primary winding with two or more secondary windings). Generic sub-types of electrical connection points include plugs, sockets, direct-current, single-phase, three-phase, connection points. - An Electrical connection may exist between two Electric power systems at two of their respective connection points. Generic sub-types of electrical connections include Single-phase Buses, Three-phase Buses. A single-phase electric power system can be connected using different configurations at a three-phase bus (RN, SN, TN types). For the Smart Building domain: - Buildings, Storeys, Spaces, are different sub-types of Zones. Zones can contain sub-zones. Zones can be adjacent or intersect with other zones. - Two zones may share one or more connections. For example some fresh air may be created inside a storey if it has two controllable openings to the exterior at different cardinal points. A graphical overview of the SAREF4SYST ontology is provided in Figure 1. In such figure: - Rectangles are used to denote Classes. The label of the rectangle is the identifier of the Class. - Plain arrows are used to represent Object Properties between Classes. The label of the arrow is the identifier of the Object Property. The origin of the arrow is the domain Class of the property, and the target of the arrow is the range Class of the property. - Dashed arrows with identifiers between stereotype signs (i.e. "`<< >>`") refer to OWL axioms that are applied to some property. Four pairs of properties are inverse one of the other; the property `s4syst:connectedTo` is symmetric, and properties `s4syst:hasSubSystem` and `s4syst:hasSubSystem` are transitive. - A symbol =1 near the target of an arrow denotes that the associated property is functional. A symbol ? denotes a local existential restriction. ![SAREF4SYST overview](diagrams/overview.png) @en