- From: Rafah A Hosn <rhosn@us.ibm.com>
- Date: Fri, 6 Jan 2006 10:20:59 -0500
- To: www-di@w3.org, w3c-mmi-wg@w3.org
Hello Debbie Thank you, and the MMI group, for reviewing the DCI second last call draft. Following are a set of responses to the comments that the group has made. (1) "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." Response: the DCI specification does not confine developers as to how many instances of the DCI tree they can/should have or who should host these instances as these are implementation dependent. One possible implementation in a multimodal framework is to have one instance of the DCI tree hosted by the interaction manager and have appropriate remote access mechanisms for remote devices that need to update/montior properties in that tree. (2) Remote access to properties Response: we acknowledge the need for protocols and access methods for remote properties however we believe that this is out of scope, at least for the first release of the DCI specification. (3) Efficiency concerns for multiple updates Response: again, we do acknowledge the need for efficiency mechanisms (as mentioned in section 4.1.4) specially to alleviate the number of events fired, for example, when a property gets updated very frequently and an application only requires notification at certain intervals. We have decided to leave this out of this release and have implementors decide how best to optimize property updates and access. Thank you again, --- rafah
Received on Saturday, 7 January 2006 17:13:36 UTC