<trackbot> Date: 03 June 2015

<jhund> trackbot, start meeting

<trackbot> Meeting: Web of Things Interest Group Teleconference

<trackbot> Date: 03 June 2015

<jhund> Meeting: WoT IG thing description task force call

<jhund> scribe:Arne

<jhund> Scribe: Arne

<jhund> ScribeNick: Arne

1. Overview of WoT TD wiki page

http://www.w3.org/WoT/IG/wiki/Thing_Description

2. Agenda Point: JSON-LD

Souleiman unfortunately not available today

Sebastian is showing Souleymans' slides

Question: is JSON-LD equivalent to RDF ?

Assumption: RDF -> JSON-LD works fine ... JSON-LD -> RDF is difficult

Sebastian: last week presentation in SSN ... how does it look like in JSON-LD?
... once Souleiman joins us we can discuss in detail

3. Agenda: Evrythng presents WoT Label

Dom presents slides "towards a lightewight standard to make things talk web"

Dom same slides as in Munich

Dom: idea to resolve the "mess" of the IoT
... bringing order in the chaos on the Application Level
... at least have uniformity on the Application Layer
... mission is bridging gap between things and Web
... results are from compose EU project + evrythng
... WoT != IoT --> need for simple set of rules (protocol, resource models, support for extensions)
... goal: 1. blueprints, 2. standard resource model
... helpful for e.g.: automatic UI generation, automatic mashups, API to API integration, M2M communication ...
... find the document here: bit.ly/WOT-LABEL
... use same blueprints, resources, formats for thing, gateway, cloud

Johannes: more important than format is the data model

Dom: agrees. first decide on entities and structure
... then see about data format
... quite often used in the field: MessagePack

Dave: agrees. scalability is important

Dom: could see base model encoded in JSON and then extensions in JSON-LD

<jhund> +1 for media type

Dave: actually JSON-LD already supports that
... JSON-LD allows to specify default namespace

Dom: shows slide: actors: 1. clients & 2. web things (virtual counterparts of physical objects)
... Client performs "Actions" on Web Things
... Web Thing communicates "Events" to Client
... Web Thing has "Properties" (e.g. temperature)

Darko: how can a client understand what a web thing offers?

Dom: we propose a common way of modelling properties
... the practicality of a full semantic web approach is not yet given
... shows related proposals: GATT REST API, Apple Home Kit, Google Brillo & Weave

Dave: what is needed are well-defined and shared vocabularies
... it relates to discovery... you want vocabularies for that

Johannes: Question: could {wt}/meta store semantic annotation?

Dom: yes

Ari: have you looked into IPSO smart object
... it is an ongoing initiative and they are looking for input

Sebastian: asks for a presentation on IPSO smart objects

Ari: yes we can do that

Dom: compose and evrythng API do not define yet semantic models for things

Sebastian: what is now the WoT label?

Dom: the idea is to give a label to things that are Web friendly
... it was just the initial name for the initiative
... http://devices.webofthings.io
... next steps: 1. document now open for comments, 2. subscriptions & web sockets, 3. major protocols integration (mqtt, coap), 4. integration points (semantic web, social networks,...), --> first draft June 16.

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/his/Souleymans'/
Succeeded: s/deep source/IPSO/
Found Scribe: Arne
Found Scribe: Arne
Inferring ScribeNick: Arne
Found ScribeNick: Arne

WARNING: No "Topic:" lines found.

Present: Soumya Johannes_Hund Arne_Broering
Found Date: 03 Jun 2015
Guessing minutes URL: http://www.w3.org/2015/06/03-wot-td-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report