-
Notifications
You must be signed in to change notification settings - Fork 8
Glossary of Terms
This wiki page collects terms in use and their (often multiple, possibly conflicting) definitions, as well as references to more detailed definitions if available. It is not intended to create a new taxonomy, but to collect terminology that already is in use. (See, e.g., Terminology for Layers for active work on terminology.)
Each term should be qualified with its source, i.e., where is the term being used already (and possibly point to a document defining the term).
We might also try to map terms to each other where different terms are being used for related concepts.
Names: Ari Keränen, Michael McCool (notes from the workshop)
"Semantic interoperability means enabling different agents, services, and applications to exchange information, data and knowledge in a meaningful way, on and off the Web." Semantic Integration & Interoperability Using RDF and OWL
"Semantic interoperability is the ability to interpret the meaning of the exchanged data unambiguously as information in the appropriate context. However, the goal of the connectivity function is limited to provide syntactic interoperability between participating endpoints." The Industrial Internet of Things Volume G5: Connectivity Framework
"Semantic interoperability can be defined as the ability of two or more assets (e.g. agents, machines, systems) to exchange and understand each other’s data correctly."
"[...] semantic interoperability provides the means for two systems to understand each other’s conventions and functions behind the data, in the context in which it is used. This can be achieved with different representation languages, but it amounts to either a) a sharing of information models, or b) a conversion of information models, the former being the more scalable approach." IEC White Paper: Semantic interoperability: challenges in the digital transformation age
a short string that indicates what some part of a representation means [RESTFUL-APIS]
(from RESTful Design for IoT)
Hypermedia Control: A component, such as a link or a form, embedded in a representation that identifies a resource for future hypermedia interactions. If the client engages in an interaction with the identified resource, the result may be a change to resource state and/or client state.
Link: A hypermedia control that enables a client to navigate between resources and thereby change the client state.
Resource: An item of interest identified by a URI. Anything that can be named can be a resource. A resource often encapsulates a piece of state in a system. Typical resources in an IoT system can be, e.g., a sensor, the current value of a sensor, the location of a device, or the current state of an actuator.
- Language (Type-X grammars, etc.) -- or more specific terms [WISHI-20181011]