W3C

List of comments on “Delivery Context: Client Interfaces (DCCI) 1.0” (dated 4 July 2007)

Quick access to

There are 4 comments (sorted by their types, and the section they are about).

question comments

Comment LC-1918
Commenter: Debbie Dahl <dahl@conversational-technologies.com> on behalf of MMI WG (archived message)
Context: in
assigned to Keith Waters
Resolution status:

Registration for events:
MMI Architecture allows Interaction Manager (IM) and Modality
Components( MC) to be distributed. And except in the case of
nested-modality components, modality components communicate with each
other only through the Interaction Manager. Given this principle of
MMI architecture, MMI authors would be required under the proposed
DCCI spec, to implement another DCCI-interface component to register
and obtain the local DCI events to pass on to IM for every device on
which any modality component is running..

For example, a device-client could be getting the text-to-speech
streamed from a TTS server. Now, if the user mutes the speaker on the
device, an event gets generated on the local device through DCI, but
the IM running on the server (a different device) will not get this
event to signal the TTS-component to stop streaming audio, as it will
not have a way to remotely register and get this event from the
device. So, under the proposed specification, an MMI author would be
forced to implement another MMI component just for passing on DCI
events to the IM. Please, note that the local Modality Component
cannot directly do this job, as the local Modality Components are to
be implemented as black-boxes and as such cannot snoop on these events
and determine which ones should be passed-on to the Interaction
Manager.

We would like to hear from DCI-WG on how this remote-registration for
events could be done, under the the current DCI framework.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

general comment comments

Comment LC-1917
Commenter: Debbie Dahl <dahl@conversational-technologies.com> on behalf of MMI WG (archived message)
Context: 1.1 Uses for DCCI
assigned to Keith Waters
Resolution status:

-Registration for events:

-Notification of Events ( Section 1.1 Uses for DCI ):

"...It also provides notifications when properties change.."

While the specification describes use of DOM3 events, given that DCCI
will have a different root-element ( namespace), it is not clear how
components that want the notifications register for the
same..
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

editorial comments

Comment LC-1785
Commenter: Yi JongPil (aka JP) <jp.yi@samsung.com> (archived message)
Context: Abstract (Spelling of the word programing)
assigned to Rhys Lewis
Resolution status:

Hi editor.

I have a comment for spec.

# miss spelling

Original

This document defines platform and language neutral programing interfaces that provide Web applications access to a hierarchy of dynamic properties representing device capabilities, configurations, user preferences and environmental conditions.

Correction

This document defines platform and language neutral programming interfaces that provide Web applications access to a hierarchy of dynamic properties representing device capabilities, configurations, user preferences and environmental conditions.

Best Regards.
From JP.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1919
Commenter: Debbie Dahl <dahl@conversational-technologies.com> on behalf of MMI WG (archived message)
Context: 2.1 Interfaces
assigned to Keith Waters
Resolution status:

Section 2.1 of DCCI specification on Interfaces :

"....DCCI is an interface that focuses on making properties from the
delivery context available to code executing within a web client
[GLOSS]...

The glossary referenced above DOES NOT contain definition of
web-client, but client as described below :

Client ( www.w3.org/TR/di-gloss)
The role adopted by an application when it is retrieving and/or
rendering resources or resource manifestations.
This term was taken verbatim from Web Characterization Terminology
& Definitions Sheet.

Further, from MMI perspective clients needs not be web-clients (
meaning implementing HTTP protocol for communication with servers..)
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Add a comment.


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: Overview.php,v 1.46 2013-10-04 08:11:33 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org