<inserted> scribenick: taki1
Sebastian: I also say to hello to
everyone.
... I would like to intriduce Michael Lagally.
... we have two chairs.
Lagally: I am very pleased to be
here.
... I worked on Architecture, TD, etc. Joined over a year
ago.
... we want to discuss next step, gather new ideas.
... Kaz wored really hard.
Kaz: I am the team contact for WoT
WG.
... Thank you very much for coming.
Lagally: welcome Matthias
Kovasch.
... Welcome Michael McCool.
... Welcome Zontan.
... Welcome Michael Koster.
Sebastian: you are aware that they
are main players.
... I give you some thoughts.
... who joined the first workshop?
... it appears half of the audience joined
... it was 4-5 years ago.
... it was a great event.
... we reached the first milestone.
... this workshop should create new roadmaps.
lagally explains the timeline slide...
Lagally: there are two groups.
... IG and WG.
... we had a demo session. there is demo next room today too.
... working group is working on specifications.
... now we are here in 2nd workshop.
... to get things compiled, how TD can be useful in new
scenarios.
... and define charter for the next 2 years.
... we are planning new task forces depending on new ideas.
Kaz explains workshop statistics.
Kaz: Participants, open day 140,
workshop 61
... organizations 60 adn 46.
... new comers 25 and 14.
... new comers are very important.
Sebastian talk about logistics...
<rzr> http://irc.w3.org/?channels=#wotws is the right link
<rzr> not w3c.org
Lagally is talking about agenda...
Lagally: morning, welcome session.
briefing from Jeff.
... then usecases deployments.
... and tooling and implementations.
... afternoon contines, coffee break. then security and
provacy.
... wrapup at the end of the day.
... seond day. keynote speech from Mr. Chinn Hwa Lim
... Future work, collaboration with SDO in afternoon.
... next step and wrap up at the end of 2nd day again.
Sebastian: social event
tonight.
... we can go to beer garden.
... it is *not* sponsored.
... Where we go, I will let you know later.
... thank you again. yesterday was great, and let's continue.
Jeff: Good morning.
... thank you Sebastian.
... WoT made progress.
... yesterday was a celebration.
... congratulations.
... today is about doing some hard work.
... to figure out what to do next.
... please take agenda seriously.
... learn from each other.
... what are most important for us to work next.
... and learn what people are doing.
... including liaisons with IoT-oriented organzations.
... thank you.
Matthias: thank you
Matthias explains what WoT has achieved...
Matthias: there were many IoT
eco-systems.
... unfortunately there were IoT silos.
... could not interoperate even when they used the same
protocols.
... WoT enables applications.
... by simplifying integration.
... there was internet, and applications on top. This is analogy.
WWW did good job to interconnect applications.
... IoT is in similar situation.
... IP is common, but on top IP, IoT eco-systems are
different.
... We wanted to use Web technology.
... we defined building blocks.
... to interconnect silos.
... Web Thing has interaction model with narrow waist model.
... Thing description is the centerpiece.
... scripting api is working note.
... we should gather more experiences.
... security concerns. security and privacy guidance for secure
WoT.
... This is high overview.
Lagally talks about WoT architecture...
Lagally: cloud service can be a
Thing.
... edge can be a Thing. mobile devices can be a Thing.
... Things can be used/exposed,
... Zigbee, etc. many protocols can be used.
... appliances, fridges, lamps. industry devices.
... virtual device can be a Thing.
... as long as it can be described by TD.
... There is Interaction affordances. properties, actions and
events.
... event notifies events.
... Hypermedia control. Can relate things by links.
... forms can describe how to submit requests to Things.
... architecture consists of several building blocks.
... TD contains information model, vocabulary, JSON-LD
representation.
... Binding Templates is for integrating various protocols.
... Scripting API. ECMAScript-based API
... security and privacy guidelines. cross-cutting security
guidelines.
Lagally explains what is TD...
Lagally explains what is protocol bindings are...
Lagally talks on communcations model between Thing and Consumer...
Lagally: TD is the lingua franca.
Lagally talks on indirect communications through intermediary...
Lagally: typically it is a proxy.
home network has firewall.
... servient in the middle can also aggregate many things.
... architecture itself is flexible.
Sebastian introduces Thing Description...
Sebastian talk on motivation behind TD...
Sebastian: automation devices are
often accompanied with paper documentation.
... you have webpage manual.
... and also code-snippets.
... what is the name, URI? Functionality, what kind of data?
Engineers need to know.
... protocols, serialization, security requirements... Engineers
need to know.
... TD should provide those information.
... People start with landing HTML page and can interact with Web
application.
... TD is the same for WoT.
... TD can describe many kinds of devices.
... TD is based on JSON, consistent with JSON-LD.
... TD spec defines very small set of terms.
... title, id, created time, and other metadata.
... TD contains security schemes.
... TD has property, action and events.
... TD has datatype system borrowed from JSON-LD.
... TD provides context extension.
... If you want, you can add additional term definitons such as
iot.schema.org.
... This is a powerful constructs, and allows to use existing
knowledge.
... TD allows use of links.
... This was TD internal.
Question: addition of context, isn't it metadata?
Matthias: whole TD is metadata.
Question: you can plugin additioal semantics.
Sebastian: Yes, exactly.
... e.g. industry-specific terms.
McCool: we use extension for protocol binding as well.
Question: agreement is necessary for semantics.
Sebastian: Yes.
Joshue modular accessibility semantics, for example.
McCool: we should incubate semantic
modules.
... for now core vocabulary is very slim.
Matthias: bottom-up semantics and top-level semantics.
Sebastian continues on explaining protocol binding...
Sebastian: we are open to using other
protocols.
... context extention can play a role here as well for changing
parameters of protocols.
... It was a brief introduction to TD.
Zoltan starts introducing Scripting API...
Zoltan: the work started in IG.
... in Working group, used GitHub to develop working group
Note.
... it is API for node.js. Not really for browser. This is an
issue.
... Web has scripting API. It is easy to use for everyone.
... half of all web develpers develops JavaScript programs.
... webpage, URL, HTML. Thing, URI, WoT Scripts. there are
analogies.
Zoltan explains Scripting API's role in architecture.
Zoltan: Scripting API is for
describing behaviours.
... scripts can run on cloud, gateway or on devices.
Zoltan explains three approaches....
Zoltan: no exposed API, simple API
(e.g. Dave Ragget's proposal) and current API.
... current API follows TD specification closely.
... we will discuss more tomorrow.
... I also like simple API as well.
... Ege tried other languages.
... we documented everything.
Jeff: is it a matter of fashion? plus and minuses. what is the fasion? how do you decide what is best?
Zoltan: we listen to people.
Matthias: people prefer different approaches depending on who you ask.
Jeff: we can describe which community should use which styles.
Matthias: some people also say they do not need scripting API, some others suggest simplification.
Zoltan: you need to be aware of other
languages.
... time will tell.
Kaz: possible impact on e.g. NHK
broadcasting company. They used updated scripting.
... we also need to talk with those industry guys.
McCool talk on security and provacy guidelines...
McCool: WoT is descriptive. we are
not defining new security mechanism.
... each document has security and privacy section.
... TD spec has one section as well.
... we created security and provacy guideline document.
... there is also security testing plan document.
... best guideline is evolving.
... we need to constantly update this separate guideline
document.
... TD can describe insecure devices as well.
Kathy: security is out of band of
TD.
... secure-wiress connection, for example.
... therefore, very confusing.
McCool: We call it security schemes.
TD is about describing how to access a Thing.
... to help developers.
Kathy: why we need it?
McCool: We had discussion.
Kathy: security is somewhere else.
McCool: TD should describe some information.
Lagally: we have dedicated security discussion. FYI.
Matthias: we aee also following IETF work.
Lagally explains subsequent agendas.
Lagally: Please observe time.
... we are 37 minutes late.
Dom: web of all other things. CPG,
apparel, etc.
... I write "building the web of things".
... IoT came from researcher presentation at P&G .
... company connects billion things.
... majority is everyday thing. CPG goods, bluetooth devices,
etc.
... every thing can have digital identity.
... the other end there is enterprise.
... in apparel, counterfits are problems.
... samsung worked on washing machine that understands what it is
washing.
... there are now smart closet, etc.
... transportation. what tracks are carrying.
... Amazon Go need to understand everything in store.
... it requires standardization.
... our company undersands needs for standardizing CPG, Apparel,
Pharma.
... GS1 well known for barcodes.
... Digital Link and EPCIS. Web identity and tracking. those two
standards are important.
... GS1 Digital Link standard. I chair this group.
... fastest standard in GS1 ever.
... it gives identity to everything.
... can fetch information from URI.
... Coca Cola produces billions of items a year. it was not
possible a couple of years.
... Now technologies changed to make it possible.
... transform dumb number into URL.
... NFC tag, for example. can carry URI.
... user resolver delivers web content for digital links.
Dom shows WOMI as GS1 DIgital link.
Dom: is it for salmon.
... QRCode structure. base url, product category, GTON, batch
number...
... If you click, it shows salmon information. where it was born,
it was put into sea, how it was harvested.
... nice story about salmon.
... this was just an example.
... There are open source tools.
... next one is EPCIS 2.0 for making track and trace first class
citizen of the Web.
... EPCIS 1.0 exists already.
... 2.0 is moving information system into the Web.
... movement of goods cab be described.
... 1.1 was based on SoAP.
... 2.0 is REST and JSON-LD.
Dom shows an example of EPCIS...
Dom: Back to W3C WoT building
bridges.
... Building bridges for all the things!
... use cases to merge the two world.
... we can print sensors. it is happening.
... questions?
McCool: privacy concerns?
Dom: One million dollar
question.
... same as smart things.
... we need framework in place.
McCool: QRCode and smart things are different in nature.
Dom: QRCode does not cause problem
unless it becomes active.
... we are working on it.
Victor: content negotiation. is it machine-readable from the URI?
Dom: Yes. JSON-LD.
... You can also use link-type. two formats are mandatory. JSON and
JSON-LD.
Victor: Bottle interact with other smart thing. How is it so?
Dom: pack of straeberry and the track. the temperature need to be set accordingly.
Zoltan: trucks have energy source.
Dom: exactly.
... Tag can be destroyed at checkout.
Question: bluetooth can do what extra?
Dom: not really.
Jeff: Did you use TD?
Dom: I have not. But it is the intention.
Question: How can we pilot?
<inserted> scribenick: taki
Kathy: SmartThing already does that.
Dom: we are waiting for WoT Recommendation ratification.
<inserted> scribenick: taki2
Dom: tag printing pricing is
shrinking.
... NFC 5 cents tag. UHF tag 1 cent. bluetooth tag is a bit
expensive.
Zoltan: NFC readers are expensive.
Dom: Every phone has one.
Lagally: Thank you.
Johannes: I was active in this
group.
... Now working in EcoG
... FTP, NNTP... survival of fittest.
... Java Applets are extinct.
... mail is now read and write in web mailer.
... Occam's razor of green field IT
... web front end, API is REST api. This is how people do
now.
... IIoT space. Web is pushed by people in this room.
... domain of silos. OPC-UA. Bacnet, ...
... vendor platform silos. gRPC, AWS IoT...
... EV charging domain: OCPP
... current version 1.6 switched to JSON over websocket.
... monitor and controls charging station.
... extension can be used.
... there are many parties involved.
... multi-stake holders
... field charging HW manufacturer automotive, site owner,
utility...
... Highly complex game. Charing car use more electricity than a
home.
... there are fleets of buses for example.
... web enables multi-stake holder system.
... promises of web.
... seamless IT integration. single signon.
... integration of payment, calendar, maps ...
... field-level integration into web is necessary.
... parking sensors. cashier, the vehicle's IVI requires
that.
... web-ecosystem. 75% of all developers are web developers.
... you want to tap into those developers.
... long-tail market. Web was about niches that everyone can come
up with.
... that makes break-through happen.
... WoT and IIoT. cross-domain integration crossing
boundaries.
... aonyone use React.js. we have react-wot implementation.
... including scripting API.
... Thank you.
Zoltan: TD. WHo writes it?
Johannes: REST API, WoT runtime.
Mobilephone uses bluetooth LE. Binding should be simple.
... It should be an effort of an hour.
Zoltan: do you plan to publish TD?
Johannes: sometimes we use internal API. other time we use public API.
Alan_B: transportation workshop. transportation and WoT. I encourage to submit position pater.
Alan: will be in September.
McCool: different of WoT vs openapi.
Johannes: we do not have TD
yet.
... I currently use swagger. WoT is similar.
... establising pattern is special in WoT.
Milan: why you need new OS?
Johannes: it is more about software
for charging.
... powerline communcation, charging station safety-oriented
protocols, every vehicles are different.
... our model is software as service.
Lagally: thank you.
Kathy: I will make demo after Ben's presentation.
Ben: I and Kathy are from
Mozilla.
... we are NPO.
... we are working on emerging technologies including IoT.
... and WoT implementation.
Ben shows mizilla IoT team...
Ben: WebThings is an open
source.
... there are gateway and framework.
... there are smart home use cases...
... different vendors, different proticols.
Ben shows gateway architecture...
Ben: front-end, back-end and
adapters.
... TLS tunneling service.
... We have pre-built images for gateways.
Ben shows gateway UI...
Ben: there us a rule engine.
... it can show logs.
... experimental voice feature.
... there is add-on for browsers.
... 30K downloads so far.
... goal is to put directly into routers.
Ben shows framework example...
Ben: challenges.
... HTTPs in local networks.
... self-signed certificate is not secure.
... there are workarounds but not ideal solution.
... W3C group HTTP on local network is working on this.
... Chalkenge 2 is HTTP on resource constrained devices.
... use of gateway. websocket is still heavyweight. CoAP is not
native supported by browsers.
... challenge 3. autentication.
... it relies on gateway.
... challenge 4. Scripting API.
... client side mimned mainly at Java Script.
... framework implement different APIs fpr each languages.
... challenge 5. declarative protocol bindings.
... in practice, WoT protocol binding is not felxible enough.
... but making TD more complex is not good.
... we recommend to use gateway.
... we provide Web Thing Description, REST API, Websocket API.
Those three documents.
... We propose to simplify TD spec, and create Thing protocol spec
for each binding.
Ben suggests charter proposal...
Ben: TD spec should be usable without
need for binding template.
... add protocol binding as another deliverable.
McCool: What should be included?
Ben: REST API should be separate.
Sebastian: TD supports the use of RDF
definition of HTTP.
... you are expecting the same for other protocols.
... they should be done in same way as HTTP.
Ben: REST support was not flexible enough in our experiment.
Sebastian: multiple resouce. what is it?
Ben: action queue. action resource,
and delete or cancel it.
... there is no way defined right now.
Kathy: desk in mountain view.
... turn on kitchen.
... you can see them turned on.
Kathy is demonstrating Mozilla WebOfThing.
Kathy: there are add-ons.
... I have a light, door-sensor, open weather map.
Kathy shows log information...
Kathy: that was my demo.
Johannes: collections are not expressable right now. we can publish a note. We can dicuss what are missing.
Ben: need for describing existing
protocols. TD gets more complex.
... we should come up with compromise.
Jeff: we cannot reach a conclusion today. we need to dicuss charter with chairs.
Matthias: we skipped some features to
see convergence.
... HATEOAS for example.
... we needed to publish core standard first.
... I hope we can settle the differences.
Ben: We tried to bridge real devices but it did not work. what is why we are making this proposal.
Lagally: ready for coffee
break?
... if you have requirements, please put them together and
submit.
McCool: we can incubate in IG.
... compromise can be the use of defaults to bridge the gap in two
approaches.
<kaz> [break till 12:25]
<zkis> scribenick: zkis
Panasonic home IoT: connected, SW defined, upgradeable.
Intend to support already connected devices in WoT abstract architecture.
Using a local/home gateway to support existing devices.
Panasonic presented a demo with a Smart home room, virtual things (simulator), a WoT client in a browser and a WoT client on Node-RED.
Panasonic exposed APIs based on WoT interaction model
One such application is HomeX which leverage Panasonic "touchpoints" in the home (all things controllable).
Showing a concept video, presenting use cases, e.g. assisted laundry program, notifying about favorite TV programs + switching on TV, multi-room music playback with user presence sensing, tips about food preparation.
Expectations on standardization: align with existing standards as much as possible, using WoT interaction model. For APIs we need domain specific vocabularies.
Some of them are covered (home appliances), others are not (audio-visual, outside home, etc).
Questions.
Question about the own API vs TD + bindings. Answer: open API and TD are complementing each other.
Question: the Panasonic API was presented, in previous presentation a REST API was mentioned; what is the similarity? Answer: yes, it's a RESTful API.
The demo yesterday was a BMW i3 connected to the cloud with a WoT connector.
Goals: abstracting vehicles, semantic annotaions on parts, interact with the many automotive domains, etc.
Today there are a lot of solutions, fragmentation is a problem.
Requirements: be able to deal with safety, complexity, legacy.
Presenting the WoT ontology used.
Data model to represent Vehicle Signal Specification (VSS) by Genivi consortium working together with W3C Automotive WG.
Semantic Sensor Network ontology, SOSA pattern / to model what is a car signal. For instance SOSA Sensor, ObservableSignal, ObservableProperty etc.
SOSA provides the classes, VSS ontology provides the signals.
A vehicle is a Thing. Signals are Properties. Actuable signals are Actions. DataSchema uses the domain Units.
SOSA does not support events, so WoT Events are not supported ATM.
Event modeling pattern is mapped to Event Ontology.
Presenting demos about TD.
Demo architecture: using the vehicle web API backend, created a TD, exposed as Thing, made simple demo Node-RED flows.
Example: when the user moved far enough from the unlocked vehicle, the lock is activated.
Lessons learned: safety-security-privacy adapted to the vehicle. Complexity needs breaking down into subdomains (each with separate TDs instead of one huge TD) with separate security aspects.
For instance infotainment, engine, HVAC, etc.
Different experts can work on each part.
All parts might have their own security scheme.
Questions.
Question: are there open issues with the security schemes described in WoT?
Answer: yes, found that out late, so you can define different schemes and then use it. But in this case splitting up the TDs makes more sense.
Question: TD for each car manufacturer; how do car manufacturers benefit from doing that?
Answer: there is no common data model or API. VSS is one solution. In the end, open specifications would help. They should agree in a core set of interactions in all APIs.
Question: what the level of maturity there is about the vehicle description (which is proprietary ATM)
Answer: it's quite early now, VSS is about 2 years now, divinding into domains is an old idea, but using the WoT TD is a relatively new thing.
Question: BMW, JLR, VW are in the same room here - encouraging there. Answer: the need is seen in the industry, pushing for WoT.
Question: on the main alignment pattern slide, what was the "mental state". Answer: stress level, mental load while driving.
Usually applications integrate devices one by one, each with separate interface. A gateway provides one integrated interface to applications.
A gateway encapsulates complexity and provides adaptors for each device type.
The integrated interface can be done using WoT interactions.
Protocol bindings can be used for the adaptors.
Also, a special adapter can be used by the protocol bindings.
Based on adapters, virtual devices can be created out of physical devices.
It might employ TD conversion, protocol convertion, device management.
All this is part of an Adapter runtime.
A tree of gateways could be deployed, where the root works as directory for devices and adapters
A large scal system requires multiple multi-layered gateways deployment
Experiment: 1400 devices connected in 3 fields, a) smart home, b) smart factory, c) smart agriculture.
Application handles all fields, based on cloud gateway.
Toward zero configuration: this integration enables building the system with zero configuration.
WoT allows a common glue between IoT platforms, instead of bridging each platform to each other platform.
Will concentrate on the data format. JSON and CBOR are accepted, but what about others?
When a Thing is WoT compliant, the client can get the TD and interact right away.
However, with legacy devices, this is not possible.
This is similar experience to web browsers being the entry point to access served content of various types.
Most of available data is in CSV format. TD supports CSV natively.
Proposes native type annotation for CSV
The second example is TLV (type-length-value) data format.
TLV, notably ASN.1 is used everywhere. TD should natively support ASN.1
Call for TD being more versatile.
Questions.
Thomas: there is already work on CSV-JSON conversion. Answer: that is one way to do it.
Question: now we use JSON Schema, which is not a full standard now, we could extend it, so what is the minimal delta that is needed
Kathy: we came across the same problems and solved with adapters as well.
Ari: this is a broad problem that is looked upon elsewhere too, so we should work on this together.
Lunch break.
<kaz> [till 14:40]
<soumya> scribenick: soumya
topic - research and survey of use case for wot
tomoaki - presenting customers use cases
tomoaki - showing the motivation behind the talk. it is important to note how customers use such technologies
tomoaki - there is a need for research on use cases, need to consider both manufacturer and customer perspectives
tomoaki - showing some details of the attitude survey of IoT from Japan
tomoaki - result is interesting, about 66% has heard of IoT but only 60% of the respondants can explain IoT.
tomoaki - JP Govt. has plans to use IoT from 2020
tomoaki - shows a more detailed survey for IoT appliances in bedroom, living room, entrance etc.
tomoaki - shows some conclusions for results of survey
tomoaki - concludes his lightening talk.
tomoaki - it is necessary to help the customer to bridge the gap between understanding and use of IoT
sebastian opens floor to question.
sebastian - ponders on the importance for users to know about IoT
tomoaki - customers should know what is IoT and that might have influence on buying IoT products, services.
moving to next speaker
topic - MIoT Platform
[MIoT Platform] targeted for connecting people and home
[MIoT Platform] statistics about their platform
[MIoT Platform] smarphone & smart speaker centric functions
[MIoT Platform] timeline with different connectivity modules
[MIoT Platform] provides rich sdks - RTOS, Android, Linux and many coonective solutions
[MIoT Platform] provides multiple access or control of iot devices
[MIoT Platform] shows the smart voice control - device status, device control, continuos update etc
[MIoT Platform] provides rich trigger conditions like human body sensor, light sensor, water sensor etc
[MIoT Platform] 1.98 Million users have over 5 iot devices
[MIoT Platform] works with traditional BlueTooth solution
[MIoT Platform] creating a BlueTooth Mesh as well
[MIoT Platform] shows an example of BLE-Wi-Fi mesh
[MIoT Platform] mentions that whole platform capability is open to share
[MIoT Platform] shows an architecture of the platform
[MIoT Platform] is built using layered model
[MIoT Platform] shows its functional model for smart home application profile
[MIoT Platform] is operational with gateway and cloud-only scenarios
[MIoT Platform] works with other vendors (CLoud to CLoud, module level integration..)
[MIoT Platform] concludes the talk
[MIoT Platform] resembles WoT deployment scenario 6
[MIoT Platform] using own standards, yet to be there
topic - Virtual-Thing: TD based Virtualization
Jeff - asks about interoperability
hassib - introducing their work
hassib - lists problems - no easy way to simulate a thing based on its TD, hard to test a mashup with physical access to the devices, rynning tests might overwhelm iot devices
hassib - solution is to simulate a thing based only on its TD
hassib - it uses original TD and node-wot servient
hassib - virtual thing is available in npm repository and is easy to start
hassib - as a future work, create a digital twin
hassib - digital twin acts as a reverse proxy
hassib - showing some limitations (some are inherited from node-wot)
hassib - concludes his talk
question - is it a standalone module?
hassib - it is an npm package and open source
matthias - nice tooling, will be valuable in future. what is the meaning behind digital twin here.
hassib - not defining what is a digital twin, in this context, the digital twin is like a reverse proxy not just a digital representation.
klotz - are you working with other partners?
hassib - outlines his motivation and describes his intention to look into partnerships
taki - usage of virtual thing in test purpose (comment)
topic - wot store
luca - wot store is a generic software platform for the management of W3C-compliant things and applications of the WoT SECO
luca - wot store has a modular architecture with things manager, applications manager, data manager
luca - things manager performs things discovery, TD etc
luca - there is a web & CLI for this
luca - provided in github
luca - application manager allows sharing, update, visualization etc
luca - application manager performs semantic discovery of applications as well.
luca - data manager is doing data filtering, flow aggregation, plotting
luca - market service - it is a rest api
luca - implementation benefits from node.js ecosystem
luca - use cases - industry 4.0 (update all, data analysis), home automation (new thing integration, UI, mashup application), smart agriculture (update all, data analytsis)
luca - future works on control access mechanism, digital twin.
lucus - dependencies like if some applications depends on properties of other thing applications?
luca - code and libraries can be used and system will download and install them
zoltan - what is an application in the talk?
luca - Thing application is same as Thing behavior (properties, events, actions).
zoltan - it might lead to confusion
topic - rapid iot app development
kunihiko - talking about node red based development
kunihiko - current issues include many barriers like ambigious documentation, limited capability of some SDKs
kunihiko - wot TD can be used as open specification in this context
kunihiko - node red is widely used for its intuitive aspect
kunihiko - combined node red with wot which results into a tool called node generator
<kaz> (ege is taking notes locally for this session)
# Notes Last Sesssion ## Siemens: Security from Oliver Pfaff lifecycle of a thing, bootstrapping of security ### Common Practices Security should be easy and secure Not done: Site -> Trust the device, Device-> Know the site = not done yet and difficult Relevant initiatives: * Anima: have manufacturer install a service on site that does the authentication for the device when the device is installed ### Questions Ari: Recommending IETF group on this ML: Companies working on this? MM: How to trust the service as the site owner? MK: The service can change owner, doesn't have to be the manufacturer. ## Web of Twins from Philippe Coval ### What is DT Connectivity between real device and digital representation DTs are model driven Privacy by design IoT.js is a language for the emb. devices ### Robot arm We can think what a robot can be and program a DT Video on Youtube: Using the DT on a VR glass in order to control a real device in the end Architecture overview for the Robot arm but any other thing in general ### Color Sensor Reading the color of an object and changing the DT color on webthing ### Summary We can create DTs using js and displaying them on browser for different devices ## Open Mic
<kaz> scribenick: ege
Here are the notes from the last session of day 1
# Notes Last Sesssion ## Siemens: Security from Oliver Pfaff lifecycle of a thing, bootstrapping of security ### Common Practices Security should be easy and secure Not done: Site -> Trust the device, Device-> Know the site = not done yet and difficult Relevant initiatives: * Anima: have manufacturer install a service on site that does the authentication for the device when the device is installed ### Questions Ari: Recommending IETF group on this ML: Compa
## Security Bootstrapping from Oliver Pfaff
lifecycle of a thing, bootstrapping of security
### Common Practices
Security should be easy and secure
Not done:
Site -> Trust the device, Device-> Know the site = not done yet and difficult
Relevant initiatives:
* Anima: have manufacturer install a service on site that does the authentication for the device when the device is installed
### Questions
Ari: Recommending to work together with the T2TRG IRTF group on this
ML: Companies working on this?
MM: How to trust the service as the site owner?
MK: The service can change owner, doesn't have to be the manufacturer.
## Web of Twins from Philippe Coval
### What is DT
Connectivity between real device and digital representation
DTs are model driven
Privacy by design
IoT.js is a language for the emb. devices
### Robot arm
We can think what a robot can be and program a DT
Video on Youtube: Using the DT on a VR glass in order to control a real device in the end
Architecture overview for the Robot arm but any other thing in general
### Color Sensor
Reading the color of an object and changing the DT color on webthing
### Summary
<rzr> https://www.youtube.com/watch?v=sUayRsjV1Ys
We can create DTs using js and displaying them on browser for different devices
### Open Mic: (Couldn't take any notes)
:)
<rzr> https://github.com/rzr/twins source code of robot twins if anyone want to test them
<akeranen> Securing TD delivery was out of charter but something that could be worked on next. Standardization on security and provisioning would be helpful to users. DNS-SD, CoRE Resource Directory, etc relevant here. In IIC whole group on trustworthiness of IoT.
Discovery: mozilla: mdns where you publish the URI of the TD to the network
Accesibility: How devices can accomodate the needs of the users, depending on the user
a lot of people seem to be motivated about accesibility, lots of hands raised
mk: verifiable claims can be a
building block
... thing directory is an item in the working group
... should we start it now or get fb and do it a bit later
hassib belhaj: what about a google search for wot?
scribe: global search
mk: before there was also directories
for web, no search
... ietf is doing that, through core link format
... local search doesn't make too much sense
hb: but what about IP cameras or weather data providing sensors
mmcool: mdns is sort of
obsolete
... how to discover a directory, bootstrapping a system
sebastian kaebisch: there was already discussions on that
mk: I had called it a red hole
(audience giggles)
s/ red hole /rat hole
sk: one topic is then certainly discovery then
mk: gs1 standard have new patterns
that we should explore
... eventing is still not (clear)
... multiplexing multiple interactions into a single connection
sk: considering passive things
mm: new metadata?
ben francis: schema.org?
mm: what schema then?
... who is interested in scripting
... standardizing it
mk: what about more complex
interactions
... I believe that web has solutions for it
jeff: not to add these directly
... what is in the edge of what we are doing but not in the spec
yet
... the collection of things we are putting together, can they be
done in a timeframe that fits the market needs
kaz: I put a long list of possible topics
johannes: how to do onboarding, helping on how to choose solutions/technologies
ari: join forces (ietf and w3c) since this is a common problem
dominique: all the pieces are here but "how do you put them together"
mm: it is not just putting up a website
dg: it has to come from the
community
... we needed collections, we had to add it ourselves
bf: onboarding new members -> making the group more approachable
seb: how to trust the td