13:06:06 RRSAgent has joined #wot 13:06:06 logging to http://www.w3.org/2015/08/12-wot-irc 13:06:09 Zakim has joined #wot 13:06:15 jhund has joined #wot 13:06:20 Darko_Anicic_ has joined #wot 13:06:35 Sebastian has joined #wot 13:06:39 please come here for the joint call of TD and AP 13:06:45 Claes has joined #wot 13:06:58 dape has joined #wot 13:07:40 scribenick: kaz 13:08:34 Arne_ has joined #wot 13:08:59 present+ Johannes_Hund 13:09:27 Present: kaz, sebastian, arne, claes, daniel, darko, johannes, kajimoto, nimura, markus, taki, matsukura 13:09:47 sebastian: first call after the f2f meeting 13:10:02 ... thing description and application protocol 13:10:34 ... we'll clarify which call will happen next week, etc. 13:11:17 ... report from application protocol TF 13:11:29 topic: AP-TF report 13:11:54 johannes: first question is report from the Sunnyvale meeting 13:12:14 ... and report by Darko 13:12:33 Present+ Claes_Nilsson 13:12:47 ... would give report from the Sunnyvale meeting 13:12:55 ... presentation about the outcome 13:13:00 ... had a breakout session 13:13:13 ... also joint discussion with TD/SP 13:13:22 ... about web of things model 13:14:17 (shows presentation https://www.w3.org/WoT/IG/wiki/images/8/8c/TF-AP_breakout_report_consensus.pdf) 13:14:45 johannes: architecture model 13:14:50 ... technology landscape 13:14:57 ... lifecycle states 13:15:06 ryuichi has joined #wot 13:15:08 ... abstract resource model 13:15:53 ... identified iteration 13:16:01 ... still need further refinement 13:16:27 (picture of three WoT Servient: p4) 13:16:59 johannes: use Web Protocol Client to access remote WoT Servient 13:18:16 ... direct access or via some Web service 13:18:48 ... existing domain specific protocols may be used like bluetooth 13:19:38 ... need some refinement 13:19:49 (Points to address) 13:20:00 johannes: difference between protocols 13:20:07 ... orange vs blue 13:20:19 ... constrained device 13:20:27 ... what is the minimal servient 13:20:47 ... one servient hosting several virtual instances 13:20:56 ... servecies in the cloud 13:21:15 (Technology landscape of TF-AP) 13:21:32 johannes: protocols, resource models and api patterns 13:21:59 (Lifecycle states of a WoT Servient) 13:22:13 johannes: discussion initiated by Kajimoto-san 13:22:25 ... offline/standalone 13:22:35 ... registered/paired 13:22:41 ... activated/connected 13:22:59 ... important for security viewpoint as well 13:23:06 (Abstract Resource Model) 13:23:21 (Protocol-agnostic thing model for web things) 13:23:51 johannes: protocol agnostic way to express things 13:24:14 ... would handle HTTP, CoAP, etc., at once 13:24:22 ... meta data should be also handled 13:24:51 (Runtime Properties) 13:25:01 johannes: create interaction 13:25:18 ... dynamic operations 13:25:32 ... read,write, subscribe, observe 13:25:47 ... read data at some specific point 13:25:52 (Actions) 13:26:13 johannes: invocable action on the physical thing 13:26:27 ... issue a state change? 13:26:48 ... enables us atomic change of multiple resources 13:26:57 (Next steps) 13:27:24 johannes: need to complete and transfer the technical landscape 13:27:55 sebastian: some gaps? could you please repeat the last part? 13:28:06 johannes: tech landscape from the wiki 13:28:16 ... and evaluation models 13:28:29 ... to discover what would be the best way 13:28:58 ... define a model based on the use cases 13:29:13 ... that is my report from the Sunnyvale meeting 13:29:30 ... anybody from AP-TF is welcome to comment 13:29:50 sebastian: link for the use cases? 13:30:30 -> http://w3c.github.io/wot/three/master/plugfest 13:30:52 s/three/tree/ 13:31:28 -> https://github.com/w3c/wot/tree/master/plugfest Plugfest page 13:31:40 johannes: there is a github as above 13:32:26 sebastian: making examples based on use cases described here 13:32:52 johannes: would have more consistent plubfest 13:32:59 s/plubfest/plugfest/ 13:33:02 q+ 13:34:00 kaz: how could we put together all the use cases that are already on the WoT wiki pages 13:34:04 ack k 13:34:18 johannes: agree with we should gather all the use cases 13:34:31 ... though not sure how to use them for the plugfest scenario 13:35:00 ... would be pretty obvious on home electronics use cases here 13:35:28 sebastian: some of the use cases fitting quite well with this plugfest scenario 13:35:41 ... very nice scenario 13:35:48 ... home automation 13:37:01 kaz: thinks it would be nice to concentrate on home automation use cases for plugfest 13:37:24 ... and probably some of the TF-AP participants should be able to make contribution for that 13:37:56 johannes: before TPAC demonstration, we need to consider what to be modeled 13:38:11 kajimoto: any idea to include any thing description into this? 13:38:26 ... maybe good sample for that purpose 13:38:41 johannes: good to provide some sample 13:39:15 ... TF-TD could provide some notation for that 13:39:25 sebastian: very good experience 13:39:46 ... to decide what the basic model would be 13:39:48 ... and see what is missing 13:40:47 kaz: yeah, so we could think about some initial small profile of the Thing Description for this Plugfest use case 13:40:49 sebastian: exactly 13:41:06 johannes: we just started the discussion 13:41:20 ... any more comments/questions on the Plugfest? 13:41:36 ... we can have discussion on Github and the ML 13:41:47 sebastian: yes 13:41:50 ... btw, who would take the slot next week? 13:42:01 johannes: next week for TD or AP? 13:42:26 ... myself don't care :) 13:42:58 sebastian: would like to have TD next week unless there is any specific opinion 13:43:01 johannes: ok 13:43:18 ... next Wed. 19th should be TD call 13:43:24 ... and AP call on 26th 13:43:37 ... if there is no objections 13:43:42 s/is/are/ 13:43:52 sebastian: ok 13:44:03 ... next week we'll have a TD call on 19th 13:44:16 ... and AP on 26th 13:44:30 ... also on Thursdays we'll have SP/DI calls 13:44:47 ... we'll do that until TPAC 13:45:07 johannes: need to leave now 13:45:31 sebastian: would take over 13:45:47 topic: TD report 13:46:00 sebastian: shows the agenda of the Sunnyvale meeting 13:46:11 ... outcome from the breakout 13:47:37 https://www.w3.org/WoT/IG/wiki/images/d/d1/Breakout_report_sunnyvale.pdf 13:48:02 markusmaresch has joined #wot 13:48:16 rrsagent, make log public 13:48:20 rrsagent, draft minutes 13:48:20 I have made the request to generate http://www.w3.org/2015/08/12-wot-minutes.html kaz 13:48:48 sebastian: TD model 13:48:53 ... minimal set of vocabulary 13:48:56 ... data type 13:49:07 ... JSON-LD examples 13:49:14 (TD Model) 13:49:30 sebastian: metadata component 13:49:47 ... name of the things, product ID, etc. 13:50:02 ... also includes what kind of protocols are supported 13:50:09 ... encoding information 13:50:17 ... EXI, JSON, etc. 13:50:27 ... data and data type 13:50:51 ... reuse existing data type 13:51:06 ... refer to data types defined here 13:51:39 ... interaction model pattern 13:51:46 ... property, action and event 13:52:41 ... that is the basic structure of the proposed Thing Description 13:53:25 darko: information on APIs? 13:53:37 ... accessible by get 13:53:54 sebastian: this is a basic model 13:54:28 ... what kind of property has which charasteristics depends on vocabulary 13:54:56 ... what we're doing here is very abstract modelling 13:56:07 ... if we have a concrete protocols, we need to think about how to map the protocol to this model 13:56:28 ... would talk about a bit more concrete categories 13:56:47 ... describe the components more precisely 13:56:56 (Minimal Vocabulary Set) 13:57:23 sebastian: metadata: name, protocols and encoding 13:57:47 ... which has to be written 13:58:11 ... could use some specific vendor's protocol 13:58:28 ... could reuse existing ontologies like SSN 13:58:41 ... data: xsd convention 13:58:57 ... definition by XSD 13:59:16 ... able to define data types and data access manners 13:59:40 ... XSD is very powerful for that purpose 14:00:30 ... and well-know property: name, input/output, writable 14:00:47 s/know/known/ 14:00:48 rrsagent, draft minutes 14:00:48 I have made the request to generate http://www.w3.org/2015/08/12-wot-minutes.html kaz 14:01:22 ... need to clarify by TPAC 14:01:39 (Data Type Definition) 14:01:52 sebastian: rely on XSD data types 14:02:00 ... define suitable subset 14:03:17 ... proposals to be discussed during the next meetings 14:03:26 (Examples in JSON-LD) 14:03:32 sebastian: not finished yet 14:04:04 (JSON-LD (Snippet)) 14:04:33 sebastian: IETF thing2thing meeting 14:05:08 ... will continue the discussion on present sensor, switch, etc. 14:05:31 -> https://github.com/w3c/wot/tree/master/plugfest Plugfest scenario 14:05:56 sebastiona: see "Things" section of the above plugfest scenario 14:06:18 (For the next Web Meetings) 14:06:35 sebastian: will check relevant security aspects 14:07:00 ... volunteers for participation 14:07:08 ... demonstrators 14:07:22 ... that's it 14:07:37 ... happy with the outcome from the Sunnyvale meeting 14:08:08 ... questions? 14:08:14 q+ 14:09:07 ack k 14:09:30 kaz: what do you think about the possible collaboration between the TF-TD and the TF-AP? 14:09:47 ... could both the TFs work together for the Plugfest demo at TPAC 2015? 14:10:24 sebastian: unfortunately, couldn't attend the IETF meeting in Plag(?) itself 14:10:43 s/Plag(?)/Plague/ 14:11:13 ... not full potential of TD for the demo but could provide some descriptions for that purpose 14:11:38 ... would look more protocol implementations 14:12:24 kaz: maybe we might want to have a joint call once a month, etc. 14:12:32 sebastian: might be a good idea 14:12:47 ... we'll share a same slot in any case 14:13:12 topic: Report on Spatial Data by Darko 14:13:54 darko: would inform on the Spatial Data group 14:13:59 ... possible collaboration 14:14:26 ... our focus is defining minimum vocabulary for Thing Description 14:14:46 ... we might get help from other groups who work on related topics 14:15:06 ... Spatial Data group works with the OGC 14:15:22 ... related to vocabulary/ontology work 14:15:31 ... trying to make ontology standard 14:15:46 ... standard vocabulary for sensors 14:16:20 ... our minimal vocabulary can be mapped with SSN ontology 14:16:30 ... data provided by other sensors 14:16:47 ... actuators as well 14:16:57 ... semantic description for actuators is missing withing W3C 14:17:11 ... Spatial Data group is working on actuators as well 14:17:19 ... would input from us WoT IG 14:17:31 ... requirements on vocabulary 14:17:55 ... if we could provide requirements on semantic model for actuators 14:17:59 ... would be great 14:18:37 ... Carry Tailor (?) would input from us 14:18:50 ... would have a joint session with us 14:18:54 ... during TPAC 14:19:12 sebastian: interesting 14:19:23 ... ontology outside for sensors, etc. 14:20:12 ... what should we do if we want to use that kind of ontology with Thing Description? 14:20:47 ... how to handle company specific ontology? 14:21:01 darko: a few examples describing sensors 14:21:19 ... discovery on the basis of SSN ontology 14:21:35 ... described by the Thing Description language? 14:21:56 ... what the traditional aspect is like 14:22:21 ... what is the capability of sensors? 14:22:32 ... depending on the conditions 14:22:45 ... important aspects for applications 14:23:08 ... would be good to work with other groups who are taking cares 14:23:29 ... query devices based on the capability descriptions 14:23:35 sebastian: tx 14:23:46 ... think we should invite them to our calls 14:24:01 ... how does it fit with our model 14:24:10 s/how/to see how/ 14:24:57 arne: make sense to find thing description model 14:25:21 ... new version of SSN would include actuator capability 14:26:07 sebasitan: building concepts based on the new version of SSN? 14:26:22 arne: defining a light-weight profile based on that 14:26:51 sebastian: would talk with related groups 14:27:05 ... and let them know what kind of problems we have 14:27:25 ... and see if we could simply reuse their mechanisms, e.g., SSN 14:27:32 s/sebasitan:/sebastian:/ 14:27:39 darko: SSN is widely used 14:28:06 ... would be better to see if SSN description suffices 14:28:23 ... not actuators yet 14:28:54 sebastian: we're getting out of time 14:29:22 ... next week we'll start our TD call at this time 14:29:47 ... and would have joint meetings like today 14:30:01 [ adjourned ] 14:31:09 Meeting: Web of Things IG - TF-AP/TF-TD joint meeting 14:31:20 Chair: Johannes, Sebastian 14:31:28 rrsagent, draft minutes 14:31:28 I have made the request to generate http://www.w3.org/2015/08/12-wot-minutes.html kaz 14:32:18 s/would have/would (from time to time) have/ 14:32:20 rrsagent, draft minutes 14:32:20 I have made the request to generate http://www.w3.org/2015/08/12-wot-minutes.html kaz 14:54:04 markusmaresch has left #wot 15:08:40 J_Lynn has joined #wot 15:58:26 taki has left #wot 16:13:56 Zakim has left #wot 19:20:38 thor has joined #wot