https://www.w3.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=PbeaujeaW3C Wiki - User contributions [en]2024-03-28T10:46:15ZUser contributionsMediaWiki 1.41.0https://www.w3.org/wiki/index.php?title=MBUI_Telecon_2013_April_25&diff=65715MBUI Telecon 2013 April 252013-04-26T07:40:52Z<p>Pbeaujea: </p>
<hr />
<div>== Chair ==<br />
* Gaelle Calvary<br />
<br />
== Present ==<br />
* Vivan Motti<br />
* Heiko Braun<br />
* Jaroslav Pullmann <br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Nesrine Mezhoudi<br />
* Gaelle Calvary<br />
* Pascal Beaujeant<br />
<br />
''add yourself if your name is missing and you were on the call''<br />
<!--<br />
* Heiko Braun<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Paolo Bottoni<br />
* Jean Vanderdonckt<br />
* Nesrine Mezhoudi<br />
* Davide Spano<br />
* Fabio Paternò<br />
* Pascal Beaujeant<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
* Jaroslav Pullman<br />
* Vivian Motti<br />
* Dave Raggett<br />
* Fabio Paterno<br />
* Sebastian Feuerstack<br />
* Ignacio Marín<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Gerrit Meixner<br />
* Javier Rodríguez<br />
* Cristina González<br />
--><br />
<br />
== Regrets ==<br />
<br />
* Fabio Paterno<br />
* Gerrit Meixner<br />
* Joelle Coutaz<br />
* Jean Vanderdonckt<br />
<br />
== Scribe ==<br />
* Gaelle Calvary<br />
<br />
== Agenda ==<br />
see http://lists.w3.org/Archives/Public/public-mbui/2013Jan/0006.html<br />
<br />
== Minutes ==<br />
<br />
=== Glossary of MBUI-Terms ===<br />
<br />
here are short minutes of today's call:<br />
<br />
* We worked on the glossary.<br />
* We decided to skip "Abstraction task" as Pisa did not attend the meeting.<br />
* We worked on the selected terms from "Concrete Interaction Object" to "Cross-cutting" + "Target".<br />
* For all the "Concrete xx" entries, we updated the definitions so that to make them consistent with the corresponding "Abstract xx" entries.<br />
* The pending tasks are:<br />
** @all: if possible, provide references for terms like "Context sensitivity", "Context awareness".<br />
** @UCL: check the definition of "Cross-cutting". I took the current one from one of your paper but there are perhaps more SE definitions?</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2013_April_25&diff=65714MBUI Telecon 2013 April 252013-04-26T07:35:52Z<p>Pbeaujea: </p>
<hr />
<div>== Chair ==<br />
* Gaelle Calvary<br />
<br />
== Present ==<br />
* Vivan Motti<br />
* Heiko Braun<br />
* Jaroslav Pullmann <br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Nesrine Mezhoudi<br />
* Gaelle Calvary<br />
* Pascal Beaujeant<br />
<br />
''add yourself if your name is missing and you were on the call''<br />
<!--<br />
* Heiko Braun<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Paolo Bottoni<br />
* Jean Vanderdonckt<br />
* Nesrine Mezhoudi<br />
* Davide Spano<br />
* Fabio Paternò<br />
* Pascal Beaujeant<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
* Jaroslav Pullman<br />
* Vivian Motti<br />
* Dave Raggett<br />
* Fabio Paterno<br />
* Sebastian Feuerstack<br />
* Ignacio Marín<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Gerrit Meixner<br />
* Javier Rodríguez<br />
* Cristina González<br />
--><br />
<br />
== Regrets ==<br />
<br />
* Fabio Paterno<br />
* Gerrit Meixner<br />
* Joelle Coutaz<br />
<br />
== Scribe ==<br />
* Gaelle Calvary<br />
<br />
== Agenda ==<br />
see http://lists.w3.org/Archives/Public/public-mbui/2013Jan/0006.html<br />
<br />
== Minutes ==<br />
<br />
=== Glossary of MBUI-Terms ===<br />
<br />
here are short minutes of today's call:<br />
<br />
* We worked on the glossary.<br />
* We decided to skip "Abstraction task" as Pisa did not attend the meeting.<br />
* We worked on the selected terms from "Concrete Interaction Object" to "Cross-cutting" + "Target".<br />
* For all the "Concrete xx" entries, we updated the definitions so that to make them consistent with the corresponding "Abstract xx" entries.<br />
* The pending tasks are:<br />
** @all: if possible, provide references for terms like "Context sensitivity", "Context awareness".<br />
** @UCL: check the definition of "Cross-cutting". I took the current one from one of your paper but there are perhaps more SE definitions?</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2013_April_25&diff=65713MBUI Telecon 2013 April 252013-04-26T07:34:47Z<p>Pbeaujea: Created page with "== Chair == * Gaelle Calvary == Present == * Vivan Motti * Heiko Braun * Jaroslav Pullmann * Nikolas Kaklanis * Paolo Bottoni * Nesrine Mezhoudi * Gaelle Calvary * Pascal Beauj…"</p>
<hr />
<div>== Chair ==<br />
* Gaelle Calvary<br />
<br />
== Present ==<br />
* Vivan Motti<br />
* Heiko Braun<br />
* Jaroslav Pullmann <br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Nesrine Mezhoudi<br />
* Gaelle Calvary<br />
* Pascal Beaujeant<br />
<br />
''add yourself if your name is missing and you were on the call''<br />
<!--<br />
* Heiko Braun<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Paolo Bottoni<br />
* Jean Vanderdonckt<br />
* Nesrine Mezhoudi<br />
* Davide Spano<br />
* Fabio Paternò<br />
* Pascal Beaujeant<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
* Jaroslav Pullman<br />
* Vivian Motti<br />
* Dave Raggett<br />
* Fabio Paterno<br />
* Sebastian Feuerstack<br />
* Ignacio Marín<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Gerrit Meixner<br />
* Javier Rodríguez<br />
* Cristina González<br />
--><br />
<br />
== Regrets ==<br />
<br />
* Fabio Paterno<br />
* Paolo Bottoni<br />
<br />
== Scribe ==<br />
* Gaelle Calvary<br />
<br />
== Agenda ==<br />
see http://lists.w3.org/Archives/Public/public-mbui/2013Jan/0006.html<br />
<br />
== Minutes ==<br />
<br />
=== Glossary of MBUI-Terms ===<br />
<br />
here are short minutes of today's call:<br />
<br />
* We worked on the glossary.<br />
* We decided to skip "Abstraction task" as Pisa did not attend the meeting.<br />
* We worked on the selected terms from "Concrete Interaction Object" to "Cross-cutting" + "Target".<br />
* For all the "Concrete xx" entries, we updated the definitions so that to make them consistent with the corresponding "Abstract xx" entries.<br />
* The pending tasks are:<br />
** @all: if possible, provide references for terms like "Context sensitivity", "Context awareness".<br />
** @UCL: check the definition of "Cross-cutting". I took the current one from one of your paper but there are perhaps more SE definitions?</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Teleconference_Calls&diff=65712MBUI Teleconference Calls2013-04-26T07:28:35Z<p>Pbeaujea: </p>
<hr />
<div>* [[Model-Based User Interfaces|MBUI Wiki Home Page]]<br />
<br />
Pages for each teleconference:<br />
<br />
* [[MBUI Telecon 2012 March 15]]<br />
* [[MBUI Telecon 2012 March 29]]<br />
* No call on April 5 due to Easter holidays<br />
* [[MBUI Telecon 2012 April 12]]<br />
* [[MBUI Telecon 2012 April 19]]<br />
* [[MBUI Telecon 2012 April 26]]<br />
* [[MBUI Telecon 2012 May 3]]<br />
* [[MBUI Telecon 2012 May 10]]<br />
* [[MBUI Telecon 2012 May 24]]<br />
* [[MBUI Telecon 2012 May 31]]<br />
* [[MBUI Telecon 2012 June 7]]<br />
* [[MBUI Telecon 2012 July 5]]<br />
* [[MBUI Telecon 2012 July 19]]<br />
* [[MBUI Telecon 2012 July 26]]<br />
* [[MBUI Telecon 2012 August 2]]<br />
* [[MBUI Telecon 2012 September 6]]<br />
* [[MBUI Telecon 2012 September 13]]<br />
* [[MBUI Telecon 2012 September 20]]<br />
* [[MBUI Telecon 2012 October 4]]<br />
* [[MBUI Telecon 2012 October 11]]<br />
* [[MBUI Telecon 2013 October 18]]<br />
* [[MBUI Telecon 2012 November 15]]<br />
* [[MBUI Telecon 2012 November 22]]<br />
* [[MBUI Telecon 2012 November 29]]<br />
* [[MBUI Telecon 2012 December 13]]<br />
* [[MBUI Telecon 2012 December 20]]<br />
* [[MBUI Telecon 2013 January 10]]<br />
* [[MBUI Telecon 2013 January 17]]<br />
* [[MBUI Telecon 2013 January 24]]<br />
* [[MBUI Telecon 2013 February 7]]<br />
* [[MBUI Telecon 2013 april 18]]<br />
* [[MBUI Telecon 2013 april 25]]</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2013_April_18&diff=65459MBUI Telecon 2013 April 182013-04-18T13:35:24Z<p>Pbeaujea: /* Glossary of MBUI-Terms */</p>
<hr />
<div>== Chair ==<br />
* Joëlle Coutaz<br />
<br />
== Present ==<br />
* Vivan Motti<br />
* Heiko Braun<br />
* Carmen Santoro<br />
* Jean Vanderdonckt<br />
* Jaroslav Pullmann <br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Gaelle Calvary<br />
* Pascal Beaujeant<br />
<br />
''add yourself if your name is missing and you were on the call''<br />
<!--<br />
* Jean Vanderdonckt<br />
* Heiko Braun<br />
* Pascal Beaujeant<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Paolo Bottoni<br />
* Jean Vanderdonckt<br />
* Nesrine Mezhoudi<br />
* Davide Spano<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
<br />
* Davide Spano<br />
* Paolo Bottoni<br />
* Jaroslav Pullman<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Dave Raggett<br />
* Fabio Paterno<br />
* Davide<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Sebastian Feuerstack<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Ignacio Marín<br />
* Heiko Braun<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Gerrit Meixner<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Jaroslav<br />
* Sebastian Feuerstack<br />
* Gerrit Meixner<br />
* Sebastian Feuerstack<br />
* Heiko Braun<br />
* Fabio Paternò<br />
* Jaroslav Pullmann <br />
--><br />
<br />
== Regrets ==<br />
<br />
* Fabio Paterno<br />
* Paolo Bottoni<br />
* Nikolas Kaklanis<br />
<br />
== Scribe ==<br />
* Jaroslav Pullmann <br />
<br />
== Agenda ==<br />
see http://lists.w3.org/Archives/Public/public-mbui/2013Jan/0006.html<br />
<br />
== Minutes ==<br />
<br />
=== Glossary of MBUI-Terms ===<br />
<br />
here are short minutes of today's call:<br />
<br />
#we agreed on consistent handling of synonymous and "W3C recommended" terms<br />
#I will apply this formatting to the reminder of the document<br />
#glossary terms "Abstract Interaction Object" - "Application task" have been reviewed<br />
#the term "Abstract task" appears in Paolo's Story Editor use case. Since it overlaps with<br />
"Abstraction task" as defined in Task Model document we ask for its replacement/removal<br />
#next week we agreed to consider relevance of terms "Backward recoverability" - "Consistency"<br />
for inclusion into the core glossary (otherwise to become part of an extended glossary) and<br />
move further with the review</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2013_April_18&diff=65458MBUI Telecon 2013 April 182013-04-18T13:35:11Z<p>Pbeaujea: </p>
<hr />
<div>== Chair ==<br />
* Joëlle Coutaz<br />
<br />
== Present ==<br />
* Vivan Motti<br />
* Heiko Braun<br />
* Carmen Santoro<br />
* Jean Vanderdonckt<br />
* Jaroslav Pullmann <br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Gaelle Calvary<br />
* Pascal Beaujeant<br />
<br />
''add yourself if your name is missing and you were on the call''<br />
<!--<br />
* Jean Vanderdonckt<br />
* Heiko Braun<br />
* Pascal Beaujeant<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Paolo Bottoni<br />
* Jean Vanderdonckt<br />
* Nesrine Mezhoudi<br />
* Davide Spano<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
<br />
* Davide Spano<br />
* Paolo Bottoni<br />
* Jaroslav Pullman<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Dave Raggett<br />
* Fabio Paterno<br />
* Davide<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Sebastian Feuerstack<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Ignacio Marín<br />
* Heiko Braun<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Gerrit Meixner<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Jaroslav<br />
* Sebastian Feuerstack<br />
* Gerrit Meixner<br />
* Sebastian Feuerstack<br />
* Heiko Braun<br />
* Fabio Paternò<br />
* Jaroslav Pullmann <br />
--><br />
<br />
== Regrets ==<br />
<br />
* Fabio Paterno<br />
* Paolo Bottoni<br />
* Nikolas Kaklanis<br />
<br />
== Scribe ==<br />
* Jaroslav Pullmann <br />
<br />
== Agenda ==<br />
see http://lists.w3.org/Archives/Public/public-mbui/2013Jan/0006.html<br />
<br />
== Minutes ==<br />
<br />
=== Glossary of MBUI-Terms ===<br />
<br />
here are short minutes of today's call:<br />
<br />
#we agreed on consistent handling of synonymous and "W3C recommended" terms<br />
#I will apply this formatting to the reminder of the document<br />
#glossary terms "Abstract Interaction Object" - "Application task" have been reviewed<br />
#the term "Abstract task" appears in Paolo's Story Editor use case. Since it overlaps with<br />
"Abstraction task" as defined in Task Model document we ask for its replacement/removal<br />
#next week we agreed to consider relevance of terms "Backward recoverability" - "Consistency"<br />
for inclusion into the core glossary (otherwise to become part of an extended glossary) and<br />
move further with the review</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2013_April_18&diff=65457MBUI Telecon 2013 April 182013-04-18T13:27:20Z<p>Pbeaujea: Created page with "here are short minutes of today's call: - we agreed on consistent handling of synonymous and "W3C recommended" terms - I will apply this formatting to the reminder of the doc…"</p>
<hr />
<div>here are short minutes of today's call:<br />
<br />
- we agreed on consistent handling of synonymous and "W3C recommended" terms<br />
<br />
- I will apply this formatting to the reminder of the document<br />
<br />
- glossary terms "Abstract Interaction Object" - "Application task" have been reviewed<br />
<br />
- the term "Abstract task" appears in Paolo's Story Editor use case. Since it overlaps with<br />
"Abstraction task" as defined in Task Model document we ask for its replacement/removal<br />
<br />
- next week we agreed to consider relevance of terms "Backward recoverability" - "Consistency"<br />
for inclusion into the core glossary (otherwise to become part of an extended glossary) and<br />
move further with the review<br />
<br />
<br />
Best regards<br />
Jaroslav</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Teleconference_Calls&diff=65456MBUI Teleconference Calls2013-04-18T13:26:48Z<p>Pbeaujea: </p>
<hr />
<div>* [[Model-Based User Interfaces|MBUI Wiki Home Page]]<br />
<br />
Pages for each teleconference:<br />
<br />
* [[MBUI Telecon 2012 March 15]]<br />
* [[MBUI Telecon 2012 March 29]]<br />
* No call on April 5 due to Easter holidays<br />
* [[MBUI Telecon 2012 April 12]]<br />
* [[MBUI Telecon 2012 April 19]]<br />
* [[MBUI Telecon 2012 April 26]]<br />
* [[MBUI Telecon 2012 May 3]]<br />
* [[MBUI Telecon 2012 May 10]]<br />
* [[MBUI Telecon 2012 May 24]]<br />
* [[MBUI Telecon 2012 May 31]]<br />
* [[MBUI Telecon 2012 June 7]]<br />
* [[MBUI Telecon 2012 July 5]]<br />
* [[MBUI Telecon 2012 July 19]]<br />
* [[MBUI Telecon 2012 July 26]]<br />
* [[MBUI Telecon 2012 August 2]]<br />
* [[MBUI Telecon 2012 September 6]]<br />
* [[MBUI Telecon 2012 September 13]]<br />
* [[MBUI Telecon 2012 September 20]]<br />
* [[MBUI Telecon 2012 October 4]]<br />
* [[MBUI Telecon 2012 October 11]]<br />
* [[MBUI Telecon 2013 October 18]]<br />
* [[MBUI Telecon 2012 November 15]]<br />
* [[MBUI Telecon 2012 November 22]]<br />
* [[MBUI Telecon 2012 November 29]]<br />
* [[MBUI Telecon 2012 December 13]]<br />
* [[MBUI Telecon 2012 December 20]]<br />
* [[MBUI Telecon 2013 January 10]]<br />
* [[MBUI Telecon 2013 January 17]]<br />
* [[MBUI Telecon 2013 January 24]]<br />
* [[MBUI Telecon 2013 February 7]]<br />
* [[MBUI Telecon 2013 april 18]]</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2013_January_24&diff=65220MBUI Telecon 2013 January 242013-04-11T10:38:54Z<p>Pbeaujea: /* Present */</p>
<hr />
<div>== Chair ==<br />
* Dave Raggett<br />
<br />
== Present ==<br />
<br />
* Dave Raggett<br />
* Heiko Braun<br />
* Klaus/Johannes/Thomas<br />
* Joelle Coutaz<br />
* Davide Spano<br />
* Carmen Santoro<br />
* Jaroslav Pullmann <br />
* Javier Rodríguez<br />
* Cristina González<br />
* Ignacio Marín<br />
* Paolo Bottoni<br />
* Nikolas Kaklanis<br />
* Vivian Motti<br />
* Pascal Beaujeant<br />
<br />
''add yourself if your name is missing and you were on the call''<br />
<!--<br />
* Nikolas Kaklanis<br />
* Fabio Paternò<br />
* Paolo Bottoni<br />
* Gaelle Calvary<br />
* Jean Vanderdonckt<br />
* Heiko Braun<br />
* Pascal Beaujeant<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Paolo Bottoni<br />
* Jean Vanderdonckt<br />
* Nesrine Mezhoudi<br />
* Davide Spano<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
<br />
* Davide Spano<br />
* Paolo Bottoni<br />
* Jaroslav Pullman<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Dave Raggett<br />
* Fabio Paterno<br />
* Davide<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Sebastian Feuerstack<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Ignacio Marín<br />
* Heiko Braun<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Gerrit Meixner<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Jaroslav<br />
* Sebastian Feuerstack<br />
* Gerrit Meixner<br />
* Sebastian Feuerstack<br />
* Heiko Braun<br />
* Fabio Paternò<br />
* Jaroslav Pullmann <br />
--><br />
<br />
== Regrets ==<br />
<br />
* Gerrit Meixner<br />
* Fabio Paternò<br />
* Jean Vanderdonckt<br />
<br />
== Scribe ==<br />
* Dave Raggett<br />
<br />
== Agenda ==<br />
see http://lists.w3.org/Archives/Public/public-mbui/2013Jan/0006.html<br />
<br />
== Minutes ==<br />
<br />
=== AUI meta-model ===<br />
<br />
Dave asks if we have any status updates.<br />
<br />
Paolo: I sent the updates to the UCL.<br />
<br />
Vivian: Jean is unavailable today, but we haven't had time to apply the updates.<br />
<br />
Paolo: Perhaps Vivian, myself and Heiko could have a chat on IRC to reach a consolidated diagram?<br />
<br />
Vivian: yes, that is a good idea.<br />
<br />
Paolo: let's aim for Monday or Tuesday next week and we can arrange the details via email.<br />
<br />
Heiko: that's okay for me too.<br />
<br />
Pascal: could we arrange the time slot via doodle so that we can get Jean involved. I will send the URL for the poll.<br />
<br />
Paolo: perfect.<br />
<br />
=== Introductory Document ===<br />
<br />
Joelle: I will take over editorship next week.<br />
<br />
There was the issue of many versus one example in the document, what was the decision?<br />
<br />
Carmen: last week we agreed to use one use case.<br />
<br />
Joelle: UCL has updated the car rental use case which now looks good.<br />
<br />
Carmen: we should focus on the car rental example.<br />
<br />
Jaroslav: the aim was to use the same example for the different levels of abstraction.<br />
<br />
Joelle: is the document as it is okay, or do we need to break it down and stick to one example (UCL car rental) or do we stick with multiple examples.<br />
<br />
Jaroslav: my understanding is that we will use the same use case.<br />
<br />
Joelle and Paolo agreed that the other use cases would be moved to a separate document.<br />
<br />
Carmen: we should go through the table, either merging the examples or selecting an existing one. We could put the other examples in an appendix document.<br />
<br />
Joelle: okay<br />
<br />
Carmen: I put a comment as there is an error in the table for the numbering. <br />
<br />
Joelle: how should we do the selection?<br />
<br />
Carmen: I will make a proposal via email on Tuesday afternoon, and need a quick response as I only have Wednesday morning to make the updates, everyone agree?<br />
<br />
We voice our agreement.<br />
<br />
Jaroslav: will we use different examples for different levels of the Cameleon reference framework?<br />
<br />
Joelle: okay I will will propose the values for the table in the document Tuesday and start editing it on Wednesday morning.<br />
<br />
Dave thanks Joelle.<br />
<br />
Dave: any other things to discuss today?<br />
<br />
Jaroslav will meet with Gerrit tomorrow. Does it make sense to introduce links into the Google doc from the introductory note to the glossary? They could be easily converted.<br />
<br />
Dave: yes we can do that, my aim is to move swiftly to publication.<br />
<br />
Next week several of us will be at a Serenoa meeting, so does it make sense to cancel next week's MBUI teleconference?<br />
<br />
general agreement.<br />
<br />
Our next telecon will be 7 February 2013.<br />
<br />
end of meeting.</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_May_24&diff=65219MBUI Telecon 2012 May 242013-04-11T10:37:21Z<p>Pbeaujea: /* Present */</p>
<hr />
<div>== Agenda ==<br />
<br />
The agenda is:<br />
<br />
* Invited Experts<br />
* Upcoming face to face in Pisa<br />
* Progress on abstract user interface modelling language<br />
* Progress on task modelling language<br />
* Progress on working group note<br />
* Any Other Business<br />
<br />
== Present ==<br />
<br />
* Dave Raggett<br />
* Javier Rodriguez<br />
* Cristina Cachon<br />
* Gaelle Calvary<br />
* Joelle Coutaz<br />
* Nikolas Kaklanis<br />
* Sebastian Feuerstack<br />
* Jaroslav Pulman<br />
* Davide Spano<br />
* Carmen Santoro<br />
* Francois Beuvens<br />
* Pascal Beaujeant<br />
<br />
== Regrets ==<br />
<br />
* Gerrit Meixner<br />
* Jean Vanderdonckt<br />
<br />
== Chair ==<br />
<br />
* Dave<br />
<br />
== Scribe ==<br />
<br />
* Dave<br />
<br />
== Minutes ==<br />
<br />
Sadly Gerrit is off sick and unavailable to chair tomorrow's call and<br />
has asked me to step in for him. He should be back in time for next week's call, but I will be on a short vacation with my wife.<br />
<br />
It would be helpful if you can use IRC indicate your presence in the calls. The web address for your browser is irc.w3.org. The channel is #mbui. <br />
<br />
To indicate your presence, please type:<br />
<br />
Presence+ followed by your name<br />
<br />
This will make it easier to keep accurate records in the minutes.<br />
<br />
<br />
=== Invited Experts ===<br />
<br />
A reminder that if you aren't employed by a W3C Member organization and are working for an academic institution, you should apply to become an invited expert, see:<br />
<br />
http://www.w3.org/wiki/Model-Based_User_Interfaces#Getting_Involved<br />
<br />
This is to ensure that we stick by the rules for the W3C Patent Policy.<br />
<br />
=== Upcoming face to face in Pisa ===<br />
<br />
ISTI • Area della Ricerca CNR,<br />
via G. Moruzzi 1, 56124 Pisa, Italy<br />
<br />
9am June 14 through midday on June 15<br />
<br />
<br />
Our thanks to ISTI-CNR for hosting the meeting which will follow the Serenoa meeting. You are recommended to book your flights as soon as practical, and to find a hotel in the central city area. A bus connects the city center with the airport or you can take the train. I will work with the ISTI team to provide details for how to get to the meeting room.<br />
<br />
If needed, we may be able to provide a means for people to call in by Skype.<br />
<br />
If you have any particular dietary needs please let me know and I will pass the information on.<br />
<br />
Gerrit will work on the agenda, but please send your suggestions to the list.<br />
<br />
<br />
=== Progress on abstract user interface modelling language ===<br />
<br />
Francois: Still in progress. We plan to submit our first version before the F2F.<br />
<br />
FDave: any reason why not to put the text directly in to the google doc?<br />
<br />
Francois: We prefer to elaborate a version internally and to submit a stable version.<br />
<br />
Dave: thanks I was worried that no one was working on it, so this is good news.<br />
<br />
Dave: In regards to an accessible version of the AUI meta model, will you be able use a table as was discussed by email?<br />
<br />
Francois: I can't really understand you [too strong an echo]<br />
<br />
=== Progress on task modelling language ===<br />
<br />
Carmen: we are working on the google doc, and have added a table providing a comparision with other task modeling languages and temporal operators, which is a very useful contribution. Gerrit asked about a CTT operator. This can be modeled in different ways. For the moment we can keep it, but we could consider removing it later if needed. <br />
<br />
Davide has addressed some of the comments. Carmen goes through the details (not minuted). For the UML diagram we've added the precondition element to the meta model. To improve the accessibility we've included links and bookmarks to make it easier to navigate through the classes. We've noticed that links don't always work well in google docs, but that shouldn't be a problem when we move it to HTML.<br />
<br />
Dave: I am working an an XSLT script to map the google doc to HTML and will be able to show it in Pisa.<br />
<br />
=== Progress on working group note ===<br />
<br />
Jaroslav has worked on the glossary using the material from the Cameleon project and compared versions and think we have an audience problem. The Cameleon descriptions are aimed at a scientific audience and is too abstract with lots of references to research. It is not obviuous what the relevance is more broadly.<br />
<br />
The model and description are used in different places but are essentially synonymous. We need to add some examples of usage. We could look at the different documents we are writing and try understand what's needed.<br />
<br />
<br />
Dave: we should aim at developers and managers in businesses as these are the people we want to invest in deploying model based UI design techniques.<br />
<br />
Jaroslav: this is an important task and I invite people's help.<br />
<br />
Joelle: should we focus on different audiences?<br />
<br />
Jaraslav: we need to find a common understanding, and this is likely to make this a large document.<br />
<br />
I think you're suggesting we have two levels of definitions for the different audiences.<br />
<br />
Joelle: yes<br />
<br />
Jaroslav: show would we split up the document?<br />
<br />
Joelle: we look at the current glossary and flag which ones we want to export. We don't have to physical documents, but we have candidates for an external glossary.<br />
<br />
Jaroslav: the glossary on the W3C Note would be informative.<br />
<br />
It is proving hard to understand the importance of specific terms without context, which is why we need examples of usage. Some terms are really abstract and hard to understand. We should aim for a simpler set of definitions.<br />
<br />
All of us should start reviewing the glossary and marking whether you agree or to add your own interpretation.<br />
<br />
Joelle: can you give me an example of a term that is too abstract?<br />
<br />
Jaroslav: the best way is for me to do so in the google doc.<br />
<br />
Joelle: ok<br />
<br />
Dave: Any one else working on the Note at the moment?<br />
<br />
[no]<br />
<br />
=== Any other businesss ===<br />
<br />
Joelle: Is anyone interested in staying at the same hotel?<br />
<br />
[yes]<br />
<br />
Dave: we should add our hotels to the meeting wiki page to help with that.<br />
<br />
Joelle will forward some hotel information she received from ISTI.<br />
<br />
... end of meeting...</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_June_7&diff=65218MBUI Telecon 2012 June 72013-04-11T10:36:50Z<p>Pbeaujea: /* Present */</p>
<hr />
<div>Chaired and scribed by Dave<br />
<br />
== Present ==<br />
<br />
* Dave Raggett<br />
* Javier Rodriguez<br />
* Cristina Cachon<br />
* Nikolas Kaklanis<br />
* Sebastian Feuerstack<br />
* Davide Spano<br />
* Fabio Paterno<br />
* Jean Vanderdonckt<br />
* Vivian Motti<br />
* Francois Beuvens<br />
* Pascal Beaujeant<br />
<br />
== Regrets ==<br />
<br />
* Jaroslav Pullman<br />
* Gerrit Meixner<br />
* Gaelle Calvary<br />
<br />
== Minutes == <br />
<br />
'''Reminder: everyone to read through the editor's drafts and bring their comments to the face to face!'''<br />
<br />
<br />
UCL: we have updated the gdoc for the AUI with the first version of the meta model. We are addressing the comments from Sebastian.<br />
<br />
Jean: what is the most appropriate methodology tor each the goal, e.g. bottom up or top down when it comes <br />
<br />
Fabio: so far it seems that you are following a top down approach.<br />
<br />
Jean: we have been trying to take into account all of the partners input, but this takes a lot of time.<br />
<br />
Fabio: we explain why we put in the task model document where we disagree with a comment<br />
<br />
Jean: we need a consistent approach across subgroups<br />
<br />
Fabio/Davide: we discussed a bit for the task model and for the AUI. We tried to keep the major concepts with an extensional approach, and minor concepts as intensional.<br />
<br />
Jean: for which part, give us an example?<br />
<br />
Davide: task categories as extensional and task types as intensional<br />
<br />
Fabio: this seems reasonable<br />
<br />
Jean: for the AUI if we take the category "select" I would have as many subclasses as I have ...<br />
<br />
Jean: intension provides the most concise representation in the meta model<br />
<br />
Jean: we have a choice between adding a new subclass or adding to an ennumeration<br />
<br />
Fabio: at some point for the sake of brevity we would choose intensional. It depends on the level of granularity we are considering. It would be better to extend the main concepts.<br />
<br />
Jean: we can model the same concepts in many different ways.<br />
<br />
Fabio: the main concepts can be extended, and the low level concepts can be intensive<br />
<br />
Dave: perhaps this is something we need to resolve at the face to face as it feels like it will be hard to reach a consensus on the phone?<br />
<br />
Jean: you have as many subclasses as you have types, right?<br />
<br />
Fabio: no.<br />
<br />
Jean: for the metamodel in the google doc, there are 3 subclasses without any attributes<br />
<br />
Fabio: no, these are associations, not subtypes<br />
<br />
Jean: In AI there is a nice classification of user tasks, I might like to add these<br />
<br />
Fabio: the diagram isn't ideal as a way to express extensibility<br />
<br />
Jean: definition by extension<br />
<br />
Fabio: we keep the categories and the attribute values can be extended.<br />
<br />
Jean: google KADS task types for details, I don't remember exactly. For the operators it is different, right?<br />
<br />
Fabio: yes. <br />
<br />
Jean: you want to modify the precondition in the choice?<br />
<br />
Fabio: non-deterministic means a choice without a precondition<br />
<br />
Jean: ...<br />
<br />
Davide: for a deterministic choice, if you define this through conditions, you don't need a deterministic choice, but you do need to represent the conditions<br />
<br />
Jean: in the UK, ...<br />
<br />
Fabio: boolean conditions for deterministic choices, without need for subclasses.<br />
<br />
Further discussion about concurrent and parallel task models.<br />
<br />
Jean: the main question we have is about the methodology, so that the standard has the greatest coverage?<br />
<br />
Fabio: we want to avoid too many operators. We have a table that compares different notations, at least for the ones we have looked at so far.<br />
<br />
Jean: for the line CTS, there are some that are not in the table<br />
<br />
Fabio: which ones?<br />
<br />
Jean: ... concurency is interleaved or parallel?<br />
<br />
Fabio: so far we have left this in an abstract way so that it can be left to the context<br />
<br />
Jean: if I want to choose between one or the other, how do we do that?<br />
<br />
Fabio: if we think this is important, we can elaborate the distinctions<br />
<br />
Jean: what process do we need to achieve a consensus?<br />
<br />
Dave: we can do this at the face to face - to get people to present different approaches and to then see if we can reach a consensus on a synthesis or to pick the best approach, noting the reasons for doing so.<br />
<br />
Jean: order independence is a particular case of concurrency?<br />
<br />
Fabio: no. <br />
<br />
Jean: concurrency is the most abstract class?<br />
<br />
Fabio: there are two possible implementations of concurrency, but is it important to capture which at the level of task models<br />
<br />
Jean: perhaps not at an early stage of the design work<br />
<br />
Jean: to come back to the methods, you have used a bottom up approach for the task models, right?<br />
<br />
Fabio: yes<br />
<br />
Jean: we've used a top down approach for the AUI which is very time consuming. Should we switch to a bottom up approach?<br />
<br />
Fabio: perhaps you should make a proposal, and we can see<br />
<br />
Jean asks Dave for his views on how to proceed<br />
<br />
Dave: we don't need to finalize everything right away, and first publication of the drafts is the immediate priority. We should aim for stable specifications towards the end of this year.<br />
<br />
Jean asks for comment on the new version of the AUI in the google doc.<br />
<br />
Davide: it seems to be in the right direction<br />
<br />
<br />
No more comments on the AUI.<br />
<br />
Dave any more to say on the Task model specification?<br />
<br />
Fabio: no, we have already covered that, but please read through and bring your comments to Pisa.<br />
<br />
<br />
== Any other business ==<br />
<br />
Jean: will you have a skype connection at the face to face?<br />
<br />
Fabio: yes, we can arrange that</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_July_26&diff=65217MBUI Telecon 2012 July 262013-04-11T10:36:12Z<p>Pbeaujea: /* Present */</p>
<hr />
<div>Chaired by: Marius, scribed by Dave<br />
<br />
== Present ==<br />
<br />
* Dave Raggett, W3C<br />
* Marius Orfgen, DFKI<br />
* Nikolas Kaklanis, ITI<br />
* Jaroslav Pullman, Fraunhofer<br />
* Sebastian Feuerstack, USC<br />
* Cristina Cachon, CTIC<br />
* Javier Rodriguez, CTIC<br />
* Ignacio Marin, CTIC<br />
* Vivian Motti, UCL<br />
* Francois Beuvens<br />
* Fabio Paterno, ISTI<br />
* Carmen Santoro, ISTI<br />
* Davide Spano, ISTI<br />
* Pascal Beaujeant, UCL<br />
<br />
<!--<br />
* Gaelle Calvary, LIG<br />
* Joelle Coutaz, LIG<br />
* Jean Vanderdonckt<br />
--><br />
<br />
== Regrets ==<br />
<br />
* Gaelle Calvary, LIG<br />
* Joelle Coutaz, LIG<br />
* Gerrit Meixner, DFKI<br />
* Paolo Bottini, University of Rome<br />
<br />
== Planned Agenda ==<br />
<br />
# Resolution on publishing FPWD for task models<br />
# Progress on the AUI document<br />
# Progress on Introduction and Glossary documents<br />
<br />
<br />
== Minutes == <br />
<br />
=== Publication of the task model document ===<br />
<br />
* http://www.w3.org/2011/mbui/drafts/task-models/<br />
<br />
Proposed Resolution: to publish task models specification as a First Public Working Draft using task-models at its short name<br />
<br />
We've already received some emails in favour from people who couldn't make today's call.<br />
<br />
Any objections to the proposed resolution?<br />
<br />
None given.<br />
<br />
*Resolved: to publish task models specification as a First Public Working Draft using task-models at its short name*<br />
<br />
Jaroslav asks a question about operators. He wants to ensure that the glossary is in sync, see his email at:<br />
<br />
* http://lists.w3.org/Archives/Public/public-mbui/2012Jul/0010.html<br />
<br />
For the next draft, he proposes introducing a subsection header on operators (beneath section 3 Meta-Model) and to provide illustratory examples of the CTT notation for termporal operators.<br />
<br />
Vivian agrees with Jaroslav for the operators, and would like to suggest we look at the task types in the reference she sent in email, see:<br />
<br />
* http://lists.w3.org/Archives/Public/public-mbui/2012Jul/0018.html<br />
<br />
Fabio: yes, we can look at that for consideration for the next version of the working draft.<br />
<br />
See also Paolo's comments at:<br />
<br />
* http://lists.w3.org/Archives/Public/public-mbui/2012Jul/0017.html<br />
<br />
where he says that the metamodel does not clearly separate the nature of the<br />
tasks from their structuring <br />
<br />
Vivian: another question on selection vs filtering (?)<br />
<br />
Fabio: yes, there should be such a distinction.<br />
<br />
=== Progress on the AUI document, additional editors? ===<br />
<br />
* [https://docs.google.com/document/d/1UGZz_xaPuSbMtRb4a-14tM9CM8tHmbEWuLVuNNnx25o/edit AUI draft]<br />
<br />
Vivian: we have updated the diagam and some of the text, and are working on completing the updates for next week's call.<br />
<br />
Dave: we can review it in next week's call!<br />
<br />
=== Progress on Introduction and Glossary documents ===<br />
<br />
* [https://docs.google.com/document/d/1Xp50GZ8EfY017AT_pCMBq5PeK8cwNEZi1a8hXexJkCc/edit Intro draft]<br />
* [https://docs.google.com/document/d/1gt5c_M13DZFgdE84j8MdYml7nNC0u-u7AgnbnES_8Ho/edit Glossary draft]<br />
<br />
Marius: what progress has there been on the introduction document?<br />
<br />
No responses.<br />
<br />
(we have all been focusing on the task model document)<br />
<br />
=== Any Other Business ===<br />
<br />
Fabio: what about having a break in the calls during part of August due to vacations?<br />
<br />
Dave: I will set up a poll as not everyone is on the call.<br />
<br />
Marius: yes a doodle poll or similar.<br />
<br />
''end of meeting''</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_October_4&diff=65216MBUI Telecon 2012 October 42013-04-11T10:35:22Z<p>Pbeaujea: /* Present */</p>
<hr />
<div>==Present==<br />
* Gerrit Meixener <br />
* Jaroslaw Pullman <br />
* Nikos<br />
* Paolo Bottoni<br />
* Sebastian <br />
* Joelle Coutaz <br />
* Jean Vanderdonckt <br />
* Pascal Beaujeant<br />
* Fabio Paternò <br />
* Davide Spano<br />
<br />
==Minutes ==<br />
<br />
=== Abstract UI document ===<br />
* Paolo asks whether the AUI meta-model we are defining should be a reference that all our languages should conform to, or if we are going to define a new language. Fabio thinks that we are going to create a new meta-model and a new associated language. The authors of the existing languages have the freedom to decide to conform to it or to map their languages to the proposed one. Sebastian agrees with Fabio, saying that people may have different needs and create subclasses for that. Paolo says that there is also the possibility to explicitly say that a language is conform to the meta-model, providing the mapping of concepts between the language and the standard. <br />
* Discussion about the requirements for the standard implementation. Fabio says that we are required to provide two different implementations of the standard, which are supposed to be interoperable. Therefore, it should be possible to export the model with an implementation and open it with the other and vice-versa. Jean says that it should be sufficient to include an Import/Export function from and to the standard language.<br />
* Discussion on the abstract syntax for the AUI language. Jean says that we should propose something that is not implementation-dependent, providing an XSD or an OWL description. It is not clear if we should stop at the abstract syntax or if we are going to provide also a concrete one. Paolo says that there are two possible ways to create the language: referring the concepts either through subclassing or through instantiation. He will write a section on the document explaining the two possibilities.<br />
* Document refinement for Lyon. Jean proposes to continue modifying the draft document, stopping a week before the Lyon meeting. At that time, the will prepare a version to be discussed in Lyon. The participants should create their list of questions in order to speed-up the discussion at the F2F. Everybody agrees.<br />
* AUI concept. Joelle noticed that we have still a fuzzy view on what should be modelled at the abstract level and what should not. She proposes to stick to a shared definition and try to apply it to decide. Sebastian says that, in addition, we should remove the concepts that do not have the consensus. Fabio says that this is correct in theory, but we may end to have almost nothing modelled, therefore we should be careful.<br />
<br />
=== Working group note ===<br />
<br />
*Sebastian says that the use cases are really different in the level of detail. Some of them are too generic. Joelle suggests to describe scenarios that we already implemented in our own projects, in order to have a good level of detail. Jean says that we should in addition mention the benefits of MBUI approaches. Fabio and Jean may provide references to comparative studies (whit and without MBUI development).<br />
*Nikos' section on user modelling. It is a very detailed description of a user model. Jean and Fabio suggest to create a shorter version with a more brief description of the concepts, moving the details into an appendix or a separate document.<br />
<br />
===Heiko's email about the Task model XSD===<br />
<br />
* Fabio says that the problems mentioned were simply typos and that they have been fixed. We are waiting for Dave in order to publish the updated version of the XSD.<br />
<br />
==Actions==<br />
<br />
* Write a section on instantiation and subclassing on the AUI document (Paolo)<br />
* Refine the AUI meta-model description (All)<br />
* Refine the level of detail of the use cases in the Working Group Note (Use case responsibles)<br />
* Publish the fixed version of the task model xsd (Dave)</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_November_22&diff=65215MBUI Telecon 2012 November 222013-04-11T10:34:23Z<p>Pbeaujea: /* Present */</p>
<hr />
<div>Scribed by Vivian<br />
== Present ==<br />
<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Pascal Beaujeant<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Fabio Paterno<br />
* Davide<br />
* Carmen Santoro<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Gerrit Meixner<br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Jaroslav<br />
* Sebastian Feuerstack<br />
<br />
== Regrets ==<br />
* Heiko Braun<br />
* Ignacio Marín<br />
* Dave Raggett<br />
<br />
== Scribe ==<br />
* Vivian Motti<br />
<br />
== Minutes ==<br />
<br />
We started the discussions based on the emails previously sent by Heiko, Sebastian and Paolo (concerning modelling producer - consumer)<br />
* Open issues of the AUI documents<br />
<br />
=== Modelling behaviors, events and producer-consumer relationship ===<br />
* Section meta-model: new version of the meta-model for configuration (pictures to be moved to another document)<br />
** Everything is linked to the configuration<br />
** Unify the definition (uniform names)<br />
<br />
* The UI commons will be a separate document (exclusive)<br />
** 1st drawing: configuration meta-model <br />
** Its configuration concerns a set of models (not 'just' a mapping model): composition of items<br />
** Items can be codes, models, i.e. any artifact that is general to any model<br />
** Definition compliant with configuration software management<br />
* Jean: we focus on the models<br />
** A configuration associates versions of the models: AUI, task, domain...<br />
<br />
* Davide: move the configuration to the Introduction document and call within the AUI doc?<br />
* Jean: Yes, in principle we can have an integrated view, but later, this should be moved to another document.<br />
** locate the packages, but they will be separate definitions<br />
<br />
* Jean: regarding Heiko's comments, in summary, keep behavior as event-condition-action patter<br />
** links action direct to producer, and behavior to the consumer<br />
** this pair (P,C) then connected by an interaction unit<br />
** Paolo says an action can be connected to both producer and consumer of a resource (new or existing)<br />
** understood by types<br />
* Paolo agrees<br />
* Heiko's proposal defends that producer is connected to the input, and the consumer linked to the interaction unit<br />
** further clarifications needed<br />
* For Jean, Paolo's model is symmetric and more general<br />
** because an action is linked to both: P and C of a resource <br />
<br />
* Joelle doesn't understand the link between producers and consumers<br />
** in Paollo's version (blue background)<br />
* Fabio: further clarifications needed for the role of P and C<br />
* Paollo: minutes updated (last call-meeting) -> motivations, issues raised<br />
** Connections between interaction units and behaviors<br />
** Several types of behaviors that are connected (navigations, ...)<br />
** how to model the notion of behavior?<br />
** with Producer, Consumer?<br />
** with Listener and Senders?<br />
** Resources can be consumed: data, ...<br />
** Beside the behavior model<br />
** Action: could use resources, consume resources<br />
** Behavior: collection of actions, can be connected to a unit that supports its behavior<br />
** Notion provides an underline specification (abstract approach to consider behaviors' types)<br />
** overall view<br />
* Jean: listeners can be seem as consumers, and senders as producers, however it is a more general definition<br />
* Paolo agrees<br />
* Jean: event is a sub-class of resources<br />
* Joelle: says why? it is unusual<br />
* Davide: asks whether one resource only is associated with several resources <br />
* Paolo: says it is a good question, 2 perspectives are involved<br />
** Consumers can be seem as an interface that collects resources (not specific class)<br />
** there is a method to consume a resource<br />
** consumer: group of elements that consume a set of resources<br />
** how events are shared or propagated (are consumed) among the members<br />
** event is actually consumed by the first action<br />
** 1st action reproduces the event, it is propagated until the last one consumes it<br />
** 2 ways of seeing it<br />
* not the single action, but the overall behavior consumes it<br />
** action guarantees the behavior is still valide<br />
** Events: as a sub-class of a resource<br />
*** resource is a type (we do not imposed anything specific to be relied)<br />
** Way of characterizing resources (as P or C)<br />
* Jean: another example than an event as a particular type of resources<br />
** Paollo: not physically consumed (credential of the badget ?)<br />
** Paollo: reader checks the presence of a resource that is consuming it<br />
* Davide: Heiko's propose producer may be only Input interaction unit, shouldn't it be any type? and also external entities?<br />
** Paollo: general model for defining behavior: producers and consumers may have specific inputs<br />
** Paollo: not particulary happy with this definition, model should connect unit and behavior via an event support (input of the user, but not only... other ways of generating events too), a person enters the room and triggers an event for example<br />
** characterize how an event is tiggered (not necessarily with a user input)<br />
* Joelle: IU can be both a producer and a consumer, right? To check. Support this.<br />
* Paollo: actually a P and a C are the behaviors, a IU can support the triggering of a generation of an event, and the consequences of the behavior (e.g. if a new resource is available)<br />
* Fabio: an output or a container cannot be a producer (according to the diagram)<br />
* Jean, Joelle concerns<br />
* Paollo: does not agree with such definition<br />
* Fabio: specific design, expressed by the diagram of Sebastian<br />
* Paollo: to be discussed, not yet agreed<br />
* Paollo: consumer produces, only on the side of a behavior, not the intermediate way of relating IUs and behaviors (representation support)<br />
* Jean: behavior directly connected to the IU, definition of the behavior via this channel<br />
* Paollo: not the behavior, but the event<br />
* Jean: one IU linked to one or to many behaviors (attached to it), link in this way (before in the abstract user interface model class)<br />
* Paollo: different issue, syntactic feedback, related to the UI model, behaviors related to the AUI model or to the task model (one are directly connected to the unit, others not)<br />
* Jean: link between behavior model should go direct to the UI commons package<br />
* Paollo: connections are really through the notion of events, way of relating unit to the events <br />
** events support: present and connected to events, update the version because the units could also support presentation to the user or the effects of a behavior<br />
* Jean: explained in the action part, do not want to impose a particular vocabulary now<br />
** to proceed: diagram from Paollo: more general, so define a separated behavior model linked to the UI commons model, connects to the AUI model (express behavior correctly)<br />
* Joelle: please create a consolidated version of the models, according to the discussion<br />
* Jean: Paollo's model is more general<br />
** idea: concentrating the behavior in a different model (across levels), this proposal supports this<br />
** the separate model and package must check whether the links are enough between the behavior and UI commons (for AUI, domain, task model...)<br />
** applicable to anythig, e.g. DRY principle<br />
** concentrate behavior at one place<br />
** declinate them depending on the requirements<br />
** span across abstraction levels<br />
* Gaelle: any impacts at the task meta model?<br />
* Paollo: yes<br />
* Fabio: two different abstraction level, logical activities, better not to mix the two aspects, understandable description of the concepts <br />
* Jean: could we also express a behavior at the task level?<br />
* Gaelle, Paollo agrees<br />
* Fabio: difference between task and an action: not describe low level implementation<br />
* Gaelle: do we use the behavior model to model the temporal relationships between tasks?<br />
* Fabio: now the temporal relations are describe with operators<br />
* Joelle: Jean will do a consolidation (behavior from the top level comments) then we see how it applies to the other levels (task, etc)<br />
* Paollo: task model is primarily to describe organization and the temporal relations<br />
** at the general level it also describes a transformation of the resources (like in the task), at the CTT environment this is also modelled<br />
* Jean: like information passing?<br />
** Paollo: represent the reflected transformation, I do not see a direct impact on the task meta model, but it is related...<br />
* Joelle: we will see what happens after a consolidation<br />
** more clear the models in focus<br />
* Paollo: check the minutes<br />
* Joelle: cannot understand the minutes, follow the discussions currently<br />
* Jean: direction to separate things<br />
* Joelle: advice will come later, clean version of the AUI, consensus Jean and Paollo<br />
** be careful with last minute changes... hard to follow, analyse...<br />
**Jean: Abstract behavior model (sent via emails)<br />
* Joelle: hard to follow the discussion, does it serve both as a Consumer and a Producer, check and assure this (this is the case in real life)<br />
* Jean: now we have realizations and dependencies at the UML class diagram<br />
* Fabio: separate the behavior into a separate model?<br />
* Jean: yes, following Lyon's decision<br />
* Fabio: one single place describing what the AUI is, clean, focused, <br />
* Jean: yes, it follows Lyon's proposal, a class diagram for both proposals can be done, and then compared (behavior integrated or separated)<br />
* Fabio: agrees, it sounds good<br />
* Jean: ok, both options will be then discussed next week<br />
* Gerritt: for the next week: use cases descriptions are already better now, and is the topic for discussing next week<br />
* Jean: further references to reinforce the usage of model-based, more references are still needed though <br />
* Gerritt: yes, more references would better support, please add them in the Introduction document<br />
* Jean: next version of the model by next Wednesday (email will be sent notifying it)<br />
<br />
== Actions ==<br />
* ...<br />
<br />
== Decisions ==<br />
*</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_November_22&diff=65214MBUI Telecon 2012 November 222013-04-11T10:34:11Z<p>Pbeaujea: /* Regrets */</p>
<hr />
<div>Scribed by Vivian<br />
== Present ==<br />
<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Fabio Paterno<br />
* Davide<br />
* Carmen Santoro<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Gerrit Meixner<br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Jaroslav<br />
* Sebastian Feuerstack<br />
<br />
<br />
== Regrets ==<br />
* Heiko Braun<br />
* Ignacio Marín<br />
* Dave Raggett<br />
<br />
== Scribe ==<br />
* Vivian Motti<br />
<br />
== Minutes ==<br />
<br />
We started the discussions based on the emails previously sent by Heiko, Sebastian and Paolo (concerning modelling producer - consumer)<br />
* Open issues of the AUI documents<br />
<br />
=== Modelling behaviors, events and producer-consumer relationship ===<br />
* Section meta-model: new version of the meta-model for configuration (pictures to be moved to another document)<br />
** Everything is linked to the configuration<br />
** Unify the definition (uniform names)<br />
<br />
* The UI commons will be a separate document (exclusive)<br />
** 1st drawing: configuration meta-model <br />
** Its configuration concerns a set of models (not 'just' a mapping model): composition of items<br />
** Items can be codes, models, i.e. any artifact that is general to any model<br />
** Definition compliant with configuration software management<br />
* Jean: we focus on the models<br />
** A configuration associates versions of the models: AUI, task, domain...<br />
<br />
* Davide: move the configuration to the Introduction document and call within the AUI doc?<br />
* Jean: Yes, in principle we can have an integrated view, but later, this should be moved to another document.<br />
** locate the packages, but they will be separate definitions<br />
<br />
* Jean: regarding Heiko's comments, in summary, keep behavior as event-condition-action patter<br />
** links action direct to producer, and behavior to the consumer<br />
** this pair (P,C) then connected by an interaction unit<br />
** Paolo says an action can be connected to both producer and consumer of a resource (new or existing)<br />
** understood by types<br />
* Paolo agrees<br />
* Heiko's proposal defends that producer is connected to the input, and the consumer linked to the interaction unit<br />
** further clarifications needed<br />
* For Jean, Paolo's model is symmetric and more general<br />
** because an action is linked to both: P and C of a resource <br />
<br />
* Joelle doesn't understand the link between producers and consumers<br />
** in Paollo's version (blue background)<br />
* Fabio: further clarifications needed for the role of P and C<br />
* Paollo: minutes updated (last call-meeting) -> motivations, issues raised<br />
** Connections between interaction units and behaviors<br />
** Several types of behaviors that are connected (navigations, ...)<br />
** how to model the notion of behavior?<br />
** with Producer, Consumer?<br />
** with Listener and Senders?<br />
** Resources can be consumed: data, ...<br />
** Beside the behavior model<br />
** Action: could use resources, consume resources<br />
** Behavior: collection of actions, can be connected to a unit that supports its behavior<br />
** Notion provides an underline specification (abstract approach to consider behaviors' types)<br />
** overall view<br />
* Jean: listeners can be seem as consumers, and senders as producers, however it is a more general definition<br />
* Paolo agrees<br />
* Jean: event is a sub-class of resources<br />
* Joelle: says why? it is unusual<br />
* Davide: asks whether one resource only is associated with several resources <br />
* Paolo: says it is a good question, 2 perspectives are involved<br />
** Consumers can be seem as an interface that collects resources (not specific class)<br />
** there is a method to consume a resource<br />
** consumer: group of elements that consume a set of resources<br />
** how events are shared or propagated (are consumed) among the members<br />
** event is actually consumed by the first action<br />
** 1st action reproduces the event, it is propagated until the last one consumes it<br />
** 2 ways of seeing it<br />
* not the single action, but the overall behavior consumes it<br />
** action guarantees the behavior is still valide<br />
** Events: as a sub-class of a resource<br />
*** resource is a type (we do not imposed anything specific to be relied)<br />
** Way of characterizing resources (as P or C)<br />
* Jean: another example than an event as a particular type of resources<br />
** Paollo: not physically consumed (credential of the badget ?)<br />
** Paollo: reader checks the presence of a resource that is consuming it<br />
* Davide: Heiko's propose producer may be only Input interaction unit, shouldn't it be any type? and also external entities?<br />
** Paollo: general model for defining behavior: producers and consumers may have specific inputs<br />
** Paollo: not particulary happy with this definition, model should connect unit and behavior via an event support (input of the user, but not only... other ways of generating events too), a person enters the room and triggers an event for example<br />
** characterize how an event is tiggered (not necessarily with a user input)<br />
* Joelle: IU can be both a producer and a consumer, right? To check. Support this.<br />
* Paollo: actually a P and a C are the behaviors, a IU can support the triggering of a generation of an event, and the consequences of the behavior (e.g. if a new resource is available)<br />
* Fabio: an output or a container cannot be a producer (according to the diagram)<br />
* Jean, Joelle concerns<br />
* Paollo: does not agree with such definition<br />
* Fabio: specific design, expressed by the diagram of Sebastian<br />
* Paollo: to be discussed, not yet agreed<br />
* Paollo: consumer produces, only on the side of a behavior, not the intermediate way of relating IUs and behaviors (representation support)<br />
* Jean: behavior directly connected to the IU, definition of the behavior via this channel<br />
* Paollo: not the behavior, but the event<br />
* Jean: one IU linked to one or to many behaviors (attached to it), link in this way (before in the abstract user interface model class)<br />
* Paollo: different issue, syntactic feedback, related to the UI model, behaviors related to the AUI model or to the task model (one are directly connected to the unit, others not)<br />
* Jean: link between behavior model should go direct to the UI commons package<br />
* Paollo: connections are really through the notion of events, way of relating unit to the events <br />
** events support: present and connected to events, update the version because the units could also support presentation to the user or the effects of a behavior<br />
* Jean: explained in the action part, do not want to impose a particular vocabulary now<br />
** to proceed: diagram from Paollo: more general, so define a separated behavior model linked to the UI commons model, connects to the AUI model (express behavior correctly)<br />
* Joelle: please create a consolidated version of the models, according to the discussion<br />
* Jean: Paollo's model is more general<br />
** idea: concentrating the behavior in a different model (across levels), this proposal supports this<br />
** the separate model and package must check whether the links are enough between the behavior and UI commons (for AUI, domain, task model...)<br />
** applicable to anythig, e.g. DRY principle<br />
** concentrate behavior at one place<br />
** declinate them depending on the requirements<br />
** span across abstraction levels<br />
* Gaelle: any impacts at the task meta model?<br />
* Paollo: yes<br />
* Fabio: two different abstraction level, logical activities, better not to mix the two aspects, understandable description of the concepts <br />
* Jean: could we also express a behavior at the task level?<br />
* Gaelle, Paollo agrees<br />
* Fabio: difference between task and an action: not describe low level implementation<br />
* Gaelle: do we use the behavior model to model the temporal relationships between tasks?<br />
* Fabio: now the temporal relations are describe with operators<br />
* Joelle: Jean will do a consolidation (behavior from the top level comments) then we see how it applies to the other levels (task, etc)<br />
* Paollo: task model is primarily to describe organization and the temporal relations<br />
** at the general level it also describes a transformation of the resources (like in the task), at the CTT environment this is also modelled<br />
* Jean: like information passing?<br />
** Paollo: represent the reflected transformation, I do not see a direct impact on the task meta model, but it is related...<br />
* Joelle: we will see what happens after a consolidation<br />
** more clear the models in focus<br />
* Paollo: check the minutes<br />
* Joelle: cannot understand the minutes, follow the discussions currently<br />
* Jean: direction to separate things<br />
* Joelle: advice will come later, clean version of the AUI, consensus Jean and Paollo<br />
** be careful with last minute changes... hard to follow, analyse...<br />
**Jean: Abstract behavior model (sent via emails)<br />
* Joelle: hard to follow the discussion, does it serve both as a Consumer and a Producer, check and assure this (this is the case in real life)<br />
* Jean: now we have realizations and dependencies at the UML class diagram<br />
* Fabio: separate the behavior into a separate model?<br />
* Jean: yes, following Lyon's decision<br />
* Fabio: one single place describing what the AUI is, clean, focused, <br />
* Jean: yes, it follows Lyon's proposal, a class diagram for both proposals can be done, and then compared (behavior integrated or separated)<br />
* Fabio: agrees, it sounds good<br />
* Jean: ok, both options will be then discussed next week<br />
* Gerritt: for the next week: use cases descriptions are already better now, and is the topic for discussing next week<br />
* Jean: further references to reinforce the usage of model-based, more references are still needed though <br />
* Gerritt: yes, more references would better support, please add them in the Introduction document<br />
* Jean: next version of the model by next Wednesday (email will be sent notifying it)<br />
<br />
== Actions ==<br />
* ...<br />
<br />
== Decisions ==<br />
*</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_December_13&diff=65213MBUI Telecon 2012 December 132013-04-11T10:33:19Z<p>Pbeaujea: /* Present */</p>
<hr />
<div>== Present ==<br />
<br />
* Fabio Paterno<br />
* Davide Spano<br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Jaroslav Pullman<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Dave Raggett<br />
* Pascal Beaujeant<br />
<br />
<!--<br />
<br />
* Fabio Paterno<br />
* Davide<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Sebastian Feuerstack<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Ignacio Marín<br />
* Heiko Braun<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Gerrit Meixner<br />
<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Jaroslav<br />
* Sebastian Feuerstack<br />
--><br />
<br />
== Regrets ==<br />
*Gerrit Meixner<br />
* Sebastian Feuerstack<br />
* Heiko Braun<br />
<br />
== Scribe ==<br />
* Dave Raggett<br />
<br />
== Agenda ==<br />
* Current status of the Abstract UI document<br />
* Current status of the Introductory documents<br />
<br />
<br />
<br />
== Minutes ==<br />
<br />
=== Current status of the Abstract UI document ===<br />
<br />
See Paulo's email: http://lists.w3.org/Archives/Public/public-mbui/2012Nov/0023.html<br />
<br />
and the updated meta models in the AUI draft where the behaviour is separated off and represented in terms of event-condition-action, and producers and consumers of resources.<br />
<br />
Paolo: The idea is to define behaviours separately from the rest of the AUI.<br />
<br />
We could could have a range of UI events. We would no longer have a direct connection between the abstract interaction unit.<br />
<br />
Fabio: suggest we review the changes and see if we agree,<br />
<br />
Davide: comment about the naming.<br />
<br />
Paolo: producer, consumer and reader. The presentation doesn't consume resources but rather just checks that they are there.<br />
<br />
Paolo: ... support for creation and deletion of abstract UI interactors<br />
<br />
Jean: there are now two links for the AUI editor's draft and we may soon have a third. For now the main AUI draft has a second figure for the behaviour model. The first is the updated AUI meta model, its main improvements are:<br />
<br />
# link to behaviour which will be defined in separate draft<br />
# ability aggregate sub units to combine input and output<br />
# constraints can be applied to any interaction units (or aggregations thereof)<br />
<br />
Paolo: I agree with this except for [...missed...]<br />
<br />
Jean: the unit input and output doesn't define what the unit does<br />
<br />
Paolo explains how his approach is more open to extensions with new types.<br />
<br />
Fabio: which variant would be easier for external people to understand?<br />
<br />
Paolo: that would depend on who you ask<br />
<br />
Jean: data output is data for presentation to the user.<br />
<br />
Jean and Paolo discuss some refinements.<br />
<br />
Jean: we have two decisions to make. first is whether we agree on the separation of behaviour as suggested by Paolo, and the second is on hierarchy of event types.<br />
<br />
Davide: we associate the behaviour with the interaction units for each kind of unit as appropriate.<br />
<br />
Concerned that the proposed approach is harder to understand.<br />
<br />
Dave: it would be good to have some specific UI examples and their corresponding abstract UI and behaviour models. This is necessary to explain the rationale to external people.<br />
<br />
Jean: any other comments on the meta models in the updated draft?<br />
<br />
Please make them on emain and the wiki as we are running short of time in this call.<br />
<br />
Davide: think there is another class missing, for a resource that can be read and not consumed.<br />
<br />
Paolo: yes.<br />
<br />
Jean: we hear the comments and will try to update the document accordingly.<br />
<br />
Fabio: no time today for the introductory document ...<br />
<br />
Jean: let's start with that on the next call.<br />
<br />
Fabio: that document is in a good shape, but does need to some editorial work to make it a bit more fluid. Who is leading that work? We will focus on that next week.</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2013_January_17&diff=65212MBUI Telecon 2013 January 172013-04-11T10:32:04Z<p>Pbeaujea: /* Present */</p>
<hr />
<div>== Chair ==<br />
* Fabio Paternò<br />
<br />
== Present ==<br />
<br />
* Dave Raggett<br />
* Heiko Braun<br />
* Joelle Coutaz<br />
* Davide Spano<br />
* Carmen Santoro<br />
* Jean Vanderdonckt<br />
* Jaroslav Pullmann <br />
* Nikolas Kaklanis<br />
* Fabio Paternò<br />
* Paolo Bottoni<br />
* Gaelle Calvary<br />
* Pascal Beaujeant<br />
<br />
''add yourself if your name is missing and you were on the call''<br />
<!--<br />
* Jean Vanderdonckt<br />
* Heiko Braun<br />
* Pascal Beaujeant<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Paolo Bottoni<br />
* Jean Vanderdonckt<br />
* Nesrine Mezhoudi<br />
* Davide Spano<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
<br />
* Davide Spano<br />
* Paolo Bottoni<br />
* Jaroslav Pullman<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Dave Raggett<br />
* Fabio Paterno<br />
* Davide<br />
* Carmen Santoro<br />
* Nikolas Kaklanis<br />
* Paolo Bottoni<br />
* Sebastian Feuerstack<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Ignacio Marín<br />
* Heiko Braun<br />
* Vivian Motti<br />
* Jean Vanderdonckt<br />
* Jérémie Melchior<br />
* Nesrine Mezhoudi<br />
* Joelle Coutaz<br />
* Gaelle Calvary<br />
* Gerrit Meixner<br />
* Javier Rodríguez<br />
* Cristina González<br />
* Jaroslav<br />
* Sebastian Feuerstack<br />
* Gerrit Meixner<br />
* Sebastian Feuerstack<br />
* Heiko Braun<br />
* Fabio Paternò<br />
* Jaroslav Pullmann <br />
--><br />
<br />
== Regrets ==<br />
<br />
* Gerrit Meixner<br />
<br />
== Scribe ==<br />
* Dave Raggett<br />
<br />
== Agenda ==<br />
see http://lists.w3.org/Archives/Public/public-mbui/2013Jan/0006.html<br />
<br />
== Minutes ==<br />
<br />
=== AUI meta-model ===<br />
<br />
Heiko: Paolo made some revisions to the AUI meta-model diagrams and added event support into the AUIUnit. I've uploaded them to:<br />
<br />
* https://code.google.com/p/mbui-diagrams/source/browse/#svn%2Ftrunk%2FW3C-MainPackages<br />
<br />
It's a VPP 10 format. Please let us know if this causes problem for you. In any case, we've exported the images as well:<br />
<br />
* https://code.google.com/p/mbui-diagrams/source/browse/#svn%2Ftrunk%2Fexport<br />
<br />
Paolo explains the changes that were made and asks for any observations.<br />
<br />
Fabio: which part is the connection to behaviour?<br />
<br />
Paolo: through the trigger event.<br />
<br />
Fabio: an event trigger some action but I am not sure how this is represented?<br />
<br />
Paolo: we are not representing the behaviours in detail, we have some broad categories and this can be subclassed as needed.<br />
<br />
If we are more specific, we would overly constrain what kinds of models are possible. I don't think we should do that.<br />
<br />
Fabio asks Jan for comments.<br />
<br />
Jan: we are still considering it - questions of expressivity and representation.<br />
<br />
The representation class seems to be an abstract class, is that right?<br />
<br />
Paolo: no<br />
<br />
Jan: perhaps we should be using inheritance to simplify things? This might involve multiple inheritance, e.g. from eventSupport and presentationSupport.<br />
<br />
Paolo: yes that could be a problem. Enumeration is an alternative.<br />
<br />
Jan: presentationSupport is too concrete, perhaps we could come up with a better name?<br />
<br />
Jan: we need to think about this some more to consider the implications of this new structure and then to reflect the changes back in the main diagram and put it online.<br />
<br />
Some discussion about the event hierarchy. Could this be simplified, for example by having a property indicating the type of event and other properties depending on that. Not all attributes would be applicable to all event types.<br />
<br />
<br />
=== Use cases in introductory document ===<br />
<br />
Gaelle: do we agree on switching to a single example throughout?<br />
<br />
The suggestion is to use the car rental example to illustrate different aspects of model-based UI design.<br />
<br />
Jan notes that in section 3.2, ??? should be removed <br />
<br />
Fabio: I think we need more concrete examples.<br />
<br />
Jan: so you prefer to have a comprehensive description of each use case in one place. Then to provide an account of how the model supports specific aspects of MBUI throughout the document.<br />
<br />
Fabio: yes.<br />
<br />
Jan: we would provide links to the model browser rather then embedding lots of diagrams.<br />
<br />
Fabio: what actions are needed?<br />
<br />
Gaelle: the Grenoble team will refine the document and then invite everyone to review, okay?<br />
<br />
Yes.<br />
<br />
Gaelle: we just need the detailed car rental example.<br />
<br />
Jan: The model browser (he calls it a voyager) for the car rental example can be found at http://www.fabiennemineur.be/tree<br />
<br />
We can put other examples online very quickly. You can view the task, abstract and concrete UIs.<br />
<br />
after some discussion, Jan says that there could be multiple AUI's per task model.<br />
<br />
Fabio: not sure ...<br />
<br />
Jaroslav: what about providing a context selector for different users, different devices and show how this is reflected?<br />
<br />
Jan: excellent feedback, for now it is a hierarchy, we could add a list box for this.<br />
<br />
Jaroslav: this would be showing the added value of the model-based approach<br />
<br />
Fabio: to summarise: we will different use cases for each context and put them in an appendix. In addition we will link to Jan's model browser.<br />
<br />
The appendix could get pretty long, but that's not a real problem.</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Editor%27s_Drafts&diff=63286MBUI Editor's Drafts2012-12-20T14:30:10Z<p>Pbeaujea: </p>
<hr />
<div>This is a list of editor's drafts for the Model-Based UI Working Group. We are currently using Google Docs as convenient means for collaborative editing. When the Working Group judges a document is ready for publication as a W3C Technical Report, the document will be exported to HTML and checked against W3C's publication rules.<br />
<br />
* [https://docs.google.com/document/d/1Xp50GZ8EfY017AT_pCMBq5PeK8cwNEZi1a8hXexJkCc/edit Introduction to Model-Based User Interface Design] Working Group Note expected Q4 2012<br />
<br />
* [https://docs.google.com/document/d/1gt5c_M13DZFgdE84j8MdYml7nNC0u-u7AgnbnES_8Ho/edit Glossary of MBUI-Terms] Working Group Note expected Q4 2012<br />
<br />
* [https://docs.google.com/document/d/18_lPkx1boQgoGurMYgTSa4NzZIhlrvFmgAZDS-a4rT8/edit Adaptation of User Interfaces] Working Group Note expected Q4 2012<br />
<br />
* [http://www.w3.org/TR/2012/WD-task-models-20120802/ MBUI - Task Models] First Public Working Draft - 2 August 2012, a revised draft is in preparation<br />
** [https://docs.google.com/document/d/19FxTUuZDlnVKxa5CAsefaaBQdZmVAMLMq12UfCmI49Q/edit MBUI - Task Models] <br />
** [http://www.w3.org/2011/mbui/drafts/task-models/ draft FPWD]<br />
<br />
* [https://docs.google.com/document/d/1UGZz_xaPuSbMtRb4a-14tM9CM8tHmbEWuLVuNNnx25o/edit MBUI - Abstract User Interfaces] First Public Working Draft expected Q4 2012<br />
** [https://docs.google.com/document/d/1Tj-h3-mM0gaD6CYU89qdZiNVCIS8AdFgxVktwHYzZBI/edit MBUI - Configuration Model] <br />
** [https://docs.google.com/document/d/1tg0GeQvZ_iEzl5EzO30VMQQTYpUgpo8Ak5Qba2U4jZU/edit MBUI - UI Commons] <br />
<br />
* [https://docs.google.com/document/d/1-Nzb3_R6bJnqe7CZ7_mVJLRaqTVDz26ssNLV_pSW_TQ/edit MBUI - User Models]<br />
<br />
<br />
=== Exporting Google doc to clean HTML ===<br />
<br />
Google Docs provide a means to export documents to HTML, but the markup is messy. Dave has extended HTML Tidy to support this, but you still need to do quite a bit of manual editing afterwards, see source of draft FPWD for task models.<br />
<br />
We may want to consider switching to using the wiki for editor's drafts as these are easily converted to nicely nested sections in HTML5 using the following Chrome extension:<br />
<br />
* http://www.w3.org/2012/07/wikibook/<br />
<br />
This would also ensure that the document content is held on the W3C server without the (very small) risk of Google dropping their document service.</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Editor%27s_Drafts&diff=63285MBUI Editor's Drafts2012-12-20T14:28:06Z<p>Pbeaujea: </p>
<hr />
<div>This is a list of editor's drafts for the Model-Based UI Working Group. We are currently using Google Docs as convenient means for collaborative editing. When the Working Group judges a document is ready for publication as a W3C Technical Report, the document will be exported to HTML and checked against W3C's publication rules.<br />
<br />
* [https://docs.google.com/document/d/1Xp50GZ8EfY017AT_pCMBq5PeK8cwNEZi1a8hXexJkCc/edit Introduction to Model-Based User Interface Design] Working Group Note expected Q4 2012<br />
<br />
* [https://docs.google.com/document/d/1gt5c_M13DZFgdE84j8MdYml7nNC0u-u7AgnbnES_8Ho/edit Glossary of MBUI-Terms] Working Group Note expected Q4 2012<br />
<br />
* [https://docs.google.com/document/d/18_lPkx1boQgoGurMYgTSa4NzZIhlrvFmgAZDS-a4rT8/edit Adaptation of User Interfaces] Working Group Note expected Q4 2012<br />
<br />
* [http://www.w3.org/TR/2012/WD-task-models-20120802/ MBUI - Task Models] First Public Working Draft - 2 August 2012, a revised draft is in preparation<br />
<br />
<br />
* [https://docs.google.com/document/d/19FxTUuZDlnVKxa5CAsefaaBQdZmVAMLMq12UfCmI49Q/edit MBUI - Task Models] First Public Working Draft July 2012<br />
** [http://www.w3.org/2011/mbui/drafts/task-models/ draft FPWD]<br />
<br />
* [https://docs.google.com/document/d/1UGZz_xaPuSbMtRb4a-14tM9CM8tHmbEWuLVuNNnx25o/edit MBUI - Abstract User Interfaces] First Public Working Draft expected Q4 2012<br />
** [https://docs.google.com/document/d/1Tj-h3-mM0gaD6CYU89qdZiNVCIS8AdFgxVktwHYzZBI/edit MBUI - Configuration Model] <br />
** [https://docs.google.com/document/d/1tg0GeQvZ_iEzl5EzO30VMQQTYpUgpo8Ak5Qba2U4jZU/edit MBUI - UI Commons] <br />
<br />
* [https://docs.google.com/document/d/1-Nzb3_R6bJnqe7CZ7_mVJLRaqTVDz26ssNLV_pSW_TQ/edit MBUI - User Models]<br />
<br />
<br />
=== Exporting Google doc to clean HTML ===<br />
<br />
Google Docs provide a means to export documents to HTML, but the markup is messy. Dave has extended HTML Tidy to support this, but you still need to do quite a bit of manual editing afterwards, see source of draft FPWD for task models.<br />
<br />
We may want to consider switching to using the wiki for editor's drafts as these are easily converted to nicely nested sections in HTML5 using the following Chrome extension:<br />
<br />
* http://www.w3.org/2012/07/wikibook/<br />
<br />
This would also ensure that the document content is held on the W3C server without the (very small) risk of Google dropping their document service.</div>Pbeaujeahttps://www.w3.org/wiki/index.php?title=MBUI_Telecon_2012_April_19&diff=57948MBUI Telecon 2012 April 192012-04-19T14:17:06Z<p>Pbeaujea: </p>
<hr />
<div>== Agenda ==<br />
<br />
* Current status of the working group note<br />
* Current status in the two task forces (Task model, Abstract UI)<br />
* Next F2F meetings (June in Pisa, October/November at the Tech Plenary in Lyon?)<br />
<br />
== Present ==<br />
<br />
* Sebastian, Nikos, Jaroslav, Gerrit, Dave, Vivian, François, Pascal, Yaskari, Fabio, Carmen, Martin, <br />
<br />
Please correct the names as I am unsure of spelling, and didn't hear everyone clearly!<br />
<br />
== Regrets ==<br />
<br />
== Chair ==<br />
<br />
* Gerrit<br />
<br />
== Scribe ==<br />
<br />
* Dave<br />
<br />
== Minutes ==<br />
<br />
Vivian: for the AUI spec we will update the Google Docs document, but we don't have a complete document as yet. She has also been in touch with Jaroslav on the task models.<br />
<br />
Gerrit asks Fabio what has been done on the Task Models task force.<br />
<br />
Fabio: we suggest starting with CTT and asking for input on potential changes. We can start to analyse different proposals, but that would slow down the initial publication, so we prefer a pragmatic approach.<br />
<br />
Gerrit: for me this sounds okay.<br />
<br />
Fabio: we will put a first version of the class diagram and a description of the various elements into the draft specification document.<br />
<br />
Gerrit: and we can then ask for input on what variations there are across different approaches. Is this okay for other people? Any other suggestions? [None heard]<br />
<br />
Gerrit asks Jaroslav to repeat himself due to poor audio earlier on.<br />
<br />
Jaroslav: I will contributing to the terminology section of the introductory note, and to the section on when to use MBUI. Vivian has sent me some relevant documents for me to read through. You can then provide me with feedback.<br />
<br />
Dave asks Gerrit for any feelings on deadlines for getting the documents ready.<br />
<br />
Gerrit: suggest finalizing use cases by next Thursday. Sebastian has done a good job on copying use cases into the draft note from the wiki. How long will ISTI need for a first draft for task models?<br />
<br />
Fabio: a first draft should be possible for next week?<br />
<br />
Gerrit: and how about you Vivian?<br />
<br />
Vivian: yes, we could provide a first draft for the AUI for next week, we can adapt some of the content from the Serenoa deliverable.<br />
<br />
Gerrit: we should then review these drafts in the next call, and give people some time for making comments, e.g. one or two weeks. This will allow people to look at other proposals <br />
<br />
== Next Face to Face Meeting ==<br />
<br />
Gerrit asks if we could have a two day meeting in Pisa?<br />
<br />
Fabio: that should indeed be possible. We discussed this at the Serenoa meeting a few days back, and wondered if we could start Monday morning and finish Tuesday lunch time, and then start the Sereno meeting in the afternoon and continue it the next day.<br />
<br />
Gerrit: that sounds good, i.e. Monday June 11 - Tuesday June 12<br />
<br />
<br />
== MBUI Meeting at W3C Tech Plenary in Lyon, November 2012 ==<br />
<br />
'''Action''': Dave to provide info about the TP and add a new slot for the meeting in our wiki.<br />
<br />
== Any Other Business ==<br />
<br />
Jaroslav likes the idea of including some more practical examples of applying the models. Dave had added a slot for that to the draft Note.<br />
<br />
Dave: we could perhaps use the examples from the Serenoa M18 demo?<br />
<br />
Carmen: that would be useful.<br />
<br />
Dave: I will have a go, but will be rather busy over the next few days.<br />
<br />
Jaroslav: it would also be good to point to real world applications of MBUI design even if they are using proprietary modelling languages.<br />
<br />
Fabio: we also have some papers that describe case studies in different domains, we could provide references to.<br />
<br />
Jaroslav: it would be great to provide pointers to industrial applications in particular.<br />
<br />
Gerrit: I could contribute some info on automotive applications, and will ask the company concerned.<br />
<br />
Jaroslav: perhaps you could also see if they are interested in participating in the standardization? Having practical real world stories is really important.<br />
<br />
Gerrit: looking at the company's website, they give a list of benefits.<br />
<br />
Jaroslav: perhaps SAP could also help?<br />
<br />
=== Invited Experts? ===<br />
<br />
Dave notes that we have people on the list who aren't registered participants, and would like to know who would like to become invited experts.<br />
<br />
Gerrit: we should add a section to the wiki on participation.<br />
<br />
Sebastian: I would like to be considered as an Invited Expert.<br />
<br />
'''Action''': Dave to provide information on becoming an Invited Expert on the wiki and to the mailing list.<br />
<br />
== Next Call - April 26 ==<br />
<br />
Dave gives his regrets for the next call as he will travelling.</div>Pbeaujea