DOCSLIB.ORG

(Iot) to Web of Things (Wot): Protocols, Data Formats, Etc. MINES

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
(Iot) to Web of Things (Wot): Protocols, Data Formats, Etc. MINES From Internet of Things (IoT) to Web of Things (WoT): Protocols, data formats, etc. MINES Saint-Étienne, CNRS Lab Hubert Curien UMR 5516 Amelie Gyrard & Maxime Lefrancois [email protected] [email protected] 9 November 2017 Agenda I. Introduction: Web of Things (WoT) o Pioneer o W3C WoT Architecture II. Protocols, Formats & Tools o Protocols: MQTT, CoAP, etc. o Format: XML, JSON, etc. o Tools: NodeRed, Postman, etc. III. Towards the Semantic Web of Things (SWoT) o Ontology Catalogue for IoT with LOV4IoT o Deducing meaningful information from sensor data – Reasoning with SLOR o Semantic-based Smart Cities IV. In parallel: Quizz, Demos, MindMaps V. Conclusion: Evaluation form, Assignments, Project Suggestions 2 The rules for this class: Rule 1: Answer the quizz! Rule 2: Follow interactive demos on your computer! Rule 3: Take notes you have an evaluation form at this end of the class! Rule 4: Assignments to learn much more at home! 3 Agenda I. Introduction: Web of Things (WoT) o Pioneer o W3C WoT Architecture II. Protocols, Formats & Tools III. Towards the Semantic Web of Things (SWoT) IV. In parallel: Quizz, Demos, MindMaps V. Conclusion: Evaluation form, Assignments, Project Suggestions 4 Before IoT and WoT • Marc Weiser o Father of Ubiquitous Computing o 1991 o The Computer for the 21st Century [1] • Also Pervasive Computing, Context Awereness, etc/ • Also Internet of Things (IoT) o Kevin Ashton o 1999: Beginning of RFIDs (Radio Frequency Identification) o Usage of Internet • Without the need to use web technologies [1] http://www.ubiq.com/hypertext/weiser/SciAmDraft3.html 5 Connecting the things to the Web • Example: NetAtmo provides web-based applications to monitor data. 6 Assignment • Find and classify other devices (e.g., NetAtmo) providing web-based visualizations and access to data generated. o Documentation for developers, technologies, cost, etc. 7 Do you know who is this person? 8 Tim Berners Lee • Inventor of the World Wide Web in 1989 • Director of the World Wide Web Consortium (W3C) • He received the 2016 Turing Award "for inventing the World Wide Web, the first web browser, and the fundamental protocols and algorithms allowing the Web to scale“. 9 What is the Web of Things (WoT)? Who is the pioneer of WoT? 10 Pioneer of the Web of Things (WoT): Dominique Guinard • PhD thesis: A Web of Things Application Architecture [Guinard 2011] • Book: Building the Web of Things [Guinard and Trifa 2016] • Book: Using the Web to build the IoT [Guinard and Trifa 2016] • Co-founder & CTO EVRYTHNG • Web of Things community in 2007 11 Recommendations: WoT Books to read 12 Towards the Web of Things (WoT) • Internet of Things basics have been introduced in the previous classes. • How to send data produces by sensors/devices to the web o Connecting the things/objects to the Web! => The Web of Things (WoT)! • => We need some protocols? o The applications accessing the sensor data need to know how to communicate with the objects, e.g., which protocols to use. 13 OSI (Open Systems Interconnection) Model • OSI model already learnt (IoT, Reseaux, Programmable Web) • In this class: mainly focused on the application and presentation layers https://www.postscapes.com/internet-of-things-protocols/ 14 Web of Things (WoT) & OSI model layer Book: Building the Web of Things [Guinard and Trifa 2016] 15 HTTP: Hypertext Transfer Protocol • HTTP is an application layer protocol that allows web- based application to communicate and exchange data • Analogy: Carrier pigeons, post mail: 16 HTTP: List of Headers https://en.wikipedia.org/wiki/List_of_HTTP_header_fields 17 Assignment HTTP: Video to watch at home https://www.youtube.com/watch?v=eesqK59rhGA 18 W3C Web of Things (WoT) & W3C WoT Architecture • World Wide Web Consortium (W3C) o Standardisation for the web • W3C Web of Things Interest Group (WoT IG) proposed the notion of “Servient” that is currently being defined to standardized software objects in WoT applications [1] [1] https://www.w3.org/WoT/IG 19 Web Services with REST • REST: Representational State Transfer • REST is an architectural style for developing distributed applications and is the basis upon the web is built. • Loosely coupled services that can be easily reused • Services implemented using URIs, HTTP, and standardized media types. • Application programming interface (API) to interact with Things PhD Thesis: https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm [Fielding 2000] https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_1 20 REST • RESTful Web services o Java implementation: JAX-RS • HATEOAS: Hypermedia As The Engine Of Application State o A way for machines to understand APIs and navigate them without having any information about them beforehand • HYDRA o http://www.hydra-cg.com/ 21 Web of Things • Mainly based on Web technologies o Web services o URLs and URIs: set of readable characters and a way to locate the resource E.g., https://www.youtube.com/ o HTML for provifing the Graphical User Interface (GUI) o JavaScript o CSS for customizing the GUI 22 Agenda I. Introduction: Web of Things (WoT) II. Protocols, Formats, Useful Tools o Protocols: MQTT, CoAP, etc. o Format: XML, JSON, etc. o Tools: NodeRed, Postman, etc. III. Towards the Semantic Web of Things (SWoT) IV. In parallel: Quizz, Demos, MindMaps V. Conclusion: Evaluation form, Assignments, Project Suggestions 23 Interaction Protocols: Application Layer Interaction Protocols Request/Response Publish/Subscribe E.g., HTTP E.g., CoAP E.g., MQTT E.g., XMPP 24 Interaction Protocols: Application Layer Interaction Protocols Request/Response Publish/Subscribe E.g., HTTP E.g., CoAP E.g., MQTT E.g., XMPP 25 Request/Response • Request/response: the first computer sends a request for some data and the second computer responds to the request. o Example: HTTP, CoAP • Analogy: o Ring the doorbell, call somebody https://code.tutsplus.com/tutorials/http-the-protocol-every-web-developer-must-know-part- 1--net-31177 26 Interaction Protocols: Application Layer Interaction Protocols Request/Response Publish/Subscribe E.g., HTTP E.g., CoAP E.g., MQTT E.g., XMPP 27 Publish/subscribe • Publish/subscribe (Pub/sub): o Publishers are sending messages o Subscribers are receiving messages o Publishers and subscribers don’t know about the existence of one another. o Broker, which is known by both the publisher and subscriber, which filters all incoming messages and distributes them accordingly. o Example: MQTT, XMPP • Analogy: o Follow someone/something on Facebook and receive notifications 28 Interaction Protocols: Application Layer Interaction Protocols Request/Response Publish/Subscribe E.g., HTTP E.g., CoAP E.g., MQTT E.g., XMPP 29 HTTP 30 Postman: Plugin for Chrome to query APIs/web services Real-time Demo 31 Real-time Demo • http://devices.webofthings.io Book: Building the Web of Things [Guinard and Trifa 2016] 32 Postman Example Book: Building the Web of Things [Guinard and Trifa 2016] 33 Postman Example: Asking for JSON Book: Building the Web of Things [Guinard and Trifa 2016] 34 Content Negociation • The process of asking for a specific encoding is called content negociation in the HTTP 1.1 specification. 35 Postman Example: Asking data from a specific device Book: Building the Web of Things [Guinard and Trifa 2016] 36 Postman – HTTP Headers 37 Postman – HTTP Headers 38 Interaction Protocols: Application Layer Interaction Protocols Request/Response Publish/Subscribe E.g., HTTP E.g., CoAP E.g., MQTT E.g., XMPP 39 COAP Video https://www.youtube.com/watch?v=O4aaICV8ywA 40 CoAP: Constrained Application Protocol • Internet Engineering Task Force Standard for Internet of Things • Instead of having http:// o Coap://myhouse.local/lamps.7/status • HTTP like verbs: GET, POST, PUT, DELETE, OBSERVE, DISCOVERY 41 Interaction Protocols: Application Layer Interaction Protocols Request/Response Publish/Subscribe E.g., HTTP E.g., CoAP E.g., MQTT E.g., XMPP 42 MQTT video https://www.youtube.com/watch?v=exMm-fmU5ck 43 MQTT (MQ Telemetry Transport) Protocol • MQTT is a lightweight publish/subscribe messaging protocol • MQTT is light weight, open, simple, and designed so as to be easy to implement. • Eclipse Mosquitto™ is an open source message broker that implements the MQTT protocol [1] https://mosquitto.org/ http://docs.oasis-open.org/mqtt/mqtt/v3.1.1/os/mqtt-v3.1.1-os.html 44 Assignment: MQTT Hands-on session • Getting Started With MQTT and Java o http://tgrall.github.io/blog/2017/01/02/getting-started-with-mqtt/ 45 MQTT @Eclipse IoT • Eclipse: Integrated Environment Development (IDE) • Moquitto: light and full feature broker • Paho for clients (Java, C/C++, Python, Js, Go, Lua) • Moquette: Java Broker with websockets • Ponte: Node.js server bridging MQTT, HTTP, CoAP • Kura: M2M application framework with MQTT as default transport 46 CloudMQTT • Implementation of MQTT based on Mosquitto • Will be used for the hands-on session https://www.cloudmqtt.com/docs.html 47 Interaction Protocols: Application Layer Interaction Protocols Request/Response Publish/Subscribe E.g., HTTP E.g., CoAP E.g., MQTT E.g., XMPP 48 XMPP • XMPP: Extensible Messaging and Presence Protocol o Chat Protocol based on XML o Improved for IoT Interaction Protocols Request/Response Publish/Subscribe E.g., HTTP E.g., CoAP E.g., MQTT E.g., XMPP 49 Data exchange can be done with: Data Serialization Format JSON XML EXI CBOR CSV EXCEL Etc. 50 Data Format: XML • XML: eXtensible Markup Data Format Language o Markup language that defines a set JSON XML of rules for encoding documents in a format that is both human-readable and machine-readable o Less and les less popular because of EXI CBOR JSON CSV Excel Etc. • XML Example: 51 Data Format: JSON Data Format • See also Course Programmable JSON XML Web EXI CBOR • JSON is becoming more and more popular, it replaces more and more XML CSV Excel • JSON can be easily used in web services.
Load more

Recommended publications
  • ISSN: 2320-5407 Int. J. Adv. Res. 5(4), 422-426 RESEARCH ARTICLE
    ISSN: 2320-5407 Int. J. Adv. Res. 5(4), 422-426 Journal Homepage: - www.journalijar.com Article DOI: 10.21474/IJAR01/3826 DOI URL: http://dx.doi.org/10.21474/IJAR01/3826 RESEARCH ARTICLE CHALLENGING ISSUES IN OSI AND TCP/IP MODEL. Dr. J. VijiPriya, Samina and Zahida. College of Computer Science and Engineering, University of Hail, Saudi Arabia. …………………………………………………………………………………………………….... Manuscript Info Abstract ……………………. ……………………………………………………………… Manuscript History A computer network is a connection of network devices to data communication. Multiple networks are connected together to form an Received: 06 February 2017 internetwork. The challenges of Internetworking is interoperating Final Accepted: 05 March 2017 between products from different manufacturers requires consistent Published: April 2017 standards. Network reference models were developed to address these challenges. Two useful reference models are Open System Key words:- Interconnection (OSI) and Transmission Control Protocol and Internet OSI, TCP/IP, Data Communication, Protocol (TCP/IP) serve as protocol architecture details the Protocols, Layers, and Encapsulation communication between applications on network devices. This paper depicts the OSI and TCP/IP models, their issues and comparison of them. Copy Right, IJAR, 2017,. All rights reserved. …………………………………………………………………………………………………….... Introduction:- Network reference models are called protocol architecture in which task of communication can be broken into sub tasks. These tasks are organized into layers representing network services and functions. The layered protocols are rules that govern end-to-end communication between devices. Protocols on each layer will interact with protocols on the above and below layers of it that form a protocol suite or stack. The most established TCP/IP suite was developed by Department of Defence's Project Research Agency DARPA based on OSI suite to the foundation of Internet architecture.
    [Show full text]
  • RT-ROS: a Real-Time ROS Architecture on Multi-Core Processors
    Future Generation Computer Systems 56 (2016) 171–178 Contents lists available at ScienceDirect Future Generation Computer Systems journal homepage: www.elsevier.com/locate/fgcs RT-ROS: A real-time ROS architecture on multi-core processors Hongxing Wei a,1, Zhenzhou Shao b, Zhen Huang a, Renhai Chen d, Yong Guan b, Jindong Tan c,1, Zili Shao d,∗,1 a School of Mechanical Engineering and Automation, Beihang University, Beijing, 100191, PR China b College of Information Engineering, Capital Normal University, Beijing, 100048, PR China c Department of Mechanical, Aerospace, and Biomedical Engineering, The University of Tennessee, Knoxville, TN, 37996-2110, USA d Department of Computing, The Hong Kong Polytechnic University, Hong Kong, China article info a b s t r a c t Article history: ROS, an open-source robot operating system, is widely used and rapidly developed in the robotics Received 6 February 2015 community. However, running on Linux, ROS does not provide real-time guarantees, while real-time tasks Received in revised form are required in many robot applications such as robot motion control. This paper for the first time presents 20 April 2015 a real-time ROS architecture called RT-RTOS on multi-core processors. RT-ROS provides an integrated Accepted 12 May 2015 real-time/non-real-time task execution environment so real-time and non-real-time ROS nodes can be Available online 9 June 2015 separately run on a real-time OS and Linux, respectively, with different processor cores. In such a way, real-time tasks can be supported by real-time ROS nodes on a real-time OS, while non-real-time ROS nodes Keywords: Real-time operating systems on Linux can provide other functions of ROS.
    [Show full text]
  • OSI Model and Network Protocols
    CHAPTER4 FOUR OSI Model and Network Protocols Objectives 1.1 Explain the function of common networking protocols . TCP . FTP . UDP . TCP/IP suite . DHCP . TFTP . DNS . HTTP(S) . ARP . SIP (VoIP) . RTP (VoIP) . SSH . POP3 . NTP . IMAP4 . Telnet . SMTP . SNMP2/3 . ICMP . IGMP . TLS 134 Chapter 4: OSI Model and Network Protocols 4.1 Explain the function of each layer of the OSI model . Layer 1 – physical . Layer 2 – data link . Layer 3 – network . Layer 4 – transport . Layer 5 – session . Layer 6 – presentation . Layer 7 – application What You Need To Know . Identify the seven layers of the OSI model. Identify the function of each layer of the OSI model. Identify the layer at which networking devices function. Identify the function of various networking protocols. Introduction One of the most important networking concepts to understand is the Open Systems Interconnect (OSI) reference model. This conceptual model, created by the International Organization for Standardization (ISO) in 1978 and revised in 1984, describes a network architecture that allows data to be passed between computer systems. This chapter looks at the OSI model and describes how it relates to real-world networking. It also examines how common network devices relate to the OSI model. Even though the OSI model is conceptual, an appreciation of its purpose and function can help you better understand how protocol suites and network architectures work in practical applications. The OSI Seven-Layer Model As shown in Figure 4.1, the OSI reference model is built, bottom to top, in the following order: physical, data link, network, transport, session, presentation, and application.
    [Show full text]
  • Fedramp Master Acronym and Glossary Document
    FedRAMP Master Acronym and Glossary Version 1.6 07/23/2020 i​[email protected] fedramp.gov Master Acronyms and Glossary DOCUMENT REVISION HISTORY Date Version Page(s) Description Author 09/10/2015 1.0 All Initial issue FedRAMP PMO 04/06/2016 1.1 All Addressed minor corrections FedRAMP PMO throughout document 08/30/2016 1.2 All Added Glossary and additional FedRAMP PMO acronyms from all FedRAMP templates and documents 04/06/2017 1.2 Cover Updated FedRAMP logo FedRAMP PMO 11/10/2017 1.3 All Addressed minor corrections FedRAMP PMO throughout document 11/20/2017 1.4 All Updated to latest FedRAMP FedRAMP PMO template format 07/01/2019 1.5 All Updated Glossary and Acronyms FedRAMP PMO list to reflect current FedRAMP template and document terminology 07/01/2020 1.6 All Updated to align with terminology FedRAMP PMO found in current FedRAMP templates and documents fedramp.gov page 1 Master Acronyms and Glossary TABLE OF CONTENTS About This Document 1 Who Should Use This Document 1 How To Contact Us 1 Acronyms 1 Glossary 15 fedramp.gov page 2 Master Acronyms and Glossary About This Document This document provides a list of acronyms used in FedRAMP documents and templates, as well as a glossary. There is nothing to fill out in this document. Who Should Use This Document This document is intended to be used by individuals who use FedRAMP documents and templates. How To Contact Us Questions about FedRAMP, or this document, should be directed to ​[email protected]​. For more information about FedRAMP, visit the website at ​https://www.fedramp.gov​.
    [Show full text]
  • A Comparative Evaluation of OSI and TCP/IP Models
    International Journal of Science and Research (IJSR) ISSN (Online): 2319-7064 Index Copernicus Value (2013): 6.14 | Impact Factor (2013): 4.438 A Comparative Evaluation of OSI and TCP/IP Models P. Ravali Department of Computer Science and Engineering, Amrita Vishwa Vidhyapeetham, Bengaluru Abstract: Networking can be done in a layered manner. To reduce design complexities, network designers organize protocols. Every layer follows a protocol to communicate with the client and the server end systems. There is a piece of layer n in each of the network entities. These pieces communicate with each other by exchanging messages. These messages are called as layer-n protocol data units [n-PDU]. All the processes required for effective communication are addressed and are divided into logical groups called layers. When a communication system is designed in this manner, it is known as layered architecture. The OSI model is a set of guidelines that network designers used to create and implement application that run on a network. It also provides a framework for creating and implementing networking standards, devices, and internetworking schemes. This paper explains the differences between the TCP/IP Model and OSI Reference Model, which comprises of seven layers and five different layers respectively. Each layer has its own responsibilities. The TCP/IP reference model is a solid foundation for all of the communication tasks on the Internet. Keywords: TCP/IP, OSI, Networking 1. Introduction Data formats for data exchange where digital bit strings are exchanged. A collection of autonomous computers interconnected by a Address mapping. single technology is called as computer networks.
    [Show full text]
  • Internet of Things (Iot): Protocols White Paper
    INTERNET OF THINGS (IOT): PROTOCOLS WHITE PAPER 11 December 2020 Version 1 1 Hospitality Technology Next Generation Internet of Things (IoT) Security White Paper 11 December 2020 Version 1 About HTNG Hospitality Technology Next Generation (HTNG) is a non-profit association with a mission to foster, through collaboration and partnership, the development of next-generation systems and solutions that will enable hoteliers and their technology vendors to do business globally in the 21st century. HTNG is recognized as the leading voice of the global hotel community, articulating the technology requirements of hotel companies of all sizes to the vendor community. HTNG facilitate the development of technology models for hospitality that will foster innovation, improve the guest experience, increase the effectiveness and efficiency of hotels, and create a healthy ecosystem of technology suppliers. Copyright 2020, Hospitality Technology Next Generation All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of the copyright owner. For any software code contained within this specification, permission is hereby granted, free-of-charge, to any person obtaining a copy of this specification (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the above copyright notice and this permission notice being included in all copies or substantial portions of the Software.
    [Show full text]
  • The OSI Model: Understanding the Seven Layers of Computer Networks
    Expert Reference Series of White Papers The OSI Model: Understanding the Seven Layers of Computer Networks 1-800-COURSES www.globalknowledge.com The OSI Model: Understanding the Seven Layers of Computer Networks Paul Simoneau, Global Knowledge Course Director, Network+, CCNA, CTP Introduction The Open Systems Interconnection (OSI) model is a reference tool for understanding data communications between any two networked systems. It divides the communications processes into seven layers. Each layer both performs specific functions to support the layers above it and offers services to the layers below it. The three lowest layers focus on passing traffic through the network to an end system. The top four layers come into play in the end system to complete the process. This white paper will provide you with an understanding of each of the seven layers, including their functions and their relationships to each other. This will provide you with an overview of the network process, which can then act as a framework for understanding the details of computer networking. Since the discussion of networking often includes talk of “extra layers”, this paper will address these unofficial layers as well. Finally, this paper will draw comparisons between the theoretical OSI model and the functional TCP/IP model. Although TCP/IP has been used for network communications before the adoption of the OSI model, it supports the same functions and features in a differently layered arrangement. An Overview of the OSI Model Copyright ©2006 Global Knowledge Training LLC. All rights reserved. Page 2 A networking model offers a generic means to separate computer networking functions into multiple layers.
    [Show full text]
  • CBOR (RFC 7049) Concise Binary Object Representation
    CBOR (RFC 7049) Concise Binary Object Representation Carsten Bormann, 2015-11-01 1 CBOR: Agenda • What is it, and when might I want it? • How does it work? • How do I work with it? 2 CBOR: Agenda • What is it, and when might I want it? • How does it work? • How do I work with it? 3 Slide stolen from Douglas Crockford History of Data Formats • Ad Hoc • Database Model • Document Model • Programming Language Model Box notation TLV 5 XML XSD 6 Slide stolen from Douglas Crockford JSON • JavaScript Object Notation • Minimal • Textual • Subset of JavaScript Values • Strings • Numbers • Booleans • Objects • Arrays • null Array ["Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"] [ [0, -1, 0], [1, 0, 0], [0, 0, 1] ] Object { "name": "Jack B. Nimble", "at large": true, "grade": "A", "format": { "type": "rect", "width": 1920, "height": 1080, "interlace": false, "framerate": 24 } } Object Map { "name": "Jack B. Nimble", "at large": true, "grade": "A", "format": { "type": "rect", "width": 1920, "height": 1080, "interlace": false, "framerate": 24 } } JSON limitations • No binary data (byte strings) • Numbers are in decimal, some parsing required • Format requires copying: • Escaping for strings • Base64 for binary • No extensibility (e.g., date format?) • Interoperability issues • I-JSON further reduces functionality (RFC 7493) 12 BSON and friends • Lots of “binary JSON” proposals • Often optimized for data at rest, not protocol use (BSON ➔ MongoDB) • Most are more complex than JSON 13 Why a new binary object format? • Different design goals from current formats – stated up front in the document • Extremely small code size – for work on constrained node networks • Reasonably compact data size – but no compression or even bit-fiddling • Useful to any protocol or application that likes the design goals 14 Concise Binary Object Representation (CBOR) 15 “Sea Boar” “Sea Boar” 16 Design goals (1 of 2) 1.
    [Show full text]
  • 1.2. OSI Model
    1.2. OSI Model The OSI model classifies and organizes the tasks that hosts perform to prepare data for transport across the network. You should be familiar with the OSI model because it is the most widely used method for understanding and talking about network communications. However, remember that it is only a theoretical model that defines standards for programmers and network administrators, not a model of actual physical layers. Using the OSI model to discuss networking concepts has the following advantages: Provides a common language or reference point between network professionals Divides networking tasks into logical layers for easier comprehension Allows specialization of features at different levels Aids in troubleshooting Promotes standards interoperability between networks and devices Provides modularity in networking features (developers can change features without changing the entire approach) However, you must remember the following limitations of the OSI model: OSI layers are theoretical and do not actually perform real functions. Industry implementations rarely have a layer‐to‐layer correspondence with the OSI layers. Different protocols within the stack perform different functions that help send or receive the overall message. A particular protocol implementation may not represent every OSI layer (or may spread across multiple layers). To help remember the layer names of the OSI model, try the following mnemonic devices: Mnemonic Mnemonic Layer Name (Bottom to top) (Top to bottom) Layer 7 Application Away All Layer 6 Presentation Pizza People Layer 5 Session Sausage Seem Layer 4 Transport Throw To Layer 3 Network Not Need Layer 2 Data Link Do Data Layer 1 Physical Please Processing Have some fun and come up with your own mnemonic for the OSI model, but stick to just one so you don't get confused.
    [Show full text]
  • Decentralized Identifier WG F2F Sessions
    Decentralized Identifier WG F2F Sessions Day 1: January 29, 2020 Chairs: Brent Zundel, Dan Burnett Location: Microsoft Schiphol 1 Welcome! ● Logistics ● W3C WG IPR Policy ● Agenda ● IRC and Scribes ● Introductions & Dinner 2 Logistics ● Location: “Spaces”, 6th floor of Microsoft Schiphol ● WiFi: SSID Publiek_theOutlook, pwd Hello2020 ● Dial-in information: +1-617-324-0000, Meeting ID ● Restrooms: End of the hall, turn right ● Meeting time: 8 am - 5 pm, Jan. 29-31 ● Breaks: 10:30-11 am, 12:30-1:30 pm, 2:30-3 pm ● DID WG Agenda: https://tinyurl.com/didwg-ams2020-agenda (HTML) ● Live slides: https://tinyurl.com/didwg-ams2020-slides (Google Slides) ● Dinner Details: See the “Dinner Tonight” slide at the end of each day 3 W3C WG IPR Policy ● This group abides by the W3C patent policy https://www.w3.org/Consortium/Patent-Policy-20040205 ● Only people and companies listed at https://www.w3.org/2004/01/pp-impl/117488/status are allowed to make substantive contributions to the specs ● Code of Conduct https://www.w3.org/Consortium/cepc/ 4 Today’s agenda 8:00 Breakfast 8:30 Welcome, Introductions, and Logistics Chairs 9:00 Level setting Chairs 9:30 Security issues Brent 10:15 DID and IoT Sam Smith 10:45 Break 11:00 Multiple Encodings/Different Syntaxes: what might we want to support Markus 11:30 Different encodings: model incompatibilities Manu 12:00 Abstract data modeling options Dan Burnett 12:30 Lunch (brief “Why Are We Here?” presentation) Christopher Allen 13:30 DID Doc Extensibility via Registries Mike 14:00 DID Doc Extensibility via JSON-LD Manu
    [Show full text]
  • Interoperability for the Semantic Web: a Loosely Coupled Mediation Approach Antoine Zimmermann
    Interoperability for the Semantic Web: A Loosely Coupled Mediation Approach Antoine Zimmermann To cite this version: Antoine Zimmermann. Interoperability for the Semantic Web: A Loosely Coupled Mediation Ap- proach. Modeling and Simulation. Université Jean Monnet, 2021. tel-03163932 HAL Id: tel-03163932 https://tel.archives-ouvertes.fr/tel-03163932 Submitted on 9 Mar 2021 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. These` d'habilitation Universite´ Jean Monnet Ecole´ doctorale 488 Sciences, Ing´enierieet Sant´e(SIS) Interop´erabilit´epour le Web s´emantique : une approche par m´ediationfaiblement coupl´ee Soutenue publiquement par : Antoine Zimmermann MINES Saint-Etienne´ Membres du jury : Olivier Boissier Professeur, MINES Saint-Etienne´ Tuteur de recherche Pierre-Antoine Champin Ma^ıtrede conf´erenceHDR, Universit´eClaude-Bernard Examinateur J´er^ome Euzenat Directeur de recherche, Inria Examinateur Fabien Gandon Directeur de recherche, Inria Rapporteur Andreas Harth Professeur, Friedrich-Alexander-Universit¨atErlangen-N¨urnberg Rapporteur
    [Show full text]
  • Resilient Video Coding for Wireless and Peer-To-Peer Networks
    Resilient Video Coding for Wireless and Peer-to-peer Networks Resilient Video Coding for Wireless and Peer-to-peer Networks Proefschrift ter verkrijging van de graad van doctor aan de Technische Universiteit Delft, op gezag van de Rector Magnificus Prof. dr. ir. J. T. Fokkema, voorzitter van het College voor Promoties, in het openbaar te verdedigen op 2 oktober 2007 om 10.00 uur door Jacco Reynoud TAAL elektrotechnisch ingenieur geboren te Rotterdam. Dit proefschrift is goedgekeurd door de promotor: Prof. dr. ir. R. L. Lagendijk Samenstelling promotiecommissie: Rector Magnificus, voorzitter Prof. dr. ir. R. L. Lagendijk, Technische Universiteit Delft, promotor Prof. dr. ir. P. F. A. Van Mieghem Technische Universiteit Delft Prof. dr. ir. H. J. Sips Technische Universiteit Delft Prof. dr. ir. C. H. Slump Universiteit Twente Prof. dr. ir. P. H. N. de With Technische Universiteit Eindhoven Univ.-Prof. Dr.-Ing. Eckehard Steinbach Technische Universität München Dr. A. Reibman AT&T Research A This document is typeset with the LTEX ÑeÑÓiÖ typesetting system. The photo on the cover is taken in April 2006 in the pedestrians tunnel connecting the old and new part of Shanghai. This work was carried out in the ASCI graduate school. ASCI dissertation series number 155 Advanced School for Computing and Imaging ISBN: 978-90-9022238-7 Copyright c 2007 by J. R. Taal All rights reserved. No part of this material may be reproduced or transmitted in any form or by any means, electronic, mechanical, including photocopying, recording or by any information storage and retrieval system, without the prior permission of the copyright owner.
    [Show full text]