RE: [TF-TD] TD section in current practices document

Dear all,



I added a few things on Github as per comments from last TF-TD web-meeting (and from e-mails below):

-       I wrote a proposal for URI resolution in TDs, see http://w3c.github.io/wot/current-practices/wot-practices.html#note-on-uri-resolution

-       I also wrote a small documentation for the JSON-LD context we have just introduced, defining a WoT "common" vocabulary, see https://github.com/w3c/wot/tree/master/TF-TD/Common%20Vocabulary



Both documents might be relevant especially to Plugfest participants. Please comment.



Moreover, I wanted to announce here that the Thing Repository we used last time is up and running again, same addresses. You can store and retrieve both old and new TDs, however, the query feature might not fully work for old ones.



coap://vs0.inf.ethz.ch:5687/td<coap://vs0.inf.ethz.ch:5687/td/>

http://vs0.inf.ethz.ch:8080/td



Regards,

Victor



From: Charpenay, Victor [mailto:victor.charpenay@siemens.com]
Sent: Dienstag, 29. März 2016 10:36
To: tkamiya@us.fujitsu.com; public-wot-ig@w3.org
Subject: RE: [TF-TD] TD section in current practices document



Hi Takuki,



thanks for your comments. As I wrote the section regarding TD samples, I will answer you directly:

1.       I gave a few details about the "@context" part here: http://w3c.github.io/wot/current-practices/wot-practices.html#td-context. If you already read it and still think it could be extended, we can discuss that point tomorrow in the TD telco. I also sent an e-mail last Thursday about the second context file (about common terms for WoT), tell me if it helps.

2.       To build the full URIs in example 2, you concatenate the Thing's base URIs with each hrefs index-wise (i.e. uris[0] + hrefs[0], uris[1] + hrefs[1], ...). Is that right? In that case, as you point out, hrefs should be inverted, so that it makes more sense. It seems to be the easiest way to go but it's not the only one. One could e.g. concatenate hrefs with the retrieval URI (as defined in https://tools.ietf.org/html/rfc3986#section-4.2), which might differ from the URIs embedded in the document. I will also add this point to tomorrow's agenda.



Regards,

Victor



From: Takuki Kamiya [mailto:tkamiya@us.fujitsu.com]
Sent: Freitag, 25. März 2016 02:50
To: Kaebisch, Sebastian; public-wot-ig@w3.org<mailto:public-wot-ig@w3.org>
Subject: RE: [TF-TD] TD section in current practices document



Hi Sebastian,



Examples 10, 11 and 12 use two jsonld documents as its context as

follows.



  "@context": ["https://w3c.github.io/wot/w3c-wot-td-context.jsonld",

               "https://w3c.github.io/wot/w3c-wot-common-context.jsonld"]



I am not very familiar with how the content of those jsonld files should

be processed. Brief description on that aspect in the document using

an example would help understand the mechanics better.



Besides that, Example 2 uses two uris and two hrefs. For the http,

the full uri of "status" property seems to become

http://www.myled.com:8080/myled/myled/status

Notice "myled" appears twice.







Thank you,



Takuki Kamiya

Fujitsu Laboratories of America







From: Kaebisch, Sebastian [mailto:sebastian.kaebisch@siemens.com]
Sent: Thursday, March 17, 2016 1:48 PM
To: public-wot-ig@w3.org<mailto:public-wot-ig@w3.org>
Subject: [TF-TD] TD section in current practices document



Dear TD members,



in yesterday's web meeting, I presented for the plugfest the TD section of the current practice document [1] that tries to reflect the new inputs of the Nice f2f meeting. I would also like to give a short introduction to the members who were not able to attend yesterday's web meeting:



The "Quick Start: TD Samples" section gives a quick introduction about the usage of the TD [2]. Example 1 shows the core idea of the TD. There, you can already see some simplifications in the structure of the TD compared to the version that was used for the Nice and Sapporo plugfest. This is the case for the "metadata" field which is not used anymore (name, encoding, protocol is now used on the 1st level) and this is also true for the "interactions" field (properties, actions, and events are now used directly).



Example 2 gives a sample how you are able to extend additional semantics, e.g., to properties by integrating other context in the TD.



Example 3 shows a more advanced TD that uses multiple protocols, encodings, interactions, and some security information (JWT).



Please comment on the new TD structure. Any feedback is welcome.



Still, what has not been addressed yet are the opportunity to define type restrictions (e.g., define a range of numbers) or define more complex data types, e.g., of a property.



Here, also, any ideas are welcome.



Best wishes

Sebastian



[1] http://w3c.github.io/wot/current-practices/wot-practices.html#thing-description



[2] http://w3c.github.io/wot/current-practices/wot-practices.html#quick-start-td-samples