Re: Reused IDs ( LC-2064)

 Dear Elliotte Harold ,

The Mobile Web Best Practices Working Group has reviewed the comments you
sent [1] on the Last Call Working Draft [2] of the Content Transformation
Guidelines 1.0 published on 1 Aug 2008. Thank you for having taken the time
to review the document and to send us comments!

The Working Group's response to your comment is included below, and has
been implemented in the new version of the document available at:
http://www.w3.org/TR/2009/WD-ct-guidelines-20091006/.

Please review it carefully and let us know by email at
public-bpwg-comments@w3.org if you agree with it or not before 6 November
2009. In case of disagreement, you are requested to provide a specific
solution for or a path to a consensus with the Working Group. If such a
consensus cannot be achieved, you will be given the opportunity to raise a
formal objection which will then be reviewed by the Director during the
transition of this document to the next stage in the W3C Recommendation
Track.

Thanks,

For the Mobile Web Best Practices Working Group,
Dominique Hazaël-Massieux
François Daoust
W3C Staff Contacts

 1. http://www.w3.org/mid/48AC262B.2070701@metalab.unc.edu
 2. http://www.w3.org/TR/2008/WD-ct-guidelines-20080801/


=====

Your comment on the document as a whole:
> A purely editorial note: your markup is reusing the ID sec-purpose 
> (perhaps others) more than once. This makes the document invalid:
> 
> <a name="sec-purpose" id="sec-purpose">From the point of view of this 
> document, Content Transformation is the
>                      manipulation in various ways, by proxies, of 
> requests made to and content
>                      delivered by an origin server with a view to
> making 
> it more suitable for mobile
>                      presentation.</a></p><p><a name="sec-purpose" 
> id="sec-purpose">The W3C Mobile Web Best Practices Working Group
> neither 
> approves nor disapproves of Content Transformation, but
>                      recognizes that is being deployed widely across 
> mobile data access networks. The
>                      deployments are widely divergent to each other, 
> with many non-standard HTTP
>                      implications, and no well-understood means either
> 
> of identifying the presence of
>                      such transforming proxies, nor of controlling
> their 
> actions. This document
>                      establishes a framework to allow that to 
> happen.</a></p><p><a name="sec-purpose" id="sec-purpose">The overall 
> objective of this document is to provide a means, as far as is
>                      practical, for users to be provided with at least
> a 
> </a><a 
>
href="http://www.w3.org/TR/di-gloss/#def-functional-user-experience">"functional
> 
> user experience"</a>
>                      <a href="#ref-DIGLOSS">[Device Independence 
> Glossary]</a> of the Web, when mobile, taking into account the
>                      fact that an increasing number of content
> providers 
> create experiences specially
>                      tailored to the mobile context which they do not 
> wish to be altered by third
>                      parties. Equally it takes into account the fact 
> that there remain a very large
>                      number of Web sites that do not provide a 
> <em>functional user
>                      experience</em> when perceived on many mobile 
> devices.</p>


Working Group Resolution (LC-2064):
We understand that the comment was triggered because of some misleading
"View Selection Source" option in your browser.

The document was thoroughly checked and does not contain any duplicated
ID.

----

Received on Tuesday, 6 October 2009 15:49:35 UTC