16:51:33 RRSAgent has joined #wot 16:51:34 logging to http://www.w3.org/2017/02/06-wot-irc 16:56:22 naka has joined #wot 17:02:07 ryuichi has joined #wot 17:03:14 sano has joined #wot 17:04:36 topic: starting the meeting 17:04:37 dape has joined #wot 17:04:54 mk: this is a joint meeting of the WoT IG and the WoT WG 17:05:01 ... the first meeting for the WG 17:05:19 ... it's open day today 17:06:16 mm: host and another co-Chair 17:06:49 taki has joined #wot 17:06:58 mk: third co-Chair, Kajimoto-san from Panasonic can't join this meeting in person but will join remotely 17:07:18 ... Yongjing Zhang, the co-Chair for the IG also will join remotely 17:08:06 ... (shows "W3C WoT Mission") 17:08:16 ... (Semantic Metadata for Interoperability) 17:08:31 ... communication between platform A and platform B 17:08:40 ... designing simple interaction model 17:08:59 ... essential elements: properties, actions and events 17:09:42 ... all the information described by TD (=Thing Description) 17:09:55 rrsagent, make log public 17:10:07 yamada has joined #wot 17:10:09 ... the challenge is protocol 17:10:32 masato has joined #wot 17:10:40 ... HTTP, CoAP, OCF CoAp, OneM2M CoAP, etc. 17:11:00 ... how to configure them and let the other side understand? 17:11:12 ... (Binding Templates) 17:11:20 ... (Simplify Application Development) 17:11:31 ... (Scripting API) 17:12:26 ... (Portable Apps Across Vendors) 17:12:36 ... (Across Components) 17:12:51 ... from gateway to cloud 17:13:01 ... (TD to Augument Existing Things) 17:13:26 ... get TD from TD repository 17:13:34 ... (W3C WoT Building Blocks) 17:13:42 ... WoT Servient 17:13:53 ... has both server/client capabilities 17:13:59 ... WoT Scripting API 17:14:05 ... WoT Thing Description (TD) 17:14:11 ... WoT Binding Templates 17:14:17 ... Security&Privacy 17:15:09 Agenda: https://www.w3.org/WoT/IG/wiki/F2F_meeting,_February_2017,_USA,_Santa_Clara 17:18:22 topic: Contributions 17:18:39 topic: [Johannes Hund] Some questions that arose while implementing a WoT Servient 17:19:31 -> http://plugfest.thingweb.io/ Plugfest.thingweb 17:19:49 -> Project Thingweb@@@ 17:20:20 jh: (WoT Architecture) 17:21:01 ... Scripting API 17:21:06 ... Runtime Environment 17:23:33 -> http://w3c.github.io/wot/current-practices/wot-practices.html#quick-start-td-samples Example 1 17:23:50 jh: shows Example 1 and then Exapmle 2 17:24:01 s/Exapmle/Example/ 17:24:20 ... (Feedback(1): Client side) 17:25:04 ... can a ConsumedThing instance be narrowed to a single protocol? 17:25:13 ... which protocol to choose if several are availabie? 17:25:23 ... is there a use case for using different ones for each call? 17:25:44 ... would I ever retriee the TD from the Thing itself and then use a different protocol to access it? 17:26:04 ... why is Mediatype (serialization) on link and model (valueType) on interaction? 17:26:27 ... (Feedback (2): Thing lifecycle) 17:26:38 ... another feed back is lifecycle 17:26:50 ... we have addXYZ but we need also removeXYZ 17:26:58 ... we can create but not delete Things 17:27:13 ... we can create but not retrieve existing ExposedThings 17:27:40 ... where does the WoT object originate (global? require/module)? 17:28:37 ... (Feedback(3) Accessing local Things) 17:29:06 ... discover gives me a ConsumedThing, how do I retrieve an ExposedThing from my runtime? 17:29:28 ... (Feedback(4) Security and scoping of scripts and things) 17:29:43 ... Things have a place, a servient where they are hosted - how about scripts? 17:30:04 tokuyama has joined #wot 17:30:20 ... Isolation: can I access exposed things on the local servient "priviledged"? 17:30:48 ... Assumption made: scripts are sandboxed, they do not share global scope but sahre the local ExposedThings 17:31:13 ... (Feedback(5): Multi-protocol) 17:31:24 ... Resource structure: the same for all protocols? 17:31:43 ... Or: is there a resource for each thing and each interaction and the protocols assign there specific URIs? 17:32:00 ... Current assumption: rules to convert (Thing, Interaction) _> URI 17:32:21 ... Protocols and Media Types are now on interaction level - why not thing level? 17:33:25 q? 17:33:26 ktoumura has joined #wot 17:33:40 @1: use case of driving? 17:33:46 jh: so far a gateway use case 17:34:03 ... edge processing, local control and back-end processing 17:34:17 ... huge variety of edge level devices 17:34:30 ... main use case driving our discussion 17:35:01 @2: ConsumedThing vs ExposedThing? 17:35:12 jh: I expose thing to share service 17:35:31 ... consume is using service 17:35:53 mm: one way to use HTTP esp. for events 17:36:14 ... more than protocol than HTTP? 17:36:22 jh: thoughts about that 17:36:49 ... exposing thing is some way of data analysis 17:37:03 ... decoupling actual device from the data 17:37:35 ... you could use multiple protocols 17:38:22 ... so far focused on Node.js but interesting to see other implementations 17:38:59 @3: type script? 17:39:04 s/type/optional type of/ 17:39:31 jh: shows github.com/thingweb/node-wot.../consumed-things 17:40:01 ... based on promises 17:40:30 @3: proper ECMAScript 215? 17:40:35 jh: possibly 17:41:05 dsr: thinking about generalizing TD 17:41:15 ... security, access control, business use cases, etc. 17:41:22 ... more heavy use of linked data 17:41:37 ... people could use the same protocols for different uses 17:46:09 s/@1/al:/ 17:47:48 s/al:/es:/ 17:48:02 s/@2:/austin:/ 17:48:09 s/es:/eve:/ 17:48:17 s/@3:/peter:/ 17:48:51 topic: [Frank Reusch] Networks of autonomous devices and their impact on WoT 17:49:14 fr: (Success criteria for WoT) 17:49:38 ... which kind of requirements are needed from an implementation perspective? 17:50:19 ... (We are a global leader in wind energy and operate; More than 3100 MW of renewable capacity) 17:51:08 ... (Future oriented products and services) 17:51:16 ... decentralized IoT 17:51:30 ... decentralized energy solutions 17:51:52 ... (What if the complete genetic material of a human being was stored in a single cell?) 17:52:37 ... (A life, depending on the proper funcitonality of a single cell, would be...) 17:53:01 ... (With DNA ("the intelligence of life") ther eis a decentralized control...) 17:53:10 ... (Lemonbeat positioning in the OSI layer model) 17:53:50 ... application layer: Lemonbeat smart Device Language "LsDL" (XML/XSD/EXI) 17:53:59 ... over HTTP/CoAP 17:54:30 ... oer TCP (for HTTP) and UDP (for CoAP) 17:54:43 s/oer/over/ 17:55:34 ... Network functionality: Lemonbeat Radio 868MHz, Long rage, low power (LoRa Modulation) 17:55:43 ... (How to make devices intelligent) 17:55:52 ... Lemonbeat DNA structure 17:56:25 ... all necessary services on board - in every device 17:56:34 ... (How to make devices intelligent) 17:57:29 ... Lemonbeat Chip: Silicon Labs 32-bit, ARM Cortex-M3 CPU Processor; Silicon Labs SI 446x Tranceiver 17:57:48 ... Flash memory inckuding Firmware, Stack 17:58:22 ... Lemonbeat Studio: access to all devices, Initial implementation, Updates flash memory, 99% offline 18:00:08 ... (Use cases for private households (B2C - Micro level)) 18:00:29 ... smart energy can be linked to eMobility and Smart Home 18:01:13 ... Tesla Model 3, Chevrolet Bolt (EU: Opel Ampera-e, Aauxhall), Mercedes EQ 18:02:04 ... (Use cases for private households (B2C - Macro level)) 18:02:18 ... a cluster of power storages in a decentralized use case 18:03:25 present+ Carlos, Daniel 18:04:51 ... (Self learning mechanism on field level (1)) 18:04:53 ... (Self learning mechanism on field level (2)) 18:05:51 ... (Self learning mechanism on field level (3)) 18:06:01 ... authorization 18:06:23 ... (Benefits of an integrated Web of Things) 18:07:03 ... the use of primary devices is benericial for WoT 18:07:32 ... (Benefits of an integrated Web of Things - contd) 18:07:40 ... benefits of integrated WoT 18:07:55 ... use of primary devices leads to a cost reduction 18:08:24 ... (Increasing total integration and value of all components of a network) 18:08:40 ... devices as a data supplier 18:09:09 s/supplier/supplier, gateway with central controller/ 18:09:19 ... devices as a data supplier, primary device includes virtual proxy 18:09:30 ... network of autonomous devices without central control 18:09:54 ... network of autonomous devices without central control, self learning mechanism on field level 18:10:11 ... network of autonomous devices without central control, complex self learning mechanism 18:10:21 ... (Alternatives for WoT) 18:10:29 ... device to device communication 18:12:06 ... options: physical gateway, virtual proxy, light WoT stack/full WoT stack, small WoT stack 18:12:19 ... (Alternatives for WoT - contd) 18:12:36 ... a power supply company ofers its customers power storages in different versions 18:13:06 ... (Findings from Silicon Valley companies and pioneers) 18:13:48 ... in each network, the benefit increases for all participants, when adding new participants 18:14:03 ... the vlue of a telecommunications network is proportional... 18:14:26 ... (Feedback "International VDI Conress on IoT" 14.12.16 - Berlin 18:14:34 s/Berlin/Berlin)/ 18:14:53 ... how intelligent devices can enhance IoT 18:15:28 ... (Feedback "IoT Tech Expo" 23.01.17) 18:15:39 s/17/17 - London/ 18:16:00 ... (Suggestion: Adding these options to the WoT architecture) 18:16:30 ... (1) Thing to thing interaction without gateway: 18:16:43 ... (2) with gateway 18:16:52 jh: two different kind of WoT stacks 18:17:03 ... what is the main difference? 18:17:13 fr: covering a lot of devices 18:17:32 ... can speaking with constraint devices using light-weight WoT 18:17:48 ... full-spec vs light-weight 18:18:05 ... my best choice is light-weight WoT 18:19:17 @4: energy area? 18:19:29 fr: decentralized energy and IoT 18:20:14 @4: there is some active device 18:20:32 zk: can you configure 2 different services at once? 18:20:48 fr: we have one generic protocol 18:21:38 ... if you want to use different use cases, you can use the lemonbeat chip for those use cases 18:21:58 ... we could combine different things 18:22:29 zk: different protocols have different provisions for security 18:22:47 ... do you have enough computing power for various provisionings? 18:23:27 mk: kajimoto-san is the editor for the architecture document 18:23:47 ... you proposed via gateway communication 18:23:55 ... that's already included in the architecture doc 18:24:25 fr: talked with Kajimoto-san several times 18:24:46 mk: e.g., they have gateways for ECHONET 18:25:01 ... abstraction for them as well 18:25:15 mm: document now on GitHub repository 18:29:41 topic: McCool] OCF Architecture 18:29:51 s/McCool/[McCool/ 18:30:09 mm: OCF OVerview and Collaboration 18:30:16 s/OVerview/Overview/ 18:31:26 ... Open Interconnect Consortium + UPnP + Electrolux, Microsoft, Qualcomm + Allseen Alliance = Open Connectivity Foundation 18:31:36 ... working on new standards 18:32:07 ... sharing public resources today 18:32:22 ... (OCF Basics) 18:32:27 ... defining data model 18:33:30 ... 4 main things: OCF Specification, oneIoTa, IoTivity Open Open Source, OCF Certification 18:34:18 ... (OCF Goals) 18:34:44 ... easy for developers, interoperability, future consolidation, multiple vertical markets, scalability 18:35:25 ... (OCF Goals - Implications) 18:37:16 ... (OCF & IoTivity) 18:37:45 ... 2 different organizations: OCF and Linux Foundation (IoTivity) 18:38:01 ... (OCF - Conceptual Framework) 18:38:54 ... Resource Model &RESTful Interactions (RAML) 18:39:04 s/&R/& R/ 18:39:38 ... Discovery, Provisioning, Comms 18:39:53 ... security, identity & permissions 18:40:18 ... Transports: cable connection, wifi, zwave, bluetooth, ... 18:40:31 ... (Accessing Resources over the Network) 18:41:00 ... Application of Service - Resource Model & RESTful Interactions 18:41:06 ... (Some Details) 18:41:23 ... I'm happy to talk with you about OCF 18:41:28 ... Michael Koster is also available 18:41:46 ... Interaction model based on CLUDN 18:41:59 ... traditional web type of API 18:42:28 ... request-response and publish-subscribe 18:42:45 sebastian has joined #wot 18:43:23 ... we can't mandate what devices do 18:43:59 ... data models are defined using RAML 18:44:17 s/data/Data/ 18:44:22 ... Standards status: 18:44:40 ... only OIC and AllJoyn standards are currently public 18:44:48 ... Current IoTivity release supports OIC 1.2 18:45:03 ... OCF 1.0 standard is under development 18:45:17 ... OCF 1.0 standard will merge features of OIC 1.2 qnd ALLJoyn 18:45:42 ... Bridges being developed to allow access to OIC and AllJoyn devices from OCF 18:45:49 s/ALLJoyn/AllJoyn/ 18:45:55 [ morning break ] 18:46:01 rrsagent, draft minutes 18:46:01 I have made the request to generate http://www.w3.org/2017/02/06-wot-minutes.html kaz 18:54:24 s/@4:/moh:/g 18:54:27 rrsagent, draft minutes 18:54:27 I have made the request to generate http://www.w3.org/2017/02/06-wot-minutes.html kaz 19:09:24 Meeting: WoT IG/WG - OpenDay / PlugFest 19:09:29 dsr has joined #wot 19:09:50 scribenick: dsr 19:10:02 topic: JSON Schema 19:10:13 i/starting the meeting/scribenick: kaz/ 19:11:01 Presentation about the ongoing work on JSON Schema 19:11:42 s/JSON Schema/[Henry Andrews] JSON Schema: status and outlook/ 19:11:54 A series of drafts with draft 6 in final review in February 2017 19:13:46 Currently tidying things up and getting ready for a release 19:14:52 We now require references to be to whole schemas 19:15:35 We also now have more uniform treatment of terms that start with $ e.g. $id 19:16:17 ktoumura has joined #wot 19:16:35 Finalizing media type registration for IANA 19:17:34 Most of the validation keywords are stable, but we've added a few new ones. 19:19:15 We considering support for limited conditionals. 19:21:08 Hyper-schema is under active development. 19:22:10 This is about adding hyperlinks to JSON. 19:24:25 We're not trying to compete with other approaches, e.g. JSON-LD 19:25:14 We're looking into a UI schema for JSON, but this is at a very early stage 19:27:36 Another idea is to consider metadata keywords for document generation. 19:28:20 We expire our drafts after 6 months (like the IETF) and want to ensure that our working documents are updated in a timely fashion. 19:28:47 We plan to prove hyper schema with some automated user agents. 19:29:08 A some point we want to roll over into an IETF working group. 19:31:12 q+ 19:31:18 We're using URI templaces. 19:32:10 s/templaces/templates/ 19:32:27 ack da 19:33:29 Daniel: are there any plans to specify semantic properties, e.g. age in years? 19:34:06 Answer: so far no, there are other approaches that are better suited 19:34:34 Matthias: there are some mechanisms in JSON-LD for semantic links. 19:35:27 Driving the design through semantic vocabularies is a valuable approach to take 19:36:09 Sebastian: we want to build upon existing vocabularies where practical 19:37:00 Another consideration is suitability for resource constrained devices, is this something where we might collaborate on? 19:37:52 Henry: we're open for adding new keywords but less so for changing existing stable keywords 19:38:37 In particular, if you could point to where JSON schema proved difficult for some use case, we would definitely like to hear about that 19:39:25 We can express CBOR more or less, and am definitely interested in further discussion. 19:40:03 Topic: Gregg Kellogg talking about JSON-LD 1.1: status and outlook 19:40:44 Greg introduces himself. He is one of the co-editors for the JSON-LD spec 19:41:16 I want to talk about the change requests we've had and are considering for JSON-LD 1.1 19:41:49 An October 2016 common crawl revealed extensive use of JSON-LD 19:42:59 Some of the topics we're looking at include collections and hypermedia API 19:43:55 A design goal was to allow JSON developers to use Linked Data as regular JSON 19:44:33 These developers focus on accessing the data and not on RDF 19:45:55 We use @context as an object property that maps names to RDF concepts 19:46:59 It also enables us to describe the type for string values, e.g. IRIs, dates, numbers etc. 19:47:55 Arrays are treated as unordered unless otherwise noted. 19:48:48 We encourage the use of @id and @type for identifiers 19:50:40 JSON-LD has some core algorithms, e.g. to use the @context to expand terms to full IRIs 19:51:52 We expected a common use case would be canonicalise terms via an expand and compact steps, so we're strong on round trip without changes 19:53:26 Gregg and Matthias discuss some examples 19:55:04 We're trying to make objects easier to find using different keys 19:56:14 This makes use of @container together with @id withing @context. 19:56:45 s/withing/within/ 19:57:41 We want to make it easier to do a good job when mapping from RDF to JSON-LD via a document frame 19:59:12 We're addressed nested properties via a new keyword @nest 20:01:31 JSON-LD 1.1 adds support for scoped contexts with a means to implicitly insert @contexts. 20:03:03 rrsagent, set logs public 20:03:14 rrsagent, make minutes 20:03:14 I have made the request to generate http://www.w3.org/2017/02/06-wot-minutes.html dsr 20:04:57 The work is happening in a W3C Community Group. If there is sufficient interest, it could morph into a Working Group for an updated W3C Recommendation. 20:05:20 We're hoping to complete our CG drafts in Q2 2017 20:05:52 No C implementation, so volunteers are welcomed! 20:06:32 But the changes are easily applied to existing implementations, e.g. Python, PHP, Java, C# and Go 20:07:21 Today, only one implementation fully supports the CG spec (Greg's Ruby implementation) 20:07:58 Greg: RDF shape expressions could be interesting for JSON schema, and can be defined using JSON-LD 20:08:26 This pretty much allows for arbitrary validation of RDF graphs 20:09:51 Happy to talk about this tomorrow 20:10:15 ... we break for lunch and resume at 2pm PST 20:10:41 rrsagent, make minutes 20:10:41 I have made the request to generate http://www.w3.org/2017/02/06-wot-minutes.html dsr 21:26:32 ktoumura has joined #wot 21:50:40 taki has joined #wot 21:57:08 tokuyama_ has joined #wot 21:58:52 yamada has joined #wot 22:00:21 dape has joined #wot 22:00:53 naka has joined #wot 22:01:14 [ lunch ] 22:01:36 Topic: Scott Jenson (Google) Humility and the IoT 22:02:48 ... or what the Physical Web taught me about ecosystems 22:03:23 We have a huge vision for the IoT rather than just little devices. 22:04:37 The question is how we get there. We have some insights about the value for smart homes, but it can be a little underwhelming to explain. 22:05:14 [joke about digging through horse manure pile to find the "pony" that must be there] 22:06:58 Short story about a designed in Copenhagen who made a device that recognized when he put on safety glasses and turned the workshop grinder on and likewise off when he removed the glasses. 22:07:09 s/designed/designer/ 22:07:28 We are seeking to create a flexible platform 22:08:10 Video interview with Jeff Jaffe talking about the broader implications over time for the Web of things 22:08:46 Too many people are creating App store APIs rather than building blocks for everyone to build on 22:10:27 Scott says that too many people think that the Web sprang fully formed from TimBL's head - but it wasn't like that - Tim needed to find a way to share information across the heterogeneous systems at CERN 22:11:05 masato has joined #wot 22:11:22 Back to the physical web. Having one mobile app you need to install for everything you want to do or to control doesn't scale 22:12:03 naka_ has joined #wot 22:12:31 The location field at the top of the browser is like forcing people back to a DOS prompt when they've gotten used to high res color video 22:13:19 The physical web bypasses entering the web address taking you direct to the web app. 22:13:48 Rather than having an app per device, get the device to point to the web app! 22:15:09 People change the address (the beacon) the device emits according to the time of day and context 22:15:15 ryuichi has joined #wot 22:15:59 a 50 cent beacon could in principle be put into medicine bottles. 22:16:46 A video of a Bluetooth smart toy that embeds a beacon and can be controlled from a browser via the Web Bluetooth API 22:17:48 New Bluetooth spec can allows you to scan for the set of beacons, causing the UX to change automatically as you walk around a store or museum. 22:18:46 We've been very pleasantly surprised by the awesome ways people are using the physical web 22:19:19 Beacons could also start to discover each other, e.g. via JSON descriptions. 22:20:02 IEEE Computer article on building a Lexus out of Lego. 22:20:09 (from Feb 2017) 22:20:52 The biggest problem we've had with the Physical Web are the onboarding issues for getting people up to speed, e.g. with security. 22:21:31 Right now adding a bunch of new devices to your home WiFi is enough to make you break out into a cold sweat 22:21:53 We've got to make enrolling new devices really really easy 22:22:17 So smart setup is key! 22:23:02 How can devices easily gain access to semantic descriptions, e.g. of the rooms in your house 22:23:56 So the semantic map is key! 22:24:00 We need standard descriptions so that devices can understand each other 22:25:15 We know that machine learning and big data are incredible. We need a way to pull data together from different devices into one place for that machine learning to take place. How can we tell devices where to send their data? 22:25:45 Some kind of middle layer for devices to communicate on 22:26:08 A first step is centralized data. 22:27:00 A further idea is centralized coordination - i.e. to be able to coordinate all the devices in your home. 22:27:49 "The best way to ruin your product's UX is to add security to it", that's because security is almost never fully through through 22:28:03 s/through// 22:28:18 s/through/thought through/ 22:28:39 My challenge to you guys is JSON+HTTP+JS = ? 22:29:31 Johannes: show the slide for the 4 points you have, can you expand ... 22:29:39 sano has joined #wot 22:29:55 Scott: joining the network should be easy, and the device should at that time get information about the house and its context 22:31:06 I buy a new lamp, plug it in, and the nearest switch then controls it. This requires the house to learn about the new device and do something that is valuable and smart for me 22:31:48 dape has joined #wot 22:32:19 How about a virtual centralized perspective, i.e. coordination rather than centralization 22:33:22 Scott: we want to see what happens when these semantic descriptions meet with the protocols 22:33:31 s/How/Eve: How/ 22:34:49 Dave: is this a re-run of the surprise that people find when then see freshly targeted ads, how do we avoid the uncanny valley/the spooky house? 22:34:56 Scott: we're already there! 22:35:12 s/then/they/ 22:36:08 Scott talks about the need to balance different human needs. We want this to evolve from simple actions. 22:37:24 Earlier Scott worries about the failures associated with spaghetti code 22:38:12 If we can have machines talking to each other with shared semantics then we can explore interesting emergent behaviors 22:38:53 Michael: distributed RDF database would allow queries across devices in your home 22:39:57 Scott: identity is a can of worms, it's hard ... can we avoid the battles it brings 22:40:20 Dave: its my home I can name things the way I want (e.g. as for mDNS) 22:41:10 ... there will need to be systems of authentication through 22:42:44 Johannes: can we split discussion of identity into the human level and the machine level for lower layers of communication. 22:43:28 Scott: I want to avoid not understanding why things behave the way they do, and to avoid rigid control rules. 22:44:45 Topic: Bruce Fleming (HP): Ambient Computing 22:45:31 Bruce introduces himself as an HP Fellow 22:47:28 Bruce reminds us of Mark Weiser's vision of ubiquitous computing from 1988. 22:48:37 We've seen shifts from mainframes (many people one computer) to PCs (one person one computer) to one person many computers. 22:49:07 present+ Mehid_Barhami 22:50:30 Ambient computing involves computers supporting you in making intelligent, helpful decisions, and in the process disappearing into the background of our daily lives. 22:50:50 He shows a short video 22:51:34 Bathroom mirror with embedded display, voice interaction to help prepare you for the day ahead 22:51:59 In the kitchen helping with preparation of dishes 22:52:24 Keeping you on track and always present during your day 22:53:17 Computers weren't visible, and all the interaction was triggered by your natural interactions including spoken requests 22:53:37 Bruce talks about the security and privacy challenges 22:54:08 With smart surfaces, the systems need to know who is in eyesight or earshot 22:54:43 The systems constantly learn from your reactions to each situation. 22:56:29 We have a long way to go, but the Web of things is clearly relevant 22:57:34 Ambient computing is a re-emerging buzzword (Deloitte, Gartner, Microsoft, TechCrunch) 22:58:35 People will get used to instant answers to their questions. 22:59:34 Bruce shows some video of smart surface desktop concepts 23:00:11 Behaviors suitable at home can't be assumed to be appropriate at the office 23:00:19 masato has joined #wot 23:01:13 Placing your phone on the smart surface, your phone is instantly recognized, enabling the surface to pick up where you left off 23:02:05 Casting, voice & audio, computer vision, gestures, smart layout, connectivity, sensors, security and hardware 23:02:31 naka has joined #wot 23:03:05 Bruce summarises challenges to overcom 23:04:16 These include self power devices that are always on always connected, sensors everywhere require strong security, constant connectivity can lead to constant work which can be a drawback 23:05:06 We need to figure out how to ensure ambient intelligence addresses societies needs 23:05:56 Questions? 23:06:08 Any thoughts on monetization? 23:07:08 Answer: today everything is transactional, but everything you saw here, assumes commodity computing 23:07:52 We've found several paths to monetization, e.g. frictionless services 23:08:27 What kinds of ecosystem does ambient computing enable/require? 23:08:59 Bruce: we're going to partner with companies for the solution spaces 23:10:15 Bruce: the operating systems will also be a commodity 23:11:12 This is a multi-device, multi-OS environment and there has to be interoperability 23:12:09 The OS is good at resource management, but everything on top of that is from an intelligent layer above 23:12:44 Don't you think that Microsoft, Apple and Google won't want to play in this area? 23:13:08 If you got to a Microsoft conference, all they talk about is services 23:13:30 s/got /go / 23:14:12 Zoltan: are there one or more semantic spaces and how do they interact 23:15:36 Bruce: the difference between home and work is fading, you're probably better connected at home 23:16:20 naka has joined #wot 23:16:27 The context will be different though. 23:17:03 Dave: we presumably need to work on human values and a shift to cognitive computing, how do you see that happening? 23:18:02 Bruce: we are exploring this through a number of different approaches. 23:19:48 This involves a major transformation and will require a major cultural change. We've been very selective about the standards group we participate in. 23:20:24 [in response to a question about HP as an original equipment manufacturer] 23:21:03 Some companies are entrenched and change will be forced upon them by "disruptors" 23:21:49 rrsagent, make minutes 23:21:49 I have made the request to generate http://www.w3.org/2017/02/06-wot-minutes.html dsr 23:24:48 [ afternoon break until 4pm ] 23:38:45 ktoumura has joined #wot