07:29:57 RRSAgent has joined #wot 07:29:57 logging to http://www.w3.org/2017/07/10-wot-irc 07:30:10 lindsay: web protocol working so far? 07:30:30 and: lemonbeat implementations? 07:30:30 ... yes, there are 07:31:16 dsr: electric car is one challenge, and... 07:31:40 and: e-mobility massively effects our infrastructure 07:31:51 ... shift the systems 07:31:55 ... 2 opportunities 07:32:09 ... challenge is renewing the end 07:32:14 ... huge tech problems 07:32:19 ... e.g., voltage drops 07:32:32 ... infrastructure like cables 07:33:04 ... using IoT compensate usual consumpation 07:33:30 mk: how many different protocols/standards are there? 07:33:32 and: can share my feeling :) 07:33:51 ... the solution provides flexibility 07:34:21 ... heat pump, heating system, water system, etc. 07:34:35 ... not based on standards so far 07:34:42 ... there are different manufacturers 07:34:48 ... using different protocols 07:35:22 ... standard interface would help interaction 07:36:00 ... if you want please follow the slides and contact me 07:36:02 ... tx! 07:37:51 topic: Logistics 07:37:52 uday: meeting followed by a social event in the evening 07:37:59 ... city tour and dinner 07:38:13 ... looking forward good discussions 07:38:18 tokuyama has joined #wot 07:38:49 taki1 has joined #wot 07:39:49 scribenick: dsr 07:40:25 topic: W3C Patent Policy for WG discussion 07:42:23 Kaz Ashimura (W3C) introduces the W3C Patent Policy and its implications for our work. 07:45:37 W3C advances specifictions through 5 steps from an initial Working Draft to the final Recommendation (W3C’s term for its standards) 07:46:08 W3C Recommendations must be available to implement on a royalty free basis. 07:46:54 You are encouraged to join the Working Group if you haven’t done so already, and to make the corresponding licensing commitments. 07:48:04 The WG Chairs can invite guests to WG meetings, however, we need to be aware about potential IPR issues that could arise from contributions from people who are not formally part of the WG. 07:48:41 Kaz shows the important points from the W3C Patent Policy document 07:50:37 When contributions are being considered for inclusion in a document intended to become a W3C Recommendation, the WG Chairs should ask the contributor to disclose any essential claims that they would not be able to provide royalty free licenses as per the W3C Patent Policy 07:51:19 Kaz lists the managed repositories relevant to the WoiT WG 07:53:24 If the WG is unable to secure licensing for essential claims under the W3C Patent Policy, the Chairs should endeavor to steer around the concerned technical aspects. 07:54:05 topic: Iotschema.org and semantic interoperability 07:54:16 Michael Koster (SmartThings/Samsung) presents. 07:55:05 rrsagent, make log public 07:55:09 There are many standards organisations, and these have taken their own approach, and in some cases are competing with each other. 07:55:11 rrsagent, draft minutes 07:55:11 I have made the request to generate http://www.w3.org/2017/07/10-wot-minutes.html kaz 07:56:07 The approach we’re taking is to enable semantic interoperability at the application layer 07:57:14 We’re looking at well known formats to describe how applications can interact with things. 07:59:02 We’re adapting the patterns from schema.org that were developed for smart search results, and combining this with other ontologies and vocabularies. 08:00:04 We want to do this in an open process that doesn’t require formal membership of a standards development organisation.. 08:00:58 Contributions based upon either the W3C Community Group or the schema.org frameworks 08:01:39 Michael presents a semantic stack model 08:02:49 This has the ontologies at the top, the web of things in the middle, and specific IoT standards suites at the bottom 08:03:39 zkis has joined #wot 08:03:56 We want to enable a means to abstract capabilities, e.g. motion sensing, turning something on and off and so forth. 08:04:48 Actuation may be incremental, e.g. light levels and colours rather than simply on and off 08:05:44 Michael describes how the iotschema,org capability pattern relates to the web of things. 08:05:47 naka has joined #wot 08:06:45 Essentially a capability is mapped to an interaction pattern with its associated properties, actions and events. 08:07:54 Michael shows a JSON based representation of an example capability 08:10:54 q+ 08:11:19 We’ve done some initial work to prepare a charter. We hold monthly teleconferences and we’re about to apply the charter to the W3C Web of Things Community Group. 08:11:41 We plan to use the CC-SA license for contributions. 08:11:44 sebastian has joined #wot 08:12:02 Collaboration with the W3C WoT IG and WG 08:12:32 We’re aiming to collaborate with other organisations to enable re-use of existing ontologies 08:13:26 Work on factoring out differences across ontologies, semantic annotations and support for composing services. 08:13:56 ack zkis 08:14:14 Zoltan: I really like the notion of capabilities 08:15:15 Michael: At Smart things, we have had several years experience with capabilities 08:15:38 Capabilities also help with security 08:16:15 capabilities could be used as funcionality units for permissions and policies 08:16:26 Capabillities are building blocks for things and not for use on their own 08:17:50 We don’t need to express capabilities directly in thing descriptions, but rather to use them to describe relationships between things and capabilities 08:19:27 Stefan: is this approach already accepted by schema.org ? 08:20:09 Michael: that’s an interesting question. We’re really at an early stage where we are working on a proposal that we want schema.org to take on board 08:21:16 Matthias: in the Web of things, we want to model the physical world. We need to relate the interaction model to the physical capabilities 08:23:52 Dave: we need to recognise that different communities will develop different vocabularies, so we need bridging ontologies that allow search using shared concepts rather than having to use the different terms for each of the different vocabularies 08:24:52 Zakim has joined #wot 08:25:33 ETSI is also working in this area. The problem of relating different models can be likened to the parts of an iceberg that is under the water - it is very much larger and risks sinking the ship of interoperability 08:25:46 s/ETSI/Lindsay: ETSI/ 08:26:11 Philipp Hoschka: what is the relationship betweeen schema.org and W3C? 08:27:53 XXX: how do you exploit these descriptions in applications? 08:28:02 s/XXX:/Tobias:/ 08:28:24 rrsagent, draft minutes 08:28:24 I have made the request to generate http://www.w3.org/2017/07/10-wot-minutes.html kaz 08:29:18 Michael: the combinations of these different kinds of descriptions can be used to support discovery, composition and adaptation by smart services 08:30:40 The Web works because it is simple, much simpler than some of the older ideas for hypermedia 08:31:11 We want to make it easier for people to innovate and contribute new ideas 08:31:51 naka has joined #wot 08:32:29 The protocol binding for the web of things maps the abstract models to the concrete protocols 08:33:52 We want to avoid the complexity of the Semantic Web and make life easier for regular developers. 08:35:02 Michael McCool: there is a risk of alienating developers if we don’t do a good job on that. 08:36:31 Kajimoto san: one challenge is what things call themselves, another is who owns the things. 08:36:51 s/Kajimoto san:/Kajimoto-san:/ 08:37:46 q+ 08:38:17 Michael: we need a means to describe the interaction model and also a means to describe the relationships between things at a semantic level 08:38:39 s/Michael McCool:/Michael_McCool:/ 08:38:51 There is a lot of other categories we need to look at including security policies 08:40:21 Lucca: we should exploit the work that has been done for the Semantic Web, why aren’t we using RDF rather than JSON? 08:40:46 s/Lucca:/Luca:/ 08:41:26 Michael: we trying to use the framework of RDF but to avoid the need for developers to first become semantic web experts 08:42:06 We have some choices to explore for this 08:42:20 q? 08:42:53 Dave: we need to keep distinct the serialisations from the underlying framework. 08:42:53 q- 08:43:28 rrsagent, make minutes 08:43:28 I have made the request to generate http://www.w3.org/2017/07/10-wot-minutes.html dsr 09:15:37 [break] 11:29:17 dsr has joined #wot 11:34:57 Karen has joined #wot 11:35:10 naka has joined #wot 11:37:36 topic: LP-WANs with SigFox 11:37:47 Presented by Juan Carlos Zuniga (Sigfox) 11:39:26 Juan introduces Sigfox. This is a company that focuses on low power wide area connectivity for IoT devices. 11:40:11 Key goals include low cost and low data rates 11:41:12 Sigfox is a connectivity provider that builds and operates the network with regional SNO operators 11:41:41 We charge for connecting devices to the Internet 11:44:10 ryuichi has joined #wot 11:45:15 Sigfox can be applied to a wide variety of domains, including assisted living, home alarms, smoke detectors, precision agriculture, tracking moving assets. 11:45:43 5 main business benefits. 11:46:47 Sigfox coverage in the USA, South America, Euroipe, South Africa, Japan and Australia 11:47:08 s/Euroipe/Europe/ 11:47:42 Sigfox is designed to scale to very large numbers of devices, 11:48:34 The sigfox foundation supports applications such as tracking protected species like rhino’s 11:49:12 Sigfox uses ultra narrow band and frequency hopping. 11:50:09 This relies on software defined radio technology, also know as cognitive radio 11:51:22 Messages are sent with multiple copies in different frequencies 11:51:58 Uplink messages have 12 byte payload, downlink 8 bytes 11:52:39 Up to 6 messages uplink per hour and 4 messages downlink 11:53:07 After sending, the device listens for a reply in a short window of time 11:54:19 Devices spend most of their time asleep with negligible power drain, allowing for years of battery operation. 11:56:02 Devices are pre-provisioned with their credentials. Standard APIs are provided for accessing data on common cloud platforms. 11:57:11 Keen on standards based interoperability. 11:57:57 Collaborative approach to security, and design for privacy 11:59:32 SCHC - static context header compression for sigfox and LoRa from LPWAN WG 11:59:59 Demos of IPv6/CoAP over LPWAN 12:01:28 Interoperability at the application layer - demos for IETF 12:01:31 naka has joined #wot 12:02:36 Privacy focused on explicit personally identifiable information 12:03:29 Example: if a trash bin is used, you know that someone is in the house. 12:03:38 naka has joined #wot 12:03:46 Proactive privacy by design principles. 12:04:24 naka has joined #wot 12:04:28 Resilience to botnets and tempered with devices - blocking and blacklisting capabilities in the cloud 12:04:58 Different levels of security according to the criticality and type of application. 12:05:23 naka has joined #wot 12:05:48 q+ about security (later, at questions time) 12:05:52 q+ 12:06:19 Michael Koster: what do you mean by device autonomy? 12:06:42 Juan: devices can talk whenevery they want, there is no need to synchronise clocks etc. 12:07:56 s/whenevery/whenever/ 12:08:57 some discussion around IPv6 via header compression 12:10:12 On-going work on layering CoAP on top of this. 12:10:49 We’re looking at supporting message fragmentation and reassembly 12:12:09 Matthias provides some additional context 12:13:19 Juan: our cloud APIs provide metadata that comes from the cloud for the device, but is not held on the device 12:13:39 s/Michael Koster:/Michael_Kosr 12:13:50 s/Michael_Kosr/Michael_Koster:/ 12:14:14 q- 12:15:23 IETF work as a collaboration across several technology groups, e.g. sigfox, LoRa and 2 others 12:16:52 Darko: what format are you using for metadata and how is it managed? 12:17:45 Juan: right now every device maker does their own thing. We are seeking ways to converge. We’re not pushing on a single approach, but want to encourge convergence 12:19:25 topic: Introduction to the BIG IoT EU project 12:19:45 Presented by Stefan Schmid (Bosch). 12:20:04 sebastian has joined #wot 12:20:49 The project started 18 months ago and is half way through 12:21:27 The project name is an acronym for bridging the interoperability gap of the Internet of Things 12:21:50 See: http://big-iot.eu/project/ 12:23:33 Photo of busy city street witg cars, trams and pedestrians, and many kind of IoT devices 12:23:58 Each of the IoT systems form independent silos 12:24:49 The objective is to enable interoperability across these silos 12:26:20 We want to foster and imcentivize collaboration via a marketplace of services 12:27:22 s/imcentivize/incentivize/ 12:27:44 The marketplace includes support for monetizing services. 12:28:30 The marketplace is aimed at developers not end users 12:30:12 Example for a smart parking service where street sensors report which spaces are not in use 12:30:46 This could involve a mix of technologies and communication standards 12:32:06 We need to support evolution of services and technologies. How can we enable applications to take advantage of new capabilities? 12:36:44 Service providers and consumers with authentication, registration, discovery, subscription and accounting 12:38:13 The service offering description specifies the access control policy 12:39:25 We use JSON-LD for the descriptions, based upon the work by the W3C Web of Things IG 12:40:59 Stefan talks us through the different kinds of information in the description. 12:41:20 s/witg/with/ 12:43:10 We provide a simple API that abstracts away from the details of the underlying platform. 12:44:06 We can provide a gateway service for accessing non Big-IoT platforms. 12:45:02 Likewise, we support proxies when it isn’t appropriate for apps to directly access devices. 12:46:01 Big-IoT is working witg Eclipse IoT for our open source strategy 12:46:21 We plan to contribute semantic models to schema.org 12:47:34 We expect to very soon have approval from Eclipse for our proposed open source project. 12:49:09 Demo of the smart parking service in Barcelona 12:50:12 Stefan talks us through how a company could add its parking lot to the service. 12:52:27 You can query for parking space providers within a given radius of a given location. 12:53:36 A new provider needs to register its offering with the marketplace 12:56:45 This involves customizing some Java code … 13:01:10 The end user app shows available places and pays for the parking charge. 13:02:00 Juan: do you see a single market or multiple marketplaces? 13:02:47 Stefan: many marketplaces, first because of the amount of data, and secondly due to regional and domain specific variations of requirements 13:03:23 Kaz: are you interested in a standard API from web pages for web based applications? 13:04:17 Stefan: this is a research project with limited resources. There are many options for commercialising our work. 13:04:51 Philipp_Hoschka talks about the Compose EU project which also worked on marketplaces for IoT services. 13:05:50 s/API/API for payments/ 13:05:56 s/web pages/web browsers/ 13:06:29 Stefan notes there are already many IoT marketplaces. 13:07:02 Matthias: how did you survey the developers for the marketplace requirements? 13:08:14 Stefan: we learned that different developers prefer different programming languages, and that Java isn’t a universal solution. 13:18:09 thor has joined #wot 13:32:48 yatil has left #wot 13:34:24 [ break ] 13:51:15 topic: Context Information Management and Privacy - Lindsay Frost (ETSI ISG CIM/NEC Europe) 13:51:34 Lindsay: charing ETSI ISC CIM 13:51:48 ... experience is very diverse 13:52:10 ... [Audience Calibration: Hands up who knows of ...] 13:52:53 ... SF book of "1984" and "Future Shock" 13:53:38 ... also "Shockwave Rider" 13:53:55 ... and then "General Data Protection Regulation" by EU Parliament 13:54:03 ... starting in May 2018 13:54:36 ... smart city/parking would require much private data 13:54:51 ... companies are not good at this kind of regulations 13:55:00 ohura has joined #wot 13:55:33 ... organization in breach of GDPR can be fined up to 4% of annual global revenue or 20M Euro 13:55:44 ... [Audience Calibration: Hands up who knows of ...] 13:56:06 naka has joined #wot 13:56:15 ... manipulating genes 13:56:35 ... changing DNA structure 13:57:10 ... whole bunch of scratch pads 13:57:46 ... like RFID embedded in cells 13:58:22 ... [cell genome "recording of event histories"] 13:58:44 ... transilation for "1984" and wiki-leaks readers 13:59:15 ... cell genome could be made to inpact "your" cells... 13:59:22 ... [Outline of this talk] 13:59:34 ... ETSI ISG work 13:59:50 ... main work is how to make exchange semantic data 13:59:59 ... how to interpret it 14:00:15 dsr has joined #wot 14:00:42 ... what would happen government set requirements for smart city trials? 14:01:01 ... [Digital Transformation for Wellington, New Zealand] 14:01:21 ... half as NEC and half as ETSI 14:01:32 ... measuring the quality of city 14:01:46 ... how to improve comfort order 14:01:57 ... sensing overcloud, etc. 14:02:07 ... using video data, etc. 14:02:35 ... tracking people 14:02:53 ... [Digital Transformation for Christchurch, New Zealand] 14:03:02 ... traffic jams 14:03:08 ... tracking number of people 14:03:18 ... [Smart Cities ... and standards] 14:03:33 ... [Standards help all stakeholders] 14:03:35 ... Standards help 14:03:52 ... voluntary/dynamic 14:04:02 ... creates an ecosystem of experts 14:04:12 ... reduce risks 14:04:35 ... governments/citizens need to ference standards 14:05:42 ... issues with execution risks, cost explosions, obsolescence, privacy, physical risks and liability 14:06:51 ... have to worry how to record provenance 14:07:04 ... need to know about your data 14:07:18 ... license, quality, freshness, etc. 14:07:44 ... [IoT-related SDOs & Fora: "Formal" overview] 14:08:47 ... De Jure: ITU-T, ITU-R, ISO/IEC ETSI, ... 14:09:07 De Facto: W3C, oneM2M, ... 14:09:12 McCool: OCF as well 14:09:31 Lindsay: [Smart City related Groups in ETSI] 14:09:41 ... ISG CIM (Context Information Management) 14:10:04 ... oneM2M here in the middle of the picture 14:10:22 ... IoT systems are annotated 14:10:40 ... problem from me is having a lot of stakeholders 14:11:03 ... [Currently >300 EU IoT/SmartCity RnD projects] 14:11:32 ... examples of A-B 14:11:41 ... all those working on IoT and APIs 14:11:53 ... [Work Item Scopes of ETSI ISG CIM] 14:12:02 ... 6 different work items 14:12:22 ... https://portal.etsi.org/tb.aspx?tbid=i54&SubTB=854 14:13:13 ... ontology to describe information model 14:13:31 ... no. 7 is security and privacy 14:13:49 ... [Privacy Issues and Exploring Solution ...] 14:14:02 ... [ETSI ISG CIM: Problem space and solution space] 14:14:04 ... mind map 14:14:12 ... goo.gl/1zFPRz 14:14:39 ... [Context Information Management: Issues] 14:14:48 ... extended mind map 14:14:56 s/extended/enlarged/ 14:15:05 ... what kind of identifiers to use? 14:15:34 ... privacy by design is a hot topic 14:15:59 ... need to have some usage data 14:16:23 ... what if including privacy information? 14:16:36 ... [Context Information Management: Privacy 14:16:36 Zakim has left #wot 14:16:47 s/Privacy/Privacy] 14:17:21 ... you can find these by visiting goo.gl/1zFPRz 14:17:39 ... using blockchain to secure the data 14:17:51 ... serialization of the data 14:18:07 ... possible attack, e.g., by undermining 14:18:43 ... de sur SDOs here 14:18:51 ... CEN-CLS/JWG-8 14:18:57 ... ISO/IEC 27550 14:19:06 ... OASIS PMRMv1.0 14:19:13 ... ISO/IEC 20547-4 14:19:18 ... etc. 14:19:31 ... [Links] 14:19:37 ... [Help on ETSI ISG CIM Discussion Issues] 14:20:06 ... 1. requirements for exchange of cross-cutting context information, to be fit for purpose in Smart Cities, S,art Agriculture and Smart Industry use cases 14:20:24 ... 2. How to ensure ISG CIM API is flexible to cope with all desirable types of context data and instance data 14:20:52 ... 3. Requirements for ISG CIM API to express the important kinds of queries for heterogeneous databases of context information for cross-cutting domains 14:21:06 Yingying has joined #wot 14:21:20 Karen has joined #wot 14:21:36 ... 4. Managing the identifier(s) for entities and referencing them in API queries, even across legacy databases 14:22:02 ... Ensuring privacy protection (fine-grained access control, encryption) on specific context data, efficiently! 14:22:40 Yingying has joined #wot 14:22:51 ... different identifiers based on various stakeholders 14:23:13 ... most of the systems are walled garden 14:23:17 yingying_ has joined #wot 14:23:33 ... usually not available by external parties 14:23:59 ... [How to help] 14:24:13 ... Ask an expert on any of the 5 Discussion Issues to contact me 14:24:30 ... Download the CIM-mindmap goo.gl/1zFPRz and suggest to me your additions 14:24:41 ... Email me about other events/organizations which I should contact 14:25:04 ... Recommend to your organization to join ETSI iSG CIM 14:25:31 ... thank you! 14:25:56 Yingying has joined #wot 14:26:43 Koster: question@@@ 14:32:42 topic: Binding the Web of Things with LwM2M for a vehicular use case - Benjamon Klotz (EURECOM) 14:33:02 Benjamin: [Goals] 14:33:10 ... Interest of WoT 14:33:48 ... integrate data from the vehicle with external knowledge bases 14:33:55 ... adds a semantic enrichment layer 14:34:08 ... can be linke with the work of the W3C AUtomotive WG (and GENIVI) 14:34:31 ... [General architecture and parts] 14:34:38 ... WoT Servient on the left side 14:35:05 ... OEM cloud on the right side 14:35:24 ... HTTP between them 14:35:34 ... and CoAP between cloud and car 14:35:41 ... [Protocol binding: LwM2M] 14:36:22 ... WoT methods -(Python snippet)- HTTP methods -(Leshan API)- LwM2M methods 14:36:29 ... [Demo setup] 14:36:31 ... OBD dongle 14:36:47 ... browser as a WoT client 14:36:56 ... OEM cloud 14:37:03 ... connected using HTTP 14:37:31 ... protocol binding and finding the device 14:37:37 ... [THing description: context] 14:37:43 s/THing/Thing/ 14:37:59 ... need: sensor/actuator ontology, car ontology 14:38:11 ... w3c-wot-td-context.jsonld 14:38:18 ... w3c-wot-common-context.jsonld 14:38:21 ... schema.org 14:38:32 ... linked version of GENIVI's VSS 14:38:41 ... [TD retrieval and parsing] 14:38:54 ... the TD file is stored in the dame repo as the WoT server 14:39:06 ... [Thing description: sequence diagram] 14:39:13 ... changed from yesterday 14:39:33 ... discovery -> consume TD -> read speed 14:40:04 ... communication among browser, WoT server and LwM2M API 14:40:44 ... [WoT communication] 14:40:53 ... WoT server: python script with Flask 14:41:01 ... WoT client 14:41:05 ... [Final interface] 14:41:09 ... API 14:41:23 ... endpoint/consumend 14:41:31 s/consumend/consumed/ 14:41:39 ... [Conclusion and future work] 14:41:48 ... challenges faced 14:41:56 ... remote access to vehicle data 14:42:09 ... protocol binding between WoT and LwM2M 14:42:32 ... link between W3C WoT and W3C Automotive 14:42:38 q+ 14:42:44 Zakim has joined #wot 14:42:45 q+ 14:42:54 ... future work 14:43:32 ... questions? 14:43:48 McCool: translation to TD? 14:43:55 ... automatically? 14:44:04 Benjamin: hand coded 14:44:55 kaz: using VISS or VIAS from the W3C Automotive? 14:45:06 Benjamin: VSS as the data model 14:45:20 Lindsay: subscribe the data? 14:45:53 Benjamin: can subscribe or get data at once as well