128
results
-
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
-
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
-
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
-
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
-
This ontology defines batteries and their state of charge ratio property. @en
-
## RDF Presentation and RDF Presentation Negotiation An RDF graph can be presented in several ways, using different media types. Examples of RDF media types include `application/rdf+xml`, `text/turtle`, `application/json+ld`. Today, most of the content consumed/produced/published, on the Web is not presented in RDF. In the Web of Things, HTTP servers and clients would rather exchange lightweight documents, potentially binary. Currently, most existing RDF Presentations generically apply to any RDF graph, at the cost of being heavy text-based documents. Yet, lightweight HTTP servers/clients could be better satisfied with consuming/producing/publishing lightweight documents, may its structure be application-specific. @en
-
An ontology to model accountability of generic systems. @en
-
An ontology to model accountability of AI systems which use machine learning. @en
-
With the aim of enhancing natural communication between workers in industrial environments and the systems to be used by them, TODO (Task-Oriented Dialogue management Ontology) has been developed to be the core of task-oriented dialogue systems. TODO is a core ontology that provides task-oriented dialogue systems with the necessary means to be capable of naturally interacting with workers (both at understanding and at ommunication levels) and that can be easily adapted to different industrial scenarios, reducing adaptation time and costs. Moreover, it allows to store and reproduce the dialogue process to be able to learn from new interactions. @en
-
Module for Action (and Frame) modelling inside domain. @en
-
Module for dialogue process and system output management. @en
-
Module for dialogue process and system output management. @en
-
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
-
RDF-STaX is an OWL 2 DL ontology that enables describing the types of RDF streams and defines relations between them. @en
-
Quality, architecture, and process are considered the keystones of software engineering. ISO defines them in three separate standards. However, their interaction has been poorly studied, so far. The SQuAP model (Software Quality, Architecture, Process) describes twenty-eight main factors that impact on software quality in banking systems, and each factor is described as a relation among some characteristics from the three ISO standards. Hence, SQuAP makes such relations emerge rigorously, although informally. SQaAP-Ont is an OWL ontology that formalises those relations in order to represent and reason via Linked Data about software engineering in a three-dimensional model consisting of quality, architecture, and process characteristics. @en