IRC log of wot on 2016-04-11

Timestamps are in UTC.

13:24:38 [RRSAgent]
RRSAgent has joined #wot
13:24:38 [RRSAgent]
logging to http://www.w3.org/2016/04/11-wot-irc
13:27:53 [yingying]
chair: Joerg_Heuer
13:28:07 [yingying]
scribe: Yingying_Chen
13:28:07 [yingying]
scribenick: yingying
13:29:05 [Kajimoto__Kazuo]
Kajimoto__Kazuo has joined #wot
13:29:35 [yingying]
Monday, 11th of April, Open Day / Plugfest
13:30:17 [yingying]
Meeting room: SH-3260 (3th floor at Sherbrooke building)
13:30:54 [yingying]
Topic: Welcome to the WoT IG Open Day
13:31:04 [yingying]
-> https://www.w3.org/WoT/IG/wiki/images/4/4c/Open-day-intro.pdf
13:31:17 [yingying]
Joerg: any questions?
13:35:49 [yingying]
...next would be a number of contributions of talk.
13:36:54 [yingying]
1. Soumya Kanti Datta (EURECOM): IoT Application Development using Semantic Web Technologies
13:37:03 [yingying]
2. Valentin Markus Josef Heun of MIT: Reality Editor project
13:37:14 [yingying]
3. Joao Sousa (Bosch): BEZIRK Platform
13:37:24 [yingying]
4. Dave Raggett: implementation work on web of things servers and gateways
13:37:34 [yingying]
5. Takuki Kamiya & Daniel Peintner: EXI for WoT
13:37:46 [yingying]
6. Michael Koster: T.B.D.
13:37:55 [yingying]
7. Matthias, Kajimoto-san, Sebastian, Johannes: Getting Started with a WoT Project
13:38:05 [yingying]
8. Ian Skerrett: "Eclipse IoT: Open Source Building Blocks for IoT Developers"
13:38:22 [yingying]
...after that would be the plugfest.
13:38:49 [yingying]
...now I would ask Soumya to give the presentation on IoT Application Development using Semantic Web Technologies
13:39:21 [yingying]
Topic: Soumya presents IoT Application Development using Semantic Web Technologies
13:39:38 [dsr]
dsr has joined #wot
13:39:51 [dsr]
present+ Dave_Raggett
13:40:21 [dsr]
scribenick: dsr
13:40:29 [yingying]
->@pointer needed.
13:40:50 [yingying]
rrsagent, make minutes
13:40:50 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/04/11-wot-minutes.html yingying
13:41:35 [dsr]
Soumya’s slide: https://www.w3.org/WoT/IG/wiki/File:Horizontal_IoT_application_development.pdf%7CHorizontal
13:42:39 [yingying]
s/->@pointer needed.//
13:43:54 [kaz]
kaz has joined #wot
13:44:16 [kaz]
rrsagent, make log public
13:44:19 [kaz]
rrsagent, draft minutes
13:44:19 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/04/11-wot-minutes.html kaz
13:44:33 [dsr]
The URI pasted badly and should be https://www.w3.org/WoT/IG/wiki/File:Horizontal_IoT_application_development.pdf
13:49:29 [Karen]
Karen has joined #wot
13:53:35 [Claes]
Claes has joined #wot
13:54:00 [Karen]
Whew
13:54:09 [Karen]
Thanks for letting me know
13:54:56 [Karen]
See you later in the day, most likely not for lunch. Ayanna said there should be a couple extra lunches as well.
13:55:05 [Karen]
So no problem for the guest who forgot to register
13:55:08 [Karen]
gotta run now
13:55:31 [ohsumi]
ohsumi has joined #wot
13:56:25 [dsr]
Soumya describes an approach in which sensors are discovered and provisioned, and provide their data in senml, which is then translated into RDF
13:56:34 [katsu]
katsu has joined #wot
13:57:15 [dsr]
This supports applications through semantic web technologies such as SPARQL.
13:59:01 [dsr]
s/senml/SenML/
13:59:32 [dsr]
He describes a process whereby during provisioning, users select semantic templates for their devices.
14:00:30 [dsr]
The RDF is handled in the cloud using the M3 Framework which itself is implemented using the Jena Framework.
14:00:59 [dsr]
An Android device is used as a home gateway that bridges the cloud to the IoT devices
14:01:30 [dsr]
The gateway is based upon the Android SDK and AndroJena
14:03:46 [dsr]
Questions?
14:05:23 [dsr]
Kaz: Referring to slide 12, This shows two sensors A and B. Can you explain this further?
14:05:39 [dsr]
[scribe missed reply]
14:06:25 [dsr]
Kaz: 2nd question on slide 13. What about coordination and synchronisation across a group of devices?
14:06:43 [dsr]
Soumya: here you can have any number of devices.
14:07:27 [taki]
taki has joined #wot
14:07:56 [dsr]
Johannes: you do reasoning in the cloud, and push actuation to the edge. Have you considered how you would handle actuation in the edge?
14:08:53 [dsr]
Soumya: actually the cloud is only used to hold the data and templates, the rest is handled in the edge
14:09:54 [dsr]
He points to the paper referenced at the bottom of slide 11. This explains everything.
14:11:09 [dsr]
Soumya: the only thing that goes to the cloud is sensor type and domain
14:12:03 [dsr]
We could do the processing in the cloud, but android devices like tablets are powerful enough for the kinds of tasks we’re looking at.
14:12:21 [dsr]
The cloud would be good for analysing very large amounts of data
14:12:43 [katsu]
katsu has joined #wot
14:12:48 [dsr]
Question about vehicles
14:13:03 [kaz]
s/Can you explain this further?/And those sensors A and B know their own capability, i.e., A is thermometer for human body and B is thermometer for room temp. So they have some memory and remember their capability. Right?/
14:13:14 [kaz]
s/[scribe missed reply]/right./
14:14:11 [dsr]
The data is key to enabling new services
14:14:31 [dsr]
Topic: Valentin Markus Josef Heun of MIT: Reality Editor project
14:14:52 [kaz]
s/synchronisation across a group of devices?/synchronization across a group of devices? Sometimes we want to synchronize multiple devices depending on the application./
14:15:09 [dsr]
Joerg introduces Valentin
14:15:28 [kaz]
s/here you can have any number of devices./yes, that is a challenge. here you can have any number of devices./
14:15:45 [dsr]
Valentin: I am a PhD student at the MIT Media Lab.
14:16:14 [dsr]
I did a degree in design and am now working on computer science and bridging the two areas
14:16:48 [dsr]
The IoT area is particularly interesting in respect to the human machine interface.
14:17:04 [dsr]
My thanks to Johannes for inviting me to talk today.
14:17:33 [dsr]
I will talk about an augmented reality interface to the real world.
14:17:45 [kaz]
present+ Joerg_Heuer(Siemens), Dave_Raggett(W3C), Johannes_Hund(Siemens), Joao_DE_Sousa(Bosch), Victor)Charpenay(Siemens), Valentin_Heun(MIT_MediaLab), Daniel_Peinter(Siemens), Taki_Kamiya(Fujitsu) present+ Matthias_Kovatsch(Siemens), Soumya_Kanti_Datta(Eurecom), Kazuaki_Nimura(Fujitsu), Ryuichi_Matsukura(Fujitsu), Kaz_Ashimura(W3C) present+ Toru_Kawaguchi(Panasonic), Katsuyoshi_Naka(Panasonic), Kazuo_Kajimoto(Panasonic), Yoshiaki_Ohsumi(Panasonic), Yingying_Chen(W3
14:17:53 [dsr]
He shows a smart phone for controlling a smart home.
14:18:29 [kaz]
present: Joerg_Heuer(Siemens), Dave_Raggett(W3C), Johannes_Hund(Siemens), Joao_DE_Sousa(Bosch), Victor)Charpenay(Siemens), Valentin_Heun(MIT_MediaLab), Daniel_Peinter(Siemens), Taki_Kamiya(Fujitsu)
14:18:34 [dsr]
Will the IoT machines just chat together or do we want to stay in control.
14:18:42 [kaz]
present+ Matthias_Kovatsch(Siemens), Soumya_Kanti_Datta(Eurecom), Kazuaki_Nimura(Fujitsu), Ryuichi_Matsukura(Fujitsu), Kaz_Ashimura(W3C)
14:18:55 [kaz]
present+ Toru_Kawaguchi(Panasonic), Katsuyoshi_Naka(Panasonic), Kazuo_Kajimoto(Panasonic), Yoshiaki_Ohsumi(Panasonic), Yingying_Chen(W3C), Sebastian_Kaebisch(Siemens), Louay_Bassbouss(Fraunhofer_FOKUS), Claes_Nilsson(Sony)
14:19:01 [dsr]
Right now there are a huge number of maps for controlling IoT services, it is completely overwhelming.
14:19:08 [dsr]
s/maps/apps/
14:19:31 [dsr]
How can we recover the relative simplicity of the real world.
14:20:38 [dsr]
We need a way that ordinary people can cope with. Terminals and lots of arkane commands won’t work. Graphical user interfaces were an improvement.
14:21:10 [dsr]
We need to associated icons on the apps with the real world devices, e.g. a door handle, light switch or thermostat
14:22:14 [dsr]
He shows a video of a card with a sensor. The augmented reality display adds a computer generated display that appears to be attached directly to the card
14:23:32 [dsr]
He shows several other examples where human interaction with physical objects drives the human machine interface shown in the augmented reality display.
14:24:14 [dsr]
He asks how can we balance virtual/physical object interaction?
14:24:59 [dsr]
When you buy a product (e.g. a toaster) you first learn how it is operated. You can then set it up to meet your needs
14:25:30 [dsr]
Much less interaction is needed once the set up phase is done
14:26:29 [dsr]
e.g. a car radio where you preset the buttons to your favourite stations
14:27:21 [dsr]
Spatial interaction with physical objects exploits your spatial memory
14:28:14 [dsr]
End user programm is way too complicated. This is why we need to machines to talk to each other and learn from us
14:29:02 [dsr]
Question: you’re switching from operation to programming, …
14:29:15 [dsr]
Answer: let me explain as I continue
14:30:39 [dsr]
For the automotive industry, it takes 5 years to get to market, so they need to predict where to aim for in 5 years time. This is hard.
14:31:24 [dsr]
We need an abstraction layer to relate devices and enable them to talk to each other.
14:32:36 [dsr]
Each physical device has a number of components that you can interact with.
14:33:02 [dsr]
These can be mapped into numeric parameters
14:33:48 [dsr]
He talks about one device without a timer being connected to another device to use that device’s timer.
14:34:53 [dsr]
Many IoT devices commit you to handing control to a cloud based service.
14:35:36 [dsr]
It would be nice to allow users ton retain control and change the service as desired.
14:37:09 [dsr]
In a video of demos, each device has a 2D bar code that the smart phone can used to identify how to talk to it. This makes it easy to create new augmented reality user interfaces for these devices.
14:37:44 [dsr]
s/2D/generalisation of a 2D/
14:38:49 [dsr]
The project is implemented entirely on open web standards, e.g. HTTP, WebSockets, JSON, HTML5, JavaScript
14:40:15 [dsr]
He cites the recent news stories of NEST ending support for earlier devices turning them into useless objects.
14:40:35 [dsr]
We need to give users power to control their things
14:41:13 [dsr]
s/can used/can use/
14:42:03 [dsr]
He notes that the devices use multicast broadcasting over UDP.
14:42:35 [dsr]
Each device holds its own description
14:44:31 [dsr]
The reality editor uses IFRAMEs to project web pages onto the physical scene
14:45:25 [dsr]
More details on OpenHybrid.org
14:45:55 [dsr]
Questions:
14:46:08 [dsr]
Sebastian: where is the semantics, that wasn’t clear to me
14:47:50 [dsr]
Valetin: the work comes from the user perspective, semantics are more important in dynamically changing environments
14:48:36 [dsr]
Joerg: you shows how to define behaviours for combinations of physical objects. This will need semantic info to scale up
14:48:55 [dsr]
Valetin: I am exploring this in my thesis work
14:49:40 [Claes]
present+ Claes_Nilsson
14:49:50 [dape]
dape has joined #wot
14:50:07 [dsr]
Johannes: your work relates to things we’ve been thing of at Siemens, e.g. how to decompose things, and how to model them
14:50:55 [dsr]
For example, contrasts between properties and actions, and processes that last for some extended time period
14:52:30 [dsr]
Joao Sousa: how do you cope with different people being confused by how things have been set up, or when you come back to something after a period in which you’ve forgetten what you did earlier
14:52:59 [dsr]
Valentin: the behaviour is not stored in your smart phoen
14:53:08 [dsr]
s/phoen/phone/
14:55:01 [dsr]
The domain effects what kinds of interactions make sense, i.e. are they safe or would they cause a risk of harm
14:56:22 [dsr]
Joao: what’s the implementation architecture?
14:56:47 [dsr]
Valetin: the bar code for each device identifies a URI on a web server for apps to talk to
14:59:18 [dsr]
Valetin’s contact info: heun@media.mit.edu
15:00:13 [dsr]
We thank Valentin and start a coffee break of 30 mins
15:00:30 [dsr]
rrsagent, make minutes
15:00:30 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/04/11-wot-minutes.html dsr
15:29:25 [dsr]
dsr has joined #wot
15:29:45 [dsr]
Topic: Joao Sousa (Bosch): BEZIRK Platform
15:31:03 [dsr]
Joao introduces himself.
15:31:49 [dsr]
I’ve been with Bosch since 2012. 16 years ago I was working on connected things at Carnegie Mellon, …
15:32:01 [ohsumi]
ohsumi has joined #wot
15:32:13 [dsr]
Zirk comes from the German world for circle
15:33:06 [dsr]
you can also use the sense of machines that have gone berserk! :-)
15:34:20 [dsr]
He mentions a story about a garage door service where customers were shocked to be told not to use their doors for the 4 hours during which the software upgrade was being applied!
15:34:49 [dsr]
Many current devices just talk to their vendors own service, i.e. each vendor operates in its own silo
15:35:09 [dsr]
Little incentive for sharing data beyond the silo
15:35:42 [dsr]
Some data is meant to be shared, others is private and not for sharing
15:36:46 [dsr]
There are concerns about leakage as different info sources are combined to build strongly identifying models about you.
15:37:29 [dsr]
Amazon uses cloud based speech processing, so now Amazon can listen to what’s happening in your home!
15:39:39 [dsr]
Other examples include Jabra (pulse rate), SleepIQ (snoring) and ToTo toilets that perform real-time analysis of bodily wastes - that info would be valuable to insurance companies, This is an unprecedented level of risk to privacy
15:40:03 [dsr]
We’re interested in allowing users to reclaim boundaries of privacy
15:40:28 [dsr]
We do this with what we call “spheres”
15:41:31 [dsr]
Communication between spheres is via “pipes” - these are requested by services and authorised by users.
15:41:53 [dsr]
Spheres of trust are boundaries of confidentiality
15:44:44 [dsr]
It is perhaps unreasonable for a sensor/appliance to be burdened with being a peer on the Internet.
15:45:14 [dsr]
We need good APIs to enable lots of local processing.
15:47:16 [dsr]
IP addresses, Geolocation and topic labels are ways of identifying who can receive messages.
15:47:36 [dsr]
s/topic/semantic topic/
15:47:42 [dsr]
s/Geo/geo/
15:48:41 [dsr]
He notes that Bosch have cameras that have embedded face recognition ...
15:49:15 [dsr]
This can be used to verify that someone is present
15:49:52 [dsr]
A smart phone can verify its owner is present and operating that device
15:51:22 [dsr]
Bezirk supports directed messages that are sent to a named end-point, and pub-sub models where senders direct messages to parties interested in a given semantic address
15:51:56 [dsr]
The latter can include the geolocation, perhaps expressed semantically rather than as lat/long
15:52:54 [dsr]
Confidentialy spheres of trust are useful socially for privacy and technically for scope and scale.
15:53:42 [dsr]
Joao notes that model interchange protocols are key
15:55:23 [dsr]
He describes context sensitive preferences, e.g. where one person values a warm room, or how strong someone likes their coffee, which might depend on the time of day etc.
15:56:13 [dsr]
IoT services should be able to learn and apply people’s preferences and to balance different people’s preferences where there is a potential conflict
15:58:18 [dsr]
As people interact with devices, the devices advertise the interactions with their users. A personal device like your smart phone can then discover other nearby devices and program them accordingly
15:58:36 [dsr]
Joao cites stepping into a rental car or into a hotel room as examples
16:00:09 [dsr]
Bosch have worked on one protocol for observations of user behaviour and another for requesting user profiles.
16:00:40 [dsr]
They’ve used a subset of the W3C semantic sensor network ontology
16:01:29 [dsr]
They want to publish the SDK for this work
16:01:41 [dsr]
and open source the implementation
16:02:59 [dsr]
s/profiles/profiles with information restricted to designated topics/
16:03:25 [dsr]
Questions:
16:03:41 [dsr]
Sebastian: how do you describe actuators?
16:04:02 [dsr]
Joao: the observation protocol is about learning behaviour
16:04:37 [dsr]
Devices may combine sensing and actuation roles
16:05:08 [dsr]
Actuation exploits the personal profiles protocol (named penguin)
16:05:28 [dsr]
Sensors just broadcast observations using the protocol named dragonfly
16:06:27 [dsr]
A user agent combines knowledge inference, knowledge modelling and knowledge filtering.
16:07:08 [dsr]
We need a conflict resolution policy for resolving conflicts between rules
16:09:19 [dsr]
If every one’s phone is their user agent, then these agents need to collaborate to resolve conflicts due to different rules for different people.
16:10:58 [dsr]
The slide also allows for resolution in the device being controlled, or perhaps its agent.
16:12:22 [dsr]
The approach allows users to ask why some preference wasn’t applied
16:13:58 [dsr]
Joerg: there could be thousands of people operating devices, so scaling becomes a challenge
16:14:51 [dsr]
It is important to find simple abstractions if we are to succeed
16:16:29 [dsr]
Louay: clients broadcast messages, how do you deal with the management of the spheres of trust
16:18:09 [dsr]
slides to be made public
16:20:54 [kaz]
i/Louay:/Kaz: in that case, maybe we could have multiple levels of manager of interactions, e.g., home level, city level and country level/
16:21:20 [kaz]
i/Louay:/Joao: possibly. let's talk about that offline./
16:21:29 [kaz]
i/Louay:/kaz: yes./
16:22:12 [kaz]
topic: Implementation work on web of things servers and gateways (Dave Raggett)
16:18:09 [kaz]
scribenick: kaz
16:24:58 [kaz]
-> https://www.w3.org/WoT/IG/wiki/images/2/25/Arduino-server-dsr-2016-04-11.pdf Dave's slides
16:38:06 [katsu]
katsu has joined #wot
16:48:18 [kaz]
soumya: lot of engineering challenges
16:48:31 [kaz]
... p24, semantic constraints
16:48:38 [kaz]
... what kind of constraints?
16:48:44 [kaz]
dsr: software and power
16:48:55 [kaz]
... maybe energy is a good metric
16:49:14 [kaz]
soumya: you can run it on a smartphone?
16:49:23 [kaz]
dsr: very powerful environment
16:49:36 [kaz]
... what if there is energy constraint
16:49:44 [kaz]
claes: very first slide
16:49:58 [kaz]
... p2
16:50:16 [kaz]
... what is the gateway?
16:50:30 [kaz]
dsr: some powerful device than arduino
16:50:45 [kaz]
... and can talk multiple protocols
16:51:50 [kaz]
... addressing issue is regarding low-layer stuck
16:52:00 [kaz]
sebastian: T2T interaction
16:52:13 [kaz]
... need to think about that
16:52:52 [kaz]
dsr: lot of opportunity for different topologies
16:53:21 [kaz]
claes: direct p2p connection?
16:53:29 [kaz]
dsr: depends on the hardware capability
16:53:47 [kaz]
joerg: constraints with device capability
16:54:18 [kaz]
... controller for communication or just sensing?
16:54:30 [kaz]
... scale from small to large
16:54:46 [kaz]
... we should follow the idea
16:54:55 [kaz]
dsr: there is a rank
16:55:20 [kaz]
... trying to understand what the architectural requirements
16:55:39 [kaz]
valentin: lot of discussions by Intel
16:56:02 [kaz]
... esp. regarding Arduino
16:56:24 [kaz]
dsr: insecure devices and secure devices
16:56:55 [kaz]
valentin: complicated to consider device-to-device infrastracture
16:57:11 [toru]
toru has joined #wot
16:57:36 [kaz]
joao: distinguish Things?
16:57:56 [kaz]
dsr: the question is how to expose the application
16:58:07 [kaz]
... had lots of discussion during previous meetings
16:58:47 [kaz]
... actions may pass a value when they're invoked
17:00:08 [kaz]
joerg: we're quite behind, so would propose we have lunch now and after that let's do the EXI session
17:00:22 [kaz]
... we'll have the demo session at another room
17:00:44 [kaz]
... so we'd have brief introduction for that later
17:00:56 [kaz]
[ lunch ]
17:01:38 [kaz]
rrsagent, draft minutes
17:01:38 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/04/11-wot-minutes.html kaz
17:45:17 [taki]
taki has joined #wot
17:47:14 [katsu]
katsu has joined #wot
18:00:21 [katsu]
katsu has joined #wot
18:02:02 [toru]
toru has joined #wot
18:03:36 [dsr]
dsr has joined #wot
18:04:36 [yingying]
scribe: yingying
18:04:39 [dsr]
Topic: Takuki Kamiya & Daniel Peintner: EXI for WoT
18:04:57 [yingying]
Topic: Takuki Kamiya & Daniel Peintner: EXI for WoT
18:05:21 [Claes]
Claes has joined #wot
18:06:02 [yingying]
Takuki shows the slides. He explained the background of XML.
18:07:11 [yingying]
Takuki: there are use cases that XML can not deal with. We need to handle these use cases.
18:08:55 [yingying]
...we saw 2 factors in use cases. One is use of schema. If there is schema, the schema can be totally or partially defined. Sometimes you could not find schema.
18:09:08 [yingying]
...another factor is the use fo compression.
18:10:24 [yingying]
...EXI design is schema-informed. schema is optional. compression is optional.
18:11:01 [yingying]
...this diagram shows the baseline grammar is used when informed no schema.
18:13:13 [yingying]
...this is some encoding result.
18:14:01 [yingying]
...another aspect to consider is the processing efficiency. EXI is good.
18:14:09 [ohsumi]
ohsumi has joined #wot
18:16:45 [yingying]
...about channeling, markup goes into structure channel and value goes to normal channel. This way EXI does better than gzip.
18:17:17 [yingying]
s/gzip/xml+gzip/
18:17:57 [yingying]
...about implementations, the top three are open source you can use. the bottom 2 are commercial tools.
18:18:05 [yingying]
...this is my part presentation.
18:18:26 [yingying]
Daniel: I will try to take over.
18:21:33 [yingying]
...what would people get from EXI rather than JSON?
18:22:27 [yingying]
...effiiency, more compact, reuse for XML and JSON.
18:22:52 [yingying]
...this is a simple example comparing JSON and EXI for JSON.
18:23:16 [yingying]
s/comparing/transforming/
18:24:34 [yingying]
...this is a measurements we did today. EXI4JSON is much better than JSON.
18:25:31 [yingying]
...this is just for JSON using a very generic schema.
18:27:20 [yingying]
...extended string: EXI strings , shared Strings, split strings.
18:29:08 [yingying]
...the WG just goes into a public WG. Here are the links for your convenience.
18:29:15 [yingying]
...comments or questions?
18:32:56 [Claes]
Claes has joined #wot
18:35:01 [yingying]
...I put the demo link here.
18:35:07 [yingying]
@pointer
18:36:00 [yingying]
Daniel: left side is JSON, right side is the binary.
18:38:12 [yingying]
Dave: what is the timeline of the WG?
18:39:16 [yingying]
Takuki: Now working on JSON/XML for WoT. CSS compaction just started.
18:40:58 [yingying]
Jeorg: Thank you.
18:41:42 [yingying]
...next topic is a WoT project from Matthias.
18:41:57 [taki]
taki has joined #wot
18:42:02 [yingying]
Topic: Getting Started with a WoT Project
18:43:45 [yingying]
Matthias: there are some of links for documents: architecture and current practice.
18:44:06 [yingying]
...wiki for preparation of next F2F plugfest.
18:44:28 [yingying]
...last ones are plugfest projects available.
18:45:32 [yingying]
...first, Kajimoto-san will introduce the architecture, I will talk about WoT interface, Sebastian will introduce the TD and Johannes will introduce the @1.
18:45:58 [yingying]
Kajimoto: this is an overview of the architecture for WoT servient.
18:47:00 [yingying]
...App script provides accesss to and control of internal data of devices.
18:47:14 [yingying]
...TD is very important to discover the thing.
18:49:17 [yingying]
...simple case: browser knows the semantics of WoT device by TD so that the brouser app calls the client API through WoT API.
18:49:48 [yingying]
...servient will call the corresponding API according to what is requested.
18:50:19 [yingying]
...some powerful devices can have the servient on itself.
18:50:38 [yingying]
...WOt Servient can also be on the smartphone.
18:51:37 [yingying]
s/WOt/WoT/
18:51:51 [yingying]
...this is a WoT servient on smart home hub.
18:52:48 [yingying]
...this is an example of WoT servient on cloud.
18:55:24 [yingying]
Matthias: let's look at the WoT API.
18:56:30 [yingying]
...above the WoT interface, we have the protocol binding. we can have multiple protocol bindings. Above the protocol bindings is the resource model.
18:57:17 [yingying]
...the servient can have the client role or server role or both.
18:58:07 [yingying]
...if you want to participate the plugfest, you need to figure out what is the role of your device.
18:58:36 [yingying]
...then select the platform that is suitable.
18:59:13 [yingying]
...client role: Angular.js and web browser.
19:00:45 [yingying]
...server role: Sensor/actuator: Arduino, ESP8266,mbed; devce simulators: Node.js.
19:01:02 [yingying]
...for proxy, not yet. Welcome to contribute.
19:01:18 [yingying]
...then pick up the protocol you want to support.
19:02:43 [yingying]
...HTTP, CoAP. for MQTT, eclipse has a project mosquitto.
19:03:12 [yingying]
Sebastian: Things Description.
19:03:14 [dsr]
dsr has joined #wot
19:04:07 [yingying]
...I want to use a WoT servient. I want to know several questions. The answer is in the TD>
19:04:19 [yingying]
s/TD>/TD/
19:04:55 [yingying]
...based on the information in TD, the T2T communication could be set up.
19:05:39 [yingying]
...describe your thing based on JSON-LD.
19:06:14 [yingying]
...how does the TD look like? Here is an example.
19:08:52 [yingying]
...We need the TD context, which has to be standardized by W3C WoT WG.
19:10:58 [yingying]
...There might be external context defined by other organization to enrich the definitions with additional semantics. This is not W3C scope.
19:13:07 [yingying]
...How to create a TD?
19:13:10 [yingying]
-> Takuki
19:13:25 [yingying]
s/-> Takuki//
19:13:35 [yingying]
-> http://w3c.github.io/wot/current-practices/wot-practices.html#sec-td
19:13:57 [yingying]
Kaz: hierarchy of the TD?
19:14:43 [yingying]
Victor: control other things?
19:14:55 [yingying]
Michael: maybe just a collection of things.
19:15:28 [yingying]
Victor: there is convention in JSON-LD.
19:15:51 [kaz]
i/control/Michael: would discuss that point/
19:16:18 [yingying]
Michael: That is what I'm just looking for. What we should do?
19:17:04 [yingying]
Dave: do we have defauls?
19:17:34 [yingying]
Michael: there could be things in one level or multiple levels.
19:17:40 [kaz]
s/defauls/defaults/
19:18:07 [yingying]
...recursively or whatever.
19:18:33 [kaz]
sebastian: would talk about the details during the breakouts
19:18:39 [kaz]
kajimoto: agree
19:18:53 [yingying]
...about the URI, do we have a better way to organize them instead of just the real order?
19:19:36 [yingying]
s/URI/media types/
19:19:48 [kaz]
s/...about/Michael: about/
19:20:31 [yingying]
Matthias: the question could be a topic for breakout session.
19:20:38 [kaz]
matthias: exactly the topics for the breakouts
19:20:55 [kaz]
s/matthias: exactly the topics for the breakouts//
19:34:24 [Kajimoto__Kazuo]
Joao: Use case "Tell me the temperature very near around me", then current things description is static, not dynamic semantics description, so current TD cannot represent such semantics.
###
19:34:24 [Kajimoto__Kazuo]
Joao: Use case "Tell me the temperature very near around me", then current things description is static, not dynamic semantics description, so current TD cannot represent such semantics.
19:25:52 [kaz]
kaz: basically Joao suggests we should think about concrete use case for each TD sample, and I'd agree
19:26:10 [kaz]
... we should generate concrete use case description for each TD sample
19:26:26 [kaz]
kajimoto: @@kajimoto
19:26:45 [kaz]
s/@1/Scripting API/
19:26:47 [dape]
dape has joined #wot
19:26:56 [yingying]
Johannes: Scripting API.
19:27:11 [toru]
toru has joined #wot
19:28:10 [yingying]
...how do we standardize the scripting API.
19:29:16 [yingying]
...let's look into the thing for the 3 kinds of APIs: client API, Server API and Physical API.
19:30:06 [yingying]
...why? to avoid fragmentation,...
19:32:46 [yingying]
...from app development viewpoint, thing vendor
19:33:03 [yingying]
...I'll show example of scripting APIs.
19:33:58 [Karen_]
Karen_ has joined #wot
19:34:54 [yingying]
Johannes showed the examples for client API, server API and Physical access.
19:35:38 [kaz]
s/@@kajimoto/Current TD is basic layer description, to represent dynamic semantics, some upper layer TD scheme is proper to be introduced./
19:36:37 [yingying]
Johannes showed an example of things discovery.
19:36:45 [yingying]
Johannes: questions?
19:37:36 [yingying]
Claes: for this plugfest, how is it supported on security consideration to access the API?
19:38:42 [yingying]
Johannes: this is an item we identified from last plugfest. Currently we don't have protocol specification on it. However, it's in our roadmap.
19:41:48 [yingying]
...we should come up with examples so that we can see what we could implement in the scripting API or Runtime.
19:42:26 [kaz]
joao: security should be handled by not applications but middleware level
19:43:39 [yingying]
Joao: Security is somehow like what is done in Java container.
19:46:01 [yingying]
[some discussion about security model]
19:50:53 [yingying]
rrsagent, make minutes
19:50:53 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/04/11-wot-minutes.html yingying
19:51:39 [kaz]
kaz: Automotive group has been discussing security use cases and clarified the need for several levels of security, i.e., OS level, middleware level, application level and data level
19:52:23 [kaz]
... also the security TF of this WoT IG has been discussing security need as well, you're welcome to join the discussion on the mailinglist
19:52:40 [kaz]
... and again I completely agree with you we should clarify security use cases as well
20:07:54 [yingying]
[tea break]
20:19:32 [yingying]
Topic: Ian Skerrett: "Eclipse IoT: Open Source Building Blocks for IoT Developers"
20:21:19 [toru]
toru has joined #wot
20:21:20 [dsr]
dsr has joined #wot
20:22:10 [kaz]
present+ Ian_Skerrett(Eclipse_Foundation)
20:24:48 [yingying]
Ian: a technology has to be open if it's widely adopted.
20:25:06 [yingying]
...there is a lot of cases and web is the best one.
20:25:35 [yingying]
...still a lot of silos in IoT which is frustrating.
20:26:38 [yingying]
...look at the MQTT by IBM and other in 1999. around 2011-2012, it was announced open source.
20:27:02 [yingying]
...MQTT is successful scenario in IoT.
20:27:13 [yingying]
...open HW is a key enabler for IoT.
20:27:49 [yingying]
...5-7 years ago, no open HW available. YOu need to buy the board.
20:28:52 [yingying]
...also open source is another key enabler for IoT.
20:29:14 [yingying]
...it allows you download thing and just try.
20:31:15 [yingying]
...this is a typical IoT Architecture.
20:32:11 [yingying]
...MQTT, @3, and oneM2M are the open standards we implemented.
20:33:10 [yingying]
...MQTT adoptions: Amazon, MSFT Azure, IBM Bluemix. Last week Arduino announced it adopts this model.
20:33:39 [yingying]
...bar chart about the protocol in use in IoT.
20:34:57 [yingying]
s/@3/CoAP/
20:35:11 [ohsumi]
ohsumi has joined #wot
20:35:52 [yingying]
...we also have IoT GW services. IBM has four implementation of MQTT.
20:37:20 [yingying]
...This is the framework Kura provides.
20:38:11 [yingying]
...We have the building blocks and then we have the IoT Solution Framework.
20:38:43 [yingying]
...in Home automation industry, it's a mess. Hundreds of statndards.
20:40:08 [yingying]
...eclipse smarthome is adopted by many companies.
20:42:05 [yingying]
...We will move on to be a server.
20:43:26 [yingying]
..Haukbit and Homo are what we have as the IoT server platform. Redhat and bosch adopt it.
20:44:36 [yingying]
...Vorto's goal: co-generators for different platforms.
20:45:18 [yingying]
...information about our community: 21 projects, 150+ developers.
20:46:46 [yingying]
...we have a portal and sandbox servers.
20:47:03 [yingying]
s/oneM2M/LWM2M/
20:47:32 [yingying]
...we are look for people to get involved.
20:47:40 [yingying]
...that's it. any questions?
20:48:04 [yingying]
Kaz: is it OK to publish the slides to w3c wiki page?
20:48:08 [yingying]
Ian: yes.
20:49:25 [yingying]
Matthias: we could add the link of implementation to our landscape.
20:49:57 [yingying]
Dave: test suite?
20:50:26 [yingying]
Ian: MQTT has almost mature test suite.
20:51:03 [kaz]
i|we could|Kaz: we might want to add the information in this slides (=Eclipse IoT and Vorto) to our Technology Landscape document at: w3c.github.io/wot/landscape.html|
20:51:38 [kaz]
s/our landscape/the protocol section of our landscape/
20:51:53 [kaz]
s/the link/a link/
20:52:40 [yingying]
Johannes: license, patent?
20:54:14 [yingying]
rrsagent, make minutes
20:54:14 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/04/11-wot-minutes.html yingying
20:55:55 [yingying]
Joerg: balance between demo and plugfest. this time we donn't add new feature.
20:56:28 [kaz]
i/open standards we made/open standards we implemented/
20:57:02 [kaz]
i/balance/topic: Plugfest and Demos/
20:57:40 [yingying]
...I would ask Johannes to give you a framework.
20:58:43 [yingying]
Johannes: we use this table to collect people's contribution.
20:59:02 [kaz]
-> https://www.w3.org/WoT/IG/wiki/F2F_meeting_2016,_April,_11th_-_13th,_Montreal,_Canada#Participation Plugfest participation table
21:01:29 [yingying]
...what is the Thingweb projects
21:03:24 [yingying]
...we are just providing some tools for people to join the WoT development.
21:05:27 [yingying]
...these are findings in this F2F.
21:06:55 [yingying]
...comments or questions?
21:07:21 [yingying]
Joao: snake?
21:09:47 [yingying]
Joerg asked people to introduce what they implemented.
21:10:00 [yingying]
Dave: mDNS gateway
21:11:14 [yingying]
Matthias: CoAP binding implemented.
21:12:40 [yingying]
Louay: SSDP support for thing exposure and discovery.
21:14:05 [yingying]
...for client, I use the tool Node-RED .
21:15:29 [kaz]
-> https://github.com/w3c/wot/blob/master/TF-DI/DiscoveryFlowsAndBindings.md Discovery Flows
21:15:38 [yingying]
Sebastian: T2T interaction based on common plugfest vocabulary.
21:44:17 [kaz]
(discussions on the TD processing flow)
21:45:01 [kaz]
note /onOff and /toggle are device dependent commands translated from the TD for air conditioner and electric stove
21:46:35 [kaz]
michael: where the TD comes from?
21:48:03 [toru]
toru has joined #wot
21:48:32 [kaz]
valentin: what about generic description for air conditioner, etc.?
22:01:37 [dsr]
dsr has joined #wot
22:26:14 [yingying]
rrsagent, make minutes
22:26:14 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/04/11-wot-minutes.html yingying
22:29:11 [kaz]
[ Open Day adjourned ]
22:29:11 [kaz]
Meeting: WoT-IG Open Day/Plugfest
22:29:30 [kaz]
rrsagent, draft minutes
22:29:30 [RRSAgent]
I have made the request to generate http://www.w3.org/2016/04/11-wot-minutes.html kaz