178
results
-
The Data Knowledge Vocabulary allows for a comprehensive description of data assets and enterprise data management. It covers a business data dictionary, data quality management, data governance, the technical infrastructure and many other aspects of enterprise data management. The vocabulary represents a linked data implementation of the Data Knowledge Model which resulted from extensive applied research. @en
-
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 Open NEE Configuration Model defines a Linked Data-based model for describing a configuration supported by a Named Entity Extraction (NEE) service. It is based on the model proposed in "Configuring Named Entity Extraction through Real-Time Exploitation of Linked Data" (http://dl.acm.org/citation.cfm?doid=2611040.2611085) for configuring such services, and allows a NEE service to describe and publish as Linked Data its entity mining capabilities, but also to be dynamically configured. @en
-
The ontology 'dtype' provides a specification of simple data types such as enumerations. These are needed in support of the conversion of XML Schemas and UML Models to OWL. Codelists are also defined in 'dtype'. @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
-
The nanopub ontology @en
-
OPMW is a OPMV profile to model the executions and definitions of scientific workflows. @en
-
The Measurement Ontology is an ontology in which measurements may be rendered @en
-
Properties allowing statement of intensional equivalence between RDF graphs @en
-
This vocabulary allows to attach an authority to a named graph @en
-
An historical ontology used by the cwm command-line tool back in the very early days of the semantic web (~ 2000- 2003 ?) @en
-
OWL Full vocabulary for defining lenses and formats on RDF models. @en
-
Representing Content in RDF as defined by http://www.w3.org/TR/Content-in-RDF/ @en
-
This vocabulary is for describing relationships between standards/specifications, profiles of them and supporting artifacts such as validating resources. This model starts with [http://dublincore.org/2012/06/14/dcterms#Standard](dct:Standard) entities which can either be Base Specifications (a standard not profiling any other Standard) or Profiles (Standards which do profile others). Base Specifications or Profiles can have Resource Descriptors associated with them that defines implementing rules for the it. Resource Descriptors must indicate the role they play (to guide, to validate etc.) and the formalism they adhere to (dct:format) to allow for content negotiation. A vocabulary of Resource Roles are provided alongside this vocabulary but that list is extensible. @en