This document:Public document·View comments·Disposition of Comments·
Nearby:Ubiquitous Web Applications Working Group Other specs in this tool
Status: allopen proposal pending resolved_yes resolved_no resolved_partial other Type: allsubstantive editorial typo question general comment undefined
Quick access to LC-1785 LC-1917 LC-1918 LC-1919
There are 4 comments (sorted by their types, and the section they are about).
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.
-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..
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.
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..)
Add a comment.