Next Step for WoT

Dave Raggett's slides

See Dave's slides (pdf)

dsr: Huge potential, but lots to do
... Gartner's expectation
... Standards as key to success
... Web standards for services
... Internet of Things as the Foundations
... Web of Things as the Skyscraper
... focus on app&service layer
... security is important
... Data in Context & Real World Models
... need to have a model for different abstractions
... Things & Avatars
... digital twin
... might have multiple representations
... each thing can have one or more virtual representations like Avatars
... The Web of Things
... diagram for the workshop in June
... a huge variety of potential application domains
... communication, samart homes, smart grid, vehicles, building automation, industrial, medical
... Application Domains
... Cyberphysical Systems
... W3C Web of Things Workshop
... Who participated
... 120 participants

Siemens' slides

See Johannes Hunds' slides (pdf)

(take Atomic Use Cases)

(Creating a common "Big Picture" based on "Atomic Use Cases"

johannes: situation, proposal and proceeding
... use cases and requirements
... atomic use cases
... tried to gather use cases from various industries

dsr: from the Berin workshop, there was need for launching IG
... IG doesn't work for recommendation specs but work for use cases and requirements
... what's needed for market, etc.
... possible separate task forces for specific technical topics
... not building new technologies
... but could work on best practices
... would record discussion points

bryan: from the earlier session
... a couple of topics on non-screen devices
... one of the key question was how do we address SSL support
... not sure if it's actual problem
... secure WebSocket for TV
... is there a problem for using SSL for local devices?
... how does W3C address underlying protocols?

dsr: let me show a slide: Opportunities for Scripting
... e.g., bluetooth
... browsers for direct access

paulc: let me be skeptical
... why browsers need these devices?
... upload data onto cloud

dsr: interest by companies, e.g., phones, watches

bryan: what are your use cases?
... industry IoT?
... connected devices with local namespace?

dsr: companies in this area have already started
... this (browsers) is a tiny part of WoT
... service platforms in the cloud or network edge as well

mark: also skeptical
... everyone of them is building their own IoT
... every layer
... my question is why do I need to care about WoT here in W3C?

dsr: what value for W3C
... most of the charter reviewers are from the viewpoints of IoT

bryan: there is a problem to solve

craig: need to talk about how to approach
... interested in IoT
... what the duration of the proposed IG?

dsr: Next Steps

<ArtB> Draft Charter for WoT IG

dsr: link to the draft charter

<brutzman> Efficient XML Interchange (EXI) is W3C Rec for smaller + faster compression/decompression of XML

<brutzman> Glue technology: IoT + EXI enables WoT at edge devices.

<brutzman> Also scales from small things to big data. Web is bigger than browsers.

<brutzman> EXI Profile for Limiting Usage of Dynamic Memory is now W3C Rec

<brutzman> EXI Profile for Limiting Usage of Dynamic Memory is now W3C Rec

<brutzman> http://www.w3.org/TR/2014/REC-exi-profile-20140909

paulc: not planning to use much time for the foundation for the mechanism?

dsr: right

(Federated Cloud-based Services)

(Applications and Services)

<brutzman> Also relevant: reduced processing, reduced power consumption, increased endurance seems to make WoT more efficient for IoT.

dsr: sensors -> service by Cloud A -> Cloud B -> Browser

nuance: what's new requirement?
... any discussions so far?

dsr: light-weight techniques
... we have to learn existing mechanisms

ann: anybody else from manufacturing interested?
... let me know if you're interested

dsr: (IoT Technologies)
... CoAP (Constrained Application Protocol)
... HTTP 2.0
... EnOcean
... Infrared
... audio as well
... USB/WiressUSB
... IEEE 1394
... Wifi
... ETSI's LTN
... Weightless
... MQTT
... XMPP
... JSON
... lot's of those technologies are used

bryan: primary focus is industry use cases?
... metadata using semantic web?
... got so from the draft charter

joerg: complete example could be the one from the morning session
... display-less device
... can be an atomic use case
... more than just an industry domain
... I have a device and would interact with that
... blood pressure, etc.
... what is the atomic use case?

dsr: (Shared Data Models)
... interoperability depens on shared data models
... discovery depends on shared vocabularies

bryan: in the social business workshop
... openness of the vocabularies

<JonathanJ1> I have updated some considerations for simple WoT architecture on the breakout session wiki page - https://www.w3.org/wiki/images/c/c6/SimpleWoTArchitecture.pdf

ann: meeting with social web guys

mark: need to resolve IPR policy as well

dsr: (End to End Security)
... security is the key for WoT
... devices may not be upgradable
... using physical security
... security requirements depend on domains
... authentication
... identity management

<MarkCrawford> My comment was that the IPR issue has been resolved. Schema.org now uses W3C IPR policy.

don: XML encryption, digital signature easily messed up
... encrypt first and compress
... current status is reaching out security group
... digital signature at the binary model

bryan: did you mean encryption? content connection?
... payload encryption?
... should address connection encryption

dsr: (Resilience)
... comet Shoemaker-Levy effect
... make sure of architecture for WoT
... heterogeneous mix of device
... hardware/software faults
... tolerance to failures
... cyber attacs by criminals and hostile states

bryan: strawman discussion
... don't impact Web
... how the Web got influenced?

craig: question on abstraction

don: don't make the web faster but make it bigger
... our concept today might be narrower than the bigger web

dsr: (The Web is about to become a whole lot bigger!)
... (Service Composition)
... ETH-Zurich
... configuration of smart environments Made Simple
... (Intent Based Search)
... for smart search
... (Discovery)
... need easy way to discovery
... any questions?

bryan: there are number of additional things
... probably there are interesting use cases

dsr: would ask to support the IG charter and join the group once it's launched

Jonghong Jeon's slides

See Jonhong's slides (pdf)

Jonghong Jeon (ETRI) posted these slides to the wiki page after the meeting, as we ran out of time in the break out session.