85
results
How to
  • sto - i40 Standards Lanscape Vocabulary
    https://w3id.org/i40/sto#
    A vocabulary to describe the relation between standards in use on the Industry 4.0, and related concepts @en
  • core - Materials Design Ontology - Core Module
    https://w3id.org/mdo/core/
    This is the core module in Materials Design Ontology. @en
  • nen2660 - NEN 2660-2:2022 'Rules for information modelling of the built environment - Part 2: Practical configuration, extension and implementation of NEN 2660-1''
    https://w3id.org/nen2660/
    Ontology which is a normative part of the Dutch NEN 2660-2 standard @en
  • seasd - The SEAS Device ontology
    https://w3id.org/seas/DeviceOntology
    The SEAS Device ontology defines `seas:Device` as physical system that are designed to execute one or more procedures that involve the physical world. @en
  • seas-op - The SEAS Failable System ontology
    https://w3id.org/seas/OperatingOntology
    The SEAS Operating Ontology defines evaluations of operating features of interest. @en
  • seas-qudt - QUDT Alignment.
    https://w3id.org/seas/QUDTAlignment
    This ontology defines proposed alignemnts with the QUDT ontology. @en
  • seas-stats - The SEAS Statistics ontology.
    https://w3id.org/seas/StatisticsOntology
    This ontology defines common evaluation interpretation concepts for statistics. @en
  • seas-sys - The SEAS System ontology
    https://w3id.org/seas/SystemOntology
    The System Ontology defines Systems, Connections between systems, and Connection Points at which systems may be connected. This ontology is then specialized for multiple domains. For example: - In electric energy: - power systems consume, produce, store, and exchange electricity; - power connections are where electricity flows between systems; - power connection points are plugs, sockets, or power busses. - In the electricity market: - players and markets are systems; - connections are contracts or transactions between two players, or between a player and a market; - connection points include offers and bids. @en
  • pep - Process Execution ontology.
    https://w3id.org/pep/
    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. @en
  • seas - SEAS ontology
    https://w3id.org/seas/
    This vocabulary is version v0.1 of the ITEA2 Smart Energy Aware Systems project vocabulary. It enables the description of electricity measurements of a site using the Data Cube W3C vocabulary. @en
  • seasb - The SEAS Battery ontology.
    https://w3id.org/seas/BatteryOntology
    This ontology defines batteries and their state of charge ratio property. @en
  • seast - The SEAS Time Ontology.
    https://w3id.org/seas/TimeOntology
    This ontology defines: - a set of subclasses of `seas:Evaluation` to better interpret evaluations of quantifiable properties. - a set of sub properties of `seas:hasProperty` to qualify time-related properties. @en
  • seasto - The SEAS Trading ontology
    https://w3id.org/seas/TradingOntology
    The Seas Trading Ontology defines concepts and relations to describe ownership, trading, bilateral contracts and market licenses: - players own systems and trade commodities, which have a price; - bilateral electricity contracts are connections between electricity traders at which they exchange electricity; - electricity markets are connections between electricity traders at which they exchange electricity, using a market license; - electricity markets can be cleared, and balanced; - evaluations can have a traded volume validity context @en
  • gist - gist ontology
    https://w3id.org/semanticarts/ontology/gistCore
    gist is a minimalist upper ontology created by Semantic Arts. @en
  • spectra - SPECTRA: A Traceability Ontology for 3GPP RAN Standardization
    https://w3id.org/spectra
    OWL 2 ontology modeling the 3GPP RAN standardization document lifecycle (Tdoc, Resolution, CR, LS, Section, Spec, TechnicalReport, TRImpact, Meeting, Company, WorkingGroup). Designed from RAN1 competency questions and validated by cross-WG instantiation against RAN2-RAN5 with no additional process-layer classes required. Also declares six entity-layer classes (RRCParameter, CapabilityItem, Feature, Procedure, PerformanceRequirement, ConformanceTest) modeling spec-body entities: ASN.1 IEs, UE capability items, named standardization features, protocol procedures, performance requirements, and conformance test specifications. @en