13:04:55 RRSAgent has joined #wot 13:04:55 logging to http://www.w3.org/2017/03/08-wot-irc 13:05:22 ying_ying has joined #wot 13:05:23 tokuyama has joined #wot 13:05:25 present+ 13:05:59 present+ Kaz, Daniel, Feng, Michael_McCool, Taki, Yongjing 13:06:48 Agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda 13:06:56 present+ Achille 13:07:07 present+ Tokuyama 13:07:11 regrets: Matthias 13:07:13 masato has joined #wot 13:07:48 scribenick: kaz 13:07:53 dape has joined #wot 13:08:07 Agenda: https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#Agenda 13:08:21 present+ Yingying 13:08:45 present+ Nimura 13:09:09 q+ 13:09:22 mm: OCF update 13:09:26 ... MoU not yet 13:09:48 ... OCF Liaison will be pretty busy for the next a few months 13:10:28 ... btw, anyone who are members of OCF here? 13:10:35 ... your help is welcome for the liaison 13:11:02 yz: my company is a member of OCF but I myself can't join the effort 13:11:17 ... let's talk about that offline 13:12:00 ... any other update? 13:12:05 ka: about minutes handling 13:12:08 ... @@@ 13:12:19 yz: anything else? 13:12:21 (none) 13:12:43 topic: [Dave Raggett] Thing description requirements from a survey of OCF, oneM2M, BACnet and EchoNet 13:13:04 dsr: will put the slides somewhere reachable 13:13:44 ... the project name is "CREATE-IoT" 13:14:06 ... Survey of IoT Platforms 13:14:18 (Dave goes through the slides) 13:14:30 dsr: [ Survey of IoT Platforms ] 13:14:59 ... work funded by the European Commission through the Create-IoT 13:15:05 ... [ Coverage ] 13:15:46 ... started to look at OCF/OIC 1.1, oneM2M, BACnet, ECHONET, Smart Device Template, ... 13:15:58 mm: what about MQTT, DDS, etc.? 13:16:06 dsr: on the roadmap 13:16:15 ... [ Methodology ] 13:16:53 ktoumura has joined #wot 13:16:53 ... read the IoT platform specs and look for common patterns 13:16:58 ... [ OCF ] 13:17:01 ... starting with OCF 13:17:08 ... OIC 1.1 13:17:16 ... RESTful interface over CoAP and HTTP 13:17:32 ... spec uses Restful API Markup Language (RAML) 13:17:49 ... modularization ongoing 13:18:09 ... each resource is defined in RAML 13:18:33 ... RAML is not used at run-time 13:18:51 ... RAML is verbose with a high degree of predictability 13:19:06 ... OCF spec online 13:19:20 mm: what about oneLTA model? 13:19:36 dsr: not aware 13:19:44 ... [ OCF OIC 1.1 release ] 13:19:51 ... 63 resources/15 Devices 13:20:13 q+ 13:20:30 ... [ oneM2M ] 13:20:44 ... RESTful interfaces over CoAP, HTTP and MQTT 13:20:56 ... defines devices in terms of composition of modules 13:21:01 ... formalized in XML 13:21:13 ... home appliances and information models 13:21:14 Look at www.oneiota.org for a list of more up-to-date OCF/OIC data models 13:21:41 s/oneLTA/oneiota/ 13:21:53 dsr: broad range of devices 13:22:01 ... specification online 13:22:14 ... [ oneM2M ] (contd.) 13:22:22 ... 40 modules/13 devices 13:22:46 yz: first slide of oneM2M 13:22:58 ... binding protocol now includes WebSocket as well 13:23:04 ... DDS also 13:23:25 ... there are tools as well 13:23:44 ... service function models are represented as resources 13:24:12 mm: OCF is similar 13:24:23 dsr: what level of commonality is there? 13:25:11 yz: not 1-to-1 mapping yet 13:25:33 mm: 2 issues 13:25:47 ... OCF define common resources 13:26:11 ... roughly compared to oneM2M 13:26:18 ... trying to work together 13:26:35 ... the question is there are existing devices 13:26:49 q? 13:27:36 yz: oneM2M was defining device models as an abstract ones 13:28:03 ... there is another source, OMA 13:28:36 ... oneM2M uses ontology but it doesn't govern the ontology 13:28:50 ... there are some examples 13:29:00 ... base ontology and domain specific ones 13:29:09 dsr: we can learn it 13:29:15 ... [ BACnet ] 13:29:21 ... building automation 13:29:58 ... core specs define information model, metadata and protocols 13:30:14 ... a bit different technology 13:30:26 ... BACnet object corresponds to properties 13:31:10 ... BACnet objects correspond to WoT properties 13:31:18 ... BACnet properties correspond to WoT metadata 13:31:42 ... Michael Newman's book available 13:32:00 ... [ ECHONET ] 13:32:07 naka has joined #wot 13:32:07 ... home automation and personal health 13:32:20 present+ Toumura 13:32:25 present+ Ohura 13:32:31 present+ Nan_Wang 13:32:36 present+ Sebastian 13:32:43 present+ Yamada 13:32:52 ... 22 properties 13:33:00 ... 44 sensors 13:33:14 present+ Daniel_Peintner 13:33:27 rrsagent, make log public 13:33:43 ...[ ECHONET Device Groups ] 13:33:47 ... air conditioners 13:33:59 ... housing/facilities 13:34:06 ... cooking/household 13:34:09 ... health 13:34:15 ... management 13:34:18 ... ... 13:34:32 ... [ HGI Smart Device Template ] 13:34:40 ... defined by the Home Gateway Initiative 13:34:54 ... XML Schema for smart home devices available online 13:35:11 yz: question on HGI 13:35:44 ... home appliance model is available in oneM2M as well 13:35:51 ... using smart device template 13:36:00 dsr: [ REST over CoAP and HTTP ] 13:36:23 ... Roy Fielding's representational state transfer design pattern for stateless protocols 13:36:45 ... different kind of abstraction 13:36:56 ... [ Results ] 13:37:03 ... [ Emergent Requirements ] 13:37:19 ... strong support for objects with properties, actions and events 13:37:27 ... object model for things 13:37:43 ... common data types: boolean, string, integer, number 13:38:22 ... less common data types: enumerations, unions, vectors, ordered/unordered collections 13:38:34 present+ Zoltan_Kis 13:38:43 ... some calls that "array" 13:39:14 ... application types in terms of predefined types 13:39:23 ... things as first class types 13:39:35 ... compound/nested properties 13:39:46 ... compound arguments for actions and events 13:39:54 ... Metadata: 13:40:02 ... min/max for numbers and integers 13:40:13 ... read-only/read-write 13:40:25 ... required/optional 13:40:36 ... units of measure including scale factors 13:40:58 ... static/changeable 13:41:16 mm: constrains of types? 13:41:30 s/constrains/what about constraints/ 13:41:52 ... begin/end of some specific characters? 13:42:13 dsr: we should have mapping mechanism 13:42:25 mm: there is OIC bridging mechanism 13:43:12 dsr: characters and character sets 13:43:17 s/sets/sets as well/ 13:43:25 yongjing has joined #wot 13:43:30 mm: regular expression too 13:43:57 dsr: sometimes metadata is static, but sometimes changeable 13:45:47 mjkoster has joined #wot 13:46:13 ... mapping of enumerated values, property names, etc., to IDs 13:46:22 ... Google protocol buffers show examples 13:46:42 HI guys, it look slike the webconf is now mwmber-only 13:46:44 ... how versioning relates to the history 13:46:50 member-only 13:47:30 dsr: [ Syntactic Modularity ] 13:47:43 ... specs like to define things 13:47:50 ... [ Semantic Modularity ] 13:47:56 sebastian has joined #wot 13:48:09 webconf wants username and password 13:48:10 ... not used by any of the IoT platforms covered so far in the survey 13:48:45 mm: there is a modularity thing 13:49:21 ... either supporting flattening or not 13:49:37 dsr: should look at use cases 13:49:44 Is there a way I can participate? 13:51:23 dsr: [ Next Steps ] 13:51:37 ... plan to flesh out this survey as a CreateIoT report 13:51:53 ... whilst also extending it to a broader IoT platforms 13:51:54 q? 13:53:06 ack k 13:53:47 kaz: do you want to put the results of this survey into the tech landscape document 13:54:08 ... would be a great input for that 13:54:20 dsr: yes 13:54:37 mm: good timing to collect data as well 13:54:53 yz: pattern of interface too 13:55:07 present+ Michael_Koster 13:55:47 yz: sometimes need extended pattern 13:56:20 dsr: if there is already some driver for an IoT platform 13:56:28 ... we don't need WoT 13:56:47 ... but if users want to control the device, may need WoT 13:57:17 (sorry, I have to go...) 13:57:20 present- 13:57:34 yz: other questions? 13:58:04 ... question on [ Semantic Modularity ] 13:58:44 ... in oneM2M, there is something related 13:58:51 ... semantic annotation 13:59:08 ... semantic classes should be validated 13:59:39 dsr: LD TF are discussing that 13:59:48 yz: can provide ideas from the oneM2M side 13:59:58 ... another question on [ Next Steps ] 14:00:16 ... targets include OMA, etc.? 14:00:23 dsr: need to leave now 14:00:44 ... will put the slides on the wiki 14:00:44 yz: tx 14:00:50 present+ Matthias 14:00:56 regrets- Matthias 14:01:13 topic: Osaka F2F 14:01:19 -> https://www.w3.org/2002/09/wbs/1/WoTF2F201705/ registration site 14:01:23 yongjing has joined #wot 14:01:32 -> https://www.w3.org/WoT/IG/wiki/F2F_meeting,_May_2017,_Osaka,_Japan#Input f2f wiki 14:02:10 kaz: mentions the registration site and wiki above 14:02:20 ... sent papers to Yongjing 14:02:46 ohura: list of recommended hotels on the wiki 14:03:04 yz: the first hotel agora hotel was not available for my stay... 14:04:00 ... asks about the papers for his visa procedure 14:04:11 kaz: clarifies the requirements 14:04:21 yz: any other questions? 14:04:22 (none) 14:04:28 topic: WG reports 14:04:41 sk: give some report 14:05:05 ... first call on Monday 14:05:25 ... talked about logistics for spec generation 14:05:30 ... GitHub, etc. 14:05:48 ... already set up the first version 14:06:02 q+ 14:06:16 yongjing_ has joined #wot 14:06:29 ... update from the Santa Clara meeting 14:06:34 ... will continue the discussion 14:06:45 ack d 14:07:08 dp: the content of the current practice document has been copied to the TD area 14:07:21 ... what would happen to the old current practice document? 14:07:52 -> https://w3c.github.io/wot-thing-description/ WG TD draft 14:08:33 -> http://w3c.github.io/wot/current-practices/wot-practices.html IG current practice document 14:08:55 sk: we need to discuss how to handle it 14:09:10 zk: ok with keeping the old doc 14:09:28 dp: as an enter point for the upcoming WG draft? 14:11:04 kaz: we can keep the IG current practice document as is 14:11:33 ... and also if we want, we can use the Current Practices area to record our progress/results from PlugFest demos 14:12:00 zk: yes, current practices are mainly records of PlugFest 14:12:10 yz: we need to check with Matthias as well 14:14:12 kaz: which would be better/easier for the Editors, (1) simply put the PlugFest results on the wiki or (2) once record the detail in the Current Practices document 14:14:35 yz: let's continue the discussion on the ML 14:14:43 s/ML/Editors ML/ 14:14:58 topic: Communication TF 14:15:21 yc: chatted with Dave and the Mar/Comm Team 14:15:29 ... press release testimonials 14:15:44 s/press/about press/ 14:16:02 ... the first public wd should be published in April 14:16:20 ... and would like testimonials from Members 14:16:33 ... the second topic is recruiting for WG 14:16:46 ... 200 people for IG while 60 for WG 14:17:10 ... Alibaba has just joined 14:17:16 ... contacting Tencent 14:17:27 s/60/69/ 14:17:37 ... will reach out other Members as well 14:17:56 ... especially for those who are participating in IG 14:18:06 s/200/218/ 14:18:09 yz: ok 14:18:53 yc: provides some more information on Chinese participation 14:19:30 topic: AOB 14:19:44 yz: any other updates? 14:19:49 ... security, scripting? 14:21:24 kaz: gives update from the Script TF 14:21:28 ... @@@ 14:21:32 yz: ok 14:21:36 ... any other business? 14:23:07 (none) 14:23:13 [ adjourned ] 15:38:39 Karen has joined #wot 16:36:23 Zakim has left #wot 18:27:28 rrsagent, make log public 18:27:31 rrsagent, draft minutes 18:27:31 I have made the request to generate http://www.w3.org/2017/03/08-wot-minutes.html kaz 18:45:29 ahaller2 has joined #wot 19:55:50 ahaller2_ has joined #wot 20:49:01 zkis has joined #wot 21:34:07 ahaller2_ has joined #wot 21:34:51 ahaller2 has joined #wot 21:54:47 ahaller2 has joined #wot