Comments on DCI

Dear Device Independence Working Group,

The Multimodal Interaction Working group [1] has prepared the following
comments on the 
second last call working draft of Delivery Context: Interfaces (DCI)
Accessing 
Static and Dynamic Properties [2]
http://www.w3.org/TR/2005/WD-DPF-20051111/


best regards,

Debbie Dahl,
MMI Working Group Chair

MMI Comments:

Comments on Content: We notice from section 4.1.2 that DCI access to remote
device properties is supported.  Consider the case where multiple devices
are cooperating in a single application.  If one of the devices wants to
monitor properties on all the others, will it have a single instance of the
DCI, with a separate branch for each device, or will it have multiple
instances of the DCI?  From section 4.1.6, it would appear that the former
would be the case, but we would like this to be made explicit.  Secondly, do
questions of efficiency arise with remote devices?  The obvious way to
implement a remote DCI interface is to maintain a local copy which would be
updated via update events.  Could there be cases where the remote DCI
interface needed less frequent updates than one local on the device?  There
will be implementation-specific ways of handling this, but is a more general
means needed? 

Editorial Comments:  

1) Section 2, point 5 contains "To be discussed 16th Sept. f2f"  Should be
replaced with results of the discussion.

2) Appendix B.1 Simple Usage.  No simple example is provided.  
3) Appendix B.2.  The prose says "set.the update frequency to 20 seconds"
but the comment in the code says "set the update event to be triggered when
the browser has moved 50 meters."  The actual code matches the comment, so
the prose probably needs to be changed.  

 
[1] http://www.w3.org/2002/mmi/
[2] DCI http://www.w3.org/TR/2005/WD-DPF-20051111/

Received on Tuesday, 20 December 2005 18:29:40 UTC