[Commentor] LC-283 Ian Jacobs [Comment] This point is problematic on several fronts: * "Reasonable" is not well-defined. That term may work well in some contexts (such as a patent policy, where people are used to it). I think you should avoid it in this document. Alternatively, say once up front in the delivery context section what you mean by "reasonable". * I am not sure who is responsible for carrying out this task. Is this the responsibility of someone who is producing content? It doesn't feel like it. * You say to do this for "any instance of an access." Even when there is caching? It may be that in that case I haven't accessed the resource, but I'm not sure of that, so it may be worth clarifying. * This should not be the first best practice note --- this is about content adaptation. I think it is important to start with the message: Design for one Web! Then, talk about how to improve the user experience above and beyond that. * The statement seems overly general. What about saying something a bit more specific, like "Follow published standards when determining device capabilities for the purpose of content adaptation." [Working Group decision] We agree that this best practice didn't fit very well with the rest of the documents, and was more a general technique than an actual best practice. As such, we have redistributed the text between some other parts of the document as well as in the Techniques. [Commentor reply] 
yes
n o r e p l y f r o m c o m m e n t e r
y e s