DOCSLIB.ORG

W3C Web of Things

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
W3C Web of Things Supporting IoT Interoperability via Open Standards Conexxus Strategy Conference, 13 Aug 2019 Michael McCool: Intel Principal Engineer / W3C WoT WG Co-chair Supporting IoT Interoperability via Open Standards Conexxus Strategy Conference, Aug 2019 Michael McCool: Intel Principal Engineer / W3C WoT WG Co-chair Outline • The Role of Open Standards in IoT – Business justification for IoT standards – Use cases • The W3C Web of Things (WoT) Standards Work – Building Blocks – Key deliverable: Thing Description – Planned work: Profiles, Thing Directory • The Future of Open Standards – Standards landscape for data and edge computing – Gaps and opportunities – Roadmap: where do we go from here? Role of Open Standards in IoT Business Justification • Why Standards? – Standards support interoperability of products from multiple vendors. ▪ Multiple sources for standardized products reduces risk. ▪ Competition reduces cost. – Standards support portability and scalability ▪ Vendors can develop products and services that can be used in multiple markets. – 40% of IoT use cases require integration of services from multiple verticals ▪ McKinsey: The Value of Digitizing the Physical World – Investing in closed systems is a business risk ▪ Machina Research: Smart Cities Could Waste $341 Billion by 2025 on Non-standardized IoT Deployments • Why Open Standards? – Free access to standards documents – Royalty-free – Wide participation Use Case: Connected Car Charging • EcoG provides PaaS support for custom fast EV charging • Can link charging access and pricing to retail activity Image provided under Creative Commons Attribution-Share Alike 3.0 Unported License by BP63Vincent Use Case: Mozilla WebThings Gateway • Mozilla provides a WoT gateway hub which bridges several other IoT standards to WoT • Devices are interconnected locally, enhancing privacy Use Case: AI-Enabled Security • AI appliance provides person identification service • Other Things provide motion detection and image capture services • Orchestration system discovers sensors and AI service and connects then to trigger alarms when person identified in interdicted zones. Other Retail Use Cases… • Inventory monitoring and order management • Automated checkout • Security and access control • Employee monitoring for hygiene management • Customer reward programs tied to activity • Loitering alerts • Foot traffic monitoring and analysis • Parking access control and guidance • Smart signage and targeted marketing • Refrigeration monitoring, including lifecycle tracking during shipment Use Case: Smart Factory Digital Twins • Provide bridge between IT and OT systems Services Monitor • Manage data and control in local cloud RS-485 and predict performance with EtherCAT digital twins. Integration: System Architecture Cloud Gateway client client Connected Car server proxy gateway Remote access and Synchronization Integration and Orchestration Device client Existing Device Web Browser Device client server server server Direct Thing-to-Thing Complement Web Integration Interaction Existing Devices 11 Goal of Standards Goal of Standards Interoperability Goal of Standards Interoperability “I can plug it in and it just works.” Goal of Standards Interoperability “I can plug it in and it just works.” In other words: standards help to automate or streamline an integration process so the user does not have to think about it. Goal of Standards Interoperability “I can plug it in and it just works.” To define: “I”, “plug”, “it” and “works” What is “Interoperability”? Ingestion Interoperability: Connect Data Sources to Data Stores • Normalize data using common semantics upon data ingestion. Transfer Interoperability: Connect Multiple Stacks • Exchange data between vertical silos. Mesh Interoperability: Connect Devices and Services • Communication and control among distributed devices and services Application Interoperability: Deploy Code across a Distributed System • Manage applications running in portable and secure contexts. Interoperability: Technical Requirements Requirement Interaction Data Discovery Application Abstraction Interpretation Mechanism Environment Priority Type 1 Ingestion Description Data Model 2 Transfer Description Data Model Introduction, 3 Mesh Description Data Model Directory Management, APIs and/or Introduction, 4 Application Data Model APIs, Description Directory Runtime W3C WoT Standards Work W3C Web of Things – Building Blocks WoT Architecture Overarching umbrella with architectural constraints and guidance on how to use and combine building blocks. WoT Thing Description (TD) Security Guidelines WoT Scripting API JSON-LD representation format to Standardized JavaScript object API for describe Thing instances with metadata. Any IoT Device an IoT runtime system similar to the Uses formal interaction model and Common Runtime Web browser. Provides an interface domain-specific vocabularies to between applications and Things to Application Script uniformly describe how to use Things, simplify IoT application development which enables semantic interoperability. and enable portable apps across Scripting API vendors, devices, edge, and cloud. The index.html InteractionData Model Model for Things WoT Binding Templates Protocol Bindings Properties Capture how the formal Interaction Model is mapped to concrete protocol Actions operations (e.g., CoAP) and platform Events HTTP CoAP features (e.g., OCF). These templates MQTT … are re-used by concrete TDs. 21 Published Candidate Recommendations • WoT Architecture • WoT Thing Description (TD) – Constraints { "@context": [ ▪ Things must have TD (W3C WoT) "https://www.w3.org/2019/wot/td/v1", { "iot": "http://iotschema.org/" } ▪ Must use hypermedia controls (general WoT) ], – URIs "id": "urn:dev:org:32473:1234567890", "name": "MyLEDThing", – Standard set of methods "description": "RGB LED torchiere", – Media Types "@type": ["Thing", "iot:Light"], "securityDefinitions": ["default": { – Interaction Affordances "scheme": "bearer„ }], ▪ Metadata of a Thing that shows and "security": ["default"], describes the possible choices (what) to "properties": { "brightness": { Consumers, thereby suggesting how "@type": ["iot:Brightness"], Consumers may interact with the Thing "type": "integer", "minimum": 0, "maximum": 100, "forms": [ ... ] } Pull }, Handle = Affordance "actions": { What? How? "fadeIn": { ... Door = Thing Open Turn Published WG Notes • WoT Security and Privacy • WoT Scripting API Guidelines – Proposal for a standard API to consume – Details beyond the security considerations and produce WoT Thing Descriptions in each specification for a holistic security – Provides interface between applications and privacy configuration of Things and network-facing API of IoT devices – Security testing plan (cf. Web browser APIs) – Documents learnings from the design • WoT Binding Templates process – Documentation for how to describe existing IoT ecosystems (e.g., OCF or generic Web) with WoT Thing Description Status and Recent Developments • Decision to adopt JSON-LD 1.1 proposed features to allow: – Default values – Object notation (name: value) instead of arrays – Alignment with common JSON practices • Security metadata – Focus on HTTPS (Basic Auth, Digest, Tokens, OAuth2) • Protocol Bindings – Focus on HTTP and structured payloads compatible with JSON – Support for Events also using subprotocols (e.g., long polling in HTTP) • Extension Points – CoAP(S), MQTT(S), and further security schemes (e.g., ACE) – Semantic annotations with custom vocabularies (JSON-LD @context and @type) WoT Next Steps: Proposals 1.1 Maintenance 1.1 Improvements 1.1~2.0 Tentative 2.0 New Items • TD Security schemes • “Profile” for Plug&Play • Privacy-preserving lifecycle • IG output – TD default values and identity management – Oauth2 flows without override • Discovery – PoP tokens – Limit URI schemes, • Thing Templates – Peer-to-peer media types, etc. – ACE? • Discovery • Implementation View Spec • TD Link Relation types – “Web Thing API”-like – Directory – TD hierarchies – Specify details such as • Protocol Vocabulary – error responses, IANA? common features, etc. – MQTT(S) • TD vocabulary ➢ Could represent (including MQTT+WS) the “Profile” – Producer • Complex Interactions – Full JSON Schema – Monitor, cancel Actions – TD Default Values – Action/Event queues • Refactoring – Error recovery ➢ Hypermedia responses – Readability etc. • Observe Defaults – Update WoT Arch – Method / subprotocol use cases • Protocol Vocabulary – More examples – CoAP(S) (including CoAPS+WS) 28 W3C WoT Resources • W3C WoT Wiki • W3C WoT Candidate Recommendations – https://www.w3.org/WoT/IG/wiki – https://www.w3.org/TR/wot-architecture/ (IG/WG organizational information) – https://www.w3.org/TR/wot-thing-description/ • W3C WoT Interest Group – https://www.w3.org/2016/07/wot-ig-charter.html • W3C WoT Working Drafts / Group Notes (charter) – https://www.w3.org/TR/wot-binding-templates/ – https://lists.w3.org/Archives/Public/public-wot-ig/ – https://www.w3.org/TR/wot-scripting-api/ (mailing list) – https://www.w3.org/TR/wot-security/ – https://github.com/w3c/wot (technical proposals) • W3C WoT Editors’ Drafts and Issue Tracker – https://github.com/w3c/wot-architecture/ • W3C WoT Working Group – https://github.com/w3c/wot-thing-description/ – https://www.w3.org/2016/12/wot-wg-2016.html – https://github.com/w3c/wot-binding-templates/ (charter) – https://github.com/w3c/wot-scripting-api/ – https://www.w3.org/WoT/WG/ – https://github.com/w3c/wot-security/ (dashboard) • Reference Implementation: node-wot – https://github.com/eclipse/thingweb.node-wot
Load more

Recommended publications
  • GATEKEEPER Platform Overview
    GATEKEEPER – Platform overview Table of contents ABSTRACT .........................................................................................................................................................4 1 ARCHITECTURE DEFINITION PRINCIPLES ................................................................................... 5 1.1 WEB OF THINGS ................................................................................................................................................................. 5 1.1.1 Principles for Gatekeeper data ....................................................................................................................... 6 1.1.2 Gatekeeper Web of Thing based architecture .................................................................................... 7 1.1.3 Role of WoT Thing Description ....................................................................................................................... 9 1.1.4 Role of FHIR and relation with Thing Description ............................................................................ 15 1.2 GATEKEEPER PLATFORM STAKEHOLDERS ........................................................................................................ 16 1.3 SECURITY AND PRIVACY CONSIDERATIONS ....................................................................................................... 17 1.3.1 Infrastructure security ..........................................................................................................................................18
    [Show full text]
  • A Secure and Scalable Smart Home Gateway to Bridge Technology Fragmentation
    sensors Article A Secure and Scalable Smart Home Gateway to Bridge Technology Fragmentation Ezequiel Simeoni 1,* , Eugenio Gaeta 1 , Rebeca I. García-Betances 1 , Dave Raggett 2, Alejandro M. Medrano-Gil 1 , Diego F. Carvajal-Flores 1 , Giuseppe Fico 1 , María Fernanda Cabrera-Umpiérrez 1 and María Teresa Arredondo Waldmeyer 1 1 Life Supporting Technologies (LifeSTech), ETSI Telecomunicaciones Universidad Politécnica de Madrid, Av. Complutense s/n, 28040 Madrid, Spain; [email protected] (E.G.); [email protected] (R.I.G.-B.); [email protected] (A.M.M.-G.); [email protected] (D.F.C.-F.); gfi[email protected] (G.F.); [email protected] (M.F.C.-U.); [email protected] (M.T.A.W.) 2 W3C/ERCIM, 2004, Route des Lucioles, Sophia Antipolis, 06410 Biot, France; [email protected] * Correspondence: [email protected] Abstract: Internet of Things (IoT) technologies are already playing an important role in our daily activities as we use them and rely on them to increase our abilities, connectivity, productivity and quality of life. However, there are still obstacles to achieving a unique interface able to transfer full control to users given the diversity of protocols, properties and specifications in the varied IoT ecosystem. Particularly for the case of home automation systems, there is a high degree of fragmentation that limits interoperability, increasing the complexity and costs of developments Citation: Simeoni, E.; Gaeta, E.; and holding back their real potential of positively impacting users. In this article, we propose García-Betances, R.I.; Raggett, D.; implementing W3C’s Web of Things Standard supported by home automation ontologies, such as Medrano-Gil A.M.; Carvajal-Flores SAREF and UniversAAL, to deploy the Living Lab Gateway that allows users to consume all IoT D.F.; Fico, G.; Cabrera-Umpiérrez, devices from a smart home, including those physically wired and using KNX® technology.
    [Show full text]
  • Sequential Behavioral Modeling for Scalable Iot Devices and Systems
    Sequential Behavioral Modeling for Scalable IoT Devices and Systems Ege Korkan1, Sebastian Kaebisch2, Matthias Kovatsch2, Sebastian Steinhorst1 1 Technical University of Munich, Germany, Email: fege.korkan, [email protected] 2 Siemens AG, Germany, Email: fsebastian.kaebisch, [email protected] Abstract—The Internet of Things (IoT) enables connectivity be- tween devices, thereby allowing them to interact with each other. A recurring problem is the emergence of siloed IoT platforms due to proprietary standards. Recently, the World Wide Web Consortium (W3C) proposed a human-readable and machine- System understandable format called Thing Description (TD). It allows to uniformly describe device and service interfaces of different IoT TD 2 TD 2 4 standards with syntactic and semantic information, and hence 1 3 Thing A Thing B 1 3 enables semantic interoperability. However, describing sequential behavior of devices, which is essential for many cyber-physical systems, is not covered. In this paper, we propose a systematic X TD Contents: asd way to describe such sequential behavior as an extension within Possible TD ­ Identification TDs, thereby increasing their semantic expressiveness through Interaction: Thing C possible, valid state transitions. This enables safe and desired asda ­ Interaction List operation of devices as well as scalability by modeling systems - Property ­ Data Type as sequential compositions of Things. We show in a case study - Action 1 ­ Data Access that previously unmodelable behavior can now be expressed and - Event TD ­ Protocols the overall manual intervention requirements of state-of-the-art ­ Security implementations can be significantly reduced. Figure 1: An abstracted view of an IoT System with 3 IoT Devices each with Index Terms—Internet of Things, Thing Description, CPS, an associated Thing Description (TD).
    [Show full text]
  • Semantic Interoperability in Internet of Things
    CORE Metadata, citation and similar papers at core.ac.uk Provided by TUT DPub SYED SAFDAR ALI SHAH SEMANTIC INTEROPERABILITY IN INTERNET OF THINGS Master of Science thesis Examiner: Prof. Kari Systä Examiner and topic approved by the Dean of the Faculty of Computing and Electrical Engineering on date 29.03.2017 i TABLE OF CONTENTS 1. Introduction . 1 2. Internet of Things . 3 2.1 Definition of the Internet of Things . 3 2.2 Internet of Things Technologies . 4 2.2.1 Network/Link Layer . 6 2.2.2 Internet Layer . 6 2.2.3 Transport Layer . 7 2.2.4 Data Protocols . 8 2.2.5 Discovery . 9 2.2.6 Device Management . 10 2.2.7 Semantic . 11 3. Interoperability in the Internet of Things . 14 3.1 Technical Interoperability . 14 3.2 Syntactic Interoperability . 15 3.3 Semantic Interoperability . 15 3.3.1 Proxy Gateway . 16 3.3.2 Unified Data Models and Frameworks . 16 3.3.3 Ontologies . 16 4. Proposed Semantic Interoperability Solution for IoT . 18 4.1 Endpoint . 19 4.2 Resource Directory . 20 4.3 Interoperability Server . 21 4.3.1 Apache Jena . 21 4.3.2 Thing Description Repository . 22 4.3.3 Semantic Engine . 24 ii 4.3.4 Management Client . 26 4.4 Interfaces . 26 4.4.1 Peer Interface . 27 4.4.2 Resource Directory Interface . 27 4.4.3 Interoperability Server Interface . 30 4.4.4 Management Interface . 32 4.5 Working Principles . 36 4.5.1 Temperature Sensor, Fan Actuator, and Central Controller reg- isters their Thing Descriptions with Interoperability Server .
    [Show full text]
  • Chairs: Carsten Bormann & Ari Keränen
    T2TRG: Thing-to-Thing Research Group IETF 105, July 24, 2019, Montréal Chairs: Carsten Bormann & Ari Keränen 1 Note Well • You may be recorded • The IPR guidelines of the IETF apply: see http://irtf.org/ipr for details. !2 Administrivia (I) • Pink Sheet • Note-Takers • Off-site (Jabber, Hangout?) • xmpp:[email protected]?join • Mailing List: [email protected] — subscribe at: https://www.ietf.org/mailman/listinfo/t2trg • Repo: https://github.com/t2trg/2019-ietf105 !3 Agenda Time Who Subject Docs RFC8576, draft-irtf-t2trg- 13:30 Chairs Intro, RG status, upcoming meetings and activities rest-iot Chairs, Report from WISHI, Pre-IETF meeting with OMA, Hackathon, 13:45 various and Morning side meeting Michael Activities on data model convergence; W3C Community Group on 13:55 Koster Schema extensions for IoT; schema.org update Michael 14:15 W3C Web of Things WG/IG update McCool 14:30 Ivaylo Petrov YANG Object Universal Parsing Interface draft-petrov-t2trg-youpi Christian 14:35 Transports for CoAP: new URI schemes of CoAP protocol negotiation Amsüss "Why Edge and IoT will never happen!!1!" (outrageous opinion 14:45 Dirk Kutscher presentation) Yong-Geun draft-hong-t2trg-iot-edge- 15:05 Problem Statement of IoT integrated with Edge Computing Hong computing Yong-Geun 15:20 Edge IoT demo Hong !4 T2TRG scope & goals • Open research issues in turning a true "Internet of Things" into reality • Internet where low-resource nodes ("things", "constrained nodes") can communicate among themselves and with the wider Internet • Focus on issues with opportunities
    [Show full text]
  • Thing Description As Enabler of Semantic Interoperability on the Web of Things Sebastian Käbisch, Darko Anicic Siemens AG - Corporate Technology
    Thing Description as Enabler of Semantic Interoperability on the Web of Things Sebastian Käbisch, Darko Anicic Siemens AG - Corporate Technology Internet of Things (IoT) will connect devices, facilities, and networks with advanced sensors, controls and software applications. Combined with the power of analytics, artificial reasoning, automation and deep domain expertise, it has the potential to increase performance gains across global industry sectors. Yet the vision of Internet of Things is challenged today by a number of issues, few of which are associated with data silos, machine interoperability, automated resource discovery, unambiguous interpretation of IoT data, smooth engineering and maintenance of IoT systems and many others. Hence a few challenges that motivate the need for IoT Semantics are: Semantic interoperability - ensures that IoT data can be comprehended unambiguously by both human users and software programs across different platforms and domains. It offers interaction between heterogeneous Things on a higher level of abstraction. Interpretation of data and knowledge – makes the data generated by Things understandable by machines and humans, without prior knowledge about Things that produced them. Unambiguity – deals with an unambiguous meaning of Thing’s data and properties. For example, it is not sufficient to know that there exists a Thing, but it is important to know what exactly a capability of the Thing is, and to unambiguously understand the data it produces or consumes. Data/knowledge integration – integrates data/knowledge from multiple vertical domains into cross-domain applications. Thing Description The approach of W3C WoT IG, which addresses challenges presented in the previous section, is grounded on Thing Description - a semantic description of actual Thing’s capabilities and the information on how to access them.
    [Show full text]
  • Describing Things in the Internet of Things
    Describing Things in the Internet of Things From CoRE Link Format to Semantic Based Descriptions Soumya Kanti Datta, Christian Bonnet Communication Systems Department, EURECOM, Biot, France Emails – {dattas, bonnet}@eurecom.fr Abstract—Efficient mechanism for describing the physical described in [2] and (ii) integrating the proposed framework into things is necessary for automatic configuration and management an oneM2M standard architecture. The work also mitigates the in the Internet of Things (IoT) ecosystem. This paper highlights an following issues – (i) settle heterogeneity of for thing evolution in Thing Description (TD) from CoRE Link Format to description, (ii) enable self-configuration management, (iii) ease semantic based descriptions. Adding semantics enable sensors and of adding and deleting things to the IoT frameworks and (iv) actuators to be represented in terms of events, properties and support mobility of the things and (v) describe the legacy things actions. This provides further granularity in TD which allows with support from proxies. Rest of the paper is organized as higher layer IoT applications and consumers to easily configure follows. Section II describes the proposed framework with an and manage the connected things. A thing management example of semantic description of a light switch. Section III framework is developed based on semantic TD. JSON for Linking focuses on the oneM2M architecture and prototyping of the Data (JSON-LD) provides a serialized representation of such TD model and is a lightweight Linked Data format. This paves way for framework. Section IV concludes the work. seamless thing to thing interaction in IoT spaces. Integration of the II. LIGHTWEIGHT THING MANAGEMENT FRAMEWORK proposed framework into oneM2M architecture and prototyping aspects are also highlighted.
    [Show full text]
  • Toward Constrained Semantic Wot
    Toward Constrained Semantic WoT Remy Rojas Lionel Médini Amélie Cordier Univ Lyon Univ Lyon, Université Lyon 1 Univ Lyon, Université Lyon 1 LIRIS, CNRS UMR5205 LIRIS, CNRS UMR5205 LIRIS, CNRS UMR5205 F-69622, Villeurbanne, France F-69622, Villeurbanne, France F-69622, Villeurbanne, France [email protected] fi[email protected] fi[email protected] ABSTRACT pragmatic point of view, even if these architectures can the- More and more things are now connected to the Internet and oretically be embedded in things, they can require a large become part of the Web of Things. The notion of \thing" amount of resources that may not be available on all devices. encompasses various types of devices, from complex robots Indeed, there is currently no technology stack that allows at to simple sensors. In particular, things may rely on limited the same time discoverability, scalable access through Web standards and semantic interoperability, aimed to fit in con- memory, storage and computing capabilities. We propose 4 an architecture able to embed both semantic and REST- strained devices . In order for such an architecture to meet ful technologies into constrained things, while being generic the requirements of both the semantic WoT and constrained and reconfigurable. It combines emerging standards such as devices, it must satisfy the following requirements: CoAP and Hydra to split RDF graphs, process requests, and • Energy efficiency: Energy consumption of devices, generate responses on-the-fly. We validate our proposition especially battery-powered, should be optimized. In by implementing such a Server in an Arduino UNO. particular, during wireless network communications, the quantity of data transmitted should be minimized.
    [Show full text]
  • SOLIOT—Decentralized Data Control and Interactions for Iot
    future internet Article SOLIOT—Decentralized Data Control and Interactions for IoT Sebastian R. Bader 1,* and Maria Maleshkova 2,* 1 Fraunhofer IAIS, Schloss Birlinghoven, 53757 Sankt Augustin, Germany 2 Institute for Computer Science, University of Bonn, Endenicher Allee 19a, 53115 Bonn, Germany * Correspondence: [email protected] (S.R.B.); [email protected] (M.M.) Received: 30 April 2020; Accepted: 8 June 2020; Published: 16 June 2020 Abstract: The digital revolution affects every aspect of society and economy. In particular, the manufacturing industry faces a new age of production processes and connected collaboration. The underlying ideas and concepts, often also framed as a new “Internet of Things”, transfer IT technologies to the shop floor, entailing major challenges regarding the heterogeneity of the domain. On the other hand, web technologies have already proven their value in distributed settings. SOLID (derived from “social linked data”) is a recent approach to decentralize data control and standardize interactions for social applications in the web. Extending this approach towards industrial applications has the potential to bridge the gap between the World Wide Web and local manufacturing environments. This paper proposes SOLIOT—a combination of lightweight industrial protocols with the integration and data control provided by SOLID. An in-depth requirement analysis examines the potential but also current limitations of the approach. The conceptual capabilities are outlined, compared and extended for the IoT protocols CoAP and MQTT. The feasibility of the approach is illustrated through an open-source implementation, which is evaluated in a virtual test bed and a detailed analysis of the proposed components.
    [Show full text]
  • Schema.Org Extensions for Iot (Iotschema)
    Schema.org Extensions for IoT (iotschema) Darko Anicic, Michael Koster Data Models and Semantic Interoperability IoT Week, Aarhus, Denmark - 20.06.2019 Data models for IoT • Web of Things Thing Description W3C Candidate Recommendation • Few other IoT ecosystems revolve around similar thing data models. The AWS IoT Things Graph The Alibaba Thing Web Thing Description Data Model (TDM) Specification Language (TSL) Common semantic layer iotschema.org Semantic interoperability for connected things . Web of Things The AWS IoT Things The Alibaba Thing Web Thing Thing Description Graph Data Model (TDM) Specification Language (TSL) Description What is iotschema ? • An open, publicly available, repository of semantic definitions for connected things • An extension of schema.org to enable descriptions of things in the physical world and their data • A common set of tools and patterns, and a community process for contribution and publication of standardized definitions • A way for domain experts to easily create semantic definitions that are relevant to their application domain What is iotschema (2) ? • A layer to bridge between device ecosystems and Semantic Web technology • Property and relation types to enable reuse of existing ontologies and definitions • SSN, SOSA, SAREF, QUDT • Property types for e.g. Feature of Interest • Annotation vocabulary for WoT Thing Description • Common definitions for application-specific Events, Actions, and Properties Who is iotschema for? • IoT platform providers will use iotschema to make it easy for third party
    [Show full text]
  • Toward a Simplified Wot Thing Model
    Toward a Simplified WoT Thing Model W3C Web of Things IG/WG F2F OpenDay Prague, Czech Republic, March 2018 Thing Description Sapporo 2015 { "@context": "http://w3c.github.io/wot/w3c-wot-td-context.jsonld", "metadata": { "name": "MyDoor", "protocols": { "WS": { Invalid JSON-LD "uri": "ws://www.example.com:80/door", container for "priority" : 1 }, metadata "HTTP": { "uri": "http://www.example.com:80/door", "priority": 2 } }, Addressing "encodings": [ "JSON" ] }, via uri + name "interactions": [{ "@type": "Property", "name": "stateOpen", "outputData": "xsd:boolean", "writable": false },{ "@type": "Event", XML Schema "name": "stateChanged", Types "outputData": "xsd:boolean" }] } Thing Description Montreal 2016 { "@context": ["http://w3c.github.io/wot/w3c-wot-td-context.jsonld", { "actuator": "http://example.org/actuator#" } ], Domain-specific "@type": "Thing", "name": "MyLEDThing", vocabulary "uris": [ "coap://www.myled.com:5683/", "http://www.myled.com:8080/myled/" ], "encodings": [ "JSON", "EXI4JSON" ], "security": { "cat": "token:jwt", "alg": "HS256", Security "as": "https://authority-issuing.org" }, metadata "properties": [{ "@type": "actuator:onOffStatus", "name": "status", "valueType": "xsd:string", "writable": true, "hrefs": [ "status", "myled/status" ] Prop. / Action / Event }], "actions": [{ on top level "@type": "actuator:fadeIn", "name": "fadeIn", "inputData": { "valueType": "xsd:short" }, "hrefs": [ "in", "myled/in" ] }], "events": [{ "name": "criticalCondition", Array arithmetic "valueType": "xsd:string", "hrefs": [ "ev", "myled/event"
    [Show full text]
  • Etsi Tr 103 715 V1.1.1 (2020-11)
    ETSI TR 103 715 V1.1.1 (2020-11) TECHNICAL REPORT SmartM2M; Study for oneM2M; Discovery and Query solutions analysis & selection 2 ETSI TR 103 715 V1.1.1 (2020-11) Reference DTR/SmartM2M-103715 Keywords interoperability, IoT, oneM2M, SAREF, semantic ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice The present document can be downloaded from: http://www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI deliverable is the one made publicly available in PDF format at www.etsi.org/deliver. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification Reproduction is only permitted for the purpose of standardization work undertaken within ETSI.
    [Show full text]