Model-Based UI

Abstract UI

http://www.w3.org/2011/mbui/drafts/abstract-ui/

Vivian sent Dave the XML Schema which is now normatively linked from the draft

Davide: this schema is for the meta model and not for serializing AUI models.

Paolo: yes. it is generated automatically from the UML

Davide: for the task models, we chose to use a schema that could be used for serialization, and it would be good if the AUI spec was the same

Paolo: how did you produce the task model schema?

Davide: by hand
... I could produce one for the Abstract UI if you like, but would need someone to check it against the metamodel

Paolo: yes, and I can check it for you.

Dave: is there a chance for having that for next week's call?

Davide: I will send Paolo a daft on Wednesday

Paolo: ok , I will then check it on Thursday

Introductory document

Joelle: a number of people sent comments, and Gaelle and I made such changes, see the red text

Jean wanted to have this paragraph on model-based design, and we think here is a good place.

Does anyone agree with this?

[yes]

Joelle: an action here is for UCL to ...
... we have a complementary document with additional details on use cases.

Jaroslav: we started to work on the separate Use Case doc at the Munich Face to Face

see https://docs.google.com/document/d/1BnITI7AoeZAlOMiRvLW0Yt45nsx9wCT3AVTgmLDu2G0

Joelle: we aren't referencing the external car rental use case document, are we?

There is no concrete CUI example in the introductory document. I think we should have one.

Paolo: I see your point. The idea was to put a overview into the introductory document and full details for car rental into a separate doc.

Joelle: I would like to see UCL reconcile the two documents.

What is missing is an explicit description of the task requirements and the context of use.

Joelle asks Paolo if he can rewrite the Story Editor use case for consistency with the others.

Paolo: ok

(see Joelle's notes in the google doc)

Joelle: we are fairly close to being done ...

This introductory document is for people new to model-based UI, so we need to avoid going into too deep technical details.

Joelle: we need all of the use cases to be consistent in structure and level of details.

Paolo: yes, I understand that

Joelle: I will be busy for the next two weeks and won't be able to attend the call due to reviews

Dave: UCL isn't on the call so we can't action them, but Paolo, could you commit to revising the Story Editor use case for the next call.

Joelle: every use case owner needs to check that it is consistent with the car rental use case description.

Dave: UCL owns the Digital Home

Davide: I will ask Fabio if he can review that use case

Dave: UC3 is minimalistic UI, I will email Gerrit and Marc to review that one
... UC4 is Story Editor which Paolo owns

Joelle: UC5 and UC6 need work from Sebastian and Gerrit.
... we own UC7 (migratory UI)

Paolo: this is a little long

Joelle: if you want to shorten this feel free to have a go ...

Paolo: this looks like two use cases

Laufe spots a small error and fixes it

Joelle: it used to be two separate use cases, do you want us to separate it again?

Paolo: I would leave that to your judgement

Joelle: I want to hear from others on this

Dave: let's first get all of the use cases into a consistent form before making a final decision.

Glossary

Dave: Jaroslav, you were making some changes?

Jaroslav: I haven't got feedback from Fabio, e.g. missing references.

Dave: can you send me a version for the website?

Jaroslav: yes, I will do that asap.
... I am sure there may be some more small changes once people have reviewed the draft

Any other business?

[no]

Dave wishes Joelle all the best for her review!