07:07:23 RRSAgent has joined #wot-di 07:07:23 logging to http://www.w3.org/2015/06/03-wot-di-irc 07:07:25 RRSAgent, make logs public 07:07:25 Zakim has joined #wot-di 07:07:27 Zakim, this will be 07:07:27 I don't understand 'this will be', trackbot 07:07:28 Meeting: Web of Things Interest Group Teleconference 07:07:28 Date: 03 June 2015 07:11:07 dsr has joined #wot-di 07:11:17 scribenick: dsr 07:11:18 Louay has joined #wot-di 07:11:34 Topic: Discovery Task Force meeting 07:11:46 Chair: Soumya 07:11:56 Present: Soumya, Louay, Dave 07:12:18 Soumya introduces the agenda. 07:13:04 The discovery TF wiki https://www.w3.org/WoT/IG/wiki/Discovery_TF 07:15:27 Louay: we should cover local network discovery 07:17:54 Another term is a registry where you can look up things that have previiously been registered. 07:18:13 Soumya: yes, we should cover resource directories. 07:20:37 Dave: We should generalise “Physical Web” to Bluetooth based discovery, Beacons, NFC, Barcodes with Googles Physical Web as one of these. 07:21:17 Soumya: let’s discuss use cases for discovery 07:21:39 I’ve volunteered to provide a use case on remote health. 07:22:07 Eduardo has volunteered on community based flood monitoring. 07:22:24 Dan has another use case, but can’t quite remember the details. 07:23:04 See: https://www.w3.org/WoT/IG/wiki/Use_case_contributions 07:23:30 Louay: I am taking over from Robert Kleinfeld who has now left FOKUS. 07:24:35 Soumya asks Dave and Louay to prepare to discuss how discovery fits into their use cases. 07:25:36 Soumya: I’ve looked at the use case from Claes. This involves a wristband talking to a smart phone which in turn talks to the cloud 07:26:26 The wristband is discovered during installation via BLE binding to the phone, and the phone needs to register the service in the cloud. 07:28:20 Dave: there are a broad range of BLE profiles for wearables and other devices. 07:29:18 Louay: Apple’s HomeKit is very similar, and they recommend using BLE and the Apple TV as a bridge to the cloud. 07:31:03 Louay: does the cloud have to trigger discovery, or is it initiated from the client? It could be either. 07:31:16 s/Louay/Soumya/ 07:31:44 Louay: the user normally has to initiate the process of registration, and we need to define a lifecycle for discovery. 07:31:58 rrsagent, set logs public 07:32:46 Soumya: what happens when you remove the wristband at the end of the day, how quickly should the cloud discover this? 07:33:21 Louay: if the device is already connected, it can signal this change in status 07:34:06 We need to define the expectations for the communication frequency 07:37:03 Dave talks through details of BLE binding as a way of grounding the discussion 07:38:07 Soumya: the next use case is home automation from Takuki Kamiya 07:39:09 see https://lists.w3.org/Archives/Public/public-wot-ig/2015Mar/0048.html 07:39:52 Soumya: he says: Each device and sensor connects to home gateway through 07:39:53 various technologies (e.g. Wi-Fi, Bluetooth, ZigBee, etc.). 07:40:27 For this case, we would have proxies in the home gateway that handle each technology 07:41:29 Louay: application perspective for discovery doesn’t care about the IoT technology 07:42:31 We have discovery then binding, but binding is out of scope for this task force. We certainly need some gateways/drivers for specific technologies 07:42:42 These need to be modular for extensibility 07:43:51 Perhaps we shouldn’t use the term proxy here as it has another sense in the web of things framework 07:43:59 Dave: drivers is perhaps a better term 07:44:34 Soumya: the IoT technology should be visible in the metadata 07:45:57 Louay: we can have an abstract interface that generalises over IoT technologies, and perhaps is more oriented around the kind of sensor or reading and independent of the IoT technologies used to connect to the sensor. 07:46:33 There may be additional data is needed to support discovery at the lower layer to address specific IoT technologies. 07:46:53 s/is/that is/ 07:47:33 Soumya shows a slide for the ETSI based IoT architecture he has implemented. 07:48:45 I used IoT technology specific data locally within the gateway, but not at the application layer 07:50:07 Dave: this is about the abstraction layers and how they relate to discovery 07:51:02 Soumya: let’s now discuss scopes and dimensions of discovery 07:52:02 Louay: we should allow for local and remote discovery, and allow applications to combine this using the same interface 07:53:54 Dave: there may be ways ot using delegation models for discovery where one agent consults another 07:54:32 s/ ot/ to/ 07:55:12 Soumya: what about the dimensions, I currently list context, location? 07:56:00 Dave: another dimension is human, who owns what 07:56:34 There needs to be access control around this 07:57:09 Dave: human constructs such as your home, your office, your friends 07:57:55 Soumya: I had a brief chat with Oliver who leads the security & privacy task force, and we plan joint discussions, likewise for the thing description TF 07:59:03 When it comes to collaborative editing of the document what do you suggest? I understand that we can’t use gdocs. 07:59:30 Louay: maybe GitHub, issue tracking and pull requests, which works quite well if you have an editor in charge 08:01:04 Dave: I would support this and suggest initial discussion by email on the outline structure 08:01:26 Louay: markdown would be a simple choice for the GitHub document 08:02:14 Example from other WG: https://github.com/w3c/presentation-api/blob/gh-pages/uc-req.md 08:03:36 It also integrate well with GitHub processes 08:06:13 Soumya: any other suggestions for the next call? [no] 08:09:54 … end of meeting 08:10:04 rrsagent, make minutes 08:10:04 I have made the request to generate http://www.w3.org/2015/06/03-wot-di-minutes.html dsr 10:26:21 Zakim has left #wot-di 10:57:39 dsr has joined #wot-di 12:23:07 dsr has joined #wot-di