00:10:55 RRSAgent has joined #wot 00:10:55 logging to http://www.w3.org/2017/05/16-wot-irc 00:11:17 Meeting: WoT f2f in Osaka - Tuesday, OpenDay 00:11:31 remote: Michael_Koster, Yingying_Chen 00:11:49 topic: Greetings from Panasonic 00:12:01 Ohsumi-san and Fuchiue-san 00:12:21 topic: Today's agenda - Naka-san 00:12:46 naka: explains today's schedule 00:12:56 ... and provide logistics information 00:13:12 ... coffee and lunch will be served at the HUB space 00:13:38 ... demo available at the presentation room during coffee breaks 00:13:48 .... wifi available 00:14:00 ... demo tour and social dinner in the evening 00:14:16 ... leaving here at 16:40 00:14:40 ... ISO rep not available, so Naka-san will give brief explanation 00:14:57 topic: ISO/IEC JTC1 SC41 work 00:15:04 naka: scope and standards 00:15:29 ... explains the work briefly 00:16:03 taki has joined #wot 00:16:21 kaz: IRC is available at #wot 00:16:22 naomi has joined #wot 00:16:32 ryuichi has joined #wot 00:16:34 tokuyama has joined #wot 00:16:40 yamada has joined #wot 00:16:43 naka: Getting Started with WoT Project 00:17:03 kaji: [ Conceptual Architecture and Objective ] 00:17:40 ktoumura has joined #wot 00:18:14 shigeya has joined #wot 00:18:15 ohura has joined #wot 00:18:37 shigeya has left #wot 00:18:44 shigeya has joined #wot 00:19:06 ... [ Practical viewpoint of Silo vs WoT ] 00:19:41 ... one-stop universal platform 00:20:26 toru has joined #wot 00:21:19 ... [ WoT Framework example ] 00:22:06 ... [ Usage of Semantics on WoT ] 00:22:34 ... global identical vocabulary needs to be defined 00:22:46 ... regardless of languages, etc. 00:23:23 Katsuyoshi_Naka has joined #wot 00:23:36 ... attribute for discovery 00:24:45 ... [ WoT Framework example ] 00:25:37 ... WoT client and WoT server 00:25:55 sano has joined #wot 00:27:12 ... [ WoT Servient building block ] 00:27:45 ... servient has both the capabilities of server and client 00:27:51 ... [ WoT server in device itself ] 00:28:24 ... [ WoT server for constraint device ] 00:29:18 ... [ WoT interoperability PoC in Panasonic ] 00:29:25 ... 5 different services 00:29:38 ... smart apps platform 00:29:44 ... smart home platform 00:30:14 ... IRKit platform 00:30:20 ... Hue platform 00:30:28 ... Alexa platform 00:30:49 s/services/services included in Panasonic demo yesterday/ 00:33:23 kaji: [ Cross Interaction Demo ] 00:34:17 ... KDDI tmp sensor and Siemens app 00:34:40 ... Siemens app controls Panasonic light 00:34:51 ... Fujitsu app also controls Panasonic light 00:35:03 ... [ Standardization process in WoT ] 00:35:16 ... Yongjing mentioned the story during the AC meeting in Beijing 00:36:47 ... please join WoT IG/WG! 00:37:07 ... questions/comments? 00:37:30 (no specific questions/comments) 00:37:37 kaji: shows photos 00:37:50 ... from Santa Clara meeting 00:38:26 ... and video from Osaka 00:38:54 ... and then video from Santa Clara again 00:40:57 sebastian has joined #wot 00:41:00 topic: Logistics note - Naka-san 00:41:03 smatsui3 has joined #WoT 00:41:10 naka: IRC channel: #wot 00:41:12 yongjing_zhang has joined #wot 00:41:13 Maurice has joined #wot 00:41:27 Hiroyuki_Nishida has joined #wot 00:41:36 Yoji_Nagao has joined #wot 00:41:37 Kanji_Mihara has joined #wot 00:41:38 tanakak has joined #wot 00:41:38 ... can join using http://irc.w3.org/?channels=#wot 00:41:43 Yasufumi_Ichikawa has joined #wot 00:41:52 barryleiba has joined #wot 00:42:03 topic: Star Micronics introduction - Miura-san 00:42:17 nunoken has joined #wot 00:42:19 Yoshihisa_Homma has joined #wot 00:42:22 koji: tx for inviting me 00:43:00 Yoshio_Takahashi has joined #WoT 00:43:22 ... 3 main products 00:43:36 NUchida has joined #wot 00:43:46 ... automatic lathes, small printers, precision products 00:44:00 kajimoto has joined #wot 00:44:05 shinya_nakai has joined #wot 00:44:08 ... legacy POS printer 00:44:23 ... 2nd top world share 00:44:26 Matsuda has joined #wot 00:44:31 ... also mobile POS printer 00:44:47 ... 1st world share 00:44:56 ... various partners 00:45:05 ... POS market pyramid 00:45:17 ... mobile POS market is our focus 00:45:38 ... why Star is No.1? 00:45:44 shinya_nakai has left #wot 00:45:55 ... keeping up with the trend of smartphone/tablet market 00:46:02 ... many innovative solutions 00:46:23 Katsuyoshi_Naka has joined #wot 00:46:26 ... MFi certified 00:46:32 ... multiple lineups 00:46:45 ... easy-to-use SDK freely available 00:46:51 ... so easy setup 00:47:12 ... original software services like WebPRNT, PassPRNT and AllReceipts 00:47:24 ... that's why Star's printers are de-facto 00:47:46 ... software solutions including Star SDK 00:48:03 ... both for iOS and Android 00:48:20 sam has joined #wot 00:48:28 ... not only APIs but also source codes 00:48:37 ... Star WebPRNT 00:49:11 ... from iOS, Android and Surface 00:49:36 ... HTML/JS + StarLine XML/HTTP over wifi 00:49:54 ... web bridge function for Bluetooth 00:50:23 ... Star PassPRNT as software-based printer server 00:50:34 ... driver application 00:51:12 remote+ Sam 00:51:22 ... Star AllReceipts 00:51:46 ... digital receipt is provided by AllReceipts service 00:51:50 ... current situation 00:52:08 ... our printer supports this kind of multiple I/F 00:52:25 ... USB-A, USB-B, LAN and another USB-A 00:52:36 ... tx 00:53:19 kaz: ok to upload this presentation? 00:53:25 koji: let me check 00:53:47 mm: printer driver as a web service? 00:53:51 ... payload as XML? 00:53:53 koji: yes 00:54:36 kaz: koji mentioned a difficulty of basic printer which restricts sizes 00:54:46 ... in this case any data is available, the slide says 00:54:54 ... do you have any specific problems? 00:54:58 Kanji_Mihara_ has joined #wot 00:55:23 kaz: w3c wot group has a difficulty of streaming data 00:55:32 ... we need some method on it 00:55:40 ... how to specify data 00:55:58 koji: BoS printer market we need to have 100% guarantee 00:56:20 ... streaming idea works but not perfect solution for 100% guraantee 00:56:33 ... we have to set data links inside of Thing Description 00:56:44 ... client have to count data 00:56:45 s/a difficulty/difficulty/ 00:56:50 mm; JSON market 00:57:03 ... tickets 00:57:14 ... are you looking that market? 00:57:36 koji: we might sell ticket service 00:57:47 kaz: mm, you mean online store? 00:57:57 mm: no, my point is point of sale 00:58:41 ... we have IoT application to log in 00:58:55 koji: we support multipul language 00:59:03 ... and right to left, left to right 00:59:19 ... this is not for wot but we focus Thing Description 00:59:23 kaz: another question 00:59:38 ... do you have usual http and @2 style of printing? 00:59:46 ... W3C CSS writing mode spec 00:59:56 ... do you use that kind of specs on printing? 00:59:59 koji: yes 01:00:06 ... it'll fit our concerning point 01:00:15 ... this software idea can fit as well 01:00:28 ... inside of apps to generate convert commands 01:00:41 ... it can easy to generate receipt 01:00:45 kaz: interesting point 01:00:56 ... relating semantics and CSS style 01:01:08 koji: any questions? 01:01:09 s/relating/relationship between/ 01:03:23 Sumie_Miki has joined #wot 01:16:20 barryleiba has joined #wot 01:19:32 dsr has joined #wot 01:27:12 YosukeUkita has joined #wot 01:27:36 [ morning break ] 01:28:10 SeijiNimura has joined #wot 01:28:32 n_uchida has joined #wot 01:30:00 naomi has joined #wot 01:30:03 naomi has joined #wot 01:35:00 Susumu has joined #wot 01:36:21 hitoshi has joined #WoT 01:39:34 toru has joined #wot 01:41:29 Miki has joined #wot 01:41:35 taki has joined #wot 01:41:52 topic: OCF 1.0 Overview - Michael McCool 01:42:00 mm: [Outline] 01:42:10 Takai has joined #WoT 01:42:33 ohura2 has joined #wot 01:42:34 ... OCF history, background and markets 01:42:45 ... OCF architecture and principles 01:42:47 ... working on diagrams 01:43:07 ... changes between OIC 1.1 and OCF 1.0 draft candidate 01:44:25 ... [OCF - High Level Goals] 01:44:32 ... easy for developers 01:45:04 ... common data model 01:45:18 ... initial target is smart home 01:45:26 ... [OCF&IoTivity] 01:45:46 .., open source implementation 01:45:58 ... budget under Linux Foundation 01:46:11 Yoshihisa_Homma has joined #wot 01:46:16 ... C++ implementation and now Node implementation 01:46:56 ... primary focus on CoAP 01:47:19 ... [OCF - Conceptual Framework] 01:47:38 ... profiles, core framework and transports 01:47:55 ... core framework is standard mechanism 01:48:12 ... interaction/data model, resource model 01:48:23 ... discovery, data transmission, data management, device management 01:48:42 ... transports: bluetooth, wifi, lte, ... 01:48:51 ... [OCF - Resource Model] 01:49:13 SeijiNimura has joined #wot 01:49:55 ... common properties and resource specific properties 01:50:07 ... interfaces basically provide views 01:50:18 ... sensor view, etc. 01:51:12 ... [Resource Model - examples] 01:51:30 ... resource URI: /a/light1 and /a/fan1 01:52:45 ... /a/light1 - rt: oic.ex.light; if: oic.if.rw; prop: discoverable, observable; n: myHallWayLight; State: 0 (off); Dim Level: 0 01:53:07 ... [Common Interaction Model - Transport Agnostic] 01:53:23 ... Create, Retrieve, Update, Delete, Notify 01:56:13 ... [Let's look deeper at a Resource ...] 01:56:20 ... Server - DevA 01:56:49 ... [There can be more Properties] 01:56:58 ... [Resource Type - Data Modeling] 01:57:05 ... 2 things to describe metadata 01:57:18 ... first thing is set of properties 01:57:26 ... by JSON Schema 01:57:48 ... and verbs using RAML (ReStful API Modelling Language) 01:58:03 ... describes the request and response 01:58:17 ... and now the third option 01:58:29 ... emerging standard, Swagger (aka, open API) 01:58:37 ... OIC introspection 01:59:21 ... [Table 19: oic.wk.p resource type definition] 01:59:47 ... OCF specification defines "oic.wk.p" resource type for platform and its list of properties 02:00:00 ... [Link] 02:00:11 ... how to define te connection between two resources 02:00:21 ... /a/room and /switch 02:00:27 ... relative URL 02:00:33 ... { 02:00:43 ... "href": "/switch", 02:00:50 ... "rel": "contains", 02:00:59 ... "anchor": "/a/room", 02:01:12 ... ... 02:01:18 ... [Collections] 02:01:28 ... also scenes 02:01:36 ... set of devices 02:01:45 ... can be stores 02:01:46 s/stores/stored/ 02:01:55 ... [Collections...example] 02:02:05 ... "Room" collection - room has lights and fan 02:02:27 ... /my/room/1 02:02:30 ... { 02:02:36 ... "rt": "acme.room", 02:02:59 ... "if": ["oic.if.r", "oic.if.rv"], 02:03:01 ... ... 02:03:07 ... [Interfaces] 02:03:12 ... subset of resources 02:03:26 ... interface provides a "view" into a Resource or Collection 02:03:41 ... Interface defines allowed methods and semantics on that "view" 02:03:50 ... OCF has a set of predefined Interfaces 02:04:09 ... [OCF ER Model] 02:04:23 ... not from the official OCF spec... 02:04:47 ... platform-devices 02:05:01 ... WoT semantics define similar model 02:05:25 ... [Major Changes in OCF 1,0 (Draft) CR from OIC 11 02:05:30 s/11/1.1/ 02:05:38 s/1.1/1.1]/ 02:06:11 ... Swagger/OpenAPI for: data modeling, introspection, RAML is still used in main spec definition 02:06:35 ... Enhanced security: alignment with IETF ACE and AllJoyn 02:06:45 ... better specification of uses of certificates 02:06:54 ... better management of onboarding and offboarding processes 02:07:07 ... mandatory access control, system management 02:07:47 ... [Summary] 02:07:55 ... resource-oriented architecture 02:08:39 ... IoTivity 02:08:45 ... New features in OCF 1.0 02:09:59 ... Questions? 02:10:14 dsr: relationship between OCF and narrow-band verticals? 02:10:37 mm: OCF work is protocol/transport-agnostic 02:10:53 ... CoAP designed based on UDP 02:12:16 tanakak has joined #wot 02:12:45 topic: T2TRG Overview Discussion - Michael Koster 02:12:56 mk: [T2TRG] 02:13:01 ... started in March 2015 02:13:11 ... chartered by IRTF 02:13:35 ... investigate "Internet of Things" applications and architecture beyond IETF CoRE/CoAP 02:14:25 ... [Topics] 02:14:29 ... quite broad 02:14:37 ... REST and Hypermedia for connected things 02:14:49 ... Event-state duality, pub-sub pattern, notification 02:14:58 ... Connected Thing Life Cycle 02:15:04 ... Management and Operations 02:15:27 ... Work with Industry SDOs and Fora - work with W3C WoT on data models and semantics 02:15:57 s/narrow-band verticals/narrow band IoT/ 02:17:02 ... Plugtests, Interop tests 02:17:40 ... Practical Semantic Interoperability 02:17:45 ... Mobile code 02:17:47 ... Security 02:18:53 ... [Research Drafts] 02:19:03 ... RESTful design guidance 02:19:12 ... Security challenges for IoT 02:19:38 ... Hypermedia content types 02:19:53 ... CoRAL - CBOR Encoding of Hypermedia Controls 02:20:07 ... HSML - SenML + Link-Format Hypermedia Controls 02:20:12 ... [Events] 02:20:23 ... meet in conjunction with IETF and related activities 02:20:33 ... joint meetings with Industry Fora, e.g., OCF 02:20:49 ... semantic interop in conjunction with IETF 99 in Prague, July 15-16 02:20:57 .. planning for semantic interop events 02:21:12 ... multiple device ecosystems participating 02:21:35 ... [Meetings] 02:22:46 ... IETF 93, IETF 94, Jan 2016 (Sophia Antipolis Plugtest), March 2016 (with IAB Semantic Interop), IETF 95, IETF 96, Sep. 2016 (Joint with W3C WoT IG), Oct. 2016 (with Eclipsecon), IETF97, Mar. 2017 (joint with OCF), ... 02:22:52 ... [Next T2TRG Event] 02:23:04 ... T2TRG Joint Semantic and Hypermedia Interoperability Workshop 02:23:13 ... with IETF 98, Prague, Jul 15-16 02:23:28 ... OCF, LWM2M/IPSO, W3C WoT, iot.schema.org 02:23:54 ... example topics: cross-ecosystem semantic interop planning, hypermedia controls for actions, hypermedia-driven apps, models and model translation 02:24:56 ... [References] 02:25:09 ... datatracker.ietf.org/rg/t2trg/charter 02:25:16 ... github.com/t2trg 02:25:26 ... datatracker.ietf.org/rg/t2trg/documents/ 02:25:34 s|charter|charter/| 02:25:37 ... questions? 02:25:45 rrsagent, make log public 02:25:52 rrsagent, draft minutes 02:25:52 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 02:26:34 mm: next f2f of wot will be held Duseldolf 02:26:46 s/Duseldolf/Dusseldolf/ 02:27:08 mk: ending on Thursday and will travel to Prague on Friday 02:27:48 Zakim has left #wot 02:29:13 topic: Security Process in W3C WoT - Elena Reshetova 02:29:31 er: [Importance of Security for WoT] 02:29:55 ... why security is important for WoT? 02:30:13 ... 10 things to know about the Oct 21 IoT DDos attacks 02:31:25 ... avarage IoT device is compromised after being online for 6 mins 02:31:35 ... large-scale IoT security breach coming in 2017 02:31:58 ... here are the biggest IoT security threats facing the enterprise in 2017 02:32:04 ... very popular topic 02:32:15 ... [Always good to remember] 02:32:46 ... 3 principles: start early, involve everyone and explore existing solutions 02:34:59 ... [How do we do it?] 02:35:16 ... 1. threat model - understand what you need to protect and why 02:35:47 ... 2. scoping - organize and prioritize threats, define security objectives 02:36:07 ... 3. state of the art - study related areas and their approaches to security 02:36:23 ... 4. solutions - find a suitable mitigation for each in-scope threat 02:36:46 ... 5. implementation and evaluation - implement and test each solution 02:36:50 hitoshi has joined #WoT 02:37:47 Yoji_Nagao has joined #wot 02:39:12 shinya_nakai has joined #wot 02:39:36 ... questions? 02:39:57 ... (continues) 02:40:24 ... [1. Threat model - Understand what you need to protect and why] 02:40:29 sano has joined #wot 02:40:45 ... stakeholders, assets, attackers/attack surfaces, threats 02:43:23 ryuichi has joined #wot 02:43:52 Tak has joined #wot 02:44:24 ... [Resources] 02:44:46 ... WoT security documentation: github.com/w3c/wot/tree/master/security-privcy 02:44:57 ... WOT IG security webconf: www.w3.org/WoT/IG/wiki/IG_Security_WebConf 02:45:01 ... that's all 02:45:07 naka: questions? 02:45:53 naokis has joined #wot 02:46:02 kaz: everybody from this meeting room is encouraged to join the Security TF :) 02:46:10 elena: good point 02:46:15 [ Lunch ] 02:46:19 rrsagent, draft minutes 02:46:19 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 02:46:30 afternoon session will start at 13:30 02:46:33 rrsagent, draft minutes 02:46:33 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 02:46:47 remote+ Elena 03:11:47 yingying has joined #wot 03:36:30 shigeya has joined #wot 03:43:47 barryleiba has joined #wot 03:50:43 YosukeUkita has joined #wot 03:51:09 YosukeUkita has left #wot 03:51:47 YosukeUkita has joined #wot 04:04:05 naokis has joined #wot 04:09:28 ohura has joined #wot 04:10:26 kaz has joined #wot 04:19:16 naomi has joined #wot 04:24:54 SeijiNimura_ has joined #wot 04:26:16 Yoshihisa_Homma has joined #wot 04:29:56 dsr has joined #wot 04:30:59 sano has joined #wot 04:31:13 topic: OpenFog - Masahiro Shimohori 04:31:44 n_uchida has joined #wot 04:32:18 ms: [Building this necessary interoperability of fog-enabled applications requires a collaborative approach] 04:32:50 ... funded by the 5 companies and one univ 04:33:08 ... Intel, MS, Cisco, Dell, ARM, Princeton Univ. 04:34:13 ... [OpenFog mission] 04:34:18 ... mission statement 04:34:56 ... To drive industry and academic leadership in fog computing architecture, testbed develpment, and a variety of interoperability ... 04:35:04 ... [OpenFog COnsortium] 04:35:11 ... 57 members 04:35:26 taki has joined #wot 04:35:30 ... 6 founders 04:35:43 ... affiliations, contributing members, and other members 04:35:50 Miki has joined #wot 04:36:12 ... [OpenFog Consortium goals] 04:36:12 hitoshi has joined #WoT 04:36:21 ... technology, innovation, education 04:36:41 ... testbed to demonstrate interoperability 04:36:44 kotakagi has joined #wot 04:36:56 toru has joined #wot 04:37:19 ... ... evangelize fog computing 04:37:32 ... doing a lot of efforts 04:37:39 ... [Organizational structure] 04:37:47 ... technical WGs 04:38:29 ... architecture framework, SW infrastructure, communications, security, manageability, liaisons, testbed 04:38:40 ... under the technical committee 04:39:29 sano_ has joined #wot 04:39:30 ... and marketing committee, social impact committee, americas committee, greater china region committee, japan committee and european committee (planned) 04:39:41 ... [OpenFog Reference Architecture] 04:39:47 ... www.OpenFogConsortium.org/RA 04:40:12 ... [The OpenFog reference Architecture Framework] 04:40:29 ... software/device developers 04:40:52 ... interoperability in IoT, 5G, AI and other complex data/network intensive apps 04:41:23 ... and creating common language for fog computing and wil help unify the edge/fog ecosystem 04:41:48 ... under a single, interoperable, testable set of hardware and software standards 04:42:05 ... [Key pillars of the OpenFog architecture framework 04:42:46 s/framework/framework]/ 04:43:24 ... security, scalability, open, autonomy, RAS, agility, hierarchy, programmability 04:44:45 ... [Architecture description with perspectives] 04:46:48 ... green layer: sensors, actuators, control; protocol abstraction; hardware platform instracture 04:47:22 ... dark blue: network, accelators, compute, storage; OpenFog Node Security; OpenFog Node Managment; Hardware Virtualization 04:47:34 ... blue: Node Management & Software Backplane 04:47:43 ... Orange: Application Support 04:47:53 ... grey: Application Services 04:48:43 ... vertical mechanisms: Security, Manageability, Data Analytics&Control, ... 04:49:22 ... perspectives; node view (green), system view (dark blue), software view (blue); 04:49:34 ... [A closer look at fog nodes] 04:50:18 ... gog nodes communicate with each other in a distributed manner 04:50:37 ... new value chain and business entities 04:50:43 ... [Technical WG focuses] 04:50:55 ryuichi has joined #wot 04:51:30 ... [Reference Architecture Contributions] 04:51:45 ... [Node Security] 04:51:55 ... basis of Fog security 04:52:06 ... hardware root-of-trust 04:52:18 ... physical security 04:52:26 ... [Network Security Aspect] 04:52:41 ... node to cloud 04:52:47 ... REST over TLS 04:52:56 ... node to node 04:53:08 ... HTTP over TLS, CoAP over DTLS 04:53:14 ... node to device 04:53:27 ... IP adaptation 04:54:22 ... [Data Security Aspect] 04:54:26 ... Data in Use 04:54:41 ... data in memory undergoing procesisng 04:54:48 ... [New Work & Task forces] 04:55:01 ... new TFs established 04:55:09 ... [Security Requirement Taskforce] 04:55:18 ... mission statement 04:55:52 ... to define sets of requirements that has to express the fundamental security (and in the future evaluation) requirements for an OpenFog compliant (in the future certified) node and system. 04:56:21 ... as a reminder, the work shall support both brown and green field implementations 04:56:26 hitoshi has joined #WoT 04:56:44 YosukeUkita has joined #wot 04:57:14 ... [Security Requirement Taskforce (contd.)] 04:57:19 ... Method 04:57:28 ... [Security MVIs] 04:57:35 YosukeUkita has left #wot 04:57:48 ... minimum viable interface 04:58:44 YosukeUkita has joined #wot 04:58:55 ... [Smart Objects for an OpenFog Architecture: SW Infrastructure WG - Task Group] 04:59:41 ... What are Smart Opbjects? 04:59:48 s/Opbjects/Objects/ 04:59:57 ... Why do we care about Smart Objects? 05:00:06 ... Smart Object Landscape, ... 05:00:14 ... [What's a Smart Object?] 05:00:33 ... an object that describes its own possible interactions 05:00:52 ...can be physical, e.g., sensor, computing device, wearables 05:01:10 ... can be cyber, elgl, data, executable code, apps, services, clouds 05:01:55 ... [Why do we care about Smart Objects?] 05:02:27 ... reduce time and cost to develop, deploy and maintain IoT applications 05:02:58 ... data interoperability; service, object and software composition 05:03:20 ... [Smart Object Landscape] 05:06:51 ... W3C Semantic Web, W3C Web of Things, ipso, OCF, IIC, Haystack Connect, UPnP, Allseen Alliance, IETF, OPC, RDA, NIST 05:10:11 taki has joined #wot 05:11:29 Ichikawa has joined #wot 05:11:40 ... [Smart Object Issues] 05:11:44 ... a lot of challenges 05:12:25 ... frameworks: standards, ontologies, interoperability 05:12:30 ... [Charter] 05:13:31 ... working closely with other SDOs including W3C 05:14:03 ... [Transaction Management & Orchestration Princeples] 05:14:21 ... [Logical Transaction Layers - concept] 05:14:41 ... distributed resources 05:15:01 ... 1. Fog Platform Infrastructure - Shared Resources 05:15:16 ... 2. Microservice Logical Fabric assemblies 05:15:25 ... 3. Data, Object, Interface&Access 05:15:39 ... 4. Fog Transaction&Management 05:15:48 ... defines scope of services 05:16:10 ... e.g., with a building 05:16:24 ... would control temperature and humidity 05:16:42 ... resources are connected to storages 05:17:26 ... project could be energy management 05:18:06 ... [What is a Transaction?] 05:18:52 ... transaction based TLA time (e.g., 10sec) 05:19:06 ... Internet (3sec) 05:19:11 ... Application (3sec) 05:19:19 ... System+Storage (2sec) 05:19:28 ... Network (2sec) 05:19:56 s/10sec)/10sec) consists of:/ 05:21:21 mm: fog as distributed cloud 05:21:39 ... micro services? 05:22:18 ... access to a service, e.g., computer vision 05:22:21 ... public devices 05:22:41 ... difference in computing storage 05:22:58 ms: go back to the diagram of "Logical Transaction Layers" 05:23:30 ... these are system infrastructure view (=Fog Platform Infrastructure layer) 05:24:07 ... metrics of business for a transaction 05:24:19 ... [Transaction Level Management Elements] 05:24:28 ... the fog is logical description of resources 05:24:46 ... on top of that, orchestration layer 05:24:54 ... and delivery model 05:25:12 ... on the left side 05:25:31 ... transaction management e.g., by blockchane 05:25:56 ... [Resource, Data, Object Transaction Management] 05:26:09 ... [Moving forward...] 05:26:26 ... [OpenFog Priorities (2017-2018)] 05:26:39 ... technical WGs under the technical committee 05:27:02 yakura_ryoichi has joined #wot 05:27:13 ... interface standardization with an SDO -> open reference implementation 05:27:40 ... certification and interoperability fogfests 05:27:56 yakura_ryoichi has joined #wot 05:28:18 ... regional use cases and test cases 05:28:39 s/test cases/test cases from regional committees/ 05:28:46 ... APIs to standardize 05:29:12 mm: questions? 05:29:41 unida: regarding smart object 05:29:44 ... diversity is one problem 05:29:50 ... how to overcome? 05:30:12 ms: study in the market 05:30:28 ... e.g., W3C perspectives, OCF perspectives 05:30:37 ... common vocabulary in those areas 05:30:47 ... not to have one specific standard 05:30:56 ... but consider interoperability 05:31:03 ... use cases behind the use cases 05:31:26 s/use cases behind/common vocabulary/ 05:31:39 s/specific/single/ 05:32:01 ... other SDOs like OIC, AllSeen 05:32:21 ... maybe OCF would have different profiles 05:32:49 yz: similar question 05:33:04 ... you plan to pick up one of existing standards 05:33:27 ... or interoperability like WoT 05:33:44 ms: would take existing good things 05:33:51 ... don't want to reinvent wheels 05:34:05 ... interoperability with existing standards 05:34:17 ... may work on open source project with other SDOs 05:34:28 ... also testbed project 05:34:41 yz: common vocabulary? 05:34:54 ... can be done with somebody collaboratively? 05:35:00 ... how to host that? 05:35:14 ms: openfog has a liaison committee 05:35:28 s/committee/wg/ 05:35:40 ... liaison from technical viewpoint 05:36:02 ... communicate with other SDOs 05:36:25 ... simple liaison and collaborative work on common vocabulary 05:36:40 yz: generating your own vocab? 05:36:53 ms: don't have to be a single entity 05:37:10 rrsagent, draft minutes 05:37:10 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 05:37:12 taki has joined #wot 05:37:50 scribenick: dsr 05:39:03 Kazayuki Ashimura presents W3C work on automotive. 05:39:22 The automotive industry has seen lots of change. 05:40:00 Kaz runs through the list of Automotive WG meetings 05:40:19 He presents a diagram showing the vehical signal architecture. 05:40:46 The bottom level is the car’s internal system as exposed e.g. on the CAN bus 05:42:02 The Vehicle Information API is exposed via Web Sockets using a Vehicle server. 05:43:18 Kaz mentions the VW submission https://www.w3.org/Submission/2016/01/ 05:43:34 Work has started on a test framework. 05:45:38 The Vehicle Signal Spec is defined by GENIVI not W3C. 05:45:59 Kaz lists some links to related other work. 05:47:44 The Web of Things architecture will enable an ecosystem of automotive related services. 05:49:03 The VIAS (Vehicle Information API spec) defines an API that is exposed to applications in a web browser. 05:50:30 The VISS (Vehicle Signal Spec) feeds a JavaScript library that then exposes the VIAS API to applications. 05:52:27 Michael McCool asks a question on how to satisfy requirements for functional safety certification. 05:53:47 One solution is to prevent the apps from being able to control the car in ways which would risk safety. 05:54:23 This may require a module that enforces this. 05:55:03 Kaz: the car maker is responsible for that. 05:56:04 Michael: this becomes very challenging for self-driving cars. 05:57:16 Kaz: web of things needs to handle safety and security 05:58:04 Kajimoto-san asks about requirements such as response time. 05:58:50 rrsagent, make minutes 05:58:50 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html dsr 05:59:16 … we break for coffee and a group photo … 06:00:10 barryleiba has joined #wot 06:03:30 zkis has joined #wot 06:08:46 sam has joined #wot 06:11:52 KojiMiura has joined #wot 06:14:12 naokis has joined #wot 06:18:28 zkis has joined #wot 06:26:00 Maurice has joined #wot 06:26:38 YosukeUkita has joined #wot 06:28:39 naomi has joined #wot 06:28:59 naomi has joined #wot 06:30:11 sano has joined #wot 06:30:18 dsr has joined #wot 06:31:43 Yoshihisa_Homma has joined #wot 06:32:42 topic: oneM2M Overview - Norikazu Yamasaki 06:32:45 ny: agenda 06:32:59 ... overview of oneM2M partnership project 06:33:11 ... standardization at IoT/M2M Service Layer 06:33:19 ... release 2 and release 3 ... 06:33:28 [Global Partnership Project 06:34:06 s/[/... [/ 06:34:40 ... 8 partner type 1: atis, TIA, ETSI, tsdsi, CCSA, TTA, ARIB, TTC 06:34:57 ... also patner type 2 (vertical payers and industry groups) 06:35:32 ... BBF, OMA, HGI (merged into oneM2M), New Generation M2M Consortium, Global Platform, CEN&CENTRIC 06:35:45 ... [200+ Members Organizations] 06:35:53 toru has joined #wot 06:36:22 ... [Purpose & Deliverables] 06:36:39 ... oneM2M purpose: to specify and promote an M2M common service layer 06:37:02 ... oneM2M deliverables: technical reports (informative) and technical specs (normative) 06:37:15 ... [oneM2M Organization Structure] 06:37:54 ... Steering Committee - finance, legal, marketing, methods/proc., certification 06:38:02 ... [WOrk Process] 06:38:07 s/WOrk/Work/ 06:38:40 ... various use cases: enargy, enterprise, healthcare, public services, residential, other, transportation, industry 06:39:03 ... common requirements based on the use cases 06:39:10 ... that is stage 1 06:39:29 ... stage2/3 is specification 06:39:40 ... [M2M/IoT Common Service Layer] 06:39:57 ... M2M Service Layer was defined by ITU-T FG-M2M 06:40:02 ... software layer 06:40:25 ... between M2M apps and communication hardware/software that provides data transport 06:40:40 ... nomally rides on the top of IP 06:40:52 ... [oneM2M Architecture Approach] 06:41:18 ... Pipe (vertical) 06:41:33 ... Horizontal Interoperability (based on Common Service Layer) 06:42:42 ... [oneM2M Architecture] 06:43:38 ... application layer (consists of Application Entity): device AE, Gateway AE 06:43:59 ... Service Layer (consists of Common Service Entity) 06:44:20 ... Network Layer (consists of Network Service Entity) 06:44:40 ... defining interface between entities 06:44:54 smatsui3 has joined #wot 06:45:01 ... [Common Service Functions (CSFs) 06:45:32 ... registration, discovery, security, group management 06:45:37 Miki has joined #wot 06:45:52 ... data management&repository, subscription¬ification, device management, application&service management 06:46:00 ... ... 06:46:10 ... [Communication Protocols 06:46:20 s/Protocols/Protocols]/ 06:46:31 ... reuse IP-based existing protocols 06:46:43 ... service layer core protocols: CoAP, MQTT, etc. 06:46:53 ... [Timeline of oneM2M Key Events] 06:47:21 ... 2012 - 2013 - 2014 - 2015 - 2016 - 2017 06:47:42 ... oneM2M partnership project launch: Q3, 2012 06:47:49 ... Release 1 Issued: Q1, 2015 06:48:01 ... Interoperability Test Event #1: Q3, 2015 06:48:10 ... Interoperability Test Event #2: Q2, 2016 06:48:23 ... Release 2 Issued: Q3, 2016 06:48:38 ... Interoperability Test Event #3: 2017 06:48:48 ... [oneM2M Release 2 Features] 06:49:30 ... oneM2M as eneric interworking framework: AllJoyn/AllSeen, OIC, LWM2M 06:49:52 ... Semantic interoperability 06:50:03 ... [Ongoing Collaborations] 06:50:13 ... with other SDOs 06:50:50 ... utiliaztion: OMA, BBF, OASIS, HGi, IETF, ETSI 06:51:25 ... Interworking: Allseen, OCF (including OIC and UPnP) 06:51:34 ... Collaboration: IIC 06:52:18 ... liaison&collaboration: ITU-T, GSMA, W3C, 3GPP, IEEE, ISO/IEC JTC1/WG10 06:52:28 ... related to IoT technology 06:52:51 ... regarding collaboration with W3C, the detail will be explained by Yongjing 06:53:09 ... [Toward Release 3] 06:53:12 kotakagi has joined #wot 06:53:16 ... Release 3 planning 06:53:38 ... work track 1: Market Adoption Track (high priority) 06:53:57 ... work track 2: Industrial IoT and smart cities 06:54:09 ... work track 3: Forward Looking Areas 06:54:17 rrsagent, draft minutes 06:54:17 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 06:54:54 i/Michael_Koster, Yingying_Chen/scribenick: kaz/ 06:54:56 rrsagent, draft minutes 06:54:56 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 06:55:05 ... [Phased Approach for ertification] 06:55:14 ... initial phase: Oct. 2016- 06:55:23 ... Global Phase: 2Q, 2018? 06:55:47 i/koji mentioned/scribenick: naomi 06:55:53 rrsagent, draft minutes 06:55:53 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 06:56:20 ... [OSS and Implementation] 06:56:36 ... Industry-driven open source software/platforms 06:56:56 ... LAAS-CNRS: OM2M 06:57:00 ... KETI: OCEAN 06:57:10 ... Cisco: Open Daylight 06:57:22 ... examples of commercial implementations/demos 06:57:48 ... LG, Huawei, SK Telecom, Sierra Wireless, Ericsson, LG U+, kt, ... 06:57:59 ... [Busan Smart City Project/Korea] 06:58:11 ... [Smart City/France] 06:58:22 ... [UK] 06:58:25 ... [India] 06:58:41 ... [LG U+] 06:58:58 ... [Open IoT Platform (sensinov/France)] 06:59:13 i/mm: [Outline]/scribenick: kaz/ 06:59:19 rrsagent, draft minutes 06:59:19 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 06:59:49 i/ny: agenda/scribenick: kaz/ 06:59:50 rrsagent, draft minutes 06:59:50 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 07:01:28 smatsui3 has left #wot 07:02:56 topic: Relationship between WoT and oneM2M - Yongjing Zhang 07:04:09 yz: [Technical Highlights] 07:04:17 ... [Architecture Configurations] 07:04:40 rrsagent, draft minutes 07:04:40 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 07:04:55 ... Infrastructure Node (IN) 07:05:00 ... Middle Node (MN) 07:05:07 ... Application Service Node (ASN) 07:05:15 ... Application Dedicated Node (ADN) 07:05:22 ... Non-oneM2M Node (NoDN) 07:06:05 ... lot of options 07:06:15 ... [Generic CRUD procedure] 07:06:30 ... create request/response 07:06:37 ... retrieve request/response 07:06:45 ... [Communication Models] 07:06:55 ... blocking synchronous 07:07:01 ... non-blocking synchronous 07:07:10 ... non-blocking asynchronous 07:08:53 ... [oneM2M Resource Model vs WoT] 07:09:16 ... CSEBase - base 07:10:27 ... cseType - @type 07:11:03 ... supportedResourceType, pointOfAccess, nodeLink - property? 07:12:55 ... [Data Management] 07:13:10 ... different resource types 07:13:21 ... support hierarchical data model 07:13:28 ... suppport semantic annotation 07:13:38 s/suppp/supp/ 07:13:54 ... can represent (depending on implementation context) 07:14:00 ... eventable 07:16:24 ... [Subscription & Notification (event) 07:16:38 ... can set event criteria 07:16:52 ... target address of notification 07:17:44 ... [Device Management] 07:18:31 ... mgmtObj as a template is specialized to individual management resource, e.g., deviceinfo and firmware 07:18:39 ... some are actionable and some are not 07:19:25 mm: hybrid function 07:19:40 yz: [Group Management] 07:20:11 mm: OCF has same functionality 07:20:30 yz: [Semantics] 07:20:53 ... RDF descriptors 07:21:26 ... semantic discovery/query 07:21:41 ... [Security: Enrolment & Security Association] 07:22:13 ... enrollment phase and security association phase 07:22:23 s/Enrolment/Enrollment/ 07:22:29 ... [Security: Encryption] 07:22:42 ... [Security: Authorization (Access Control)] 07:23:01 ... protocol specific 07:23:40 ... [oneM2M Interworking Overview] 07:24:13 ... to make different standards/technologies working smoothly together 07:24:21 ... - transparent interworking 07:24:30 ... - translucent interworking 07:24:40 ... - semantic interworking 07:24:41 ... [OIC/OCF Interworking] 07:24:54 ... OIC/OCF domain and oneM2M domain 07:26:05 ... [Ontology based Interworking] 07:26:14 ... oneM2M based ontology 07:26:45 ... the upper ontology serving as the anchor to facilitate/automate the mapping from external systems to oneM2M resource tree 07:27:19 ... [Proximal Interworking via HAIM] 07:27:42 ... mapping at the semantic level 07:27:57 ... common template 07:29:07 ... [HAIM example] 07:30:43 ... SDT concepts vs WoT concepts 07:32:10 ... [Interworking: WoT->oneM2M] 07:32:32 ... exposing the WoT interface described in TD to oneM2M systems 07:32:46 ... benefit: WoT services/data can be consumed by oneM2M apps 07:33:10 ... question: do oneM2M apps need to understand WoT data model at all? 07:34:04 ... [Interworking: oneM2M->WoT] 07:34:13 ... exposing oneM2M interfaces to WoT systems 07:34:27 ... benefit: oneM2M services/data can be consumed by WoT servients 07:34:44 ... question: is WoT descriptive enough for oneM2M data models and interfaces? 07:35:23 ... [Annex: oneM2M specification walkthrough] 07:35:46 kaji: comments/questions? 07:36:06 seba: we should look into the details 07:36:19 ... scenario for the next PlugFest 07:36:31 s/scenario/possible scenario/ 07:36:50 yz: can provide further information for discussion 07:36:56 rrsagent, draft minutes 07:36:56 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 07:37:24 [ OpenDay ends] 07:37:26 rrsagent, draft minutes 07:37:26 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 07:37:52 Demo Tour at Panasonic Center Osaka 07:37:54 and then Dinner! 07:37:57 rrsagent, draft minutes 07:37:57 I have made the request to generate http://www.w3.org/2017/05/16-wot-minutes.html kaz 07:46:17 zkis has joined #wot 07:52:14 naomi has joined #wot 08:25:32 yingying has joined #wot 08:30:43 yingying_ has joined #wot 11:59:14 Karen has joined #wot 12:29:08 Karen_ has joined #wot 12:32:04 Karen__ has joined #wot 12:58:06 barryleiba has joined #wot 13:22:25 shigeya has joined #wot 13:53:08 Karen has joined #wot 15:26:47 naomi has joined #wot 16:13:30 Karen has joined #wot 17:31:26 zkis has joined #wot 17:45:22 hyojin has joined #wot 19:10:32 Karen_ has joined #wot 19:53:39 ahaller2 has joined #wot 20:42:01 dsr has joined #wot 21:35:14 Karen has joined #wot 21:44:12 Karen_ has joined #wot 21:44:59 shigeya has joined #wot 22:24:50 shigeya has joined #wot 23:20:17 ahaller2 has joined #wot 23:30:26 naomi has joined #wot 23:33:01 naomi has joined #wot 23:41:08 dsr has joined #wot 23:56:26 yingying has joined #wot 23:58:11 shigeya has joined #wot