Review comments Discovery & Registration of Multimodal Modality Components sections 1-3

Hey there,

I started reviewing the Discovery & Registration of Multimodal Modality
Components working draft. Here are some first comments on sections 1-3

Abstract
--------

This document is addressed to people who want either to develop Modality
Components for Multimodal Applications distributed over a local network or
"in the cloud"
-->
This document is addressed to people who want to develop Modality Components
for Multimodal Applications distributed over a local network or "in the
cloud"

...in order to preserve the overall state of the distributed elements.
--> At this point it is not clear why there are distributed elements. Please
explain the rational

In this way, Modality Components can be composed...
--> "In this way is not pointing towards a solution. Better: "Therefore,
Modality Components can be composed..."

Status of This Document
-----------------------

We modify the
state diagram
--> no newline after "the"

1. Introduction
--------------

To the best of our knowledge, there is no standardized way to build a web
Application that can dynamically combine, and control discovered components
by querying a registry build based on modality states. 
--> This is a very academic style of writing
Also: What about UPnP (https://openconnectivity.org/), SDP
(https://tools.ietf.org/html/rfc4566)

First, we propose to define a new component ...
--> Is a Standard proposing something or rather defining how it should be
done?

What is the relation of the table to the text? IMHO, it should be referenced
somehow.

2. Domain Vocabulary
--------------------

Interaction Context
--> Why is there a new definition of interaction context instead of reusing
the established term of a context in the MMI specification? What is the
actual difference between these two?

Multmodal System
For the purposes of this document, a Multimodal System is any system
communicating with the user through different modalities such as voice,
gesture, or handwriting in the same interaction cycle identified by a unique
context. 
--> According to this definition, 2 users using the same setting of modality
components but interacting in 2 different sessions at the same time or one
after the other would use 2 different multimodal systems

In this light: Do we need the terminology of a session or is this covered by
context?

Modality Component
Does this definition cover sensor data?

Application
The difference to Multimodal System does not become clear. A term must not
be explained with the help of other undefined terms like "rich multimodal
user experience"

Push notifications
...to send new events or data to the client through progressive download or
long-polling HTTP request from the client
--> Why is this restricted to HTTP. This protocol can be an example but the
MMI specification allows for more variations at this point 

3. Scope
--------
The semantics of the NewContextRequest event is different and mostly
oriented to the interaction phase, while the registering process is part of
a previous phase, ...
--> There is nothing know about the different phases so far

On the other hand, the Extension and Status notifications are dedicated to
the exchange of interaction data, ...
--> The Extension and Status notifications are dedicated to the exchange of
interaction data, ...

For example, at load-time, when the system prepares and registers the
information about the Modality Components (availability, technical
characteristics, cost).
--> This is not a sentence

In all these cases, the Modality Components enter and quit the multimodal
system dynamically, and they must declare to the system, their existence,
availability and capabilities in some way:
--> In these use cases, the Modality Components may enter and quit the
multimodal system dynamically. Hence, they must declare to the system, their
existence, availability and capabilities in some way:

Figure 1:
Why is the Interaction Manager part of the Multimodal Framework but not the
modality component?

The term "Multimodal Framework" should be avoided since it is already used
at https://www.w3.org/TR/mmi-framework/

The figure refers to Pull and Push notifications but only Push appears as a
term in the vocabulary. Is there a reason for it?

Dirk

Received on Monday, 28 November 2016 10:31:23 UTC