12:06:33 <RRSAgent> RRSAgent has joined #wot
12:06:33 <RRSAgent> logging to http://www.w3.org/2016/01/25-wot-irc
12:06:40 <Zakim> Zakim has joined #wot
12:20:06 <mkovatsc> mkovatsc has joined #wot
12:22:44 <kaz> [luhch]
12:22:51 <kaz> s/luhch/lunch/
12:29:16 <cabo1> cabo1 has joined #wot
12:44:08 <Karen> Karen has joined #wot
12:45:26 <kaz> topic: Plugfest planning
12:45:35 <kaz> johannes: any volunteer to start?
12:46:19 <kaz> sebastian: still have problems but can start
12:46:59 <mkovatsc> any remote participants in here?
12:47:28 <mkovatsc> we want to have quick pitches about what everyone brought to the Plugfest at 2pm
12:48:57 <kaz> ... (Auto TD Registration & T2T Setup)
12:49:09 <kaz> ... have two things
12:49:19 <kaz> ... heater and temp sensor
12:50:06 <kaz> ... first scenrio is register each TD from the heater and the sensor to the TD repository
12:50:25 <kaz> ... also provide the source for task description
12:50:34 <michael> Michael here
12:50:55 <kaz> ... temp sensor should send the task for the heater to turn on/off
12:51:06 <kaz> present+ Michael_Koster(remote)
12:51:22 <kaz> ... temp sensor sends a message to the heater
12:51:29 <kaz> ... to turn it off
12:51:43 <kaz> ... HTTP connection
12:52:00 <kaz> ... all I need is thing description on data types, etc.
12:52:06 <kaz> ... simple interaction using that
12:53:52 <kaz> kaz: do you have two different implementation models?
12:53:56 <kaz> sebastian: no
12:54:24 <kaz> ... for the initial stage, devices send their Thing Description to the central TD repository
13:00:50 <kaz> ... there are various possible implementation models
13:01:30 <kaz> ... note that the GUI on the PC to configure the sensor is optional and just used to handle the sensor easily
13:02:36 <projector_> projector_ has joined #wot
13:03:05 <mkovatsc> mkovatsc has joined #wot
13:03:07 <mkovatsc> https://hangouts.google.com/hangouts/_/xcqkbhnlc4dzgdrw3jdtjfdtu4a
13:03:56 <mkovatsc> we are adding the presentation computer to the hangout to share slides
13:06:36 <kaz> i/we are/matthias: we are/
13:13:51 <kaz> rrsagent, make log public
13:13:56 <kaz> rrsagent, draft minutes
13:13:56 <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/25-wot-minutes.html kaz
13:18:43 <kaz> (the iPad has been connected with Michael finally)
13:22:26 <kaz> toru: next Panasonic
13:22:40 <kaz> ... (Nice plugfest overview and findings)
13:22:54 <kaz> ... (Background and objectives)
13:23:00 <Soumya> Soumya has joined #wot
13:23:22 <kaz> ... in Sapporo, had discussion on server/client model
13:23:44 <kaz> ... would verify interoperability this time
13:23:53 <kaz> ... (System configuration)
13:24:04 <kaz> ... implemented security features
13:24:47 <kaz> ... collaborative work with Siemens
13:25:05 <kaz> ... access to the Wot Servient on the cloud
13:25:15 <kaz> ... devices in Osaka
13:26:00 <kaz> ... (Servient Specificaiton)
13:26:23 <kaz> ... Protocol, Method, Things and properties, Security, Discovery, Implementation
13:26:48 <kaz> ... lights and air conditioner
13:27:07 <kaz> ... using MS Asure for the cloud side
13:27:19 <kaz> ... (Findings from the plugfest)
13:28:11 <kaz> ... convention of naming properties, property value range, feedback of operation
13:28:49 <kaz> ... should ignore the out-of-range value?  or substitute with the Max/Min values?
13:29:49 <kaz> johannes: one question
13:30:02 <kaz> ... asynchronous feedback?
13:30:25 <kaz> toru: showing the progress to the users, etc.
13:33:05 <kaz> david: (shows homestar.io page)
13:33:31 <kaz> ... (homestar.io:20000/api/things)
13:34:49 <kaz> ... shows description
13:35:13 <kaz> ... @id, @contet, istate, ostate, model, meta
13:35:19 <kaz> s/contet/context/
13:35:21 <mkovatsc> mkovatsc has joined #wot
13:35:49 <kaz> ... also JSON-LD description
13:37:58 <dpjanes> dpjanes has joined #wot
13:38:06 <dpjanes> http://homestar.io:20000/api/things/urn:iotdb:thing:REST:6acd18449fe571d3a1d12ef66aa443dd:rest-dimmer-light/model
13:38:20 <dpjanes> https://github.com/dpjanes/homestar-rest/blob/master/models/RestDimmerLight.iotql
13:38:55 <kaz> ... istate is the actual state
13:39:00 <kaz> ... ostate is what is requested
13:39:49 <kaz> ... let's look at the actual data
13:40:08 <kaz> ... (data)
13:40:17 <kaz> ... change Web API
13:40:27 <kaz> ... and see the resulted date is changed
13:40:48 <kaz> ... this is the model here
13:41:20 <Yingying> Yingying has joined #wot
13:43:01 <kaz> ... might have temperature sensor with some specific temperature range
13:43:23 <kaz> ... switching over to my terminal
13:43:29 <Yingying_> Yingying_ has joined #wot
13:43:49 <kaz> ... (select id, meta:schema:name)
13:44:50 <kaz> ... (select id, istate:temperature)
13:45:51 <kaz> ... kelvin or celsius for temperature
13:46:37 <dpjanes> set istate:on = true;
13:47:34 <kaz> ... two different devices use the same semantics
13:48:37 <kaz> ... what's the best way?
13:49:08 <kaz> s/what's/but what's/
13:49:37 <kaz> carsten: would be good to have presentation tomorrow but pretty interesting demo
13:50:27 <kaz> johannes: a bit hard to follow
13:50:36 <kaz> ... the concept of actions
13:51:37 <kaz> ... you model state transition using istate/ostate
13:52:15 <kaz> david: how do we know?
13:52:22 <kaz> ... two ways
13:53:58 <kaz> ... we can detect the state transition by checking the actual change of states
13:55:02 <kaz> carsten: we do have interface and find out the change
13:55:20 <kaz> ... the action interface is useful for cooking dinner
13:57:14 <kaz> johannes: we can discuss the detail during one of the TF-AP calls
13:57:23 <kaz> ... is that OK?
13:57:26 <kaz> david: ok
13:57:37 <kaz> rrsagent, draft minutes
13:57:37 <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/25-wot-minutes.html kaz
13:58:08 <kaz> (next Nimura-san from Fujitsu)
13:58:37 <dpjanes> Docs here for how to play with the API
13:58:37 <dpjanes> https://github.com/dpjanes/homestar-coap/tree/master/docs/plugfest
14:05:02 <kaz> @@@nimura
14:05:27 <kaz> (next Darko)
14:05:40 <kaz> darko: IFTTT Rule Engine
14:06:01 <kaz> ... IFTTT statements:
14:06:14 <kaz> ... if this = if a certain event occurs
14:06:29 <kaz> ... (IFTTT Rule Engine Embedded in a THing)
14:06:58 <kaz> ... Client API, Server API, Physical API, TD + IFTTT Rule Engine
14:07:02 <kaz> ... (Event)
14:07:33 <kaz> ... Event Rule -> NodeMCU - Brightness sensor
14:07:43 <kaz> ... (Action)
14:07:56 <kaz> ... Action Script -> NodeMCU - Brightness sensor
14:08:11 <kaz> ... (T2T Interaction)
14:08:52 <kaz> ... Event Rule & Action Script -> NodeMCU-Brightness Sensor -> NodeMCU-LED
14:10:20 <kaz> kaz: from software viewpoint, those NodeMCUs are WoT servients?
14:10:22 <kaz> darko: yes
14:10:35 <kaz> nimura: using COAP?
14:11:12 <kaz> ... we Fujitsu use HTTP
14:12:09 <kaz> darko: the rule engine automatically uses the client/server mechanism
14:12:24 <kaz> ... and the users don't see the event handling
14:13:09 <kaz> takuki: how does this mechanism work with the TD repository?
14:14:23 <kaz> darko: there is thing description on the NodeMCUs
14:14:51 <kaz> ari: @@@
14:15:02 <kaz> darko: you can make pattern on sensor's realing
14:15:07 <kaz> s/realing/reading/
14:15:58 <kaz> ... this is just an operation using thing description
14:16:23 <kaz> ... common set of operations can be handled by the rule engine
14:17:33 <kaz> kaz: so making a sequence of events/actions a meta command?
14:17:36 <kaz> darko: yes
14:17:48 <kaz> johannes: anybody else?
14:19:29 <kaz> (next Christian(?))
14:19:41 <kaz> chris: from Siemens
14:19:52 <kaz> ... (Plugfest@Nixe F2F)
14:20:10 <kaz> ... (Security Showcase w/ NodeMCU)
14:20:33 <kaz> ... assume that servient don't have own Internet connection
14:20:53 <kaz> ... get client_id and client_secret
14:22:04 <kaz> ... client registers servient and get rs_id and rs_secret
14:22:09 <kaz> ... more detail tomorrow
14:22:59 <kaz> (next Louay)
14:25:12 <kaz> louay: (Thing API Demo)
14:25:15 <kaz> ... two demos
14:25:23 <kaz> ... one about THing API
14:25:43 <kaz> ... HomeKit accessories
14:25:47 <michael> slides aren't updating
14:26:00 <kaz> ... weather sensor (temp, humidity)
14:26:08 <kaz> ... dor
14:26:12 <kaz> ... and outlet
14:27:05 <kaz> ... see: https://github.com/w3c/wot/blob/master/TF-AP/thing-api/thing-api-webidl.md
14:27:17 <kaz> ... inline with WebIDL description
14:27:50 <kaz> ... (demo window)
14:28:24 <kaz> ... Browse All Things
14:28:43 <kaz> ... request weather using sensors
14:28:50 <kaz> ... temperature and humidity
14:29:16 <kaz> ... same with the door
14:29:31 <kaz> ... open or closed
14:30:25 <kaz> ... client Web app accesses things
14:30:47 <kaz> ... (Thing Description Demo)
14:30:58 <kaz> ... another is demo on Thing Description
14:31:11 <kaz> ... using the same system
14:31:35 <kaz> ... WoT server using Node.js
14:31:46 <kaz> ... suppport HTTP
14:31:53 <kaz> s/suppport/support
14:32:05 <kaz> johannes: Node.js server?
14:32:12 <kaz> louay: own implementation
14:32:22 <kaz> johannes: @@@
14:32:29 <kaz> louay: there are some open questions
14:32:39 <kaz> ... discovery for connected things
14:32:51 <kaz> ... here using BLE
14:33:07 <kaz> ... imagine you're not at home
14:33:25 <kaz> ... all the things are connected with the Internet
14:34:02 <kaz> ... if we use iCloud, etc., we could assume same connection as the one at home, though
14:34:28 <kaz> ... the most important here is discussion on Thing API
14:34:47 <kaz> ... what kind of abstraction should be used is the point
14:35:06 <kaz> rrsagent, draft minutes
14:35:06 <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/25-wot-minutes.html kaz
14:35:53 <kaz> (next Tibor)
14:36:06 <toru> toru has joined #wot
14:37:14 <kaz> tibor: WoT is a W3C open project
14:37:24 <kaz> ... Node.js source
14:38:15 <kaz> s/Node/shows Node/
14:38:27 <kaz> (making the fonts bigger)
14:38:36 <kaz> tibor: [[
14:39:11 <kaz> ... properties like battery_value, is_camera_on
14:39:23 <kaz> s/[[//
14:39:36 <kaz> ... power_consumption
14:39:58 <kaz> ... interesting element is modular architecture
14:40:44 <kaz> ... HTTP, MQTT, WebRTC, etc. can be used
14:40:54 <kaz> ... would show HTTP demo
14:41:06 <kaz> ... shows terminal
14:42:53 <kaz> ... start HTTP REST server
14:43:29 <kaz> ... and shows the Web page at localhost:8888
14:43:35 <kaz> ... can see properties on the page
14:44:14 <kaz> ... also can load/unload devices
14:46:26 <kaz> ... can see the actual transferred data on the terminal
14:46:47 <kaz> s|load/unload|lock/unlock|
14:49:06 <kaz> ... web of things security at: https://github.com/w3c/web-of-things-framework/blob/master/security.md
14:50:05 <kaz> ... not done P2P connection
14:50:29 <kaz> ... UML diagram available on the above page
14:50:48 <kaz> ... shows Node.jp source again
14:50:54 <kaz> ... jwd
14:50:58 <kaz> s/jwd/jwt/
14:51:11 <kaz> ... JSON with encryption
14:51:33 <kaz> s/jwt/jwt (JSON Web Token)/
14:53:04 <kaz> johannes: implementation based on what?
14:53:18 <kaz> tibor: protocol and security?
14:57:01 <kaz> kaz: relationship between wot repository and web-of-things-framework repository?
14:57:18 <kaz> johannes: wot for the IG and framework for the CG?
14:57:28 <kaz> kaz: will ask Dave as well
14:57:57 <kaz> tibor: happy to present tomorrow
14:58:19 <kaz> johannes: will talk with Soumya about the schedule
14:58:30 <kaz> ... maybe complicated to participate remotely
14:58:46 <kaz> ... would involve you in the IG discussion closely
14:59:27 <Zakim> Zakim has left #wot
14:59:28 <kaz> tibor: tx
15:00:11 <kaz> (next Johannes)
15:00:20 <kaz> johannes: one brief slide
15:00:38 <kaz> ... (servient-side scripting API)
15:00:50 <kaz> ... Java-based implementation
15:01:08 <kaz> ... thing description parser by Victor
15:01:27 <kaz> ... API by Louay
15:02:02 <kaz> ... can show the sample script tomorrow
15:02:16 <kaz> ... one servient represents a device
15:02:39 <kaz> ... a thing can interact with each other
15:02:49 <kaz> ... two ways to expose functionality
15:03:15 <kaz> ... implemented the proposal by Oliver on security
15:03:39 <kaz> ... TD as some kind of manifest
15:03:49 <kaz> ... what should happen on the servient
15:03:54 <kaz> ... and what the servient should do
15:04:04 <kaz> ... thing to thing interaction
15:04:15 <kaz> ... handle overall behavier
15:04:27 <kaz> s/behavier/behavior/
15:04:44 <kaz> ... continuous scripting
15:05:04 <kaz> ... sample script on Github
15:05:08 <kaz> ... MIT licensed
15:05:20 <kaz> ... interact with Daniel's UI
15:05:37 <kaz> ... questions on this concept?
15:05:56 <kaz> (no questions)
15:06:14 <kaz> johannes: would suggest we go into actual plugfest and testing from now
15:06:36 <kaz> ... would see pair building
15:06:55 <kaz> ... who has implementations?
15:07:09 <kaz> ... two people implemented clients
15:07:22 <kaz> ... five people implemented servers
15:07:53 <Soumya> Soumya has joined #wot
15:08:14 <kaz> topic: initial plugfest
15:08:35 <kaz> daniel: which network are you using?
15:09:23 <kaz> sebastian: t2t
15:10:01 <kaz> daniel: Thing Description Repository
15:10:19 <kaz> ... TemperatureThingy
15:10:31 <kaz> ... get properties
15:10:43 <kaz> ... and request temperature
15:11:01 <kaz> s/get properties/send commands/
15:12:41 <kaz> ... Try AlarmThingy
15:13:25 <kaz> (test several interactions)
15:14:32 <kaz> darko: what about the brightness sensor?
15:14:49 <kaz> daniel: try Brightness sensor
15:14:56 <kaz> ... and led
15:16:24 <kaz> ... and MyLEDF for Nimura-san
15:16:53 <kaz> darko: would change the brightness now
15:18:05 <kaz> ... also ledOnOff
15:20:08 <kaz> daniel: next try MyLEDF
15:20:20 <kaz> johannes: should we try Panasonic?
15:20:28 <kaz> toru: just registered
15:21:19 <kaz> ... MyAirconditioner_P1
15:22:03 <kaz> kaz: we need to check the air conditioner in Osaka
15:23:16 <kaz> ... within the video, the white box at the top is LEDs
15:23:30 <kaz> ... the middle one is Toshiba's air conditioner
15:23:44 <kaz> ... and the third one is Panasonic's air conditioner
15:25:11 <kaz> ... we can tell whether the air conditioner is heating or cooling base on the direction of the fins
15:26:22 <kaz> toru: also shows Panasonic's client GUI
15:31:47 <kaz> ... turning on the security feature
15:32:02 <kaz> ... need to get token before sending data
15:33:50 <kaz> ... try LED and air conditioner
15:37:26 <kaz> kaz: who generates and manages the security token?
15:39:19 <kaz> oliver: minimal token is installed on the cloud server and the client
15:42:02 <kaz> kaz: wondering if we might want to have a standard way to manage/install security tokens...
15:49:11 <kaz> daniel_johannes: try Siemens GUI with Siemens LED
15:49:27 <kaz> ... and servient
16:00:33 <kaz> sebastian: would try Siemens GUI with Panasonic air conditioner
16:01:33 <kaz> ... get temperature from Siemens sensor
16:01:56 <kaz> ... and send the temperature data to Panasonic air conditioner
16:05:59 <kaz> ... this temp sensor works with the air conditioner in Osaka :)
16:13:47 <kaz> present+ Christian_Glauss(Siemens), Dave_Raggett(W3C)
16:13:51 <kaz> rrsagent, draft miutes
16:13:51 <RRSAgent> I'm logging. I don't understand 'draft miutes', kaz.  Try /msg RRSAgent help
16:14:03 <kaz> rrsagent, draft minutes
16:14:03 <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/25-wot-minutes.html kaz
16:21:09 <kaz> s/Rui_Pedro/Rui_Pedro_Fereira_da_Costa/
16:21:11 <kaz> rrsagent, draft minutes
16:21:12 <RRSAgent> I have made the request to generate http://www.w3.org/2016/01/25-wot-minutes.html kaz
16:29:05 <kaz_> kaz_ has joined #wot
16:38:15 <taki> taki has left #wot
16:59:42 <Karen> Karen has joined #wot