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

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.


-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E