07:07:26 RRSAgent has joined #wot 07:07:26 logging to http://www.w3.org/2015/04/30-wot-irc 07:07:49 ryuichi has joined #wot 07:07:51 zakim, who is here? 07:07:51 sorry, kaz, I don't know what conference this is 07:07:54 On IRC I see ryuichi, RRSAgent, Zakim, kaz, vic_exp, mkovatsc, k_nimura1, taki, dape, jhund, Joerg, flosal, trackbot 07:08:03 Kaj: Slide 2: Original input at F2F meeting in Munich 07:08:44 Kaj: Right side: HTTP protocol to WoT server. Wot Server can be adresses by URI 07:08:54 ... WoT server provides REST API 07:09:18 ... WoT Server uses TDL document (what/which device) 07:09:26 ... status at the f2F 07:09:59 Kaj; Slide 3: Use case home automation (discovery) 07:10:28 ... user uses smartphone ... dicovers available devices 07:11:20 ... WoT server is manager. App requests devices. Server responds with list 07:11:58 ... currently Panasonic uses propriatory binary format for data exchange 07:12:53 Kaj: Slide 4: After discovery App selects e.g. air conditionar 07:13:16 present+ kaz, kosuke 07:13:25 .. next step: which kind of service air conditionar can provide 07:13:31 rrsagent, make log public 07:13:36 rrsagent, draft minutes 07:13:36 I have made the request to generate http://www.w3.org/2015/04/30-wot-minutes.html kaz 07:14:24 ... Agent provides device type and additonal information (owner etc) 07:15:44 .. information come from different databases... registration and/or manufacturer 07:17:35 ... "Total Manager" communicates across multiple WoT Servers and agents 07:18:12 Kaj: Slide 5: Users can control device (with previous information) 07:18:50 ... e.g., command cool down to WoT server and WoT Agent 07:19:43 present+ johannes, claes, daniel, david, joerg, kaji, kazuaki, matthias, robert, taki, victor 07:19:46 ... WoT server interprets "abstract" command and maps it to "real" command (ECHONETLITE) 07:20:31 Kaj: Slide 6: about setup up process 07:21:11 ... WoT Server at first does not know devices 07:21:29 Meeting: WoT IG - APIs and Protocols TF 07:21:39 rrsagent, draft minutes 07:21:39 I have made the request to generate http://www.w3.org/2015/04/30-wot-minutes.html kaz 07:22:06 .. home gateway posts "add new device" to WoT Server 07:22:46 .. step3: about including device attributes 07:24:31 Kaj: Slide 6: About Notification 07:24:44 [ https://lists.w3.org/Archives/Public/public-wot-ig/2015Apr/att-0074/W3C_TF-AP20150430v2_Panasonic_Kajimoto.pdf ] 07:26:14 yes kaz, but they are the same, without the notification slide 07:26:33 ouch 07:27:13 ... GW pushes to WoT (agent/server) information to smart phone that for example air conditioner has been switched off or so.. 07:27:20 Joh: Comments? 07:27:38 s/... GW/Kaj: GW/ 07:28:08 Joh: Question: Home Gateway converts betwen Wot protocol and Echonetlite...where are those servers.. both "in" the home? 07:28:28 s/betwen/between/ 07:28:38 s/Echonetlite/Echonet-Lite/ 07:29:03 knagano has joined #wot 07:29:04 q+ 07:29:16 Kaj: WoT server implements GW function. 07:29:28 sorry yes, you're right kaz. I was looking at the end 07:29:46 ack kaz 07:29:47 JoH: Wot server in cloud or in home device? 07:29:55 Kaj: combination 07:31:05 Kaz: suggest differiantate between HW layer and Protocol layer 07:31:33 Joh: Next on the agenda. Presentation from Dom 07:32:02 Joh: iotkit-comm / Intel is next. anybody here? 07:32:06 s/ouch/[p6 of the above slides says "Home Automation (Notification)"]/ 07:32:06 ... not 07:32:22 rrsagent, draft minutes 07:32:22 I have made the request to generate http://www.w3.org/2015/04/30-wot-minutes.html kaz 07:32:28 Joh: Claes, would you prepared? 07:32:52 Claes: Not ready yet. Could provide input for next meeting 07:33:16 ... tricky part authentication won't be part of it 07:33:30 ... will provide input via mail 07:34:23 Joh: Meeting schedule: decided to have weekly meetings in the beginning... alternating timezones 07:34:48 .. setup doodle... not many people participated 07:35:30 http://doodle.com/cw5tdschat6i29w7duhctvzh 07:35:45 Joh: suggest Tuestday to Thursday due to alternating timezones 07:36:06 Claes has joined #wot 07:36:07 Joh: according doodle Thursday looks good 07:36:30 Present+ Claes_Nilsson 07:36:44 .. let's schedule next meeting on Thursday (US timezones) 07:38:19 Joerg: Proposal: shift it always by 8 hours.. will add information in wiki 07:38:52 Joh: Next on agenda: call for AI 07:39:07 ... architectural figures for use case 07:39:23 Joh: are there contributions? 07:39:45 Joh: We have one.. can sart 07:40:07 Joh: Server called serviant (acting as server and client) 07:40:26 ...serviant can be connected with other serviants... 07:40:43 .. can be connected by browsers etc 07:40:56 .. serviant uses protocol mapping 07:41:18 .. on top is API..... and Application 07:41:30 ... will send figure on mailing list 07:41:34 Joh: any comments 07:42:09 Kovatsch: looks similar to what we have in IETF (combination of server& client) 07:42:22 Joh: Any reference to link to at IETF 07:42:46 q+ 07:43:03 Kovatsch: CORE interface draft uses this approach 07:43:23 ... will provide information on IRC 07:43:25 ack kaz 07:43:42 -> https://www.w3.org/2013/10/MMI.png MMI Architecture 07:43:58 Kaz: diagram similar to multi modal archcitecture 07:44:12 https://tools.ietf.org/html/draft-ietf-core-interfaces-02 07:44:36 Only use for the mixed client/server role on devices (for now) 07:45:11 Joh: Did you use a special word for the combined serviant (server: interaction manager and client: modality component) 07:45:49 also see https://tools.ietf.org/html/draft-ietf-core-resource-directory-02: devices register in client role and then serve resources as server 07:46:42 Joh: example about REST API 07:47:15 ... mapping to protocol ...did not find abstract model.. used http 07:47:36 .. identidied WebIDL for abstract definition of API 07:48:20 ... need to define data structure for event 07:49:01 ... details can retrieved by following link 07:49:22 .. datastracutures across various format should be the same 07:49:56 ... API should use WebIDL 07:50:44 ... need to find common denominator accross the many APIs 07:51:51 ... server reports errors if any.. 07:52:42 Joh: Comments? 07:52:56 Kovatsch: missing concept of hypermedia type... 07:53:29 ... which content type.. how to send data 07:53:54 Joh: There is a task force that should deal with it.... 07:54:47 Kovatsch: It is more about the style of the API (e.g, RMI) 07:55:27 Joh: will publish document... Mattias can you annotate what you mean 07:55:36 Kovatsch: sure 07:56:20 DP: should make it available.. so that other have a better change to comment.. (said already) 07:56:29 TOPIC: AOB 07:56:53 none 07:57:18 Joh: will send out arch figure and document via mail 07:57:48 ... will also inform you about next meeting 07:58:31 s/my/me 07:59:12 [adjourned] 07:59:15 rrsagent, draft minutes 07:59:15 I have made the request to generate http://www.w3.org/2015/04/30-wot-minutes.html kaz 07:59:18 thanks... will send mail 07:59:53 perfect, thank you 08:03:25 taki has left #wot 09:21:46 LJWatson has joined #wot 09:28:19 kaz has joined #wot 10:39:30 Zakim has left #wot