<scribe> scribenick: kaz

actions

<ddahl> actions https://www.w3.org/2002/mmi/Group/track/actions/open

<ddahl> action 454?

<ddahl> action-454?

<trackbot> action-454 -- Deborah Dahl to Turn bullet list into text -- due 2016-09-05 -- OPEN

ddahl: I'm behind...

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

action-457?

<trackbot> action-457 -- Kazuyuki Ashimura to Make a strawman/template diagram for relationships between entities in a use case -- due 2016-10-10 -- OPEN

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

-> https://github.com/w3c/mmi/blob/gh-pages/usecases/images/drawing.svg basic template of entity relationship

kaz: we can use this as the template for entity relationship

dahl: wondering about the interaction between the visitor and the exhibit

kaz: possibly touch the exhibit

dahl: also ask questions and it starts talking

<ddahl> labels for arcs might be "touch" or "information about exhibit"?

kaz: good question
... could include both properties and actions

ddahl: the visitor could be a student
... and can add labels for arcs

<ddahl> should the use cases provide labels for the arcs?

kaz: yes

<ddahl> we aren't too interested in the interactions between people

kaz: and Entity 2 could be an official at the reception desk

(change the order later)

scribe: so Entity 2 should be a guide terminal device or kiosk

ddahl: ok
... and each use case should have this kind of diagram?

kaz: yes
... I'll add this image to the Overview.html
... and all the assigned use case editors should add this kind of diagrams to his/her use cases

action-458?

<trackbot> action-458 -- B Helena RODRIGUEZ to Send wot person our vocabulary to get his comments and then we can reconcile our work with their work -- due 2016-10-24 -- OPEN

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

kaz: Helena did add a subdirectory

ddahl: would be better to have some description on the tool

<ddahl> close action-462

<trackbot> Closed action-462.

-> https://github.com/w3c/mmi/tree/gh-pages/lib Helena's tools

action-463?

<trackbot> action-463 -- Kazuyuki Ashimura to Talk with johannes about a good time for an mmi/wot call, possibly during scripting time slot -- due 2016-11-28 -- OPEN

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

kaz: we've just done that

<ddahl> close action-463

<trackbot> Closed action-463.

kaz: and the conclusion from the WoT Scripting call today was bringing this to the WoT IG main call
... possibly on Wednesday, Dec. 14

ddahl: can send a link to the list
... other than the MMI Architecture spec, what would be good to be sent?

kaz: the MMI Interoperability Test Note

ddahl: and your diagram?

kaz: ok

ddahl: and my demo

kaz: and maybe Dirk also might want to send his demo and/or paper

ddahl: good idea

<ddahl> action-464?

<trackbot> action-464 -- Kazuyuki Ashimura to Write more about uc-7 -- due 2016-11-28 -- OPEN

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

kaz: not yet

charter

kaz: what should be the deliverables for the next period
... given the discussion with the WoT IG, maybe it would make sense to have a best practice doc or a guideline on bridging WoT and MMI
... and how should we handle EMMA 2.0 and MMI MC Discovery/Registration?

ddahl: the biggest thing for EMMA 2.0 is that it's a JSON version
... we sort of promised we would do that
... and we need Helena for Discovery/Registration discussion
... have not reviewed Dirk's comment yet

kaz: shall we skim that?

ddahl: we can look at that

-> https://lists.w3.org/Archives/Public/www-multimodal/2016Nov/0003.html Dirk's comments

ddahl: the comments on abstract, status, etc., are editorial

-> https://lists.w3.org/Archives/Public/www-multimodal/2016Nov/0005.html Dirk's comments on section 4

kaz: the question on "MMI framework vs MMI Architecture" is interesting

ddahl: we don't want to make the framework a standard
... all the comments look nice
... asking for good clarifications

kaz: we should talk with Dirk and Helena about this in detail during the next call

ddahl: ok

Use cases

-> https://w3c.github.io/mmi/usecases/Overview.html Use Case doc

kaz: should we add the relationship diagram to all the use cases before publishing?

ddahl: don't think so
... maybe we could remove "museum" specific points from the template and make it completely diagram

kaz: +1
... and we should change the diagram template as well
... e.g., from concrete value to "property 1", etc.

ddahl: yes
... and for the UC-7, the concrete entity might be a rice cooker and an air conditioner

kaz: right

ddahl: and maybe there is a home portal

<ddahl> the user, vendor

kaz: so Things and Stakeholders

ddahl: child vs adult is important to distinguish who can deal with the device

kaz: yes
... we might need some kind of authentication, e.g., based on age

ddahl: yes
... if there is an instanciated version of the template, e.g., for the appliance use case, it would be useful for people

kaz: +1

ddahl: which tool to use? would Inkscape be OK?
... SVG is great but if it's difficult for somebody to generate SVG, an image file would be also OK

<ddahl> yEd is a good editing tool that can export SVG

kaz: can try it if there is a Linux version

(and there is a Linux version :)

[ adjourned ]