W3C WoT In A Nutshell
W3C WoT in a nutshellYongjing Zhang (zhangyongjing@Huawei.com)W3C WoT IG Co-chair24 May 2017, oneM2M Industry Day @ TP#29
2 Web of Things (WoT) overview WoT Thing Description (TD) WoT Scripting API WoT work organization & collaboration oneM2M-WoT Interworking
W3C WoT MissionInterconnect the silos de-siloWeb of Things “enable easy integration across IoT platforms and application domains”“complementing available standards”3/31
The Role of W3C in IoT/WoT – Play to the StrengthsApplicationDeveloperApplicationDefine thing behaviour in terms of their properties, actions and events,using APIs for control of sensor and actuator hardwareThingsSoftware objects representing abstract or physical devices and stateAbstract thing to thing interactionSemantics and Metadata, Data models and DataTransferBindings of abstract messages to mechanisms provided by eachprotocol, including choice of communication pattern, e.g. pull, push,pub-sub, peer to peer, etc.TransportREST based protocols, e.g. HTTP, CoAPPub-Sub protocols, e.g. MQTT, XMPPOthers, including non IP transports, e.g. BluetoothNetworkUnderlying communication technology with support for exchange ofsimple messages (packets)Many technologies designed for different requirements(WoT focus)PlatformDeveloper(IoT focus)4
Semantic Metadata is the KeyMetadata enables interoperability Describe the interfaces exposed to applicationsDescribe the communication and securityrequirements for accessing thingsDescribe the data models, semantics, and domainconstraintsMetadata simplifies application development Decouples underlying protocolsEnables automated tooling5
W3C WoT FrameworkLocal HubsCloud MirrorsApplicationSemanticmetadata(Thing Description)Remote accessApplicationDevice ShadowVirtual ThingScripting APIInteraction ModelInteraction ModelBinding TemplatesBinding TemplatesScripting APIWeb integrationApplicationComplementingexisting devicesand platformsWeb BrowserDirectThing-to-ThingApplicationExisting Device Scripting APIInteraction ModelBinding Templates(Thing Description,Binding Templates)StandardizedAPIs for portableapplication logic(Scripting API) ThingThingScripting APIInteraction ModelBinding TemplatesPowerful or constrained Things6/31
74 Key Components: W3C WoT Building BlocksWoT Scripting API:WoT ServientA standardized API to simplify IoT application development and enable portable scripts across vendors anddevice, gateway, and cloud platforms.Runtime EnvironmentWoT Thing Description (TD):App ScriptProvides metadata of the interactions, data model, communication, as well as security mechanisms of theThingWoT Binding Templates:The TD also describes the usage of protocols. A vanilla protocol stack can be configured at runtime toproduce message that will be understood by the targeted.Security & Privacy:W3C WoT does not invent new mechanisms, but ensures that all building blocks provide means to describethe security and privacy mechanisms used in a specific platform and provides adversary testing of Things.Scripting APITDInteraction ModelBinding TemplatesServerClient
8WoT Thing DescriptionDescribe Thing, communication, and security n/
JSON-LD(Linked Data)TD Example{W3C WoT TDvocabulary"@context": ld",{ "domain": "http://example.org/actuator#" }],domain-specific"@type": "Thing",vocabulary"name": "MyLEDThing","base": "coap://myled.example.com:5683/","security": {"cat": "token:jwt","alg": "HS256","as": ions": [JSON Schema{"@type": ["Property", "domain:onOffStatus"],"name": "status","outputData": {"valueType": {"type": "boolean"}},"writable": true,"links": [{9
"interactions": [{"@type": ["Property", "domain:onOffStatus"],"name": "status","outputData": {"valueType": {"type": "boolean"}},"writable": true,"links": [{"href": "pwr","mediaType": "application/exi"},{"href": ": "application/json"}]},{"@type": ["Action", "domain:fadeIn"],"name": "fadeIn","inputData": {"valueType": {"type": "integer"},"domain:unit": "domain:ms"},"links": [{"href": "in","mediaType": "application/exi"10PropertyAction
"inputData": {"valueType": {"type": "integer"},"domain:unit": "domain:ms"},"links": [{"href": "out","mediaType": "application/exi"},{"href": "http://mytemp.example.com:8080/out","mediaType": "application/json"}]},{"@type": ["Event", "domain:alert"],"name": "criticalCondition","outputData": {"valueType": {"type": "string"}},"links": [{"href": "ev","mediaType": "application/exi"}]}]}11Event(under construction,sources, sinks, )
WoT Thing Description JSON-LD is just one possible representation Good for discussion, accepted by Web peopleTD is a semantic model Backed by RDF and Linked Data vocabularies Yet complexity of Semantic Web can be ignoredOther formats possible EXI, CBOR, for machines Custom application/wot-td json for developers Just serializations of the semantic model12/31
13W3C WoT work organization
14W3C WoTInterest Group (IG)https://www.w3.org/2016/07/wotig-charter.html Started spring 2015 218 participants Informal work, outreach Use cases, explorative work Liaisons and collaborations withother organizations and SDOs PlugFests with running codeWorking Group (WG)https://www.w3.org/2016/12/wot-wg2016.html Started December 2016 71 participants Normative work Standardization of four initialbuilding blocks identified by theIG
W3C WoT Task Forces IG WG Current Practices (has deliverable) Architecture (has deliverable) Testing (PlugFest scenarios) Thing Description (has deliverable) Thing Lifecycle Type System (JSON Schema Extensions) Synchronization of Servients Hypermedia (Actions, error handling, ) Linked Data and Semantic Processing Scripting API (has deliverable) Demonstrators Binding Templates (has deliverable) Liaison with OCF Security & Privacy Liaison with oneM2M (tbc, You’re wanted )15/31
W3C WoT Liaisons IETF / IRTF Established, joint meetings since Nov 2015Open Connectivity Foundation (OCF) Established, commonality identified and preparing inputOPC Foundation Established, active alignment and joint PlugFest coming uponeM2M Plattform Industrie 4.0 Established, need to agree on strategy etc.Initial conference callsOpenFog Initial outreach16/31
WG RoadmapFeb (Santa Clara F2F)May (Osaka F2F)Jul (Düsseldof F2F)Nov (TPAC, Burlingame) Create GitHub repos Graphical and RDF model of TD Editor’s Drafts RC for WoT Arch. FPWD Draft for test suite Release FPWD of WoT Arch. RCs for FPWD RC Implementations and Test Suite2017Mar (London? F2F)Jul (China? F2F)Nov (TPAC, Asia?) Finish security review Release FPWDs Finish security review Start release process2018May (Santa Clara?)OctDec (end of current charter) Aggressive testing /adverse security testing? RCs for CandidateRecommendations Release CandidateRecommendations (CRs)17/31
W3C WoT Online Resources W3C WoT Interest Group https://www.w3.org/WoT/IG/ (blog) https://www.w3.org/2016/07/wot-ig-charter.html (charter) / (subscribe to mailing list)W3C WoT Working Group W3C WoT GitHub (IG technical proposals) https://github.com/w3c/wotW3C WoT WG Documents https://w3c.github.io/wot-architecture/ https://w3c.github.io/wot-thing-description/ https://www.w3.org/WoT/WG/ (dashboard) https://w3c.github.io/wot-scripting-api/ https://www.w3.org/2016/12/wot-wg-2016.html (charter) https://w3c.github.io/wot-binding-templates/W3C WoT Wiki (IG WG organizational information) https://www.w3.org/WoT/IG/wiki/Main Page18/31
Web of Things Participants19/31
20oneM2M-WoT InterworkingPreliminary thoughts for discussion
Interworking: WoT oneM2M Exposing the WoT interface (described in TD) to oneM2M systems–Benefit: WoT services/data can be consumed by oneM2M applicationsActuatorprovides ThingDescriptionprovidesSensoroneM2M Application (AE)usesWoT i/fusesusesInter-workingProxy (AE)WoT i/fInter-workingProxy (AE)Mcaencapsulate& mapMcaMcaoneM2M Resource ModelCSEMNWoT TDmappingCSEMccInfrastructure Node21
Interworking: oneM2M WoT Exposing oneM2M interfaces to WoT systems Benefit: oneM2M services/data can be consumed by WoT Servients22
oneM2M HAIM vs. WoT[deviceInfo]Device Model[deviceAirConditioner]11contDefinition10.1 (L)0.1 tion]ModuleClasses0.10.110.10.n0.1Module fpowerState[toggle] subscription 10.1Data Point‘property’ or ‘action’‘action’ Action‘event’0.1WoT conceptswell mapping based on .1hwVersion0.10.1SDT conceptsDevice 0.1supportURL0.1presentationURL23/31
oneM2M general Resource Model vs. WoT‘base’‘@type’Universal Attributes �‘security’Attribute tionTimelastModifiedTimeexpirationTime? (Remotely registered devices)Common Attributes (optional)? (Local apps)‘interactions’ (property, action, urity’Attribute nsultationIDscreatordistributed vs centralized24/31
25Thanks You!For more information on W3C see:www.w3.org
The Role of W3C in IoT/WoT –Play to the Strengths 4 Application Define thing behaviour in terms of their properties, actions and events, using APIs for control of sensor and actuator hardware Things Software objects representing abstract or physical devices and state Abstract thing to thing interaction Semantics and Metadata, Data models and Data
B. W3C WoT and IETF CoRE Directories Both the IETF (in the CoRE working group) and the W3C (in the WoT working group) are currently standardizing resource description and discovery in IoT environments. Con-cretely, the IETF proposes the CoRE Link Format [3] while the W3C proposes the Thing Description [10] format. Both
W3C Web of Things Soumya Kanti Datta Research Engineer, EURECOM Coordinator, TF-DI in W3C WoT IG Email: dattas@eurecom.fr W3C Auto WG F2F Meeting April 2016
(WoT-AD), a descriptive language for the Asset aiming to mitigate such limitations. WoT-AD explicitly describes a group of Things as homogeneous object to enable mash-up, self-discovery, and simply access their resources, entities, and services. We also provide a lightweight framework that fully integrates with WoT-
WoT aims at solving the IoT interoperability puzzle and uses semantic web technologies in its Thing Description [4]. But the group currently does not provide any guidelines on testing WoT implementations. Therefore, SemTest significantly advances the current state of both the F-Interop and W3C WoT.
Technology Overview for W3C WoT Group Juan Carlos ZUNIGA Senior Standardization Expert –Sigfox 10.07.17. 1 INTRODUCTION 2 USE CASES AND DEPLOYMENTS 3 TECHNOLOGY 4 KEY FEATURES 5 IoT: ONNE TING THE “I” WITH THE “T” .
What is W3C? The World Wide Web Consortium (W3C) was founded in October, 1994 at the Massachusetts Institute of Technology (MIT) with support from the Defense Advanced Research Projects Agency (DARPA)andtheEuropeanCommission. The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web .
3.2 W3C: HTML 3.2 Specification 1997-01-14 4.0 W3C: HTML 4.0 Specification 1998-04-24 4.01 W3C: HTML 4.01 Specification 1999-12-24 5 WHATWG: HTML Living Standard 2014-10-28 5.1 W3C: HTML 5.1 Specification 2016-11-01 Examples Hello World Introduction HTML (Hypertext Markup Language) uses a markup system composed of elements which represent .
Illustration by: Steven Birch, Mary Peteranna Date of Fieldwork: 9-18 February 2015 Date of Report: 17th March 2015 Enquiries to: AOC Archaeology Group Shore Street Cromarty Ross-shire IV11 8XL Mob. 07972 259 255 E-mail inverness@aocarchaeology.com This document has been prepared in accordance with AOC standard operating procedures. Author: Mary Peteranna Date: 24/03/2015 Approved by: Martin .
