06:49:00 <kaz> kaz has joined #webandauto
06:54:57 <kaz> kaz has left #webandauto
07:41:48 <ito_jari> ito_jari has joined #webandauto
07:47:09 <harukon> harukon has joined #webandauto
07:47:59 <Alan> Alan has joined #webandauto
07:48:15 <bgidon> bgidon has joined #webandauto
07:48:22 <Alan> rrsagent, pointer?
07:48:22 <RRSAgent> See http://www.w3.org/2012/11/15-webandauto-irc#T07-48-22
07:48:47 <marie> marie has joined #webandauto
07:49:06 <Alan> Meeting: Shifting Into High Gear on the Web - Day 2
07:49:45 <Alan> Chair: Dave & Adam
07:54:32 <kkitagaw> kkitagaw has joined #webandauto
07:55:08 <maru> maru has joined #webandauto
07:57:19 <naomi> naomi has joined #webandauto
08:01:22 <hrbysh> hrbysh has joined #webandauto
08:04:49 <hrbysh> hrbysh has left #webandauto
08:06:17 <Alan> Adam: Introduction of Roger Lanco (Strategy Analytics)
08:06:23 <Alan> scribe?
08:06:40 <marie> scribe: marie
08:07:06 <kaz> kaz has joined #webandauto
08:07:09 <hrbysh> hrbysh has joined #webandauto
08:07:24 <Alan> s/Lanco/Lanctot/
08:07:26 <bgidon> Roger: Strategy Analytics intro
08:07:42 <sakazawa> sakazawa has joined #webandauto
08:07:45 <bgidon> ... multi platform environments, domains
08:08:07 <marie> scribenick: bgidon
08:08:11 <bgidon> ... user experience expertise
08:08:25 <bgidon> ... labs to do research
08:08:40 <bgidon> ... very practical activities
08:09:03 <marie> [The Big Picture]
08:09:04 <bgidon> ...the big picture
08:09:15 <bgidon> ..enhance the driving experience
08:09:39 <bgidon> [the car is a "persistent inquiry]
08:10:56 <bgidon> [Beyond the icon]
08:11:25 <surata> surata has joined #webandauto
08:11:29 <bgidon> Roger: experience with Android car last week in California
08:11:50 <bgidon> ...we think we already pass that Icon interface
08:12:00 <marie> s/pass/passed
08:12:26 <bgidon> ...what's next, next experience
08:12:39 <bgidon> ... the details
08:12:45 <marie> [infotainment design trends]
08:13:05 <bgidon> Roger: we are in gen 4
08:13:27 <bgidon> ...hybrid solution
08:14:01 <marie> [MyFord Touch; 4th gen segment leader?]
08:14:24 <timeless_scribe> timeless_scribe has joined #webandauto
08:14:39 <bgidon> ... Ford solution to allow user's phone usage
08:15:27 <bgidon> ...sync solution
08:15:51 <timeless_scribe> RRSAgent, pointer
08:15:51 <RRSAgent> See http://www.w3.org/2012/11/15-webandauto-irc#T08-15-51
08:16:02 <bgidon> ...hybrid soltion connected phone and on board systems
08:16:16 <Alan> s/soltion/solution/
08:16:18 <timeless_scribe> RRSAgent, draft minutes
08:16:18 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:16:23 <marie> [Tier 1 suppliers]
08:16:50 <bgidon> Roger: Software/services companies growing in this market
08:16:51 <timeless_scribe> s/scribe?//
08:16:56 <dsr> dsr has joined #webandauto
08:17:22 <marie> [the automotive cloud has arrived]
08:17:25 <dsr> present+ Dave_Raggett
08:18:08 <bgidon> ... 3G, LTE is on the way, we have all the technology on the table to develop consumer experience
08:18:25 <bgidon> ...social networking acess is also there
08:18:34 <marie> s/acess/access
08:19:27 <bgidon> ...the car connnectivity in the car will be monetized
08:19:56 <timeless_scribe> present+     Adam_Abramski, Andy_Gryc, Boris_Geller, Burkhard_Mayer, Christian_Müller, Diana_Cheng, Josh_Soref, Marcin_Hanclik, Marie-Claire_Forgue, Maximilian_Michel, Mikko_Ylinen, Oliver_Novakovic, Philipp_Hoschka, Roger_C_Lanctot, Ryuji_Wakikawa, Shinjiro_Urata, Simon_Isenberg, Alex_Ajao, Ludovic_Alidra, Kazuyuki_Ashimura, Daniel_Austin, Matthias_Bezold, J_Alan_Bird, Youngwoo_Choi, Chris, _Delaney, Michael_Feld, Peter_Gaus, [CUT]
08:20:17 <bgidon> ...cennectivity will provide more services to customers
08:20:22 <marie> (anticipating pbs is the key - not selling the apps)
08:20:25 <timeless_scribe> present+ Petter_Graff, William_Greenly, Magnus_Gunnarsson, Prashanth_Halady, Tatsuhiko_Hirabayashi, Raymond_Hoogendoorn, Hiroshi_Ito, HyungJin_Jeon, Woochul_Jung, Kazuhiro_Kitagawa, Haruhiko_Kondo, Pavel_Konopelko, Amy_Leeland, Mitsunori_Maru, Markus_Muenkler, Tsuguo_Nobe, Magnus_Olsson, Nils_Oppermann, Justin_(JongSeon)_Park, Erik_Pellemeier, Scott_Pennock, Alejandro_Piñeiro_Iglesias, Thomas_Rottach, Shigeyuki_Sakazawa, Cheree[CUT]
08:20:37 <timeless_scribe> s/Sebastian_//
08:20:41 <marie> s/cennectivity/connectivity
08:20:55 <timeless_scribe> present+ Sebastian_Speiser, Marius_Spika, Roman_Steiger, Tatsuaki_Takahashi, Jean-Marc_Temmos, Naomi_Yoshizawa, Roberto_Zompi
08:20:55 <bgidon> ... voice in te car: early phase for now
08:21:02 <timeless_scribe> RRSAgent, draft minutes
08:21:02 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:21:06 <marie> s/te/the
08:21:44 <dsr> rrsagent, set logs public
08:21:51 <bgidon> ...demo experience on voice environment
08:22:07 <marie> ... my message is "please think outsidethe box"
08:22:26 <marie> s/outsidethe/outside the
08:22:26 <marie> [HMI trends]
08:23:08 <bgidon> ...HMI: touch screens, sensors, language voice
08:23:36 <bgidon> ... natual language to connect services
08:24:22 <marie> [connecting the car: the details]
08:24:29 <timeless_scribe> s|s/Sebastian_//||
08:24:51 <marie> s/natual/natural
08:24:56 <bgidon> ... Displays in the car
08:25:06 <timeless_scribe> present- Cheree[CUT]
08:25:12 <bgidon> ...driver distraction
08:25:36 <bgidon> ...some discussion in US about displays
08:25:58 <timeless_scribe> present+  Cheree_Anne_Schepp, Paul_Slattery
08:26:08 <bgidon> ...3G/LTE for CRM.VRM on the way
08:26:43 <bgidon> ...Iphone integration with BMW/Mini
08:26:53 <timeless_scribe> s/marie/scribe/
08:26:53 <timeless_scribe> s/... Displays/Roger: Displays/
08:27:09 <timeless_scribe> RRSAgent, draft minutes
08:27:09 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:27:10 <marie> [Connectivity ECU-OEM]
08:27:35 <timeless_scribe> s/marie/scribe/
08:27:36 <timeless_scribe> s/marie/scribe/
08:27:47 <timeless_scribe> RRSAgent, draft minutes
08:27:47 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:28:06 <bgidon> ...connectivity ECU: forecast: 100$ in 2011, $75 in 2019
08:28:18 <timeless_scribe> s/...HMI:/Roger: HMI:/
08:28:43 <bgidon> ...LTE forecast
08:28:51 <timeless_scribe> s/... my message/Roger: my message/
08:29:03 <timeless_scribe> RRSAgent, draft minutes
08:29:03 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:29:04 <bgidon> ...Telematics ECU
08:29:40 <timeless_scribe> s/...connectivity/Roger: connectivity/
08:29:51 <timeless_scribe> s/marie/scribe/
08:29:55 <timeless_scribe> RRSAgent, draft minutes
08:29:55 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:30:27 <bgidon> Roger: OEM display deployment
08:30:31 <timeless_scribe> s/te car/the car/
08:30:49 <bgidon> [OEM Display Deployment]
08:31:27 <bgidon> Roger: everything will be merged in the car
08:31:44 <bgidon> [OEM Headunit]
08:31:45 <timeless_scribe> s/...the big picture/Roger: the big picture/
08:32:03 <bgidon> Roger: enhance the audio experience
08:32:14 <timeless_scribe> RRSAgent, draft minutes
08:32:14 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:32:32 <bgidon> ...Harman is focusing on the audio experience
08:32:54 <bgidon> ...from CD to high quality audio experience
08:33:31 <bgidon> ...Digital radio is coming
08:33:44 <bgidon> [OEM Digital Radio]
08:33:53 <DanielAustin> DanielAustin has joined #webandauto
08:34:24 <timeless_scribe> s/... user experience expertise/Roger: user experience expertise/
08:34:34 <bgidon> Roger: Radio and some info services part of Nissan services
08:34:46 <timeless_scribe> s/    scribenick: bgidon//
08:34:47 <bgidon> ...Sirius experience
08:34:51 <timeless_scribe> s|s/    scribenick: bgidon//|
08:34:57 <timeless_scribe> s/scribenick: bgidon//
08:35:10 <timeless_scribe> i/Strategy Analytics intro/scribenick: bgidon/
08:35:14 <timeless_scribe> RRSAgent, draft minutes
08:35:14 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:35:30 <bgidon> [Must have Infotainment-Western Europe]
08:36:07 <bgidon> Roger: Smarphone presence in the car
08:36:39 <bgidon> [Smarphone's impact on the in-Vehicle Experience]
08:37:33 <bgidon> Roger: BMW experience
08:37:41 <bgidon> ...safety is the key
08:37:51 <timeless_scribe> s/(anticipating/Roger: (anticipating/
08:37:55 <timeless_scribe> s/marie/scribe/
08:38:09 <bgidon> [Interest in Connected Services: US & Western Europe]
08:38:50 <timeless_scribe> s/... 3G, LTE is/Roger: 3G, LTE is/
08:38:56 <timeless_scribe> s/marie/scribe/
08:39:09 <timeless_scribe> s/marie/scribe/
08:39:10 <bgidon> Roger: Facebook and Twitter: main usage is access to the data
08:39:29 <bgidon> [Mobile Phone Usage]
08:39:35 <timeless_scribe> s/marie/scribe/
08:39:45 <timeless_scribe> RRSAgent, draft minutes
08:39:45 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:40:17 <timeless_scribe> s/... Ford solution/Roger: Ford solution/
08:40:25 <timeless_scribe> s/marie/scribe/
08:40:33 <bgidon> [Car Connectivity a Mobile Mess]
08:40:48 <timeless_scribe> s/marie/scribe/
08:40:49 <timeless_scribe> RRSAgent, draft minutes
08:40:49 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:41:10 <bgidon> Roger: Nobody is doing right
08:42:03 <timeless_scribe> s/Iphone/iPhone/
08:42:08 <bgidon> ...don't see what is in the market today
08:42:40 <timeless_scribe> s/scribe: marie/scribe: scribes/
08:43:11 <bgidon> [MyFord Touch-Coming to China]
08:43:51 <timeless_scribe> i|Strategy Analytics intro|Topic: Strategy Analytics - Car trends/forecasts|
08:43:57 <bgidon> [GM CUE]
08:44:23 <timeless_scribe> RRSAgent, draft minutes
08:44:23 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:44:32 <bgidon> Roger: UI comments, usability of the icons ?
08:44:41 <dsr> icons are a step backward
08:45:23 <bgidon> ...and Now the videos !
08:45:45 <timeless_scribe> [ RLink Video ]
08:45:50 <timeless_scribe> s/timeless_scribe/scribe/
08:45:50 <marie> [R-link Renault video]
08:46:18 <dsr> no access to the CAN bus
08:46:27 <timeless_scribe> s/dsr/scribe/
08:46:32 <timeless_scribe> s/no access/Roger: no access/
08:46:36 <dsr> you have to purchase the apps, but the service is free
08:47:02 <timeless_scribe> s/dsr/scribe/
08:47:11 <timeless_scribe> s/you have/... you have/
08:47:17 <bgidon> Roger: Renault Zoe apps video
08:47:54 <bgidon> ...RLink, you are not able to connect your phone to the system
08:48:01 <timeless_scribe> RRSAgent, draft minutes
08:48:01 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless_scribe
08:48:01 <dsr> you don't want an app system you can only use in the car
08:48:08 <timeless_scribe> s/dsr/scribe/
08:48:12 <timeless_scribe> s/you don't/... you don't/
08:48:42 <bgidon> ...you need to be able to manage in the car and out the car usage, don't lock the environment
08:49:16 <timeless_scribe> s/marie/scribe/
08:49:35 <dsr> ...Like Renault, Chrysler also wants to monetize via app store
08:50:14 <dsr> ...[Chrysler video]
08:50:34 <timeless_scribe> s/dsr/scribe/
08:50:41 <timeless_scribe> s/dsr/scribe/
08:51:08 <bgidon> [Video: Uconnect]
08:51:16 <dsr> ...4 solutions, 3 of which uses the phone for connectivity
08:51:19 <timeless_scribe> s/dsr/scribe/
08:51:54 <bgidon> [The future of HMI-Too Convential]
08:53:04 <bgidon> [Touch Screens & Voices Forecast]
08:53:46 <bgidon> Roger: voice recognition evolution
08:54:08 <bgidon> [Car Makers Need]
08:55:05 <DanielAustin_> DanielAustin_ has joined #webandauto
08:55:43 <bgidon> Roger: in the car you are a persitent query
08:55:49 <timeless_scribe> s/tent/stent/
08:56:08 <bgidon> ...s/query/inquiry/
08:56:47 <bgidon> Q&A session
08:57:34 <bgidon> Roger: LTE usage
08:58:26 <bgidon> DSR: Icon experience ?
08:59:23 <bgidon> Roger: all the content running in the background
08:59:38 <naomi> naomi has joined #webandauto
09:00:35 <dsr> s/Icon experience/you said icons are the past, what do you think is the future?/
09:01:03 <dsr> Answer: services that run in the background anticipating and adapting to your needs.
09:02:08 <bgidon> Roger: Some works in progress
09:03:23 <bgidon> ...software is the solution to the different market needs
09:04:29 <kaz> kaz: what kind of mechanism is used for modality integration?
09:04:37 <kaz> ... proprietary ones?
09:04:59 <kaz> roger: nuance should be proprietary
09:06:16 <bgidon> Roger: Android in the car as a container
09:06:41 <bgidon> ...CloudCar solution
09:07:23 <bgidon> ...regarding Apps, at the end need to control the content
09:07:45 <timeless> scribenick: timeless
09:07:53 <timeless> Adam: thank you Roger
09:07:56 <timeless> [ Applause ]
09:08:10 <timeless> Adam: without delaying further
09:08:17 <timeless> ... our next presenter is from Vodafone
09:08:26 <timeless> ... can we bring up diana's slides from vodafone
09:08:47 <timeless> Topic: Is it time to power Infotainment and Car Portal Applications with HTML5 and Device APIs?
09:08:55 <timeless> dcheng3: Good morning
09:09:01 <timeless> ... i'm a little ill, so no questions
09:09:31 <timeless> [ Diana Cheng - R&D, Web Expert ]
09:09:38 <timeless> dcheng3: i'm a member of the DAP WG
09:09:44 <timeless> ... and recently joined SysApps as well
09:09:52 <timeless> ... i'm here w/ markus muenkler
09:10:28 <timeless> [ Contents ]
09:10:41 <timeless> dcheng3: Introduction: Status of the automotive app ecosystem
09:10:52 <timeless> ... Web technologies as an enabler  for Automotive
09:10:59 <timeless> ... Readiness of Web technologies: What is missing?
09:11:05 <timeless> ... Deep Dive into the enabling HTML5 features
09:11:10 <timeless> ... Conclusions: Key takeaways
09:11:25 <timeless> [ The automotive technology ecosystem ]
09:11:33 <timeless> dcheng3: it's fragmented
09:11:41 <timeless> ... we start to see BlackBerry Tablets in cars
09:11:48 <timeless> [ The Web Technology Ecosystem ]
09:11:54 <timeless> dcheng3: I'm using HTML5 broadly
09:12:02 <timeless> ... a lot of web technologies aren't part of HTML%
09:12:04 <timeless> s/%/5/
09:12:10 <timeless> ... I'm using it as an umbrella term
09:12:14 <timeless> ... We use it
09:12:24 <timeless> ... and we have to do some adaptation for different targets
09:12:27 <timeless> ... but it's still easier
09:12:36 <timeless> ... With a web application, you can immediately push updates
09:12:43 <timeless> ... For Web Applications
09:12:50 <timeless> ... mobile browsers support HTML5 to some extent
09:13:04 <timeless> ... they're supposed to support something, but it isn't that good
09:13:08 <timeless> [ Web - So what's new? ]
09:13:12 <timeless> dcheng3: new web platforms
09:13:19 <timeless> ... starting to integrate more w/ the underlying platforms
09:13:23 <timeless> .. Tizen / Firefox OS
09:13:29 <timeless> s/../.../
09:13:36 <timeless> ... more access to underlying data/hardware
09:13:39 <timeless> ... the native gap is closing
09:13:48 <timeless> [ Are HTML5 and Browser-based APIs ready? ]
09:13:55 <timeless> dcheng3: we have the question is HTML5 ready?
09:13:58 <timeless> ... it depends on the UC
09:14:03 <timeless> ... for the FT
09:14:14 <timeless> ... if you see it on the iPad or tablet, it's a really good experience
09:14:26 <timeless> ... mobile web app from Facebook is still a really good app
09:14:31 <timeless> ... it's close enough to a native feel
09:14:36 <timeless> ... what do we need for Automotive?
09:14:41 <timeless> ... do we need all the power of native?
09:14:46 <timeless> ... probably not, most don't need it
09:14:51 <timeless> ... what needs to improve in HTML5?
09:14:59 <timeless> [ Automotive Requirements: 2 Main Fronts ]
09:15:05 <timeless> dcheng3: there are a number of areas
09:15:10 <timeless> ... automotive can include user at home
09:15:16 <timeless> ... wanting to send driving directions from PC
09:15:20 <timeless> ... it's easier to search from home
09:15:24 <timeless> ... so some sync needs to be there
09:15:32 <timeless> ... speech recognition with offline support
09:15:41 <timeless> ... cellular connectivity can't be guaranteed
09:15:45 <timeless> ... Text-to-speech
09:15:51 <timeless> ... incoming notifications/traffic notifications
09:15:56 <timeless> ... Navigation/Routing
09:16:06 <timeless> ... if we want apps in the car, we want them to be installable and easily upgradable
09:16:23 <timeless> ... [Those were in-vehicle ]
09:16:33 <timeless> ... [Mobile Car Portals ]
09:16:39 <timeless> ... If there's car sharing in the family
09:16:49 <timeless> ... the main driver could receive notifications if someone else is using the car
09:16:54 <timeless> ... and there's an accident
09:16:57 <timeless> ... and access to the camera
09:17:11 <timeless> ... take a photo of a license plate and upload it to the web
09:17:22 <timeless> [ IVI Applications - Session Handover (1/2) ]
09:17:28 <timeless> dcheng3: you leave your vehicle
09:17:36 <timeless> ... and you want to continue listening to the music
09:17:48 <timeless> ... or you park your car in a spot, and you need to walk to the destination
09:18:00 <timeless> ... your walking directions could be synced to your phone
09:18:03 <timeless> [ IVI Applications - Session Handover (2/2) ]
09:18:07 <timeless> dcheng3: we need notifications to devices
09:18:15 <timeless> ... native platforms have Android C2DM/GCM
09:18:19 <timeless> ... Apple has APNS
09:18:23 <timeless> ... BlackBerry Push
09:18:32 <timeless> ... they all have restrictions
09:18:37 <timeless> ... Android has Message Quota
09:18:43 <timeless> ... iOS has no ads allowed
09:18:49 <timeless> ... -- Web Push
09:18:54 <timeless> ... We have a way in HTML5
09:18:59 <timeless> ... Server Sent Events
09:19:09 <timeless> ... - 1 way push, push standard dom events, no specific implementation needed
09:19:14 <timeless> ... integrated in the browser
09:19:18 <timeless> ... WebSockets
09:19:28 <timeless> ... - bidirectional channel between a server and a web app
09:19:38 <timeless> ... good for sending / receiving updates from the server as well
09:19:49 <timeless> ... if you leave the vehicle and your phone receives a notification
09:19:56 <timeless> ... the user needs to start the application manually
09:20:08 <timeless> ... there's limited support for these technologies in mobile browsers
09:20:25 <timeless> ... - I had to use a polyfill to see if WebSockets are supported and if not, fall back to XHR
09:20:37 <timeless> [ IVI Applications - Speech Recognition ]
09:20:42 <timeless> dcheng3: we need speech recognition
09:20:50 <timeless> ... a lot of solutions offer `good` cdapabilities
09:20:52 <timeless> s/cd/c/
09:20:59 <timeless> ... HTML 5 Speech Input
09:21:06 <timeless> ... there was a spec from the Speech XG
09:21:28 <timeless> ... there was a proposal to do best effort recognition, just as GeoLocation does
09:21:38 <timeless> ... there was a proposal for a new W3C WG for it
09:21:44 <timeless> ... there was minimal adoption
09:21:57 <timeless> ... only webkit, and it requires sending it to network service
09:21:59 <kaz> i/there was a proposal/[ actually, it is a CG ]/
09:22:16 <timeless> ... breaks the offline support requirement
09:22:27 <timeless> [ IVI Applications - Text-to-Speech ]
09:22:31 <timeless> dcheng3: we need text-to-speech as well
09:22:43 <timeless> ... you need realtime directions
09:22:55 <timeless> ... there are apis you can embed in your web apps, e.g. Google Translate
09:22:59 <timeless> ... there's no standard
09:23:05 <timeless> ... and those require network connections
09:23:15 <timeless> ... some proposals...
09:23:22 <timeless> [ IVI Applications - Navigation (1/2) ]
09:23:28 <timeless> dcheng3: a lot of sophisticated devices
09:23:31 <timeless> ... tom-toms, etc.
09:23:37 <timeless> ... HTML5 covers many of the requirements
09:23:43 <timeless> ... GPS via GeoLocation
09:23:56 <timeless> ... watchPosition() so you get updates
09:24:05 <timeless> ... WebWorkers for route calculations
09:24:10 <timeless> ... - but requires more mobile support
09:24:27 <timeless> ... Offline requirement?
09:24:32 <timeless> ... - having navigation without connectivity
09:24:38 <timeless> [ IVI Applications - Navigation (2/2) ]
09:24:43 <timeless> dcheng3: how do we create offline applications
09:24:49 <timeless> ... how do we access maps previously loaded?
09:24:56 <timeless> ... AppCache - something that could help us
09:25:05 <timeless> ... - `widely documented to be a bit rubbish`
09:25:26 <timeless> ... if one element that you tried to get fails to download, you revert to the previous version
09:25:39 <timeless> ... WebStorage: Small quota, storage of binary assets is not easy
09:25:47 <timeless> ... has performance issues
09:25:56 <timeless> ... because it's a synchronous
09:26:01 <timeless> s/nous/nous API/
09:26:05 <timeless> ... Other APIs exist
09:26:10 <timeless> ... but they're making slow progress
09:26:14 <timeless> ... IndexedDB
09:26:43 <timeless> ... has desktop implementation, but no mobile implementations
09:26:50 <timeless> ... WebSQL was implemented in mobile browsers
09:27:02 <timeless> ... but i haven't seen information if new mobile browsers support it
09:27:09 <timeless> ... there's FileSystem/File Writer
09:27:14 <timeless> ... from Google, but Mozilla doesn't like it
09:27:18 <timeless> ... there's no locking
09:27:28 <timeless> ... Mozilla created their own File System API
09:27:33 <timeless> ... which extends IndexedDB
09:27:36 <timeless> ... there's fragmentation
09:27:46 <timeless> ... and no acceptance of existing proposals
09:27:56 <timeless> [ IVI Applications - Installable Applications ]
09:28:00 <timeless> dcheng3: W3C Widgets
09:28:08 <timeless> ... no mechanism to automatically update
09:28:20 <timeless> ... lose advantage of updates re hosted apps
09:28:26 <timeless> ... w3c widgets aren't popular
09:28:33 <timeless> ... Google has their own, Mozilla has their own
09:28:39 <timeless> ... fragmentation needs to be addressed
09:28:49 <timeless> ... need to get people to converge
09:29:07 <timeless> ... PhoneGap as an alternative
09:29:12 <timeless> ... (now Apache Cordova)
09:29:18 <timeless> ... you can push updates to native stores
09:29:25 <timeless> ... it's a workaround, it's an open source project
09:29:28 <timeless> ... not a standard
09:29:33 <timeless> [ Car Portals ]
09:29:39 <timeless> dcheng3: UC Insurance
09:29:45 <timeless> ... we have a dongle that goes in a car
09:29:52 <timeless> ... right now it's mostly static data
09:29:56 <timeless> ... it has a Global SIM
09:30:03 <timeless> ... so the user can move freely throughout Europe
09:30:09 <timeless> ... it has GPS, Accelerometer
09:30:15 <timeless> ... to log trips of user
09:30:19 <timeless> ... log driving behavior
09:30:24 <timeless> ... see if there's harsh breaking
09:30:31 <timeless> ... The Mobile Web interface looks like this
09:30:38 <timeless> [ --Picture-- ]
09:30:44 <timeless> [ Car Portals ]
09:30:49 <timeless> dcheng3: you can locate your car
09:30:52 <timeless> ... see your current position
09:30:56 <timeless> ... you can zoom in
09:30:59 <timeless> ... get directions
09:31:01 <timeless> [ Car Portals ]
09:31:05 <timeless> dcheng3: receive error messages
09:31:11 <timeless> ... from the dashboard
09:31:21 <timeless> ... we calculate a Green score, and an insurance driving score
09:31:32 <timeless> [ Car Portals ]
09:31:38 <timeless> dcheng3: i have the application, i can show it
09:31:43 <timeless> ... it behaves in modern mobile browsers
09:31:46 <timeless> ... Chrome for Android
09:31:52 <timeless> ... it behaves very nicely
09:32:00 <timeless> ... not so much so for Android 2.3 browser
09:32:06 <timeless> ... - issues w/ performance
09:32:14 <timeless> [ Car Portals - Map Visualization ]
09:32:17 <timeless> dcheng3: we embed maps
09:32:21 <timeless> ... there are lots of apis
09:32:25 <timeless> ... Nokia Maps, Google Maps
09:32:30 <timeless> ... you can make rich UIs
09:32:40 <timeless> ... Touch requirements for mobile
09:32:47 <timeless> ... it doesn't work very well in slightly stale browsers
09:32:50 <timeless> ... Android 2.3 is poor
09:33:02 <timeless> ... no pinch to zoom, double tap- nothing [useful] happens - the page jumps
09:33:14 <timeless> ... `overflow:auto` problem
09:33:24 <timeless> ... you can't scroll the content in the middle if you have fixed element content
09:33:31 <timeless> ... Android 2.3/older iOS Safari
09:33:39 <timeless> ... you have this problem
09:33:49 <timeless> ... you can find polyfill with CSS Transformations
09:33:52 <timeless> ... but it hurts performance
09:33:58 <timeless> ... it's an implementation issue, not a standards issue
09:34:07 <timeless> ... not sure about the story of pushing updates to older platforms
09:34:14 <timeless> ... going forward, we want to avoid these issues
09:34:21 <timeless> [ Car Portals - Real-time Notifications ]
09:34:26 <timeless> dcheng3: we want to send notifications
09:34:31 <timeless> ... if there's a crash/heart break
09:34:43 <timeless> ... native apps have status bar which grabs user attention
09:34:51 <timeless> ... important for emergency alerts
09:34:58 <timeless> ... we don't have them in mobile
09:35:07 <timeless> ... there's web notifications
09:35:14 <timeless> Josh_Soref: BlackBerry PlayBook has it
09:35:20 <timeless> dcheng3: most mobile browsers don't support it
09:35:33 <timeless> ... not good for getting user's attention
09:35:39 <timeless> ... Vibration API
09:35:44 <timeless> ... to couple w/ Real-time notifications
09:35:55 <timeless> ... -it's coming to mobile browsers
09:36:06 <timeless> [ Key Take-aways (1/3) ]
09:36:10 <timeless> dcheng3:a lot is covered
09:36:16 <timeless> ... we need to work to fix some
09:36:23 <timeless> ... for enterprise... UVI UC
09:36:49 <timeless> ... this technology enables `fast to mmarket`
09:36:51 <timeless> s/mm/m/
09:36:57 <timeless> ... and target a wide range of users
09:37:02 <timeless> [ Key Take-aways (2/3) ]
09:37:04 <timeless> [ Key Take-aways (3/3) ]
09:37:18 <timeless> dcheng3: need to agree on storage mechanism for large data
09:37:24 <timeless> ... WebSQL on mobile?
09:37:27 <timeless> ... IndexedDB?
09:37:31 <timeless> ... FileSystem API?
09:37:38 <timeless> ... what about building something on IndexedDB instead?
09:37:46 <timeless> ... it seems to have the underlying performance
09:37:50 <timeless> ... browsers need to support it
09:38:01 <timeless> ... Broader support for WebSockets - mobile browsers aren't there yet
09:38:06 <timeless> ... fragmentation in Web Packaging
09:38:19 <timeless> ... either changes to W3C Packaging,
09:38:25 <timeless> ... or get convergence from Browser vendors
09:38:36 <timeless> ... Need to standardize something for Text-to-speech
09:38:43 <timeless> ... with best effort and fallback to embedded solution
09:38:51 <timeless> ... best performance if connectivity is available
09:39:00 <timeless> ... Similar for Speech-recognition
09:39:05 <timeless> [ Questions? ]
09:39:11 <timeless> dcheng3: that's it
09:39:14 <timeless> [ Applause ]
09:39:33 <timeless> ph: very nice talk about what's there
09:39:36 <timeless> ... and where the gaps are
09:39:42 <timeless> ... we see a lot of stuff is available/can be used
09:39:47 <timeless> ... things need to be pushed further
09:39:51 <timeless> ... The dongle you showed?
09:39:55 <timeless> ... is that something only you can use?
09:40:00 <timeless> ... or can others use the data?
09:40:10 <timeless> dcheng3: atm, we have a company that gathers the data in the backend
09:40:17 <timeless> ... and making it friendly
09:40:20 <timeless> ... and there's a REST api
09:40:26 <timeless> ... but it isn't so open yet, no.
09:40:38 <timeless> Adam: thank you dcheng3
09:40:41 <timeless> [ Applause ]
09:41:02 <timeless> Topic: KDDDI's position for Web and Automotive issues
09:41:18 <timeless> shigeyuki: Shigeyuki Sakazawa, KDDI corporation
09:41:20 <timeless> [ Agenda ]
09:41:26 <timeless> shigeyuki: introduction of KDDI
09:41:30 <timeless> ... seamless service concept
09:41:38 <timeless> ... connecting vehicle and smart phone
09:41:51 <timeless> [ About KDDI ]
09:41:58 <timeless> shigeyuki: KDDI is a japanese telecom carrier
09:42:11 <timeless> ... mobile telecom, fiber-to-the-home, tele com solutions
09:42:16 <timeless> ... content services and banking
09:42:35 <timeless> s/shigeyuki/sakazawa/
09:42:36 <timeless> s/shigeyuki/sakazawa/
09:42:50 <timeless> [ KDDI's Convergence Strategy ]
09:42:57 <timeless> sakazawa: multi-use
09:43:07 <timeless> ... WiMAX, 4G, cable-to-home
09:43:22 <timeless> ... Vehicle issues
09:43:32 <timeless> ... application +  content services
09:43:36 <timeless> [ Seamless service concept ]
09:43:44 <timeless> sakazawa: we'd like to realize seamless service
09:43:52 <timeless> ... service anytime, anywhere, any-device
09:43:59 <timeless> ... service on a personalized basis
09:44:04 <timeless> ... service with more pleasure
09:44:15 <timeless> ... during an event: watching video, shopping, driving
09:44:22 <timeless> ... - including before/after event
09:44:32 <timeless> ... For driving-event
09:44:45 <timeless> ... Make driving plan and download maps (@home)
09:45:07 <timeless> ... Maps/music/other data downloaded in your smartphone (@driving)
09:45:14 <timeless> ... search nearby (@cafe)
09:45:28 <timeless> ... restaurants, shops, other data (@driving)
09:45:33 <timeless> ... - driving is part of our life
09:45:40 <timeless> ... want to connect everyday life to event
09:45:50 <timeless> [ Requirements for seamless service ]
09:46:01 <timeless> sakazawa: contents & Apps ubiquitous use
09:46:05 <timeless> ... vehicle personalization
09:46:07 <timeless> ... seamless networking
09:46:11 <timeless> [ Functions to be realized ]
09:46:18 <timeless> sakazawa: contents and apps ubiquitous use
09:46:24 <timeless> ... - speaker out of music from smartphone
09:46:31 <timeless> ... show a navigation map stored from smartphone
09:46:42 <timeless> ... recall address book from the phone and display on headunit
09:46:46 <timeless> .. - to make a phone call
09:46:52 <timeless> ... Vehicle personalization
09:47:00 <timeless> ... personalize various settings for a rental-car
09:47:10 <timeless> ... and erase personal information from shared car
09:47:16 <timeless> ... tune User Interface
09:47:30 <timeless> ... not just menu appearance, but also speech recognition
09:47:46 <timeless> [ Functions to be realized ]
09:47:52 <timeless> sakazawa: seamless networking
09:48:03 <timeless> ... continue streaming and sequential update
09:48:10 <timeless> ... prefetch heavy data before
09:48:19 <timeless> [ Characteristics of headunit/phone ]
09:48:23 <timeless> sakazawa: all-in-one head unit
09:48:28 <timeless> ... smartphone
09:48:36 <timeless> ... hybrid smartphone + head-unit
09:49:04 <timeless> ... - low cost, up to date service, high usability
09:49:08 <timeless> s/-/+
09:49:15 <timeless> ... - high standardization required
09:49:24 <timeless> [ two approaches for hybrid ]
09:49:33 <timeless> sakazawa: Display Image Transfer - MirrorLink
09:49:41 <timeless> ... distributed processing
09:49:46 <timeless> ... apps run on headunit
09:49:53 <timeless> .. headunit+phone share processing
09:50:07 <timeless> [ KDDI's prototype - Web Infotainment ]
09:50:12 <timeless> sakazawa: phone works as web server
09:50:17 <timeless> ... head unit loads app and runs it
09:50:27 <timeless> [ Structure of webserver on phone ]
09:50:48 <timeless> sakazawa: phone: storage (media, web app, hmi), rpc, websocket server, http server, ssdp server
09:51:16 <timeless> ... Head unit (HMI, web apps (navi, maps, multimodal), browser (ssdp, devicce api -> CAN))
09:51:36 <timeless> [ Relationship to functional requirements ]
09:51:47 <timeless> sakazawa: this configuration satisfies some functional requirements
09:51:53 <timeless> ... contents + apps ubiquitous use
09:52:07 <timeless> .. storage access to content (media content is stored in phone, can be routed to head unit)
09:52:11 <timeless> s/../.../
09:52:17 <timeless> ... native functions can be accessed from head unit
09:52:30 <timeless> ... web application in phone is personalized
09:52:35 <timeless> ... seamless networking
09:52:43 <timeless> ... storage area as cache/pre-fetch data
09:52:46 <timeless> [ Demo ]
09:52:59 <timeless> sakazawa: demo in Wireless Japan 2012
09:53:04 <timeless> ... article (in japanese)
09:53:15 <timeless> [ Future activities ]
09:53:37 <timeless> sakazawa: this is the wrong presentation
09:53:44 <timeless> ... marie will upload this slide
09:53:58 <timeless> ... we connect the smartphone and head unit
09:54:17 <timeless> ... head unit has navigation service
09:54:21 <timeless> [ Future activities ]
09:54:39 <timeless> sakazawa: standardization
09:54:54 <timeless> ... service discovery including privacy issues related to DAP WG (Web Intents)
09:55:04 <timeless> ... Create new value for users = Amazing Apps
09:55:18 <timeless> ... next generation context aware and personalized navigation
09:55:31 <timeless> ... multimodal apps + AI like a "Knight Rider"
09:55:46 <timeless> ... user could interact with the car
09:55:49 <timeless> ... that's our dream
09:55:57 <timeless> [ Thank you. ]
09:55:59 <timeless> [ Applause ]
09:56:04 <timeless> Adam: questions?
09:56:20 <timeless> takahashi: Takahashi, Mitsubishi Electric
09:56:33 <timeless> ... your structure seems similar to ACCESS's HaaP
09:58:47 <timeless> marie: we uploaded your slides
09:58:50 <timeless> ... you can try again
09:58:58 <timeless> [ Slides with picture ]
09:59:03 <timeless> sakazawa: there's a smartphone and a headunit
09:59:07 <timeless> ... connected using WiFi-direct
09:59:14 <timeless> ... smartphone with restaurant destination
09:59:24 <timeless> [ Personalization of appearance of headunit ]
09:59:31 <timeless> [ Accessing smartphone content - from headunit ]
09:59:51 <timeless> [ Buying theater ticket near destination ]
10:00:06 <timeless> sakazawa: accessed at headunit using smartphone to website
10:00:08 <timeless> [ Applause ]
10:00:12 <timeless> Adam: 15 minute break
10:00:25 <timeless> ... we want to take a group photo after the break
10:21:05 <timeless> Topic: Vistion: Web and Automotive
10:21:17 <timeless> temmos: Jean-Marc Temmos
10:21:20 <timeless> ... Hello everybody
10:21:33 <Alan> s/Vistion/Visteon/g
10:21:35 <timeless> ... yesterday I used a small script to compile and extract all the words from the position papers for this workshop
10:21:49 <timeless> ... the good news is that web and automotive are the biggest word
10:22:03 <timeless> ... w3c and api are smaller
10:22:08 <timeless> [ Plan ]
10:22:19 <timeless> temmos: a brief overview of Visteon
10:22:23 <timeless> ... HMI designc hallenges
10:22:29 <timeless> ... - tools and process
10:22:31 <timeless> s/gnc/gn/
10:22:38 <timeless> ... - bring new features to the user
10:22:48 <timeless> ... Some hints for improvement
10:22:52 <timeless> ... - UI.Cockpit
10:22:56 <timeless> ... - Web technologies
10:23:03 <timeless> ... Expectations and recomendations
10:23:20 <timeless> [ Visteon & HMI Innovation ]
10:23:32 <timeless> temmos: Visteon is a Tier 1 automotive supplier
10:23:40 <timeless> ... we're mainly focused on new generation HMIs
10:23:44 <timeless> ... for car manufacturers
10:23:55 <timeless> ... we're working on transversal frameworks
10:24:04 <timeless> ... we're involved with collaborative projects/academics
10:24:11 <timeless> ... concept car software design and development
10:24:24 <timeless> ... we work closely w/ German Center of Innovation
10:24:35 <timeless> ... we're an American company and have centers in Detroit
10:24:42 <timeless> [ Visteon & HMI Innovation ]
10:24:48 <timeless> temmos: Visteon Genivi Involvement
10:24:56 <timeless> ... we're on the Board of Directors
10:24:58 <timeless> ... etc.
10:25:02 <timeless> [ Tools and Process ]
10:25:13 <timeless> temmos: problems designing, from prototype to embedded target
10:25:17 <timeless> ... Many platforms/libraries
10:25:21 <timeless> ... lots of target specific code
10:25:42 <timeless> ... arm/atom/x86; Qt/SVG/Air; OpenGL/OpenGLES/OpenVG; Linux/Windows/QNX
10:26:06 <timeless> ... many tools, many design softwares: Flash, HTML5, EBGuide, Altia, Vaps XT
10:26:12 <timeless> ... many experts in various domains
10:26:25 <timeless> ... - artists, designers, developers - they don't want to use the same tools
10:26:28 <timeless> [ Tools and Process ]
10:26:34 <timeless> temmos: logics / graphics unclear frontier
10:26:48 <timeless> ... between behavior(intelligence) of application and the graphics side(way to display to user)
10:26:54 <timeless> ... relating to Tools
10:26:56 <Test> Test has joined #webandauto
10:27:04 <timeless> ... HTML - CSS for skinning/displaying
10:27:07 <timeless> ... JavaScript
10:27:17 <timeless> ... Vaps/EBGuide can embed state chart
10:27:21 <timeless> ... there's no clear frontier
10:27:37 <timeless> ... famous gap between development cycles (consumer electronic v. automotive)
10:27:52 <timeless> ... consortiums: Autosar, Genivi - new opportunities
10:27:56 <timeless> ... new constraints
10:28:03 <timeless> ... Technologies and standards change very fast
10:28:10 <timeless> ... Moblin -> MeeGo -> Tizen
10:28:26 <timeless> ... don't have to be early adopters, but have to follow
10:28:44 <timeless> ... EDonAp with Renault
10:28:59 <timeless> ... we have to be as technology agnostic as possible
10:29:12 <timeless> ... we have to use as much web tech as possible - it's cross platform, easier
10:29:18 <timeless> ... the set of skills required is quite limited
10:29:27 <timeless> ... as compared to the low level tools
10:29:38 <timeless> [ Improvements for the user ]
10:29:42 <timeless> temmos: Customization
10:29:46 <naomi> naomi has joined #webandauto
10:29:47 <timeless> ... Multimodal features
10:29:50 <timeless> ... context awareness
10:29:55 <timeless> ... open ended dynamic nature
10:29:57 <timeless> [ Customization ]
10:30:02 <timeless> temmos: Interface & personalization
10:30:07 <timeless> ... there's a Genivi group for it
10:30:17 <DanielAustin> DanielAustin has joined #webandauto
10:30:19 <timeless> ... there's an API for detecting where a user is sitting, what they're doing
10:30:37 <timeless> ... car re-design for new usages (car sharing, renting, auto-driving...)
10:30:54 <timeless> ... User settings and preferences should be retrieved from the smartphone
10:31:01 <timeless> ... "avoid before google mess for sync":
10:31:02 <dcheng3> dcheng3 has joined #webandauto
10:31:15 <timeless> ... customization is more than just skinning for css
10:31:27 <timeless> ... Facebook addict? want Facebook menu
10:31:32 <timeless> ... if i'm not, i want something else
10:31:38 <timeless> ... not possible with css
10:31:49 <timeless> [ Customization ]
10:31:55 <timeless> temmos: Left pedal, right pedal
10:32:07 <timeless> ... left for entertainment, right for something else
10:32:11 <timeless> [ Multi-modal ]
10:32:19 <timeless> temmos: many screens and displays
10:32:21 <timeless> ... haptics
10:32:27 <timeless> ... speakers & microphone
10:32:41 <timeless> ... - microphone array can detect position (is it a passenger), remove noise
10:32:46 <timeless> ... heads down display
10:32:50 <timeless> ... heads up display
10:32:53 <timeless> [ Multi-modal ]
10:32:57 <timeless_scribe> scribenick: timeless_scribeeclusters & guages
10:33:03 <timeless_scribe> ... off-board speech recognition in the cloud / onboard
10:33:08 <timeless_scribe> ... speech synthesis
10:33:25 <timeless_scribe> s/scribenick: timeless_scribee//
10:33:37 <timeless_scribe> s/timeless_scribee/scribe/
10:33:38 <timeless_scribe> s/timeless_scribee/scribe/
10:33:38 <timeless_scribe> s/timeless_scribee/scribe/
10:33:39 <timeless_scribe> s/timeless_scribee/scribe/
10:33:50 <timeless> [ Context awareness ]
10:34:28 <timeless> temmos: context aware applications for infotainment and ADAS UCs
10:34:31 <timeless> ... location based
10:34:35 <timeless> ... map enhanced/map enabled
10:34:44 <timeless> ... onboard/offboard seamless switching
10:34:52 <timeless> ... - very good speech recognition in cloud
10:35:04 <timeless> ... - when i lose the system, i don't want things to be completely different
10:35:23 <timeless> ... cache some info to prevent degradation when the service provider changes
10:35:31 <timeless> ... driver attention, driver state inference
10:35:34 <timeless> RRSAgent, draft minutes
10:35:34 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless
10:35:56 <timeless> [ Open and Dynamic Architecture ]
10:36:01 <timeless> temmos:  we want the system to detect
10:36:05 <timeless> ... to support hot plug
10:36:09 <timeless> ... get content from car/phone
10:36:27 <timeless> s|s/scribe/scribe/||
10:36:28 <timeless> s|s/scribe/scribe/||
10:36:34 <timeless> s/timeless_scribe/scribe/G
10:36:43 <timeless> RRSAgent, draft minutes
10:36:43 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless
10:36:47 <timeless> [ Open and Dynamic Architecture ]
10:37:03 <timeless> teemos: seamless sync car->other (mobile, cloud)
10:37:07 <timeless> ... networking and web management
10:37:12 <timeless> ... integration w/ in car systems
10:37:22 <timeless> ... Machine to Machine (M2M) communication and Swarm Intelligence
10:37:47 <timeless> s/clusters & guages/teemos: clusters & guages/
10:37:59 <timeless> ... onboard/offboard traffic
10:38:03 <timeless> [ Open and Dynamic Architecture ]
10:38:16 <timeless> teemos: in the past, hardware had to adapt
10:38:32 <timeless> ... in consumer industry, consumer wants new game, buys new console
10:38:39 <timeless> ... new model
10:38:49 <timeless> ... resources are ...
10:38:52 <timeless> ... consider task
10:38:54 <timeless> ... with agents
10:39:04 <timeless> ... get to destination; ensure driving safely
10:39:13 <timeless> ... use modeling to derive hardware+software architecture
10:39:23 <timeless> [ Open and Dynamic Architecture ]
10:39:26 <timeless> s//[ Open and Dynamic Architecture ]/
10:39:30 <timeless> RRSAgent, draft minutes
10:39:30 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html timeless
10:39:39 <timeless> ... this is the task of the D3Cos project
10:39:46 <timeless> ... they use tools for this
10:39:50 <timeless> ... safety norms are converging now
10:39:58 <timeless> ... dynamic architecture to ensure safety for pilot and driver
10:40:15 <timeless> [ Open and Dynamic Architecture ]
10:40:20 <timeless> teemos: design patterns
10:40:27 <timeless> ... we learn a lot from the XXX partners
10:40:41 <timeless> ... provide us with multimodal human interfaces
10:40:50 <timeless> [ E-Bee concept car ]
10:41:17 <timeless> s/EDonAp/E-Bee(?)/
10:41:32 <timeless> teemos: built using Linux+Genivi
10:41:46 <timeless> ... it's shown @Electronika in Germany (ending today)
10:41:51 <timeless> ... otherwise @CES
10:42:00 <timeless> [ UI.Cockpit Framework ]
10:42:15 <timeless> teemos: centralize application logic for cockpit HMI and distribute GUIs over various HTML5 client displays
10:42:20 <timeless> ... MVC based framework
10:42:39 <timeless> ... keep working w/ graphical environment that best fits on your target
10:42:52 <timeless> ... Altia might be a good choice
10:43:00 <timeless> ... but you might want to use TAT
10:43:15 <timeless> ... and you'd have to throw everything away
10:43:23 <timeless> ... client-server websocket
10:43:25 <timeless> ... xml api
10:43:28 <timeless> ... html5+js proxy
10:43:34 <timeless> [ UI.Cockpit Framework ]
10:43:44 <timeless> teemos: graphics, as many models as technologies
10:43:51 <timeless> [ UI.Cockpit Framework ]
10:43:55 <timeless> teemos: logic
10:43:58 <timeless> ... embeddic
10:44:02 <timeless> s/dic/ded/
10:44:07 <timeless> ... or stateful c++
10:44:09 <timeless> ... or rhapsody
10:44:11 <timeless> ... whatever
10:44:14 <timeless> [ UI.Cockpit Framework ]
10:44:19 <timeless> teemos: how to fetch data
10:44:25 <timeless> ... CAN bus, MOST bus, ...
10:44:31 <timeless> [ Expectations and recommendations ]
10:44:35 <timeless> teemos: flexibility
10:44:44 <timeless> ... we face standardization process for ... and Genivi
10:44:56 <timeless> ... it was just standardizing what wasn't competitive
10:45:02 <timeless> ... there will be reluctancy
10:45:10 <timeless> ... be flexible and have a limited scope
10:45:31 <timeless> ... low level access to device calls
10:45:45 <timeless> ... even if Android is getting better, for iPhone, we need more
10:45:55 <timeless> ... Graphics SVG - 2D/3G
10:46:02 <timeless> ... tools to compete w/ Adobe toolchain
10:46:08 <timeless> ... SVG is widely used, but not perfect
10:46:23 <timeless> ... clean logic / graphics separation
10:46:44 <timeless> [ Video & more info ]
10:46:50 <timeless> teemos: i'll show a video about E-Bee
10:47:29 <timeless> [ Infotainment ]
10:47:36 <timeless> teemos: btw, this was an HTML5 presentation using CSS
10:47:55 <timeless> teemos: no sound, i'll have to talk
10:48:00 <timeless> ... distributed system
10:48:17 <timeless> ... actually pretty centralized, we'd like more decentralized like airplanes
10:48:23 <timeless> ... right side we have petal
10:48:56 <timeless> ... left petal is for ADAS
10:49:08 <timeless> ... usual frontier between Infotainment and ADAS
10:49:19 <timeless> ... giving screen can show both ADAS and Infotainment
10:49:30 <timeless> ... we should ensure every means of communication
10:49:33 <timeless> ... ensures safety
10:49:42 <timeless> ... there's no API for ADAS v. Infotainment
10:50:09 <timeless> [ video crashed ]
10:50:17 <timeless> [ switch to next video ]
10:50:27 <timeless> teemos: ... augmented reality
10:50:30 <timeless> ... heads up / heads down
10:50:37 <timeless> ... context dependent hardware buttons
10:50:52 <timeless> ... this is a Nissan Leaf (for the E-Bee concept car)
10:51:08 <timeless> ... are some of you going to Logicas show?
10:51:27 <timeless> ... two camera in the car
10:51:32 <timeless> ... one in the back, one for QR code
10:51:35 <timeless> [ last video ]
10:51:42 <timeless> s/video/video: Passenger/
10:51:50 <timeless> s/video ]/video: Driver ]/
10:51:56 <timeless> teemos: door modules for interact
10:52:04 <timeless> ... each passenger has their own module area with speakers
10:52:19 <timeless> ... improve configuration for each passenger
10:52:28 <timeless> ... 4 mics, 4 sound systems
10:52:32 <timeless> ... privacy on demand
10:52:48 <timeless> ... there are plenty of other videos on the web site
10:53:00 <timeless> teemos: thanks for your attentions
10:53:02 <timeless> s/s//
10:53:05 <timeless> [ Applause ]
10:53:11 <timeless> DSR: time for one quick question
10:53:17 <timeless> ph: All displays are driven by HTML5?
10:53:21 <timeless> teemos: most of the display
10:53:25 <timeless> ... some are still in Flash
10:53:28 <timeless> [ boo ]
10:53:30 <timeless> teemos: i know it's bad
10:53:38 <timeless> ... but it's porting to HTML5
10:53:47 <timeless> ... we have Android tablets in html5
10:54:02 <timeless> DSR: rich potential UI
10:54:07 <timeless> ... we'll pick it up later
10:54:14 <timeless> ... minor change to agenda
10:54:22 <timeless> ... i'd like to bring forward the Renault presentation
10:54:30 <timeless> teemos: thank you
10:54:33 <timeless> [ Applause ]
10:54:46 <rw> rw has joined #webandauto
10:54:54 <timeless> Topipc: Drive the change - Renault
10:55:02 <timeless> renault: this isn't a presentation on R-Link
10:55:08 <timeless> ... I'm YVR
10:55:14 <timeless> ... from the advanced electronic project
10:55:18 <timeless> ... i'm involved in Genivi
10:55:22 <timeless> [ Summary ]
10:55:31 <timeless> renault: car displays are special
10:55:35 <timeless> ... technical challenges
10:55:42 <timeless> ... web technologies and standards can help
10:55:48 <timeless> s/Topipc/Topic/
10:55:56 <timeless> [ car displays are special ]
10:56:08 <timeless> renault: with TV you have HMI for watch broadcast, play games, play dvd
10:56:13 <timeless> ... but you can still use it as a TV
10:56:18 <timeless> ... smartphone is similar
10:56:25 <timeless> ... place a call, use it to wake up, go to web, control tv
10:56:28 <timeless> ... but still a phone
10:56:34 <timeless> ... for a car!
10:56:46 <timeless> ... you could use HMI for radio, web, phone, HVAC/ADAS
10:56:51 <Alan> s /YUR/Ludovic_Alidra/
10:56:57 <timeless> ... but you MUST be able to drive your car
10:57:04 <timeless> s/renault:/alidra:/
10:57:05 <timeless> s/renault:/alidra:/
10:57:07 <timeless> s/renault:/alidra:/
10:57:15 <timeless> [ Safety first ]
10:57:23 <timeless> renault: not specific web usage in a car
10:57:31 <timeless> ... safety is already addressed by usual embedded HMI
10:57:35 <timeless> ... driver distraction management
10:57:42 <timeless> ... design rules, human factors, for app developers
10:57:51 <timeless> ... should not distract, stress or require driver action while driving
10:57:59 <timeless> ... validation of app before deployment on the app store
10:58:12 <timeless> ... until more dynamic run-time solutions can be proven
10:58:36 <timeless> s|s /YUR/Ludovic_Alidra/||
10:58:39 <timeless> s/YUR/Ludovic_Alidra/
10:58:52 <timeless> [ Challenge - Performance ]
10:59:03 <timeless> alidra: user acceptance level
10:59:08 <timeless> ... response time requirements
10:59:17 <timeless> ... sw/hw optimizations
10:59:21 <timeless> ... high level for UX
10:59:26 <timeless> ... touch screen, speech
10:59:33 <timeless> ... animations, level of integration - feature coexistence
10:59:38 <timeless> ... native applications v. web apps
10:59:43 <timeless> ... html5 for native applications?
10:59:53 <timeless> [ Challenges - Functional API definition (1/2) ]
11:00:00 <timeless> alidra: both M2M and user-centric
11:00:08 <timeless> ... harmonized with Genivi
11:00:19 <timeless> ... API designed for:
11:00:22 <timeless> ... - performance
11:00:28 <timeless> ... - scalability and evolutivity
11:00:38 <timeless> ... low end products, high end products
11:00:48 <ito_jari> ito_jari has joined #webandauto
11:00:58 <timeless> ... probably find a common api for basic elements
11:01:09 <timeless> ... each OEM wants to bring specific innovation
11:01:17 <timeless> ... need a way to extend API
11:01:24 <timeless> ... link to native application
11:01:29 <timeless> ... listen to web audio
11:01:32 <timeless> ... want to stop radio
11:01:44 <timeless> ... if you switch to weather app
11:01:50 <timeless> ... you want to still listen to web radio
11:01:54 <timeless> ... security/privacy
11:01:58 <timeless> ... always on-line
11:02:06 <timeless> ... need strategies to manage off-line mode
11:02:26 <timeless> [ Challenges - Functional API definition (2/2) ]
11:02:31 <timeless> alidra: examples of params for api
11:02:43 <timeless> ... remain connected (social network)
11:02:48 <timeless> ... audio video
11:02:55 <timeless> ... PIM (calendar, yellow pages)
11:03:01 <timeless> ... Help (BCall, HelpCall, ...)
11:03:12 <timeless> ... -- trip and car centric
11:03:22 <timeless> ... trip optimization (traffic, parking, ...)
11:03:25 <timeless> ... multimodality
11:03:33 <timeless> ... save money (eco-driving, PAYD, ...)
11:03:37 <timeless> ... - pay as you drive
11:03:51 <timeless> ... maintenance facilities (manual, after-sales offers, ...)
11:03:59 <timeless> ... - need status of your car
11:04:09 <timeless> [ Challenges - Monetizing (1/2) ]
11:04:16 <timeless> alidra: try to monetize your services
11:04:18 <timeless> ... one for application
11:04:21 <timeless> ... another for car data
11:04:27 <timeless> ... want to build our own app store
11:04:36 <timeless> ... collect/aggregate/distribute data
11:04:47 <timeless> [ Challenges - Monetizing (2/2) -> M2M and User centric]
11:04:53 <timeless> alidra: imagine we collect data
11:04:55 <timeless> ... traffic
11:05:00 <timeless> ... - location+speed
11:05:09 <timeless> ... provide to third party/special partner
11:05:20 <timeless> ... party adds element/creates services
11:05:28 <timeless> ... send back information to Car/connected app
11:05:42 <timeless> [ Challenges - compatibility and interoperability with customer devices ]
11:05:45 <timeless> alidra: not a new issue
11:05:54 <timeless> ... had problem for years, e.g. w/ Bluetooth
11:06:02 <timeless> ... gap between consumer electronics / automotive
11:06:12 <timeless> ... users expect same services in smart phone in car
11:06:27 <timeless> ... compatibility/continuity of services
11:06:38 <timeless> ... Car could be a node in Home network (DLNA)
11:06:49 <timeless> ... Mobile devices in car
11:07:01 <timeless> ... Car could be in cloud/C2Car
11:07:07 <timeless> [ Web technologies and standards can help ]
11:07:18 <timeless> alidra: improve quality/reduce costs
11:07:28 <timeless> ... better quality for end user
11:07:29 <timeless> ... more interop
11:07:36 <timeless> ... security - well known solution
11:07:41 <timeless> ... improved platform neutrality
11:07:45 <timeless> ... OS, HW independent
11:07:49 <timeless> ... improved code reuse
11:07:59 <timeless> ... application re-use and porting to new systems
11:08:02 <timeless> [ End ]
11:08:04 <timeless> [ Applause ]
11:08:21 <timeless> ph: question... you said APIs
11:08:25 <timeless> ... have to be careful to standardize
11:08:29 <timeless> ... we want to compete on them
11:08:32 <timeless> ... to differentiate
11:08:37 <timeless> ... can you say a bit more about that?
11:08:43 <timeless> ... you have a whizbang feature in our car?
11:08:50 <timeless> ... want opportunity to expose that:?
11:08:56 <timeless> s/:?/?/
11:09:08 <timeless> ... why is that an issue?
11:09:22 <timeless> alidra: o
11:09:26 <timeless> s/o/no/
11:09:33 <timeless> ... you want examples of specific case?
11:09:42 <timeless> ... it isn't for me in this position
11:09:53 <timeless> ... if we standardize an api
11:09:57 <timeless> ... we'll have a small set
11:10:03 <timeless> ... very quickly, we'll need to add feature
11:10:25 <timeless> ph: so, it's more you want the flexibility to extend
11:10:31 <timeless> ... so you can move forward w/o waiting
11:11:11 <timeless> Josh_Soref: even at SDO slow pace, it seems we could standardize before you ship
11:11:29 <timeless> alidra: if we use a standard, we'll win at the end
11:11:36 <timeless> ... we'll reduce duration of development
11:11:44 <timeless> ... if we have our own api, we'll start to launch application
11:11:51 <timeless> ... we'll win later when it's standardized
11:11:58 <timeless> DSR: thanks
11:12:00 <timeless> [ Applause ]
11:12:50 <timeless> speiser: Sebastian Speiser
11:13:08 <timeless> ... we're not specific to cars
11:13:14 <timeless> ... we're looking at cyber physical systems
11:13:25 <timeless> ... i learned a lot of new car terms in the last days
11:13:39 <timeless> i/Speiser/Topic: [LOST]
11:13:51 <timeless> [ Motivation ]
11:14:02 <timeless> speiser: not just getting B from A
11:14:05 <timeless> ... driver has other goals
11:14:07 <timeless> [ Motivation ]
11:14:28 <timeless> speiser: doesn't have any heads up
11:14:38 <timeless> ... because he has speech and big team
11:14:47 <timeless> ...Formula 1 spends 1k USD / km
11:14:56 <timeless> ... Germany gets 30c / k,
11:14:59 <kaz> s/[LOST]/The Architecture of Future Automotive Applications based on Web Technologies/
11:14:59 <timeless> s/k,/km/
11:15:22 <timeless> ... speech recognition, virtual knowledge based integrating data from the web
11:15:28 <timeless> ... logical inferences, statistical learning
11:15:32 <timeless> [ High-level Architecture ]
11:15:42 <timeless> speiser: driver -> speech i/o
11:15:55 <timeless> ... -> memory -> Interoperation, Data I/O
11:16:11 <timeless> s|O|O, Stream I/O|
11:16:22 <timeless> ... Dataa I/O -> LOD
11:16:36 <timeless> ... Interoperation -> Logic Reasoner, Adaptive learner
11:16:55 <kaz> rrsagent, draft minutes
11:16:55 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html kaz
11:17:00 <timeless> [ Overview of Architecture ]
11:17:05 <timeless> speiser: for speech I/O
11:17:13 <timeless> ... don't want ...
11:17:21 <timeless> ... use patterns to convert text to logic
11:17:26 <timeless> ... use reasoning engine to control conversation
11:17:53 <timeless> ... using Cyc's project to link logic to language
11:17:59 <timeless> ... Stream I/O
11:18:06 <timeless> ... also web streams
11:18:11 <timeless> ... for temp/traffic
11:18:37 <timeless> [ Data I/O: Linking Open Data Cloud ]
11:18:57 <timeless> speiser: in 2006, Linked Data movement
11:19:05 <timeless> ... semantic web in W3C
11:19:13 <kaz> i/Sebastian Speiser/topic: The Architecture of Future Automotive Applications based on Web Technologies/
11:19:15 <kaz> rrsagent, draft minutes
11:19:15 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html kaz
11:19:22 <timeless> speiser: yearly growth rates of 200%
11:19:36 <timeless> ... small datasources
11:19:56 <timeless> s/sources/ statements/
11:20:08 <timeless> ... very large set of connected data sets
11:20:23 <timeless> [ Combining and using I/O channels ]
11:20:32 <timeless> [ Memory: Virtual Knowledge Base ]
11:20:41 <timeless> speiser: based on Linked Data and REST principles
11:21:04 <timeless> ... basic abstraction: a resource
11:21:09 <timeless> ... POI as 3D XML, RDF or JPEG
11:21:29 <timeless> ... resources have references (links) to other related resources, e.g., leading to the next step in a series of operations
11:21:34 <timeless> ... support standard operations: CRUD
11:22:06 <timeless> speiser: "Colosseum is in Rome"
11:22:13 <timeless> ... Create-Read-Update-Delete
11:22:38 <timeless> ... I'm not a REST-afarian
11:22:46 <timeless> ... beyond scalability
11:22:50 <timeless> ... you have standard operation
11:23:10 <timeless> ... interop is easier
11:23:16 <timeless> ... common operations
11:23:20 <timeless> ... fixed grammar
11:23:27 <timeless> ... just standardize vocabulary
11:23:31 <timeless> ... very different from WS*
11:23:39 <timeless> .. which was ported to HTTP and called REST
11:23:58 <timeless> ... You do a HTTP lookup on URI
11:24:04 <timeless> ... do it with an RDF program and get a reply
11:24:19 <kaz> s/../.../
11:24:22 <kaz> rrsagent, draft minutes
11:24:22 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html kaz
11:24:56 <timeless> [ Internlinking in Linked Data ]
11:25:12 <timeless> speiser: car:currentDriver owl:sameAs facebook:JohnDee
11:25:28 <timeless> car:car :location car:point ... wikipedia
11:25:38 <timeless> s/Internl/Interl/
11:25:45 <timeless> [ Streams, Services and Compositions ]
11:25:58 <timeless> speiser: streams either just leave http open and continue to listen
11:26:04 <timeless> ... or pull stream source regularly
11:26:14 <timeless> ... Services, to integrate w/ linked data
11:26:20 <timeless> ... how to build applications, compositions, workflows
11:26:29 <timeless> ...  based on REST resources?
11:27:10 <timeless> ... From university perspective, this is established technology
11:27:13 <timeless> [ Linked Services ]
11:27:50 <timeless> speiser: services honor REST
11:27:57 <timeless> ... we wanted to use RDF/Notation3
11:28:03 <timeless> ... relation between input and output
11:28:15 <timeless> ... linked between services, descriptions, and data input/output
11:28:38 <timeless> [ Production Rules for Linked Services ]
11:29:02 <timeless> speiser: my colleagues are presenting a paper about data driven programming for dynamic programming
11:29:16 <timeless> ... evaluate rules, if it matches,  invoke action(service)
11:29:48 <timeless> ... Locate() -> car location -> Lookup() -> list of gas stations -> navigate() -> programmed GPS system -> done
11:30:02 <timeless> ... car location -> cancel() -> new location -> done
11:30:09 <timeless> [ Conclusions ]
11:30:22 <timeless> speiser: use web tech to provide assistant system to drivers at reasonable cost
11:30:35 <timeless> ... make it cheaper by not needing so much adaption for every platform
11:30:50 <timeless> ... web tech in front end + back end, we can add new sources on demand
11:30:54 <timeless> ... PAYG integration
11:31:02 <timeless> ... no need for up front specification of services
11:31:12 <timeless> ... tap long tail of sensors and data sources
11:31:22 <timeless> [ Thank you for your attention ]
11:31:37 <timeless> speiser: have a loook at www.kskri.kit.edu + www.aifb.kit.edu
11:31:54 <timeless> ... we have a smart energy grid where we're using some of our proposed technologies
11:31:57 <timeless> [ Applause ]
11:31:59 <timeless> DSR: Questions?
11:32:10 <timeless> ... idea to combine this w/ semantic web
11:32:18 <timeless> ... what's needed to build an ecosystem?
11:32:22 <timeless> speiser: in terms of what?
11:32:31 <timeless> DSR: what's required to bring to market?
11:32:43 <timeless> speiser: dev cycle in car are rather long
11:32:58 <timeless> ... intermediate step is probably tablet/smartphone applications
11:33:03 <timeless> ... and installing this in a car
11:33:10 <timeless> ... we have cars from Daimler, Opal
11:33:40 <timeless> ... maybe a car manufacturer would be interested and take this on
11:33:44 <timeless> DSR: thank you
11:33:47 <timeless> [ Applause ]
11:34:20 <timeless> Topic: QWKKL
11:34:21 <timeless> felt: Michael Felt, German research center for AI, UI group, Automotive Group
11:34:33 <timeless> ... we're building HMIs for driver systems
11:34:38 <timeless> ... do a lot of user testing
11:34:44 <timeless> ... we do this in conjunction with OEMs
11:35:09 <kaz> s/QWKKL/Proposing a Meta-Language for Specifying Presentation Complexity in order to Support System Situation Awareness/
11:35:47 <timeless> ... this work is related to situation awareness
11:35:53 <timeless> [ Situation Awareness ]
11:36:02 <timeless> felt: knowing what's around you
11:36:06 <timeless> s/felt:/feld:/
11:36:06 <timeless> s/felt:/feld:/
11:36:20 <timeless> feld: went from psychological model
11:36:33 <timeless> ... define system situation awareness
11:36:38 <timeless> ... started with Endsley Model
11:36:47 <timeless> [ Endsley Model (original) ]
11:37:00 <timeless> feld: three levels: perception; comprehension; projection
11:37:20 <timeless> s/Felt/Feld/
11:37:26 <dsr> dsr has joined #webandauto
11:37:27 <timeless> ... i see a car
11:37:30 <timeless> ... i'm going to crash
11:37:34 <timeless> ... i need to press breaks
11:37:40 <timeless> ... there's a feedback loop
11:37:43 <timeless> ... there are task factors
11:37:50 <timeless> [ Endsley Model (adjusted) ]
11:38:10 <timeless> feld: assessment of user+context; update information sources ; impact estimation
11:38:15 <timeless> ... intelligent mediation
11:38:22 <timeless> ... HMI: presentation of information
11:38:39 <timeless> [ Two-fold Research Question ]
11:38:47 <timeless> feld: driver aspects / presentation aspects
11:38:48 <naomi> naomi has joined #webandauto
11:38:54 <timeless> ... define system situation awareness
11:39:04 <timeless> driver related concepts / presentation task annotation
11:39:10 <timeless> s/driver/... driver/
11:39:14 <timeless> ... ...
11:39:24 <timeless> [ Estimating presentation complexity ]
11:39:29 <timeless> feld: we have 3 options
11:39:34 <timeless> ... complexity from designer
11:39:38 <timeless> ... ideal case -> nothing to do
11:39:46 <timeless> ... (unlikely)
11:39:53 <timeless> ... unstructured representation of HMI
11:39:55 <timeless> ... Image
11:39:59 <timeless> ... difficult to do something
11:40:07 <W476C> W476C has joined #webandauto
11:40:14 <timeless> ... could use heuristic, approach, do image processing
11:40:17 <timeless> ... -> low confidence
11:40:28 <timeless> ... strucutred representation (HTML5)
11:40:33 <timeless> s/utr/tur/
11:40:44 <timeless> ... "ACE" (annotated complexity estimation)
11:40:54 <timeless> ... how do we annotate complexity automatically
11:40:59 <timeless> ... ACE is based on visual tree of interface
11:41:05 <maru> maru has joined #webandauto
11:41:08 <timeless> [ Example Ssreen Layout (sim TD) ]
11:41:12 <timeless> s/Ss/Sc/
11:41:23 <timeless> feld: based on a German collaboration
11:41:29 <timeless> ... German Options screen
11:41:35 <timeless> [ GUI Model and Visual Tree ]
11:41:46 <timeless> feld: from representation, we can derive visual tree
11:42:01 <timeless> [ Complexity Computation ]
11:42:08 <timeless> feld: compute it based on a table
11:42:14 <timeless> ... label, icon, panel
11:42:32 <timeless> ... we assume that if we do the right studies
11:42:41 <timeless> ... we can get a sufficiently close approximation of a good complexity
11:42:47 <bgidon> bgidon has joined #webandauto
11:43:04 <timeless> [ Presentation Meta Language ]
11:43:28 <timeless> feld: developer can specify multiple alternatives w/ different complexity
11:43:33 <timeless> ... system can choose based on situation
11:43:47 <timeless> ... we didn't want to invent a presentation language
11:43:52 <timeless> ... so we suggested a wrapper/meta language
11:44:07 <timeless> [ it isn't well formed XML either ]
11:44:27 <timeless> [ Implementation info a Dialogue Platform ]
11:44:42 <timeless> feld: SiAM dp (Situation-Aware Muiltimodal Dialogue Platform)
11:44:50 <timeless> ... based on SCXML state charts
11:45:03 <timeless> ... it can decide based on different ways to present something
11:45:12 <timeless> ... can do this online or offline
11:45:44 <timeless> feld: we can check how high/low the load is for a dialog
11:46:00 <timeless> [ Estimating (Input) Interaction Workload ]
11:46:10 <timeless> feld: we have to quantify user interaction cost as well
11:46:26 <timeless> ... break up complex tasks into atomic tasks
11:46:37 <timeless> ... rearrangement, text entry, number entry, pan/zoom, list selection, scrolling
11:46:42 <timeless> ... -> widgets
11:46:48 <timeless> ... i'll probably build a similar table
11:46:54 <timeless> ... to presentation complexity
11:47:06 <timeless> ... to know what the cost of a certain tax in a modality costs
11:47:17 <timeless> [ Two-fold Research Question ]
11:47:28 <timeless> [ Driver-related Cognitive Load Aspects ]
11:47:33 <timeless> feld: how to model cognitive load?
11:47:37 <timeless> feld: how to quantify cognitive load?
11:47:45 <timeless> feld: there's no such easy measure
11:47:53 <timeless> .. no "cpu cycles for human"
11:48:00 <timeless> s/../.../
11:48:04 <timeless> feld: hard to use time values
11:48:12 <timeless> [ Cognitive Load Model ]
11:48:22 <timeless> feld: top down view of literature concepts
11:48:28 <timeless> ... driver interacting w/ system
11:48:33 <timeless> ... demands "dry"
11:48:37 <timeless> ... specified in table
11:49:00 <timeless> ... cognitive demand
11:49:09 <timeless> ... environment/user interactions
11:49:22 <timeless> ... cause cognitive load
11:49:44 <timeless> ... assume multiple resources available to human
11:49:52 <timeless> ... possibly not completely separate
11:50:11 <timeless> ... all cognitive demands are transformed for the different processing resources
11:50:16 <timeless> ... wer have stage/dimension/code
11:50:18 <timeless> s/wer/we/
11:50:30 <timeless> ... maximum amounts of capacity differs for different people
11:50:38 <timeless> ... looking at levels of fill is the current cognitive load
11:51:05 <timeless> ... metrics can detect stress/distraction and affect load capacity
11:51:09 <timeless> [ Cognitive User Model ]
11:51:12 <timeless> feld: user
11:51:16 <timeless> ... processingresource (1...n)
11:51:19 <timeless> ... dimension
11:51:23 <timeless> ... cognitivecapcacity
11:51:29 <timeless> ... cognitivecost (1..n)
11:51:33 <timeless> s/capc/cap/
11:51:37 <timeless> ... dimensions
11:51:41 <timeless> ... interaction
11:51:45 <timeless> [ Related Efforts ]
11:51:51 <timeless> feld: two more topics
11:52:12 <timeless> [ Automotive Ontology ]
11:52:15 <timeless> feld: where do we store this
11:52:25 <timeless> ... yesterday we heard about sensors/knowledge in cars
11:52:34 <timeless> ... have to store it somewhere and make it available
11:52:39 <timeless> ... we created an ontology
11:52:45 <timeless> ... published last year on automotive ui
11:52:52 <timeless> [ High-Level Structure ]
11:52:58 <timeless> feld: from a user's perspective
11:53:16 <timeless> [ User Model ]
11:53:24 <timeless> feld: it could be worth adding user dimensions too
11:53:31 <timeless> ... our model is based around UML
11:53:40 <timeless> ... with mental state, time pressure, emotional state
11:53:45 <timeless> [ Meta Information ]
11:53:53 <timeless> feld: time, confidence, location, privacy
11:54:03 <timeless> feld: sensors are more or less accurate
11:54:40 <timeless> feld: privacy for Car-to-Car communication, what information can we share?
11:54:48 <timeless> ... location should be annotated for most values
11:54:52 <timeless> [ Driving Simulation ]
11:55:07 <timeless> feld: driving deviation
11:55:18 <timeless> ... is how do we measure cognitive load
11:55:27 <timeless> ... in European funded "Drive Home Safe"
11:55:41 <timeless> ... driving simulation connected directly to HMI
11:55:44 <timeless> ...sign on road
11:55:56 <timeless> ... trigger signs
11:56:03 <timeless> ... there's a physics engine
11:56:17 <timeless> [ Driving Performance Measures ]
11:56:24 <timeless> feld: we can derive performance metrics
11:56:34 <timeless> ... we can add further driving tasks
11:56:42 <timeless> ... different UIs require different tasks to test
11:56:48 <timeless> ... not just lane change
11:57:00 <timeless> ... we're looking into standardizing work tasks
11:57:08 <timeless> [ Traffic Light Control ]
11:57:13 <timeless> [ External Visualization ]
11:57:23 <timeless> feld: we worked w/ intervisual-computing-center
11:57:31 <timeless> ... so you can swap engine
11:57:42 <timeless> [ More Information on OpenDS ]
11:57:46 <timeless> feld: thank you for your attention
11:57:48 <timeless> [ Applause ]
11:57:58 <timeless> DSR: thank you, that was interesting
11:58:13 <timeless> ... do you think it'll be easy to provide tools for developers to test?
11:58:23 <timeless> feld: that's part of the Scion project
11:58:31 <timeless> ... it's an important point
11:58:50 <timeless> DSR: the car is trying to understand things that are coming
11:58:58 <timeless> feld: we have a knowledge base
11:59:13 <timeless> ... we're working on adaptivity strategies
11:59:36 <timeless> ... UI impls or interaction strategies
11:59:42 <timeless> DSR: have you tested with driver state?
11:59:48 <timeless> feld: we did Multimodal comparisons
11:59:51 <timeless> ... with biosensors
11:59:51 <surata> surata has joined #webandauto
11:59:55 <timeless> ... and saw effects there
12:00:11 <timeless> kaz: curious about protocol between modalities
12:00:14 <timeless> ... and SCXML
12:00:23 <timeless> ... do you usse MMLZZ
12:00:25 <timeless> s/usse/use/
12:00:38 <timeless> ... between simulator and speech and touchpanel?
12:00:51 <timeless> feld: it's a proprietary interface built into SimTD
12:01:01 <timeless> DSR: thanks so much
12:01:03 <timeless> [ Applause ]
12:01:13 <kaz> s/MMLZZ/MMI lifecycle events and EMMA?
12:01:19 <timeless> DSR: time for lunch
12:01:24 <timeless> ... until 2pm
12:01:49 <timeless> marie: there's a list of participants at the registration desk
12:01:53 <timeless> ... slides are on the web
13:04:32 <naomi> naomi has joined #webandauto
13:09:13 <Alan> scribe: Alan
13:09:42 <Alan> Adam: Our next speaker is a colleague of mine from Intel.  He has experience from Nissan,
13:09:47 <bgidon> bgidon has joined #webandauto
13:10:01 <Alan> ...I want to introduce Nobe-san from Intel
13:10:26 <maru> maru has joined #webandauto
13:10:26 <Alan> Nobe: Before March of this year I worked for Nissan and did many implementations.
13:10:43 <Alan> ...I have good experience on how ICT companies can work with auto companies.
13:11:27 <Alan> Nobe: Topic is Connected Car as a Cloud Computing Client.
13:11:42 <Alan> ...The implementation will only be for 25% or 30% of the autos.
13:11:57 <Alan> [What is a Connected Car]
13:12:20 <Alan> Nobe: There is a control area that has been implemented for 60 years.
13:12:39 <Alan> ...But there is instrumentation in the IVI that has been around since 2008.
13:12:48 <Alan> ...These have been monlithic designs.
13:13:12 <Alan> ...Smartphones have made it possible for these devices to be generic.
13:13:32 <Alan> ...Of course there should be some connection between a IVI and control areas.
13:13:49 <Alan> ...Data in Control Area should be read only.
13:14:20 <Alan> Nobe: The connection could be a smartphone or tablet inside the car.  Some kind of connection device.
13:14:46 <Alan> ...Make it easier to provide information to the driver.
13:15:00 <Alan> [slide has been built out]
13:15:37 <Alan> Nobe: Some is sensor data and some is Big Data supported by Cloud computing.
13:15:51 <Alan> [Issues to embed ICT devices in the Car]
13:16:18 <Alan> Nobe: We have to reconcile the difference in development life cycles.
13:16:23 <harukon> harukon has joined #webandauto
13:17:03 <Alan> ...Development cycle is 3 years followed by 3 years of sales.
13:17:58 <Alan> ...The average car stays in the market for 7 years after purchase.
13:18:27 <Alan> ... There is a total of 17 years that a vehicle design is current in the market.
13:19:04 <Alan> ...This is the conceptual difference between a vehicle and ICT.
13:19:45 <Alan> ...If we're going to embed a communications model that will change during the life of the car.
13:20:06 <Alan> ...Current models may be 2G based but next generation will be different.
13:20:27 <Alan> ...We need to think of what the requirements will be 7-8 years ahead.
13:21:01 <Alan> ...The example is on the MIPS performance available compared to the time.
13:21:59 <Alan> Nobe: Then we have to look at computer usage for the next 10 years in the market.
13:23:08 <bgidon> Nobe[Issues to embed ICT devices in the car ]:
13:25:08 <bgidon> [Application update will solve the problem]
13:25:43 <kaz> i/Issues to embed ICT/scribenick: bgidon/
13:25:48 <kaz> rrsagent, draft minutes
13:25:48 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html kaz
13:26:02 <Alan> scribenick: Alan
13:26:23 <Alan> Nobe: We have to update and download applications on a regular basis.
13:26:37 <Alan> ...Hardware is completed and fixed, but applications need to be updated.
13:27:14 <Alan> ...This concept is important to remember as we develop applications.
13:27:32 <Alan> [Market Penetration of NAVI: Recnet Change]
13:28:40 <Alan> Nobe: After introduction of iPhone the market acceptance has been greatly accelerated.
13:29:02 <Alan> ...Will be 1B units by 2015.
13:29:22 <Alan> [Contents and Services reside in the Cloud]
13:30:09 <Alan> Nobe: Most of the functionality supported by PCs will be supported by Smartphones.
13:30:31 <Alan> ...And the car will be connected to the Cloud via the smartphone.
13:30:43 <Alan> [Forseeing the Future Trend]
13:31:03 <Alan> Nobe: Three factors: Displays, Cloud and Smartphone.
13:31:38 <Alan> [How Smartphone connects Car with Cloud]
13:32:25 <Alan> Nobe: Smartphone migrations will change every 2 years, but the car system will be in place for 10 years or so.
13:32:44 <Alan> ...We need collaboration between the OEM and Smartphone providers.
13:32:57 <Alan> [Role of HTML5 for IVI Client]
13:34:23 <Alan> [discussion on how HTML5 and associated standards can work with car]
13:34:51 <Alan> Nobe: I think it's important that the car use HTML5 even when it doesn't have access to a server.
13:35:23 <Alan> [Use of Internet Contents using TA (2006)]
13:35:40 <Alan> Nobe: This is a little future look, but it's also what I was doing at Nissan.
13:35:51 <Alan> ...It links Semantic Web with the car.
13:36:27 <Alan> ...With the information, the vehicle may send out a request about how it can be serviced at a gas station.
13:36:45 <Alan> ...The display can show the information that's important for the vehicle.
13:37:06 <Alan> ...The navigation system should only display what's important for this vehicle.
13:37:21 <Alan> ...HTML5 should be implemented with the semantic types.
13:37:38 <Alan> ...Need the Web to support this with Web Services.
13:37:51 <Alan> ...It's been implemented and is being used in Japanese market.
13:38:05 <Alan> [TA: Telematics Agent slide]\
13:38:12 <timeless> s|\||
13:38:32 <Alan> [discussion on workflow / dataflow]
13:38:45 <rw> rw has joined #webandauto
13:38:53 <Alan> Nobe: Displays things like name of station and directions to get there.
13:39:06 <Alan> ...This was done fairly easily.
13:39:17 <Alan> ...It's a Web based implementation.
13:39:35 <Alan> [Example of Big Data Applications]
13:40:15 <Alan> Nobe: Location information is time-stamped. It can provide information on the traffic conditions.
13:40:31 <Alan> ...This kind of information can be used for traffic jam avoidance.
13:41:34 <Alan> [Crisis Response on Google Maps slide]
13:41:55 <Alan> [Possibilities to apply Big Data Analysis slide]
13:42:24 <Alan> [skipped 2 - 3 slides]
13:42:44 <Alan> [New Mobile Service Opportunities with Big Data slide]
13:43:06 <Alan> Nobe: This data could be used by other companies as made available by third party vendors.
13:43:16 <Alan> ...Could offer new products and services.
13:43:25 <Alan> [Summary slide]
13:43:37 <Alan> Nobe: Cars will be connected.
13:43:45 <Alan> ...HTML5 is the "glue"
13:44:13 <Alan> ...for OEMs the ICT implementations require horizontal collaborations
13:44:46 <Alan> [applause]
13:45:32 <Alan> Roger: Your previous employer and Toyota are both in danger of having fragmented solutions.  Are they looking to solve that in the future?
13:45:50 <Alan> Nobe: I think there are services that will be the same, but the implementations have been different.
13:46:30 <Alan> ...They need to get to a common base which would require hardware and software to be abandoned.  I think the market will drive that.
13:47:00 <Alan> dsr: You mentioned at the begining that the design of cars takes time, do you see that changing in the future?
13:47:21 <Alan> Nobe: Things are getting more modularity, and that implementation may make it quicker.
13:47:42 <Alan> ...The cycle is 3 years so you would have to change the sales cycle to match it.
13:47:48 <Alan> [Applause]
13:48:18 <timeless> scribe: timeless
13:48:40 <timeless> Topic: Acheiving a Safe and Seamless UX through accessible web apps
13:48:54 <timeless> iglesias: Alejandro Pinerio Iglesias, Igalia
13:49:14 <timeless> ... this year i started working on WebKit
13:49:18 <timeless> ... with ARIA and that stuff
13:49:22 <timeless> [ Topics ]
13:49:32 <timeless> iglesias: Acessibility-based solutions to improve safety
13:49:39 <timeless> ... implementation via accessibility APIs
13:49:44 <timeless> ... applicable standards and existing support
13:49:51 <timeless> [ Acessibility-based solutions to improve safety ]
13:49:57 <timeless> [ Safety First? ]
13:50:08 <timeless> iglesias: we have several cases of problems related to distraction and accidents
13:50:18 <timeless> ... people texting and walking have an accident
13:50:41 <timeless> ... in 2010, 3092 people killed in accidents related to distracted drivers
13:50:51 <timeless> [ Hands-Free via Speech Input ]
13:51:46 <timeless> [ Eyes-Minimal via Simplified UI ]
13:52:03 <timeless> iglesias: a minimal simplified UI
13:52:14 <timeless> ... is useful for people w/ difficulty with screen contents
13:52:28 <timeless> ... but also people who should not be distracted
13:52:33 <timeless> [ Eyes-Free via Gestures ]
13:52:47 <timeless> iglesias: users who cannot activate on-screen elements (disability)
13:52:55 <timeless> ... users who should not activate on-screen elements (driving)
13:53:14 <timeless> ... shouldn't use touchscreen while driving, shouldn't look at screen while driving
13:53:23 <timeless> ... shouldn't be distracted by complex UI
13:53:26 <timeless> [ Studies ]
13:53:40 <timeless> iglesias: driving is primarily a visual interaction w/ road
13:53:51 <timeless> [ Implementation via Accessibility APIs ]
13:53:55 <timeless> [ Accessibility APIs ]
13:54:23 <timeless> iglesias: accessibility APIs allow you to interact w/ apps programmatically on behalf of user
13:54:31 <timeless> ... use Voice/Sound
13:54:36 <timeless> [ Example: Remember the Milk ]
13:54:58 <timeless> iglesias: driver goes through an area
13:55:11 <marie> marie has joined #webandauto
13:55:21 <timeless> ... Remember The Milk has an alert for the area
13:55:22 <timeless> ... device checks speed decides it's safe to speak the alert
13:55:32 <timeless> ... driver says "No" to indicate response
13:55:36 <timeless> ... device clicks "No"
13:55:43 <timeless> [ Accessibility API Events ]
13:55:50 <timeless> iglesias: Focus changes
13:55:53 <timeless> ... selection changes
13:55:57 <timeless> ... text changes
13:55:58 <timeless> ... ...
13:56:05 <timeless> [ Accessibility API Actions ]
13:56:17 <timeless> iglesias: press, release, click, ...
13:56:23 <timeless> [ Accessibility API Interfaces ]
13:56:34 <timeless> iglesias: application, component, desktop, document, ...
13:56:40 <timeless> [ Accessibility API UCs ]
13:56:46 <timeless> iglesias: access to users with disabilities
13:56:49 <timeless> ... automated testing
13:56:52 <timeless> ... distraction-free access?
13:57:11 <timeless> ... most testing is probably Unit Testing
13:57:19 <timeless> ... but you eventually need to write Functional testing
13:57:26 <timeless> ... Accessibility is a good way to do Functional testing
13:57:39 <timeless> [ Requirements ]
13:57:49 <timeless> iglesias: developers: create accessible web apps
13:57:57 <timeless> ... layout engine implements accessibility support
13:57:58 <timeless> ... ...
13:58:07 <timeless> [ For Web Application Developers ]
13:58:15 <timeless> iglesias: W3C Mobile Web Initiative
13:58:19 <timeless> ... Best Practices
13:58:21 <timeless> ... ...
13:58:27 <timeless> [ For Web Application Developers ]
13:58:37 <timeless> iglesias: W3C Web Accessibility Initiative (WAI)
13:58:47 <timeless> ... Accessibility Overview
13:58:50 <timeless> ... Guidelines
13:58:52 <timeless> ... ARIA
13:58:58 <timeless> [ For Web Application Developers ]
13:59:08 <timeless> [ Layout Engines Supporting ARIA ]
13:59:10 <timeless> iglesias: Trident
13:59:12 <timeless> ... WebKit
13:59:14 <timeless> ... Gecko
13:59:15 <timeless> ... Presto
13:59:24 <timeless> ... Trident = IE
13:59:29 <timeless> ... WebKit = most others
13:59:32 <timeless> ... Gecko = Firefox
13:59:37 <timeless> ... Presto = Opera
13:59:47 <timeless> [ WebKit: Free as in Freedom ]
13:59:57 <timeless> [ WebKit: Embedded-Friendly ]
14:00:05 <timeless> iglesias: Desktop (Safari, Chromium, Epiphany, )
14:00:12 <timeless> ... iPad, iPod, iPhone, ...
14:00:13 <timeless> ...
14:00:19 <timeless> s/.../... .../
14:00:34 <timeless> [ WebKit: Developer Community ]
14:00:45 <timeless> iglesias: it's hard to quantify people
14:01:04 <timeless> ... there's chromium, apple, webkit, google, igalia, gmail, nokia, openbossa, samsunbg, rim, others
14:01:12 <timeless> [ WebKit: Accessibility ]
14:01:17 <timeless> iglesias: mature, platform-independent
14:01:24 <timeless> ... adaptations for each platform/port
14:01:34 <timeless> ... Macintosh, Chromium, GTK <- mature
14:01:41 <timeless> ... EFL, Qt, Win <- less mature
14:02:07 <timeless> [ The Indie UI WG ]
14:02:19 <timeless> iglesias: Accessibility/Automotive have the same targets
14:02:27 <timeless> ... they're working separately
14:02:47 <timeless> [ Indie UI WG Members]
14:02:56 <timeless> iglesias: access, apple, google, nokia, ...
14:03:01 <timeless> ... but no automotive members
14:03:05 <timeless> [ Summary ]
14:03:18 <timeless> iglesias: in-vehicle applications can be used more safely via alternative input/output
14:03:36 <timeless> ... quite similar to assistive technologies
14:03:51 <timeless> ... accessibility APIs are standards for accessible web applications, established, used
14:04:02 <timeless> ... automotive industry should evaluate this solution
14:04:11 <timeless> s/nokia/nokia, opera/
14:04:37 <timeless> ... - the need relating to alternative input/output
14:04:48 <timeless> ... is where the accessibility projects have been talking for years
14:04:52 <timeless> [ Questions? ]
14:05:03 <timeless> [ Applause ]
14:05:29 <timeless> DSR: cars have a rich set of UI possibilities
14:05:37 <timeless> ... i don't know how wide the range of the INDIE scope is
14:05:46 <timeless> ... headsup-displays, spatial audio? tactic?
14:05:53 <timeless> ... multidevice things
14:06:42 <timeless> iglesias: they need text input
14:06:45 <timeless> ... they need text output
14:06:56 <timeless> ... screens with icons
14:07:02 <timeless> ... this isn't acceptible in HMI
14:07:07 <timeless> ... for an accessible interface
14:07:48 <timeless> kaz: there was discussion at Indie UI during TPAC for UCs
14:07:58 <timeless> ... i was wondering if you're interesting in giving feedback about feedback
14:08:01 <timeless> ... from ecosystems
14:08:05 <timeless> ... to the Indie group
14:08:31 <timeless> iglesias: iPhone uses "Voice-over"
14:08:34 <timeless> ... they rely on gestures
14:09:04 <timeless> Adam: thanks iglesias
14:09:06 <timeless> [ Applause ]
14:09:49 <timeless> Topic: The Connected Car-Changing Business Models for Automotive
14:09:57 <timeless> delaney: Chris Delaney, CSC
14:10:01 <kaz> s/interesting in/interested in/
14:10:03 <timeless> ... a colleague put together a position paper
14:10:15 <timeless> ... i changed our presentation
14:10:21 <timeless> ... to talk about sales and deriving value
14:10:24 <timeless> [ Agenda ]
14:10:30 <timeless> delaney: Driving in the Cloud
14:10:35 <timeless> ... impact of HTML5 on IVI
14:10:42 <timeless> ... new technologies, new business models
14:10:47 <timeless> ... streamlining sales process
14:10:52 <timeless> ... delivering a customer for life
14:10:56 <timeless> ... vision of the future
14:11:06 <timeless> [ Driving in the Cloud ]
14:11:15 <timeless> delaney: left, what happens when you're building a car
14:11:22 <timeless> ... right, what happens after you've sold the car
14:11:44 <timeless> ... often there's no interaction between seller and buyer for 5 years
14:12:01 <timeless> [ Impact of HTML5 on IVI ]
14:12:11 <timeless> [ new technologies, new business models ]
14:12:21 <timeless> delaney: streamlining sales process; engage w/ customers
14:12:36 <timeless> ... buy something from Amazon, very streamlined, simple process
14:12:43 <timeless> ... buying houses hasn't changed in years
14:12:46 <timeless> ... same for cars
14:13:00 <timeless> ... enable customers to customize product on the fly
14:13:05 <timeless> ... enable fast delivery
14:13:12 <timeless> ... let customers know where the car is
14:13:29 <timeless> ... integrating Facebook w/ Salesforce, SAP
14:13:39 <timeless> ... deliver a customer for life
14:13:48 <timeless> ... deal w/ them on an ongoing basis
14:14:16 <timeless> ... McKinsey: most companies have improved productivity and operations, but not sales
14:14:32 <timeless> [ Pending Business Model Transformation ]
14:14:37 <timeless> delaney: Spotify fans?
14:14:42 <timeless> ... much more advanced than CDs
14:14:48 <timeless> ... subscription model v. purchasing car
14:14:51 <timeless> s/car/model/
14:15:04 <timeless> ... discussed Zip cars in SF, CA, US over lunch a few days ago
14:15:10 <timeless> ... renting cars instead of buying
14:15:25 <timeless> [ streamlining sales process ]
14:15:29 <timeless> [ current sales process ]
14:15:36 <timeless> delaney: you can go on internet, do research
14:15:44 <timeless> ... there may be a car configurator, In Flash
14:15:49 <timeless> ... maybe you can book a test drive
14:15:56 <timeless> ... for further info, contact dealer
14:16:06 <timeless> ... backwards/forwards negotiation
14:16:13 <timeless> ... not like Amazon
14:16:25 <timeless> [ Engage with customers: Seamless customer for life Communication ]
14:16:47 <timeless> delaney: encourage customers to return to OEM for everything
14:16:52 <timeless> [ Demo Scenarios ]
14:16:58 <timeless> delaney: 1 - Purchase Process
14:17:03 <timeless> ... 2 - In Life Management
14:17:08 <timeless> delaney: the idea is to generate discussion
14:18:02 <timeless> [ Potential Customer Interested in Honda - Likes Honda Facebook Page ]
14:18:06 <timeless> delaney: customer likes facebook page
14:18:13 <timeless> ... could have a lead in salesforce
14:18:16 <timeless> ... have 1-1 dialog
14:18:29 <timeless> [ Customer Downloads Honda App ]
14:18:34 <naomi> naomi has joined #webandauto
14:18:37 <timeless> delaney: encourage users to download it
14:19:03 <timeless> ... through iTunes store/etc.
14:19:04 <timeless> [ App Integrated with Facebook ]
14:19:15 <timeless> delaney: viewed at home through your iPad
14:19:24 <timeless> [ App start-up ]
14:19:36 <naomi_> naomi_ has joined #webandauto
14:19:36 <timeless> delaney: find showrooms, book testdrive, etc.
14:19:45 <timeless> [ Customer Books Test Drive at Local Dealer Using App ]
14:19:57 <timeless> delaney: pick model, pick date and time, confirms details, confirmation
14:20:07 <timeless> [ Customer Checks Availability of Models of Interest ]
14:20:13 <timeless> delaney: integrate model info w/ SAP data
14:20:39 <timeless> ... maybe OEM is willing to do a deal with a unit in a different location
14:20:49 <timeless> [ Customer Configuring New Car ]
14:20:55 <timeless> delaney: this is just reusing content from web
14:20:59 <timeless> [ Stock data ]
14:21:02 <timeless> delaney: pulling data from SAP
14:21:19 <timeless> [ Payment Options - Buy Now (Cash) or Finance ]
14:21:30 <timeless> delaney: go through buying process through app
14:21:37 <timeless> ... credit checks, finance - online
14:21:42 <timeless> ... give feedback on process
14:21:48 <timeless> [ A New Honda Advocate ]
14:21:57 <timeless> delaney: then you can post to Facebook
14:22:05 <timeless> ... great free advertising
14:22:17 <timeless> ... @home, i'll look at reviews on Amazon
14:22:27 <timeless> ... how do we leverage the power of social?
14:22:38 <timeless> [ Secario 2 - In Life Management - My Honda ]
14:22:41 <timeless> delaney: they bought car
14:22:48 <timeless> ... find out about servicing, hooked up to telematics
14:22:52 <timeless> ... you need to change oil
14:22:54 <timeless> ... special offers
14:22:59 <timeless> ... make it useful
14:23:03 <timeless> ... they don't want spam
14:23:08 <kaz> s/Secario/Scenario/
14:23:11 <timeless> ... if it's targeted, thought about, a value to consumer, no problem
14:23:22 <timeless> [ Promotions and Special OFfers ]
14:23:27 <timeless> s/OFf/Off/
14:23:34 <timeless> delaney: that top part is from Salesforce
14:23:41 <timeless> [ Customer Details Shown in SFDC ]
14:23:50 <timeless> [ A vision of the future ]
14:24:04 <timeless> delaney: HTML5 is what our app was based on
14:24:08 <timeless> ... communicate 1-1 w/ customers
14:24:20 <timeless> ... OEMs say they don't know much once it's sold
14:24:28 <timeless> ... having them come back for servicing/other products...
14:24:35 <timeless> ... Zip-car, where people rent the car
14:24:42 <timeless> ... there's an opportunity to communicate more often
14:25:10 <timeless> delaney: this applies to a wide range of manufacturers
14:25:16 <harukon> harukon has joined #webandauto
14:25:20 <timeless> ... in UK, the decline of High Street stores
14:25:34 <timeless> ... producer manufacturer to customer relationship gets stronger
14:25:44 <timeless> [ Questions ]
14:25:46 <timeless> [ Applause ]
14:26:10 <timeless> bbb: from your PoV
14:26:23 <timeless> ... what kind of standardization is needed for Automotive?
14:26:24 <naomi_> s/bbb/takahashi/
14:26:31 <timeless> delaney: this can be done through a wide variety
14:26:37 <timeless> ... the honda app was built using HTML5
14:26:43 <timeless> ... it could be built w/ anything
14:26:54 <timeless> ... Facebook - Salesforce integration is very good
14:27:12 <timeless> Adam: thanks delaney
14:27:15 <timeless> [ Applause ]
14:28:37 <projector> projector has joined #webandauto
14:52:44 <xx> xx has joined #webandauto
15:01:23 <Alan> PH: Expect preliminary results of this soon.
15:01:34 <Alan> ...We expect to continue this conversation.
15:01:53 <Alan> ...Outline of what we heard and why W3C is the place to work.
15:01:59 <timeless> i/PH:/scribenick: Alan/
15:02:07 <Alan> ...Also why Standardization works well.
15:02:25 <Alan> [Motivation for Web Technology slide]
15:02:39 <Alan> PH: Seens strategic for industry, there are demands and expectations.
15:03:24 <Alan> ...There is demand there.  We need to build an ecosystem of developers.
15:03:38 <naomi> naomi has joined #webandauto
15:03:45 <Alan> ...There isn't a huge market per OEM, but need to build industry demand.
15:04:10 <Alan> ...Are there other things missing?
15:04:44 <Alan> DanA: In addition to work at W3C there is lots of other work being done.  Can W3C serve a role to harmonize these efforts globally.
15:05:06 <Alan> [Motivation for W3C slide]
15:05:25 <Alan> PH: Historically there is a problem in getting the community together.
15:05:34 <Alan> ...Developers are watching what W3C does.
15:05:55 <Alan> ...And W3C standards are Royalty-Free that makes them easy to implement.
15:06:17 <Alan> ...Maybe I missed some, if you have other motivations, let me know.
15:06:25 <Alan> [crickets]
15:07:12 <Alan> SSSS: We heard about connectivity to the cloud.  We hear W3C sits there.  That might be another motivation.
15:07:35 <Alan> [Standardisation: How does it work Well? slide]
15:07:59 <Alan> s/SSSS/Boris/
15:08:48 <Alan> [Prioritize Work Items]
15:09:03 <Alan> PH: I try to collect work items from the audience.
15:09:23 <Alan> ...The idea is that people say what are the things W3C should work on.
15:09:35 <Alan> ...I'm personally interested in the vehicle APIs.
15:09:58 <Alan> ...But it would be good to hear from attendees what they want and some reasons why.
15:10:10 <Alan> ...This is preliminary but it gives us a feel for what was represented.
15:10:43 <Alan> gryc: By end-to-end you mean telematics?
15:10:59 <Alan> PH: I heard someone say it, I just wrote it down.
15:11:29 <Alan> gryc: The first five that are on your list are of interest to me.
15:11:41 <Alan> PH: OK - we'll move those to the list.
15:12:33 <kaz> s/end-to-end/M2M/
15:12:52 <Alan> gryc: I would define user-centric as a use case dealing with the driver or passenger.  M2M is vehicle data for things like insurance / fleet maintenance, etc.
15:13:06 <Alan> ...Could be anything you would use to design an API.
15:13:29 <Alan> xxxxx: So entertainment API would be part of that as well.
15:13:55 <kaz> s/xxxxx/boris/
15:14:13 <Alan> hrbysh: I think connection in vehicle.  We have to connect head unit and smart pohen.
15:14:24 <naomi> naomi has joined #webandauto
15:14:41 <Alan> gryc: If you consider that to be a user-centric device then I would say yes.
15:15:08 <Alan> ...I don't think those names are what we would standardize on, we'll end up with sublists.
15:15:22 <kaz> s/hrbysh/hirabayashi/
15:15:26 <Alan> ...Something like device-focused APIs are underneath that category as well.
15:15:34 <kaz> s/pohen/phone/
15:15:42 <Alan> PH: So device centric is interfacing smart phone.
15:16:00 <Alan> wwwww: So I think we need to think cross platform.
15:16:08 <naomi> s/wwww/matias/
15:16:14 <Alan> ....How to integrate the HMI.
15:16:22 <Alan> ...Having something on top of HTML5.
15:16:39 <Alan> dsr: Was this something we heard earlier about application portability>
15:17:30 <Alan> pavel: I think we should take out API.  I think there are things deeper than that.
15:17:43 <Alan> ...We might not want to partition APIs this way.
15:17:55 <Alan> ...There might be overlapping APIs in the categories.
15:18:04 <Alan> ...We probably don't know details today.
15:18:26 <Alan> ...I would not say the APIs will need to be partioned the way of Use Cases.
15:19:10 <Alan> gryc: To me that makes sense.  In terms of strictly bidding them, from an application point of view, they might overlap.  We have a virtual mechanic app like that.
15:19:23 <Alan> ...I'm willing to wait until a later time to categorize them.
15:19:55 <Alan> 22222: Seeing the list and the concepts.  I think people maynot be on the same page.
15:20:17 <Alan> ...Perhaps we develop an abstract reference model where you can put concepts and APIs in the same picture.
15:20:26 <Alan> ...It might facilitate discussion.
15:20:49 <Alan> 333333: Some of the speakers talked about ecosystems.
15:21:01 <Alan> ...Right now we don't have any energy for ecosystems.
15:21:02 <naomi> s/333333/kazuhiro/
15:21:14 <Alan> ...W3C might help build that and make it happen.
15:21:33 <kaz> s/22222:/magnus:/
15:22:09 <Alan> Roberto: The way we follow it in Genivi is we list the Use Cases etc. across competitive things.  Many companies are uncomfortable with such discussions.
15:22:40 <Alan> ...Trying to see what's available on the car and putting together networks that are available, then putting APIs that are available for building apps.
15:22:54 <Alan> ...This is a different approach but it has delivered results for us.
15:23:13 <Alan> PH: I share your opinion and approach, but others feel it's important.
15:23:44 <Alan> woochul: We need to figure out what's needed as automotive API.  What's missing, what's reusable.
15:24:04 <Alan> PH: That sounds like gap analysis.  Think Vodaphone took a shot at that.
15:24:49 <Alan> mikko: I think looking at the board, we have priorities to discuss.  If you have different applications running how do you prioritize them.
15:24:59 <Alan> ...That should be included in here.
15:25:00 <naomi> s/mikko/magnus/
15:25:14 <naomi> Magnus Gunnarsson, Mitsubishi
15:25:23 <Alan> dsr: I think that's what context is.  Based on teh situation, what's the priority.
15:25:51 <Alan> magnus: I also think we should consider how to create a developer society so tooling might be an important part of this.
15:26:03 <Alan> PH: What do you mean by tooling?
15:26:35 <Alan> magnus: Provide guidance on how people can build things without an actual car.
15:26:41 <Alan> ...Maybe best practices.
15:27:04 <Alan> 44444: I was going to mention best practices as well.
15:27:30 <Alan> 666666: I think we should mention something about long life cycles and synchronization as well.
15:27:43 <naomi> s/666666/Mayer/
15:28:16 <Alan> zzzzz: When it comes to lifecycles and such I think OMA is doing work there so we should work with them.
15:28:47 <Alan> xxxxxxx: I'm still not sure of what level of API we should consider.
15:28:59 <naomi> s/xxxxxxx/woochul/
15:29:14 <Alan> ...Low-level API could be hard as each car manufacturer has it's own implemnetation.
15:29:23 <Alan> ...An extraction layer would be easier.
15:29:33 <Alan> ...I'd like to know how to work on such issues.
15:29:49 <Alan> PH: We can put up both topics and see where they prioritize.
15:30:34 <Alan> Josh_Soref: I think we should look at both and then figure out who will work on which ones and have people focus on the Use Cases they could implement around them.
15:30:56 <Alan> PH: Should we get a show of hands on the topics?  I would ask that you only vote 3 times.
15:31:08 <Alan> ...Will do next round probably through an online questionaire.
15:31:19 <Alan> [Voting by topic]
15:31:49 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html Alan
15:32:24 <timeless> s/look at both/look at both (where individual vendors work with a few 2nd parties to play with low level apis to see what kind of apps they can build to generate future high level UCs)/
15:36:28 <Alan> PH: The votes are in, thanks very much, we'll publish this and see what people what to focus on.
15:36:45 <Alan> [How to get Started? slide}
15:37:04 <Alan> PH: W3C submission from a set of members.
15:37:20 <Alan> ...We do Working Groups which is where we do the body of our work.
15:37:32 <Alan> ...Where requirements arse done and work is created.
15:37:50 <Alan> ...Liaisons with other groups.
15:37:59 <Alan> ..And it's member only work.
15:38:28 <Alan> PH: An intermediate step we've introduced is Busienss Groups which doesn't normally develop standards.
15:38:46 <Alan> ...It is designed to work with other groups to figure out what to do next.
15:39:10 <Alan> ...Just wanted to give you this overview and have you think about it as the way forward.
15:39:34 <Alan> PH: Wrapping up I'd like to thank Intel, and to our Sponsors QNX and Webinos project.
15:39:36 <harukon> harukon has joined #webandauto
15:39:40 <Alan> [big applause]
15:40:12 <Alan> [adjourned!]
15:40:27 <timeless> i/adjourned/and to the scribes/
15:40:34 <timeless> i/adjourned/[big applause]/
15:40:38 <timeless> s/inserted/scribe/
15:40:39 <timeless> s/inserted/scribe/
15:40:46 <Alan> rrsagent, draft minutes
15:40:46 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/15-webandauto-minutes.html Alan
15:41:41 <timeless> s/}//
15:42:04 <timeless> s/and/marie: and
15:57:18 <timeless> RRSAgent, bye
15:57:18 <RRSAgent> I see no action items