search

w3c / wot-usecases

Repository of the WoT IG to discuss possible WoT use cases
https://w3c.github.io/wot-usecases/
21 stars 34 forks source link

Semantic interoperability use case #15

Open mlagally opened 4 years ago

mlagally commented 4 years ago

Motivate for semantic annotations and interoperability

sebastiankb commented 4 years ago

What is the motivation of that use case? E.g., TD is already designed to use semantics and to improve semantic interoperability.

mjkoster commented 4 years ago

The use case is for using external semantic vocabularies in a Thing Description, following on the current practice of @type + URI terms from iotschema.org for annotations of application semantics (e.g. temperature, motion, on/off, dimming, lock/unlock etc.).

There are additional features to consider that add semantics for location, context, and behavior to a Thing Description, also relying on external vocabularies.

It has always been a scoping factor of WoT TD to rely on semantics provided by application-focused external organizations, but we have only played with @type and iotschema.org so far. This use case is to motivate deeper design thinking about how application semantics are incorporated into Thing Descriptions.

Should we rename the use case to something more specific, like "standardized integration of application semantics"?

sebastiankb commented 4 years ago

Many thanks for clarification. I gree that we need a better explanation and a guide on how to use the external vocabulary (e.g., from iotschema.org) to increase semantic interoperability.

Should we rename the use case to something more specific, like "standardized integration of application semantics"?

+1