1. Extending the Think Description with Context W3C WoT IG - TD Break Out Session Sapporo TPAC, October 2015 Darko Anicic

2. Motivation Who are you? What function do you provide? What kind of data do you serve? How can I access the data/function? WoT Thing Description provides description of things to answer these and similar questions.

3. Points for Discussions So far, a Thing Description (TD) provides basic, non- contextual, information about a thing; Information that is provided in a TD is partially given in a form of strings that may or may not be understandable by humans, and is definitely not “understandable” by machines (i.e., by another Thing or Thing registry providing the discovery); From this point of view, TD does not answer the questions from the first slide.

4. Possible Contextual Abstraction Layers of Semantic Models - Semantic enrichment - Domain dependency Thing Description Domain Independent Model (e.g., SSN as a sensor model) Domain Dependent Models (e.g., smart home, energy…) Application Model (spanning multiple domain models)

5. Proposal w.r.t Possible Contextual Semantic Models - Not to be recommended as a subject for standardization - Provide mechanisms and best practices on how to extend TD with existing models - To be recommended as a subject for standardization Thing Description Domain Independent Model (e.g., SSN as a sensor model) Domain Dependent Models (e.g., smart home, energy…) Application Model (spanning multiple domain models)

6. Possible Abstraction Layers of Semantic Models for Hypermedia Controls/APIs Thing Description Hypermedia Controls Model (e.g., HATEOAS, Hydra, RESTdesc, RAML etc.) - Provide a general hypermedia controls model based on existing approaches Web Protocol Server Web Protocol Client Protocol Mapping … - Subject of TF- AP work