112
results
How to
  • ldp - Linked Data Platform
    http://www.w3.org/ns/ldp#
    A set of best practices and simple approach for a read-write Linked Data architecture, based on HTTP access to web resources that describe their state using the RDF data model. @en
  • uiot - Urban IoT Ontologies - Core Module
    http://www.w3id.org/urban-iot/core
    Core module of the suite of ontologies for urban IoT devices. @en
  • uiote - Urban IoT Ontologies - Electric Mobility Module
    http://www.w3id.org/urban-iot/electric
    Electric Mobility module of the suite of ontologies for urban IoT devices. @en
  • uiots - Urban IoT Ontologies - Sharing Mobility Module
    http://www.w3id.org/urban-iot/sharing
    Sharing Mobility module of the suite of ontologies for urban IoT devices. @en
  • wl - WSMO-Lite Ontology
    http://www.wsmo.org/ns/wsmo-lite#
    WSMO-Lite is a lightweight approach to the semantic annotation of Web service descriptions, defined by the STI2 working group Conceptual Models for Services @en
  • solid - Solid terms
    http://www.w3.org/ns/solid/terms
    Solid terms @en
  • atm - Air Traffic Management (ATM) Vocabulary
    https://data.nasa.gov/ontologies/atmonto/ATM#
    Defines specific air traffic management concepts used in aircraft navigation through the US National Airspace System @en
  • nas - US National Airspace System (NAS) vocabulary
    https://data.nasa.gov/ontologies/atmonto/NAS#
    Defines concepts related to the structure of the US National Airspace System (NAS) @en
  • eqp - Aircraft Equipment Vocabulary
    https://data.nasa.gov/ontologies/atmonto/equipment#
    Defines aircraft models, aircraft systems / subsystems, and aircraft characteristics @en
  • atd - Air Traffic Data
    https://data.nasa.gov/ontologies/atmonto/data#
    Defines concepts related to airport status, including weather, forecasts, and airport operations @en
  • airs - Alliance of Information and Referral Services (AIRS) Vocabulary
    https://raw.githubusercontent.com/airs-linked-data/lov/latest/src/airs_vocabulary.ttl#
    The AIRS Linked Open Vocabulary is a way to describe human services information and referral (I&R) concepts. AIRS is the Alliance of Information and Referral Services (airs.org), which possesses over 1,000 member agencies primarily in the United States and Canada. The AIRS LOV is based on the AIRS XML Schema, available at: https://airs-xml.googlecode.com/hg/tags/3.1/airs.xsd @en
  • apco - African Public Contract Ontology
    https://purl.org/cm/onto/apco
    APCO is an ontology that allows the description of public procurement terms @en
  • saref - SAREF: the Smart Appliances REFerence ontology
    https://saref.etsi.org/core/
    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
  • pubsub - Eccenca Publish-Subscribe Vocabulary
    https://vocab.eccenca.com/pubsub/
    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
  • s4ener - SAREF4EE: the EEbus/Energy@home extension of SAREF
    https://saref.etsi.org/saref4ener/
    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