13:08:17 RRSAgent has joined #wot-td 13:08:17 logging to http://www.w3.org/2015/12/09-wot-td-irc 13:08:19 RRSAgent, make logs public 13:08:21 Zakim, this will be 13:08:21 I don't understand 'this will be', trackbot 13:08:22 Meeting: Web of Things Interest Group Teleconference 13:08:22 Date: 09 December 2015 13:08:40 Chair: Sebastian 13:08:44 scribe: Yingying 13:08:53 scribenick: Yingying 13:09:37 present+ Johannes_Hund, Sebastian_Kaebisch, Joerg_Heuer, Darko_Anicic 13:09:40 joerg has joined #wot-td 13:09:57 Sebstian: This is the last TD TF meeting in this year. 13:09:57 RRSAgent, draft minutes 13:09:57 I have made the request to generate http://www.w3.org/2015/12/09-wot-td-minutes.html jhund 13:10:23 ...the agenda is: 13:10:30 present+ Joerg_Heuer 13:10:32 RRSAgent, make logs public 13:10:36 ...1. Plugfest logistics 13:10:51 ...2. Proposed plugfest topics 13:10:54 present+ Toru_Kawaguchi 13:10:57 michael has joined #wot-td 13:10:58 present+ Katsuyoshi_Naka 13:11:19 ...3. Tech Landscape 13:11:46 Sebastian show the slides for plugfest logistics. 13:12:28 Sebastian: it was agreed to have th preparation day one day before the plugfest. It will be Jan 24th. 13:12:40 ...this is the plan for next plugfest. any questions? 13:12:47 [no] 13:13:09 Sebastian: it was on wiki page as well. 13:13:40 wiki page: https://www.w3.org/WoT/IG/wiki/F2F_meeting_2016,_January,_26th_%E2%80%93_28th,_France,_Nice#PlugFest 13:14:00 Sebastian shows the wiki page for plugfest plan. 13:14:37 Sebastian: you need to input your name, your application that you would show. I just copied the table from last plugfest. 13:14:49 ...please everyone put your information on it. 13:15:20 Sebastian shows the slides for the plugfest proposal. 13:15:58 ...1st proposal like in Sapporo, using TD to some thing discovery; 13:16:12 ...2nd, to cover the security aspect. 13:16:30 ...3rd we need some API on Things. 13:17:05 ...4th, from the joint meeting with IRTF, use PlugREST. 13:17:16 ...I need some volunteers to write some howto. 13:17:24 ...what we need to do in the plugfest. 13:17:49 ...I am asking Darko, Oliver, Daniel, Suomya to help. 13:17:57 ...I will do the first one. 13:18:33 ...The 1st idea is how we use the TD to do central-based discovery. 13:19:10 ...an example: We have down here different kinds of things. 13:19:19 ...each of them has a TD. 13:19:30 ...upper layer we have TD repository. 13:19:38 ...then we have one kind of client. 13:19:49 ...it is able to request some kind of TD. 13:20:02 ...How does it look like in interaction? 13:20:15 ...The thing is going to do the thing registration. 13:20:27 ...to the TD repository. 13:21:08 ...in the client slide, open source project, which you could download it. 13:21:43 ...2 ways to do registration: one is thing does it by itself; others to do it. 13:21:58 ...the major goal is to have different TDs in the repository. 13:22:22 ...there is a client to look for different kind of things. 13:22:41 ...the idea is the TD repository will provide different TD. 13:23:21 ...need to do how-to on the TD. 13:23:37 ...it will be on the wiki page of W3C in following days. 13:23:46 ...Darko, do you want to share yours> 13:24:03 Darko: idea is to provide how-to. 13:24:13 ...this is very preliminary docs. 13:24:38 ...I will show you how the docs will be like and get your comments.Currently it's incomplete yet. 13:25:08 ...Here I summarized what this repository can be used for. It can be used by human and things. 13:25:32 ...It is also possible to discover certain things based on TD. 13:25:59 ...invoke actions on certain things. 13:26:18 ...can create, delete TD from repository. 13:26:40 ...currently we have the reading and querying functionality. 13:27:15 ...if you want to query repository, you need to provide some data like this: URI, IP address, etc. 13:27:40 ...there is a payload example. 13:27:54 ...This is a kind of response to the query. 13:28:16 ...This is a JSON-LD file. 13:28:42 ...for others like updating or deleting TD, we will fill in. 13:29:25 Michael: Resource directory is exactly the same as your repository in our state machine partner. 13:30:09 ...Hypercat, SPARCL also used. 13:31:04 ...resource directory also has some basic query. 13:31:12 Darko: will you join us on this work? 13:31:42 Michael: sure. 13:31:42 Darko: we will communicate this how to with you. 13:31:56 ...we will work together to make examples. 13:32:30 Sebatian asked Oliver to show the security part. 13:35:02 Resource Directory; https://tools.ietf.org/html/draft-ietf-core-resource-directory-05 13:35:06 less than 8 weeks remaining 13:36:01 Oliver: add secure communications but do not limit security enabling to that 13:36:11 s/SPARCL/SPARQL 13:36:26 Oliver: Security proposal to adopt IETF ACE Working Group Architecture 13:36:43 ... focus on authorizing and authentication 13:37:00 Yingying_ has joined #wot-td 13:37:28 ... add AM and AS components to the plugfest 13:38:21 ... runs in a less constrained environment 13:38:51 Yingying_ has joined #wot-td 13:39:25 ... there will be also a HowTo 13:39:57 nick: yingying 13:39:58 ACE: https://datatracker.ietf.org/wg/ace/documents/ 13:40:07 nickname: yingying 13:40:09 ... also a cheat sheet 13:40:52 ... running AM and AS instances (provided by Siemens) 13:43:08 another REST client:https://chrome.google.com/webstore/detail/advanced-rest-client/hgmloofddffdnphfgcellkdfbfbjeloo?hl=en-US 13:43:40 Oliver shows a demo 13:44:12 dape has joined #wot-td 13:44:32 Oliver using a REST client to demonstrate security APIs 13:44:56 https://www.getpostman.com/ 13:46:01 Oliver interacting with AS and AM to create authorization for a request to the RS 13:46:55 CoAP client is copper: https://github.com/mkovatsc/Copper 13:47:16 scribe: yingying 13:47:30 https://addons.mozilla.org/en-US/firefox/addon/copper-270430/ 13:48:09 Oliver: tomorrow we will look at this same thing but more details. 13:48:16 Oliver: Will discuss more tomorrow in the SP call 13:48:54 ...we can bring it to life by end of next week. 13:49:23 Sebatian: we have also another TF which concentrates on API. 13:49:48 ...Daniel will also give some first idea. 13:50:05 ...how the API would look like in next plugfest. 13:50:33 Daniel:it's as mature as security. 13:50:42 ...idea is to use WebIDL. 13:51:35 ...we also will provide javascript API. 13:51:51 ...encourage to try out other languages. 13:52:03 ...feature based on previous plugfest in sapporo. 13:52:50 ...WebIDL and Javascript API will be provided by end of next week. 13:53:17 ...I can shortly show the javascript API made in september. 13:53:41 ...very simple API that allows you to set or retrieve properties. 13:53:58 ...in addition, there will be a howto provided once the APIs are shared. 13:55:29 Michael: is the WebIDL machine-readable 13:56:18 Daniel: WebIDL is just to provide the methods like prevously javascript APIs provide. 13:56:47 Michael: it's the standardized format of scripting APIs. 13:57:10 ...there will be a WebIDL coming along with TD for everyone to use. Cool! 13:57:37 Johannes: WebIDL is that W3C uses to describe the APIs. 13:59:36 Michael: just wondering general description for general interaction pattern. 14:00:19 Sebastian: last topic is plugREST. 14:01:16 Matthias:this is the so called plugREST by IRTF. 14:01:40 ...background info is IRTF is the counterpart of IETF. 14:02:06 ...the slides are on github. 14:02:22 ...we focus on hypertext drive apps. 14:03:24 ...describes REST apps by URI, media types, link relation types, form relation types, and optionally locations. 14:03:52 ...we choose the lighting use case for the PlugREST. 14:04:27 ...there is also a draft of this use case on irtf web page. 14:04:53 ...the plan of PlugREST is to define basic components like lights and controllers. 14:05:37 ...on the long run we hope to interconnect with other app domains. 14:06:32 ...imaging you have the TD. We get the TD and can interact with the thing. 14:07:27 ...the client communicate with resouce directory. Then we can follow links to get the TD. 14:07:54 ...they are actually decentralized. 14:08:24 ...the purpose is to find IoT implementation on this. 14:08:59 ...what we implemented is a CoRE HAL to support forms and media types. 14:09:19 ...we have the hypermedia client. 14:09:48 ...we have the Java base and Javascript Runtime. 14:10:01 ...this is an example in JSON. 14:10:53 Matthias shows an example for hypermedia client. 14:12:08 Matthias shows an example of JS in Actinium. 14:12:44 Matthias: the plan for Nice F2F meeting is to make the tech demo to find more implementers. 14:12:58 ...to discuss how to harmonize W3C and T2TRG approaches. 14:13:20 ...sources not ready yet. We will make public this year. 14:13:40 rrsagnet, draft minutes 14:14:12 Michael: We use different media types. but we don't make application media type. 14:14:19 rrsagent, make minutes 14:14:19 I have made the request to generate http://www.w3.org/2015/12/09-wot-td-minutes.html yingying 14:14:59 ...the easiest way is we go to the media directory, we query some media types we want. 14:16:17 Matthias: we can have generic media types that have no semantic info in it. Then you coud group them to have specific media type. 14:17:34 ...how to balance them is the key points. 14:17:56 Michael: 3rd part is the schema.org. 14:18:06 ...there are many different ontologies. 14:18:10 akeranen has joined #wot-td 14:18:19 q? 14:18:28 ...this is the work on progress and we should continue. 14:18:45 q+ 14:21:03 [some discussion on the generic media type and app specific media types] 14:22:11 Ari: is there any minimum subset that I could implement before PlugREST. 14:22:35 Matthias: yes. I can try to give you the pointer of it. 14:23:11 Sebastian: there is already some info on wiki about plugfest. 14:23:23 ...All presentations are presented on it. 14:23:52 ...please input your name and information and the topic you would like to implement into the table. 14:24:11 s/information/organization 14:24:23 ...please input by end of next week. 14:24:44 ...I would like to take a look at the tech landscape. 14:25:08 ...Darko has now transferred the tech landscape from wiki to github already. 14:25:47 Darko: We decided to move the landscape to the github. 14:25:56 ...everyone can see it and edit it. 14:26:25 ...you can see the table containing different consortium and other information. 14:27:07 ...We provided some initial structure. Maybe you have better suggestion for the struture. we could discuss it. 14:27:21 ...we need more volunteers to work on it. 14:27:49 ...if you are now willing to do any part of it, please put your name and we then can move on. 14:28:05 rrsagent, make minutes 14:28:05 I have made the request to generate http://www.w3.org/2015/12/09-wot-td-minutes.html yingying 14:28:36 Sebastian: what is the plan? should we put the name now or give several days? 14:28:57 Darko: we can fill it right now if some volunteers are here. 14:29:31 Ari: please put note on wiki that the latest version is on github. 14:30:02 Sebastian: let's give the timeline by the end of week. 14:30:33 ...Happy Christmas! See you next year! 14:30:41 [adjourned] 14:30:46 rrsagent, make minutes 14:30:46 I have made the request to generate http://www.w3.org/2015/12/09-wot-td-minutes.html yingying 14:40:35 katsu has left #wot-td 16:20:52 bengo has joined #wot-td 17:42:07 taki has left #wot-td 17:54:34 bengo has joined #wot-td 20:02:17 bengo has joined #wot-td 20:02:58 bengo has joined #wot-td 20:25:21 bengo has joined #wot-td 20:37:54 bengo has joined #wot-td 21:22:13 bengo has joined #wot-td