Next Steps Bundang, Korea, July 2018.

Slides:



Advertisements
Similar presentations
OASIS OData Technical Committee. AGENDA Introduction OASIS OData Technical Committee OData Overview Work of the Technical Committee Q&A.
Advertisements

This presentation is property of CREATE-NET and is protected by Copyright © Best practices – Semantic interoperability Collaborative Open Market to Place.
A problem in IMS Learning Design To promote interoperability, few services Local tool frameworks like LAMS have much richer tool environment –Easy provisioning.
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
Kay Herzam Herzam IT Consulting What‘s new in ASP.NET MS TechTalk.
Just a collection of WS diagrams… food for thought Dave Hollander.
1 Document Object Model (DOM) MV4920 – XML 24 September 2001 Simon R. Goerger MAJ, US Army
Web Services Glossary Summary of Holger Lausen
TF-DI Meeting 13-Aug Agenda Discovery presentation from William Miller Review of discussions at F2F Sunnyvale Interaction patterns of tech landscape.
Sharing Using Social Networks in a Composable Web of Things Presenter: Yong-Jin Jeong Korea University of Technology and Education.
ANSTO E-Science workshop Romain Quilici University of Sydney CIMA CIMA Instrument Remote Control Instrument Remote Control Integration with GridSphere.
Save time. Reduce costs. Find and reuse interoperability solutions on Joinup for developing European public services Nikolaos Loutas
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
9 th Open Forum on Metadata Registries Harmonization of Terminology, Ontology and Metadata 20th – 22nd March, 2006, Kobe Japan. Presentation Title: Day:
Hypermedia Design for Machine APIs Web Scale Architecture for the Web of Things Michael J Koster 14 September 2015.
WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.
6. Protocol Standardization for IoT 1.  TCP/IP  HTML and HTTP  The difference between the Internet and the World Wide Web The Internet is the term.
Overview of SC 32/WG 2 Standards Projects Supporting Semantics Management Open Forum 2005 on Metadata Registries 14:45 to 15:30 13 April 2005 Larry Fitzwater.
An introduction to oneM2M
1 HGI MESSAGE TO ONEM2M TECHNICAL PLENARY HANS WERNER BITZER, DEUTSCHE TELEKOM VICE CHAIR, HGI ONEM2M TP#19, SOPHIA ANTIPOLS, FRANCE.
Plug-in Architectures Presented by Truc Nguyen. What’s a plug-in? “a type of program that tightly integrates with a larger application to add a special.
©Silberschatz, Korth and Sudarshan10.1Database System Concepts W3C - The World Wide Web Consortium W3C - The World Wide Web Consortium.
Extending the Think Description with Context W3C WoT IG - TD Break Out Session Sapporo TPAC, October 2015 Darko Anicic.
WoT Outreach: joint slide set Outreach slide set aims to increase the awareness of W3C’s WoT work # Comments Arne: Abgrenzung zu anderen Initiativen.
International Planetary Data Alliance Registry Project Update September 16, 2011.
What is oneM2M? 2 Covers: Requirements Architecture API specifications Security Interoperability Facilitate, implement and promote IoT.
Getting Started with a W3C WoT Project Eclipse Virtual IoT Meetup, 16 Jun 2016.
October 2014 HYBRIS ARCHITECTURE & TECHNOLOGY 01 OVERVIEW.
W3C WoT Thing Description
Protocol Bindings Joint oneM2M Call, 31 Aug 2016.
4.01 How Web Pages Work.
Public Working Groups Working Group, Webinars and Analysis
Eclipse Vorto Alexander Edelmann.
MEF Modeling Activities
OCF Data Model Michael J Koster.
Overview of oneM2M Home Appliances Information Model
ONEM2M RELEASE 2: SETTING THE STANDARD FOR IOT INTEROPERABILITY
Status of Active Work Items Level of Completeness
Internet Of Things (IoT)
oneM2M Work on IoT Semantic and Data Model Interoperability
Consolidated M2M standards boost the industry
Issues for TPAC Plugfest
GENIVI – W3C Collaboration October 10, 2017 | AMM Seoul
WPM ad-hoc group report TP#25
WG5 – MAS#27 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:
Prof John Davies, BT Future Cities: The role of IoT and Semantic Technology Transforming Data into Value: Data Interoperability & Open Data Platforms.
Stanford Medical Informatics
2018/7/ Smart Grid Activity Will be formed as Executive Committee Study Group Depending on how PAR is developed: Option 1: Form Technical Advisory.
oneM2M Work on IoT Semantic and Data Model Interoperability
W3C Autotive Update Kaz Ashimura, W3C 16 May 2017.
Overview onem2m.org.
Overview onem2m.org.
W3C WoT Thing Description
Prof John Davies, BT Future Cities: The role of IoT and Semantic Technology Transforming Data into Value: Data Interoperability & Open Data Platforms.
Applications of IFLA Namespaces
An introduction to oneM2M
Collaborative Open Market to Place Objects at your Service
Role Models and Lifecycles in IoT and their Impact on the W3C WoT Thing Description Michele Blank.
Existing Designs and Prototypes at RPI
An Introduction to Software Architecture
LOD reference architecture
Semantic Web Update W3C RDF, OWL Standards, Development and Applications Dave Beckett.
IEEE MEDIA INDEPENDENT HANDOVER DCN:
Why IIIF? Shane Huddleston Jeff Mixter Dave Collins Product Manager
4.01 How Web Pages Work.
W3C WoT Standardization
Web-based Imaging Management Service WIMS Working Group
ETSI TC MTS WG TST introduction
Profiles Guidance & Vocabulary
Introduction to TDL and TOP
Presentation transcript:

Next Steps Bundang, Korea, July 2018

Prague Recharter Brainstorming WG Normative: Thing Directory Make it a „Service Thing“ (i.e., it has a TD) WG Informal: Synchronization of Servients / Thing Proxies IG: Liaisons OCF oneM2M Echonet OPC UA ETSI ISG CIM OpenFog IG: Outreach and PlugFests Webpages Tool Development/Provisioning Playground See conformity testing WG: Lifecycle Management Thing Templates Already going into current TD spec Thing Types? Related to Thing Templates May use Web links WG: Hypermedia Patterns  NEED Entity Description MECHANISM IN CURRENT SPEC Action Description – monior, update, cancel running Actions Event Description – alerts with Interactions Thing as first-class citizen – define what that is WG: WoT Vocabularies Thing/Servient Management Cross-Interaction dependencies (operational constraints)  NEED GOOD EXTENSION POINT IN CORE TD VOCABULARY (e.g., „reference“ term) Security roles Thing Management (through „Management Things“ that have Interactions with standardized vocabulary) Servient/runtime management (e.g., security metadata, execution environment setup, (Proxy) Thing installation) Test Interface (in particular for Things without Scripting API) Web frontends for „install from a browser“ (cross-site scripting issues) IG: Incubation of existing concepts, Exploration of new Concepts IG: Communication patterns Protocol Bindings SubProtocols (long-poll, streaming, multi-part, SSE, Webhooks) Default protocol binding for convergence IG: WebSocket Subprotocol for WoT (maybe IETF collaboration) Mozilla proposal Panasonic proposal for Events IG: System Things Local hardware API based on Thing abstraction Discovery („local“ filter) Driver model for servients Vocabulary TD-external metadata (import/include, cf. HTML <link> to CSS) WoT Representation Formats? Payments Marketing Optional ontologies Accessibility New Interaction Types?

WG WG Normative: Thing Directory Make it a „Service Thing“ (i.e., it has a TD) WG Informal: Synchronization of Servients / Thing Proxies WG: Lifecycle Management Thing Management (through „Management Things“ that have Interactions with standardized vocabulary) Servient/runtime management (e.g., security metadata, execution environment setup) Proxy Thing installation Test Interface (in particular for Things without Scripting API) Web frontends for „install from a browser“ (cross-site scripting issues) Thing Templates Already going into current TD spec Thing Types? Related to Thing Templates May use Web links WG: Hypermedia Patterns  NEED Entity Description MECHANISM IN CURRENT SPEC: application/wot+json Action Description – monior, update, cancel running Actions Event Description – alerts with Interactions Thing as first-class citizen – define what that is  TD / link to TD WG: WoT Vocabularies  external like iot.schema.org Thing/Servient Management Cross-Interaction dependencies (operational constraints)  NEED GOOD EXTENSION POINT IN CORE TD VOCABULARY (e.g., „reference“ term) Security roles TD-external metadata (import/include, cf. HTML <link> to CSS)  LINKS, just use them

IG (1/2) IG: Liaisons IG: Outreach and PlugFests OCF oneM2M Echonet OPC UA ETSI ISG CIM OpenFog IG: Outreach and PlugFests Webpages Tool Development/Provisioning Playground See conformity testing

IG (2/2) IG: Incubation of existing concepts, Exploration of new Concepts IG: Communication patterns Protocol Bindings SubProtocols (long-poll, streaming, multi-part, SSE, Webhooks) Default protocol binding for convergence IG: WebSocket Subprotocol for WoT (maybe IETF collaboration) Mozilla proposal Panasonic proposal for Events IG: System Things Local hardware API based on Thing abstraction Discovery („local“ filter) Driver model for servients Vocabulary Payments Marketing Optional ontologies Accessibility New Interaction Types?

Scoping WG IG Thing Directory Lifecycle Management & Servient I/Fs Schemas for binary payload formats Security Guidelines? Maintenance Binding Templates Security vocabulary Grow W3C WoT ecosystem Multi-stakeholder demo Semantic capabilities Other services (calendars etc.) Vertical focus (interop, openness, …) Smart Buildings Smart Cities Collaborations iot.schema.org Linked Building Data Community Group BRICK Haystack Echonet Consortium ETSI CIM IIC Eclipse IoT (Smarthome, Vorto)