See also: IRC log
<ddahl> 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
ddahl: kind of old action
... do you still want to finish that?
helena: working with github
... not sure if the CMS works
... taking the action items in order
ddahl: checking in something?
helena: yes
... another question about the table for use case
description
ddahl: we had another action item
about the use case template, action-457
... that would address the question
... regarding action-443 itself, you're working on that?
helena: yes
<ddahl> action-454?
<trackbot> action-454 -- Deborah Dahl to Turn bullet list into text -- due 2016-09-05 -- OPEN
<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/454
ddahl: had the above action
item
... working on that
... one question about GitHub
... can I commit my changes?
kaz: yes
<ddahl> 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
kaz: not yet done
ddahl: do you think we still need the table itself?
kaz: no, don't think so
ddahl: would be easier to handle
the use case description
... do you think you still need ACTION-457?
kaz: yes
<ddahl> 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: some simple diagram would make the description easier to under stand
helena: not yet done
... need to send a message to Sebastian
kaz: fyi, the WoT IG is
restarting use case discussion to clarify the requirements for
the WoT scripting
... so at some point, we should talk with Johannes as well
helena: ok
<ddahl> action-459
<trackbot> action-459 -- Kazuyuki Ashimura to Coordinate with helena about her library software for the github -- due 2016-10-31 -- OPEN
<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/459
kaz: Helena is checking the W3C Software License
helena: looking at it
... don't think would be problematic
... the library is produced by me
ddahl: if Helena is OK with the W3C Software License, need to put the license notation on the codes?
helena: yes, can put it within
the codes and web pages
... JS, PHP scripts
... would be useful for people
ddahl: would be great
helena: will check the code/header, etc.
<ddahl> action-460
<trackbot> action-460 -- Kazuyuki Ashimura to Update the wot/mmi relationship diagram -- due 2016-11-14 -- OPEN
<trackbot> https://www.w3.org/2002/mmi/Group/track/actions/460
-> https://www.w3.org/2002/mmi/kaz/images/MMI-as-UI-for-WoT.png updated diagram
kaz: added 3 updates
... resource manager/resource description
... rice cooker/air conditioner as examples of Things
... two arrows: from MMI to WoT (WoT as a MC from MMI's
viewpoint) and fromWoT to MMI (MMI as a Servient from WoT
viewpoint)
ddahl: question about the protocol between MMI and WoT
<ddahl> debbie: can we annotate the diagram in Webex?
kaz: shares the image
ddahl: where Helena's vocabulary
should go?
... similar to the TD?
helena: Resource Manager just has index
ddahl: it would be interesting to
put the data component
... thought we had discussion the data component is part of the
IM
helena: need its own box
kaz: what would we need to handle within the MMI world?
helena: high-level
information
... name, address, port, etc.
... you can request detailed information
ddahl: MMI side could inquiry the
TD about the detail
... max/min temperature
helena: information of unit is important
ddahl: right. 70F is nice
temperature (though 70C is terrible)
... btw, regarding EMMA
... wonder what that means
... do we need EMMA there in this diagram?
... EMMA is transfered between IM and MC
kaz: right
ddahl: so EMMA is too low level for this diagram
kaz: right
... we should remove EMMA from this diagram itself
... on the other hand, I've started to think that everything
should be rather described as a service regardless of if it's a
concrete device or software
ddahl: like that idea
helena: a service is a modality here
kaz: will update this diagram based on today's discussion
ddahl: ok
ddahl: need to accept Dirk's pull request
kaz: will skim his proposal and merge it
ddahl: ok
... there is no conflict
ddahl: the current Charter ends
at the end of this year
... can we publish documents now?
kaz: yes
... there will be pub moratorium in December, though
Publication moratoria for the second harl of 2016 (Member-only)
ddahl: we have automatic
publication system now
... so we can publish an ordinary draft/note using the auto pub system
kaz: right
ddahl: other than the library, we
need to update the draft as well
... need to get the WG approval
kaz: do we still want to change
the title/shortname for the note?
... if we don't change title or shortname, we can simply add
content, e.g., the vocabulary
-> https://www.w3.org/TR/mmi-mc-discovery/ Discovery WD
kaz: we want to change the title and make it "Discovery & Registration" instead of "Registration & Discovery". right?
ddahl: the updated
WD's title is "Discovery & Registration of Multimodal Modality Components: State Handling"
... the shortname should be ok if we add vocabulary section
kaz: yes
ddahl: how about "Discovery and Registration of Modality Components"?
kaz: +1
<helena> +1
ddahl: talk with PLH about the title change
kaz: will do
<scribe> ACTION: kaz to talk with plh about the change of the title for the discovery WD [recorded in http://www.w3.org/2016/11/14-multimodal-minutes.html#action01]
<trackbot> Created ACTION-461 - Talk with plh about the change of the title for the discovery wd [on Kazuyuki Ashimura - due 2016-11-21].
[ adjourned ]