Minutes of the June 13, 2016 MMI Working Group call

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Minutes of the June 13, 2016 MMI Working Group call

Deborah Dahl
Today we continued the discussion that we started last week with Dr. Dirk Schnelle-Walka, Harman International, Connected Car Division, on his earlier comments [1] on the use case wiki[2].
This week we focused on the horizontal issues of security, privacy, accessibility and safety, and we also discussed UC-12 “Smart Car Platform” [3].
[1] comments:
[2] use cases: https://www.w3.org/wiki/MMI/Use_Cases_Categorized 



[3] Smart Car Platform: https://www.w3.org/wiki/MMI/Use_Cases_Categorized#UC-12:_Smart_Car_Platform





and below as text




      [1] http://www.w3.org/


                               - DRAFT -


          Multimodal Interaction Working Group Teleconference

                              13 Jun 2016


   See also: [2]IRC log


      [2] http://www.w3.org/2016/06/13-multimodal-irc





          Debbie, Kaz, Dirk













     * [3]Topics

         1. [4]actions

         2. [5]use case wiki

     * [6]Summary of Action Items

     * [7]Summary of Resolutions



   <scribe> scribe: ddahl






   <trackbot> action-441 -- Kazuyuki Ashimura to Submit bullet

   points on mmi to the wot landscape document on github -- due

   2016-06-13 -- OPEN





      [8] https://www.w3.org/2002/mmi/Group/track/actions/441


   kaz: will do that today


use case wiki


   <kaz> [9]Use Case wiki


      [9] https://www.w3.org/wiki/MMI/Use_Cases_Categorized


   debbie: last week we talked about UC-7





     [10] https://www.w3.org/wiki/MMI/Use_Cases_Categorized#UC-7:_Multimodal_Appliances


   kaz: last week we talked about security and privacy in WoT, we

   should talk about that for mmi interaction with appliances


   dirk: for home appliances?


   kaz: during the panel session we talked about user

   authentication, device authentication, physical danger and



   <kaz> [11]WoT Security panel session during the W3C/Keio 20th



     [11] https://www.w3.org/2016/Talks/0609-wot-panel-ka/


   dirk: we also talked about privacy issues in the SCXML paper,

   authentication was fine, but can become complex if you want to

   hide part of a screen from someone who's watching, for example


   kaz: Javascript with HTML5 isn't sufficient, need something

  like SCXML


   <kaz> [12]p11


     [12] https://www.w3.org/2016/Talks/0609-wot-panel-ka/#%2811%29


   (kaz discusses slides)


   <kaz> fyi, this is the link to the Keio 20th anniversary event:



     [13] https://www.w3.org/20/Asia/Japan/Overview.html


   debbie: safety would be especially important for people with


   ... it might be extremely important for them to access their

   home devices


   kaz: accessibility will go beyond making the web usable

   ... we need to think about that kind of relationship if

   everything is connected


   Dirk: what does this mean from an architectural point of view?

   ... in our system we targeted older people, some with

   disabilities, we addressed this with fusion and fission

   ... using modalities as appropriate


   kaz: making the system easier to access for people with

   disabilities should not make it easy for evil people to access


   debbie: should we add anything to UC-7

   ... we could add something to the template


   kaz: add a section 3 covering security, accessibility and

   safety and also add something for each use cases

   ... and add something to the template


   Dirk: in our project the security people suggested XACML,

   standardized by Oasis

   ... it allows for fine-grained permissions

   ... Extensible Access Control Markup Language





     [14] https://www.w3.org/wiki/MMI/Use_Cases_Categorized#UC-12:_Smart_Car_Platform


   debbie: this was Dirk's other comment


   kaz: during the Automotive Workshop 4 years ago, Audi was using

   SCXML, but not MMI Architecture


   Dirk: in last year's SCXML workshop there were participants

   from auto industry, but there isn't a good editor

   ... for visualizing

   ... so they were reluctant to use

   ... there was a good editor from NVIDIA presented at the

   workshop two years ago


   kaz: a UML editor should be able to generate SCXML code


   <Dirk> NVidia SCXML Editor:




     [15] http://scxmlworkshop.de/eics2014/submissions/Developing%20User%20Interfaces%20using%20SCXML%20Statecharts.pdf


   <kaz> [16]visual paradigm


     [16] https://www.visual-paradigm.com/tutorials/state-code-gen.jsp


   Dirk: this is a UML editor


   kaz: that you can save as SCXML code


   Dirk: an integration into a UML tool would help a lot


   <kaz> [17]UML tools for Linux


     [17] http://www.zipcon.net/~swhite/docs/computers/linux/UML_Tools.html


   Dirk: automotive use cases are navigation, entertainment,


   ... there is an open source approach for automotive


   kaz: GENIVI, Generic In Vehicle Infotainment

   ... for GUI part they use Qt

   ... probably some are using Linux-based system

   ... a few years ago, the alternatives were embedded C++ or

   HTML5, but now some people are thinking of MMI Architecture


   Dirk: this would be a good alternative to just attaching


   ... without a good integration of modalities

   ... we could explore how MMI can assist in the integration of



   kaz: we can add or detach a modality at any point


   debbie: we can add the automotive discussion from today to



Summary of Action Items


Summary of Resolutions


   [End of minutes]