<scribe> scribe: ddahl

actions

action-443?

<trackbot> action-443 -- B Helena RODRIGUEZ to Write up the use case of millions of images from tpac and send to the group list -- due 2016-06-27 -- OPEN

<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/443

helena: didn't have time to do that
... will do that in the next two weeks

action-444

<trackbot> action-444 -- B Helena RODRIGUEZ to Revise the vocabulary document with a new description -- due 2016-06-27 -- OPEN

<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/444

helena: did that

<helena> http://w3c.github.io/mmi-discovery/vocabulary.html

close action-444

<trackbot> Closed action-444.

action-445?

<trackbot> action-445 -- B Helena RODRIGUEZ to Update vocabulary document in github -- due 2016-06-27 -- OPEN

<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/445

helena: did that

close action-445

<trackbot> Closed action-445.

action-446?

<trackbot> action-446 -- Deborah Dahl to Review updated vocabulary document -- due 2016-06-27 -- OPEN

<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/446

debbie: will do that this week

action-447?

<trackbot> action-447 -- Kazuyuki Ashimura to Review updated vocabulary -- due 2016-06-27 -- OPEN

<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/447

kaz: will do that this week

action-448?

<trackbot> action-448 -- Deborah Dahl to Check on status of apa review of state management -- due 2016-06-27 -- OPEN

<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/448

debbie: not due until October
... should we try to get them to do that a little sooner?

helena: they should do that sooner

debbie: it would be good to discuss at TPAC

close action-448

<trackbot> Closed action-448.

action-449?

<trackbot> action-449 -- Kazuyuki Ashimura to Send cleaned-up diagrams to the list -- due 2016-06-30 -- OPEN

<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/449

kaz: will do within 5 minutes

close action-449

<trackbot> Closed action-449.

use case wiki

debbie: look at automotive use case

dirk: to be successful we need to extend GENIVI to be able to interact with MMI Architecture

<kaz> use case wiki

dirk: has a diagram, will share screens
... IM in the business logic layer takes care of orchestration
... FRANCA is a common API, MMI could go over this
... could we have multiple transport layers
... FRANCA could transport MMI events, in the car they use D-bus

kaz: working for the automotive WG, have been talking with Genivi people, now they're interested in
... web socket interface

dirk: can add MMI to Genivi without changing it
... can send these slides to the public list

<kaz> kaz: mentions there will be a f2f meeting of the automotive wg in portland in july

<kaz> ... would be great if I could refer to these slides there

debbie: could the boxes be seen as modality components?

dirk: yes, in some cases they are MC's, like speech, but in other cases they could be mapped to MC's, like tuner
... none of them seem to raise any issues for the MMI Architecture
... there are some concurrency issues, like muting audio while a phone call is going on
... could use Pause events or something like that

debbie: what are the protocols?

dirk: relying on FRANCA, the common API
... seems to be a nice fit
... some automotive vendors use state-based systems for business logic, not necessarily SCXML
... I think this could be done by SCXML

debbie: the low level layers are common resources for the components?

dirk: yes, low level services

kaz: this libraries are written in C/C++?

dirk: yes

debbie: implementations?

dirk: there is an implementation that can be downloaded
... everyone has to think about how to handle speech, touch input, etc. it would be great to show that the MMI Architecture can be used to integrate it

kaz: I like this diagram because it's focused on services, not devices

debbie: is there any scope for Discovery?

dirk: people plug in their devices and establish a connection, not sure how this is discovered, or what if you have more than one phone
... discovering which services the phones provide, contacts, messaging services, basically discovering the capabilities of attached devices

helena: was also wondering about discovery -- what if there are a lot of people in the car with tablets and phones?
... there's a lot of work to do there?
... what if I don't have an HTML5 GUI

dirk: this is based on a QT GUI

debbie: you can't say that only the driver can connect to the car, because a passenger might have music
... that everyone wants to hear

dirk: or sometimes you don't want everyone in the car to hear your music

kaz: you also don't want people outside the car to access your music

helena: what about something like a bus? Usually automotive is focused on car

dirk: buses are more complicated
... sometimes the bus provides wireless access

kaz: the W3C Vehicle API just handles cars (not buses), max of 9 seats

debbie: have people talked about moving a session to a different car?

dirk: you could use your phone to retain the state between cars

kaz: the car should be able to identify multiple users. maybe both the car IVI and the user's smartphone need to have several profiles for that purpose.

debbie: in a rental car you don't want the previous renters to still be able to interact with the car

dirk: the profiles need to be able to be forgotten
... the MMI Architecture doesn't support user profiles

debbie: should we add user profiles to the wiki

kaz: for security, privacy

dirk: agreed