W3C home > Mailing lists > Public > public-diselect-editors@w3.org > July to September 2005

Re: Sathish-1

From: Rhys Lewis <rhys.lewis@volantis.com>
Date: Wed, 31 Aug 2005 09:48:01 +0100
Message-ID: <D18551A6C7EA6241B960D4909EB75DF5023092BA@squid.volantis-uk>
To: <Sailesh.Sathish@nokia.com>
Cc: <public-diselect-editors@w3.org>

Hello Sailesh,

Resending this to correct my misspelling of the comment identifier. Apologies for any confusion

Once again, thanks for your comments on the content selection last call in http://lists.w3.org/Archives/Public/public-diselect-editors/2005AprJun/0005.html.

This mail documents DIWG's response to your comments. DIWG has recorded these as Sathish-1.

DIWG Response
We will make the following changes to the document to address the errors noted in this comment.

1) In the last line of section 4.3, replace 
      "expr attribute"
      "selid and selidName attributes"
2) In section 5.3.1, add the line
      "It can take one of the following values:"
     immediately before the description of the matchfirst value

3) In section 5.10 in the final example, replace the use of &, to signify logical and, with use of the word "and".

4) In section 3.2.1 expand the description of the diselect-reprocess event. Insert the following text immediately after the title of section 3.2.1

"The intent of this event is to allow dynamic changes that can affect selection to be reflected immediately as changes in user experience. For example, in environments   where this event can be raised by changes in delivery context, dynamic changes in the value of characteristics in that context can cause the DISelect processor to reprocess the markup and reevaluate expressions. Different values within the delivery context might result in a different user experience. This kind of behaviour is most likely when content selection is implemented within a user agent that has direct access to dynamic aspects of the delivery context".

In addition, add the following after the first sentence that begins "This event can be raised only......"

"Consequently this specification defines how the event is handled, not how it is raised."

Best wishes

Received on Wednesday, 31 August 2005 08:43:57 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:41:55 UTC