Contents

• Why this matters!
• Serenoa deliverables as standardization candidates
• Model-Based UI Design Working Group
• Ubiquitous Application Design Community Group
• Future work

Why this matters!

• Increasing range of devices and platforms
• Desktop, smart phone, tablet, TV, wearables, cars, ...
• Different languages: HTML5, Java, Objective C, C#, ...
• Need for dynamic adaptation to the context of use
  • Personal preferences and needs, including accessibility
  • Changes in ambient light, ambient noise, network connectivity, indoor and outdoor location, changes in social context beyond public/private, ...
• Application developers are unware of the potential of model-based UI design techniques
• There is a lack of effective design tools for real-world application development

Standardization Candidates

• Advanced Service Front End Description Language (ASFE-DL)
  • UI modelling language suitable for standardization
• Advanced Adaptation Logic Description Language (AAL-DL)
  • Rule language suitable for standarization
• CARF - context aware reference framework
  • Ontology as basis for a standard vocabulary?
• CADS -- context aware design space
  • theoretic and conceptual unifying approach, not suited for standardization

Model-Based UI Design Working Group

Mission to define standards for interchange of model-based user interface designs for context aware service front ends

• Launched November 2011
  • Chairs: Gerrit Meixner, Fabio Paternò
  • Home page
  • Charter (expires 30 November 2013)
  • Initial work on gathering use cases and examples of model-based user interface design languages, including ASFE-DL and ConcurTaskTrees
  • Followed on from W3C Model-Based UI Incubator Group and Rome 2010 Workshop
• Chartered Scope

  Use cases and Requirements

  As needed to guide and justify the design decisions for the development of the specifications.

  Specification of meta-models for interchange of models between authoring tools for (context aware) user interfaces for web-based interactive application front ends

  This could take the form of UML diagrams and OWL ontologies, and cover the various levels of abstraction (e.g. as defined in the Cameleon reference framework, as well as that needed to support dynamic adaption to changes in the context).

  Specification of a markup language and API which realize the meta-models.

  This is expected to draw upon existing work such as (but not restricted to) Concur Task Trees (CTT), Useware Markup Language (useML), UsiXML or UIML.

  Test assertions and Test suite for demonstrating interoperability

  This is needed to support progress along the W3C Recommendation Track, and in particular, to exit from the Candidate Recommendation phase.

  Model-based user interface design primer

  An explanation/guideline for how to apply the specifications to support the development of the associated use cases.

  Open Source Implementations

  Working Group members may wish to develop open source implementations of authoring tools to demonstrate the potential, and for use in developing and applying the test suite described above.

• Participating Organizations
  • UCL, University of Grenoble, Telefónica, Future Web Technology Labs, Fundacion CTIC, Institut Telecom, Centre for Research and Technology - Hellas, ETRI, Department of Informatics - PUC-Rio, Federal University of Sao Carlos - Brazil, University of Heilbronn, DFKI, CNR, Fraunhofer Gesellschaft, Red Hat
• Specifications
  • MBUI Task Models, Working Draft
  • MBUI Abstract UI, First Public Working Draft
• Working Group Notes
  • Introduction to Model-Based UI Design
  • Glossary of Terms for Model-Based UI

Ubiquitous Application Design Community Group

Seeks to bring together developers and researchers to explore and promote techniques for context aware design that separates out different aspects of design to speed development and reduce costs. We will do this through gathering and discussing techniques, together with developing open source demonstrators.

• Home page
• W3C Community Group: open forum, without fees
• Takes up from where the MBUI Working Group leaves off
• Foster discussion between developers and researchers
• Promote model-based user interface design
• Gather implementation feedback for task models and abstract UI specifications
• Gather use cases, requirements and suggestions for future standardization
• Assist with preparing Working Group charters for further standardization work

Future Work

• Need for extended discussion between developers and researchers
• Further standardization will depend on demonstrating industry support
• Opportunities for standards relating to:
  • Richly annotated domain models
  • Task models -- following through on MBUI Task Models
  • Abstract UI models -- following through on MBUI Abstract UI
  • Concrete UI models for common platforms (desktop, smart phone, tablet, TV, wearables, cars, ...)
  • Adapdation rules -- build upon experience with AAL-DL
  • Rich models of the context of use
• Support for live editing by distributed teams and different roles
• Support for smart design assistants that help to synchronize changes across different levels of abstraction