Edit comment LC-1917 for Ubiquitous Web Applications Working Group

Quick access to LC-1785 LC-1917 LC-1918 LC-1919

Comment LC-1917

Comment Shortname:

Commenter: Debbie Dahl <dahl@conversational-technologies.com> on behalf of MMI WG

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeDelivery Context: Client Interfaces (DCCI) 1.0 /**/ cod... Delivery Context: Client Interfaces (DCCI) 1.0 Accessing Static and Dynamic Delivery Context Properties W3C Working Draft 04 July 2007 Abstract Status of this Document Table of Contents Appendices 1 Introduction 1.1 Uses for DCCI 1.2 Reading the Specification 1.2.1 Conformance Information 1.2.1.1 Normative and Informative Parts 1.2.1.2 Normative Language for Conformance Requirements 1.3 Documentation Conventions 1.3.1 Bindings 1.3.2 Examples 2 Alternative Ways of Accessing the Delivery Context 2.1 Interfaces 2.2 Representations 3 DOM and the Data Model 3.1 Property Datatypes 3.1.1 DOM Basic Types 3.1.2 Additional Types any 3.2 Property Interfaces 3.3 Property Collections 3.4 Property Initialization 3.5 Properties in Distributed Systems 3.6 Metadata 4 Processing 4.1 Querying and Searching 4.2 Using Events 4.2.1 Controlling Event Generation 4.2.2 Using DOM3 Event Groups with DCCI 4.3 Access Control 4.4 Errors 5 IDL Definitions for DCCI 5.1 The DCCIProperty Interface 5.1.1 IDL Definition 5.1.2 Attributes value of type any valueType of type DOMString, readonly propertyType of type DOMString readonly readOnly of type boolean, readonly readonly DCCIMetadataInterface of type any readonly DCCIMetadataInterfaceType of type DOMString 5.1.3 Methods hasProperty() searchProperty() 5.2 The DCCIPropertyFilter Interface 5.2.1 IDL Definition 5.2.2 Attributes 5.2.3 Methods acceptProperty() 5.3 The DCCIComponent Interface 5.3.1 Attributes version of type DOMString 5.3.2 Methods 5.3.3 Exceptions 5.4 The DCCIException Exception 5.4.1 IDL Definition 5.4.2 DCCIException Error Codes ACCESS_VIOLATION_ERR NOT_SUPPORTED_ERR PROPERTY_FILTER_ERR 6 Event Processing Model 6.1 The DCCI-prop-change Event 6.2 How DCCI Uses Existing DOM Events 7 Conformance 7.1 Conformance Requirements for All DCCI Implementations 7.1.1 The DCCI Namespace 7.2 Additional Conformance Requirements for Implementations Based on DOM 3 8 ECMAScript Language Binding 8.1 DCCIException Interface 8.1.1 Properties of DCCIException: 8.2 DCCIProperty Interface 8.2.1 Properties of objects that implement the DCCIProperty interface: 8.2.2 Functions of objects that implement the DCCIProperty interface: 8.3 DCCIComponent Interface 8.3.1 Objects that implement the DCCIComponent interface: 8.3.2 Properties of objects that implement the DCCIComponent interface: 8.4 DCCIPropertyFilter A IDL Definitions for DCCI A.1 IDL for DCCI Implementations Based on DOM 2 A.2 IDL for DCCI Implementations Based on DOM 3 B Informative Use Case: Resolved Postal Code C Normative References XML XML-Namespaces ECMAScript DOM RFC2396 DOM2-Core DOM2-Events DOM3-Events DOM3-Core IETF RFC 2119 IDL D Informative References CPC DevInd DIWG DCO MMI MMIReqs IM OMA BT DCAP OWL SIP CCPP RDF UAPROF XPath VoiceXML LIF XHTML DISelect AJAX GPS GLOSS DDWG XAF DCOnt UPnP E Changes Since the Previous Version E.1 Normative Changes E.2 Informative Changes F Acknowledgements (Non-Normative)
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody

Type: substantive editorial typo question general comment undefined

Resolution status:

Response drafted Resolution implemented Reply sent to commenter

Response status:

No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):

Comment:

-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..

Related issues: (space separated ids)

WG Notes:

Resolution: The registration for events is performed on the DCCI node, with addEventListener() or addEventListenerNS(). The namespace of the event itself for the dci-prop-change event is to be http://www.w3.org/2007/dci per http://www.w3.org/TR/DPF#event-dci-prop-change and http://www.w3.org/TR/DPF#sec-conformance. The changed DCCI node will be the target of the event, and has its own namespace. This is unrelated to any namespace associated with the registering source.

(Please make sure the resolution is adapted for public consumption)