There are 4 comments (sorted by their types, and the section they are about).
question comments
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
Status: open
proposal
pending
resolved_yes
resolved_no
resolved_partial
other
assigned to Keith Waters
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 dispositionCommenter'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)
editorial comments
Comment LC-1785
Commenter: Yi JongPil (aka JP) <jp.yi@samsung.com> (archived message ) Context: Abstract (Spelling of the word programing)
Status: open
proposal
pending
resolved_yes
resolved_no
resolved_partial
other
assigned to Rhys Lewis
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 dispositionCommenter's response (URI):
Comment :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.
Related issues: (space separated ids)
WG Notes: In http://lists.w3.org/Archives/Public/public-dcci-editors/2007Jul/0001.html
JP suggests spelling programing as programming
Resolution: While both spellings are acceptable in normal English usage (various on-line dictionaries show this), you are correct that "programming" is more regularly used.
This will be corrected.
(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
Status: open
proposal
pending
resolved_yes
resolved_no
resolved_partial
other
assigned to Keith Waters
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 dispositionCommenter's response (URI):
Comment :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..)
Related issues: (space separated ids)
WG Notes:
Resolution: Thanks. There is a editorial correction to be made here. The
reference to "web client" and "web server" in section 2.1 should be
changed to "client" and "server". (Please make sure the resolution is adapted for public consumption)
Add a comment .