Re: "find out capabilities" best practice works against "One Web" message

[Sorry for the duplicate]

  Dear Dan Connolly ,

The Mobile Web Best Practice Working Group has reviewed the comments you
sent [1] on the Last Call Working Draft [2] of the Mobile Web Best
Practices 1.0 published on 13 January 2006 Thank you for having taken the
time to review the document and to send us comments!

This message holds the disposition of the said comments on which the
Working Group has agreed. This disposition has been implemented in the new
version of the document available at:
http://www.w3.org/TR/2006/WD-mobile-bp-20060412/

Please review it carefully and let us know if you agree with it or not
before 3 May 2006. 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 Practice Working Group,
Philipp Hoschka
Dominique Hazaël-Massieux
W3C Staff Contacts

 1. http://www.w3.org/mid/1137291083.4991.107.camel@dirk.w3.org
 2. http://www.w3.org/TR/2006/WD-mobile-bp-20060113/


=====

Your comment on [CONTEXT] Take all r...:
This draft is better than previous drafts in that it

has an explicit "One Web" section. But the first

best-practice guideline is still:



"[CONTEXT] Take all reasonable steps to find out about the

device/browser (client) capabilities, adaptation and other

transformation that takes place for any instance of an access to a

resource."

  -- http://www.w3.org/TR/2006/WD-mobile-bp-20060113/



Guideline #1 should be: design for device-independence.



Or something like that.



In simple cases, one HTML document should work well

across a variety of devices.



But even for high-profile sites with dedicated production staff,

where server-side content adaptation is worthwhile, designing

for device independence is still a good idea; lots of content

and navigation should be shared across devices.





Ah... 5.2.4 Thematic Consistency of Resource Identified by a URI

Much better. How about starting with that one?

It's a bit of a mouthful, though.



I don't see much justification for "... find out capabilities..."

and I notice there's no "what to test" subsection for it.

Working Group Resolution:
Thematic Consistency has been moved as the first Best Practice in the
latest draft.



Design for device independence, does not have a specific mobile
interpretation, it does not appear to be testable and it is hard to know
what techniques one would cite to support it, unless it is the totality of
the techniques that we suggest in support of the best practices.



We've removed the [CONTEXT] Best Practices as it did not appear to fit
well with the other best practices, and has been moved as a technique
instead.

----

Received on Wednesday, 12 April 2006 17:07:28 UTC