128
results
  • SAREF4INMA is an extension of SAREF for the industry and manufacturing domain. SAREF4INMA focuses on extending SAREF for the industry and manufacturing domain to solve the lack of interoperability between various types of production equipment that produce items in a factory and, once outside the factory, between different organizations in the value chain to uniquely track back the produced items to the corresponding production equipment, batches, material and precise time in which they were manufactured. SAREF4INMA is specified and published by ETSI in the TS 103 410-5 associated to this ontology file. SAREF4INMA was created to be aligned with related initiatives in the smart industry and manufacturing domain in terms of modelling and standardization, such as the Reference Architecture Model for Industry 4.0 (RAMI), which combines several standards used by the various national initiatives in Europe that support digitalization in manufacturing. The full list of use cases, standards and requirements that guided the creation of SAREF4INMA are described in the associated ETSI TR 103 507. @en
  • The eccenca Publish-Subscribe Vocabulary defines concepts and relations to create statements about publishers, subscribers and their subscriptions in a Publish-Subscribe environment based on the PubSubHubbub Core 0.4 specification. @en
  • This is the extension of SAREF for the EEBus and Energy@Home project. The documentation of SAREF4EE is available at http://ontology.tno.nl/SAREF4EE_Documentation_v0.1.pdf. SAREF4EE represents 1) The configuration information exchanged in the use case 'Remote Network Management' according to the EEBus Technical Report, Protocol Specification- Remote Network Management, version 1.0.0.2, 2015-09-19; 2) The scheduling information about power sequences exchanged in the use cases Appliance scheduling through CEM and remote start' and 'Automatic cycle rescheduling', according to the message structures described in General Message Structures, version 0.1.1, 2015-10-07; 3) The monitor and control information exchanged in the use case 'Communicate appliance status and info on manually planned cycles', according to the monitoring and control part of the Energy@Home Data Model, version 1.0; and 4) the event-based data exchanged in the use case 'Demand Response', according to General Message Structures, version 0.1.1, 2015-10-07. @en
  • This ontology extends the SAREF ontology for the environment domain, specifically for the light pollution domain, including concepts like photometers, light, etc. @en
  • This ontology extends the SAREF ontology for the building domain by defining building devices and how they are located in a building. This extension is based on the ISO 16739:2013 Industry Foundation Classes (IFC) standard for data sharing in the construction and facility management industries. The descriptions of the classes and properties extracted from IFC have been taken from the IFC documentation. @en
  • This ontology defines a vocabulary for describing cyber physical systems for monitoring purpose. It contains two main concepts: CPSWatch#MonitoredSystem that is a top level description of a System that is modeled and CPSWatch#MonitoringSensor that is a top level description of a sensor used to monitor the CPSWatch#MonitoredSystem. @en
  • The Internet of Things taxonomy is extended with semantic ontologies for IoT layers, containing classes, properties, individuals, and rules specific to IoT technologies, tools, and applications @en
  • A vocabulary to represent relations that should be more transparent, usually between powerfull people or institutions @en
  • The Core module represents general-purpose concepts orthogonal to the whole network, which are imported by all other ontology modules (e.g. part-whole relation, classification). @en
  • The BCI ontology specifies a foundational metadata model set for real-world multimodal Brain Computing Interface (BCI) data capture activities. The ontology defines a minimalist and simple abstract metadata foundational model for real-world BCI applications that monitors human activity in any scenario. BCI multimodal domain applications are encouraged to extend and use this ontology in their implementations. @en
  • Ontology that defines the conceptual model for the Pilot 5 - Smart Building use case @en
  • Ontology for the orchestration of the aerOS continuum. @en
  • Simple ontology for Cloud Computing Services. This ontology allows to define model of prices used in large cloud computing providers such as Google, Amazon, Azure, etc., including options for regions, type of instances, prices specification, etc. @en
  • domOS Common Ontology (dCO) represents a common information model to share a unified understanding for humans and machines and to ensure semantic interoperability in a heterogeneous IoT infrastructure. This ontology allows the decoupling of the infrastructure from the software services and applications. @en