W3C

MMI Use Cases

W3C Editors Draft 5 December 2016

This Version:
tbd
Latest Published Version:
tbd
Latest Editor's Draft:
https://w3c.github.io/mmi/usecases/Overview.html
Previous version:
none
Editors:
Debbie Dahl, W3C Invited Expert
B Helena Rodriguez, W3C Invited Expert
Kaz Ashimura, W3C
Participate:
We are on GitHub
File a bug
Commit history
Mailing list

Abstract

TBD

MMI as the possible user interface layer for the Web of Things (WoT) framework. MMI integrates various user interface modalities (and devices which provide modlities) for WoT purposes.

Status of This Document

TBD

1 Template for Use Cases

This is a generic template for proposing use cases.

Submitter(s): company (name), ...

Tracker Issue ID: ISSUE-NN

Category: How would you categorize this issue?

  1. gap in existing specifications (=> IG to draft a proposal for an existing WG), or how does this work in existing architecture?
  2. what implications does this UC have for discovery and registration?
  3. require new specification/WG (=> IG to draft a proposal for W3C Director)
  4. can be addressed as part of a guidelines document to be produced by the IG (=> The proponent should draft some text for the document)

Class: How would you classify this issue?

  1. Platform-level Use Cases, e.g., synchronizing multiple MCs
  2. Chunk of MC Use Cases, e.g., MMI output and MMI input
  3. Various MCs as extensios of Web Applications

Status: Who would work on this use case, progress, etc.

Relationship between Entities included in this use case:

relationship-between-entities

Entity: Specific systems could include human beings or devices, so "entity" could be used to mean either one

Description:

Motivation:

Dependencies:

Viewpoint:

What needs to be standardized:

Comments:

2 Use Cases

Note on Accessibility/Security/Privacy/Safety

2.1 High priority use cases

2.1.1 UC-2: Interaction with Robots

Submitter(s): Kaz & Debbie

Reviewer(s): Masahiro, Kosuke, Shinya

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Status: The Japanese participants would be the best people to elaborate on this. Helena and Raj may also be interested.

Description:


Motivation:

Dependencies:

Gaps

The current MMI Life Cycle events don't have the concept of scheduling or events scheduled to occur in the future. The simplest approach is to use the ExtensionNotification event, but that's not very standardized. Other ideas would be to use SMIL (but that's mostly for media), MIDI, SCXML, use the EMMA output functionality, or introduce a new attribute into the Life Cycle events. In addition to starting at a certain time, scheduling also introduces the idea of recurring events, for example, every day at 5:00.

What needs to be standardized:

Comments:

2.3.4 UC-7: Multimodal Appliances

Submitter(s): Kaz, Dirk (Harman)

Reviewer(s): Shinya, Masahiro, Kosuke, Ryuichi

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Status: The Japanese participants would be the best people to elaborate on this

Relationship between Entities included in this use case:

relationship-between-entities

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

Note:"UC-18 smart remote for appliances" has been merged with this use case.

2.1.3 UC-12: Smart Car Platform

Submitter(s): Kaz, Dirk (Harman)

Reviewer(s):

Tracker Issue ID: @@@

Category: 1. gap in existing specifications

Class: Various MCs

Status: Dirk would be the best person to elaborate on this.

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.1.4 UC-19 Handling millions of components

Submitter(s): Kaz, Debbie, Helena

Reviewer(s): Masairo, Shinya

Tracker Issue ID: @@@

Category: @@@

Class: Platform level

Status: Helena would be the best person to elaborate on this.

Description:


Motivation:

Dependencies:

Gaps

Requirements

What needs to be standardized:

Comments:

2.1.4 UC-19 Handling millions of components

Note: There two "UC-19" sections. May I merge these???

Submitter(s): Kaz, Debbie, Helena

Category: 2 does have implications for discovery and registration?

Class: Various MCs

Status: Submitted to be commented.

Objects

Fuctions of Objects
Object Identify Track Accountability
User Devices Multiple user devices. @ @
Master Display The display to execute the current application.    
Master Haptics Actuator The haptics actuator used in the current appication.    
Master Audio The component rendering the audio content.    

Actions


Description:

Motivation:

Dependencies:

Viewpoint:

What needs to be standardized:

Comments:

2.1.5 UC-22 Smart Hotel Room

Submitter(s): Debbie Dahl

Tracker Issue ID:

Category:

Class: Various MCs How would you categorize this issue?

  1. gap in existing specifications (=> IG to draft a proposal for an existing WG), or how does this work in existing architecture?

See https://www.w3.org/2002/mmi/2016/hotelUseCase/ for an example of how this would work in the existing architecture.

  1. what implications does this UC have for discovery and registration?

Discovery and Registration functions are very important for this use case:

  1. require new specification/WG: This can be addressed through existing specifications (EMMA, MMI Architecture, possibly ARIA), additional work on early stage specifications in progress (Discovery and Registration), existing work on security and privacy, and possibly new work on biometrics (for user authorization).
  2. can be addressed as part of a guidelines document to be produced by the IG (=> The proponent should draft some text for the document)

The requirements can be partially addressed through the existing MMI Architecture specification.


Actions

Description:

This use case describes a Smart Hotel Room, which authorizes an arriving guest to control the room and access its capabilities. Because the guest will only be staying in the room a short time and doesn't have time to learn a special GUI interface, a natural (speech or language) user interface is important. In addition, because rooms vary in their capabilities, a discovery process is essential, so that the user can become aware of the room's capabilities. Security and privacy are important for keeping the guest safe. Also, levels of authorization will be needed. For example, a child guest might be allowed to control the lights, but not the HVAC. Finally, note that this use case is closely related to UC-20 on emergency notifications. An application that allows a user to control a hotel room could also offer emergency notifications.

Motivation:

Reduces user frustration when users enter a new environment, especially when there are accessibility issues. for example, guests with limited mobility might find it difficult to use some physical controls.

There needs to be additional work on discovery and registration and on security and privacy to make this use case possible.

Dependencies:

What needs to be standardized:

Comments:

Submitter(s): company (name), ...

2.1.6 UC-23 Collaborative content sharing in a smart space

Submitter(s): Branimir (Wacom)

Category: 2 does have implications for discovery and registration?

Class: Various MCs

Status: Who would work on this use case, progress, etc.

Objects

Fuctions of Objects
Object Identify Track Accountability
User Device One or multiple user devices. @ @
Master Device The device of the moderator. @ @
Master Display The display to share visual content.    
Master Audio To share audio content.    

Actions


Description:

Motivation:

Dependencies:

Viewpoint:

What needs to be standardized:

Comments:

2.2 Other use cases

2.1.1 UC-1: Synchronizing video stream and HMI (e.g., remote surgery)

Submitter(s): W3C (Kaz Ashimura)

Reviewer(s): Masahiro, Kosuke, Shinya

Tracker Issue ID: ISSUE-NN

Category: 1. gap with existing specification

Class: Platform level

Description:

Motivation:


Dependencies:

2.3.2 UC-3: Wearable devices

Submitter(s): Kaz

Reviewer(s): Shinya, Yasuhiro

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:


Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:


2.2.1 UC-4: MMI output devices: Controlling 3D Printers using a remote HMI

Submitter(s): Kaz

Reviewer(s): @@@

Tracker Issue ID: @@@

Category: @@@

Class: Chunk of MC

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.2.2 UC-5: MMI input devices: Video Cameras work with HMI and sensors

Submitter(s): Kaz

Reviewer(s): @@@

Tracker Issue ID: @@@

Category: @@@

Class: Chunk of MC

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:


2.2.3 UC-6: Multimodal Guide Device at Museums

Submitter(s): Kaz

Reviewer(s): Shinya, Masahiro, Kosuke

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.3.5 UC-8: MIDI-based Speech Synthesizer

Submitter(s): Kaz

Reviewer(s): Masahiro, Shinya, Kosuke

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:


2.1.2 UC-9: Collaboration of multiple video cameras

Submitter(s): Kaz

Reviewer(s): @@@

Tracker Issue ID: @@@

Category: @@@

Class: Platform level

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.3.6 UC-10: Geolocation device, e.g., GPS, as a MC for Location-based Services

Submitter(s): Kaz

Reviewer(s): Kosuke

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.3.7 UC-11: Smart Power Meter

Submitter(s): Kaz

Reviewer(s):

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.3.9 UC-13: MMI Automatic visual data annotator

Submitter(s): Helena

Reviewer(s):

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.3.10 UC-14: Multimodal e-Text

Submitter(s): Kaz

Reviewer(s):

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.3.11 UC-15: English standardized tests through an MMI interface. OPENPAU project

Submitter(s): Jesus Garcia-Laborda, Teresa Magal-Royo

Reviewer(s):

Tracker Issue ID:

Category: Computer Aided Learning language, Accesibility, MMI educational interfaces, Second language skill acquisition.

Class: Various MCs

Description: The OPENPAU is a research project funded by the Spanish Government for 3 years and has worked on a navigation interface (keyboard, voice and touchscreen) to develop english tests using Moodle©.

1. Multiple modalities have been used to access the contents for second language acquisition e-learning.

2. The MMI Architecture has been used to synchronize multiple modalities of input navigation.

Motivation:

Specific developments to improve the accessibility of educational content for language learning environments by using MMI interfaces or via keyboard, voice and touchscreen.

Dependencies:

1. HTML5, CSS 2. Moodle© 3. TabletPc 4. Accesibility 5. Chrome (voice recognition browser automatically integrated)

Gaps

1. Specific developments in Moodle© (OS) that allow access to educational content accessible via keyboard, voice and touchscreen synchronously.

2. Specific examinations or tests of skill acquisition in languages as a second language in Moodle © (OS) that allows access to educational content accessible via keyboard, voice and touchscreen synchronously.

What needs to be standardized:

6. Specific educational developments in Moodle © (OS) that allows access to content accessible via keyboard, voice and touch in synchronously.

7. Oriented user interfaces in conducting tests that allow the use of integrated MMI navigation.

Comments:

2.3.12 UC-16: Remote watching using video camera and MMI interfaces

Submitter(s): Kaz

Reviewer(s): Masahiro, Kosuke, Shinya

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

home

Motivation:

Dependencies:

Gaps

What needs to be standardized:

Comments:

2.1.2 UC-17: User interface as a sensor

Submitter(s): Helena

Reviewer(s):

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

Motivation:

Dependencies:

Gaps

Requirements

What needs to be standardized:

Comments:

2.3.15 UC-20 Emergency evacuation information and notification system

Submitter(s): Kaz, Debbie

Reviewer(s):

Tracker Issue ID: @@@

Category: @@@

Class: Various MCs

Description:

Motivation:

Dependencies:

Gaps

Requirements

What needs to be standardized:

Comments:

2.1.4 UC-21 Collaborative session by remote players

Submitter(s): Kaz, Masahiro, Shinya

Reviewer(s):

Tracker Issue ID: @@@

Category: @@@

Class: Platform level

Description:

Motivation:

Dependencies:

Gaps

Requirements

What needs to be standardized:

Comments: