Editorial comments on landscape document

Hi,

A few comments on the Landscape document:
* I would drop the "1.0" from the title; it's unlikely the document will
need to be versioned down to that level - most likely, once it gets
approved as final, it won't be revised, and if it is, it can be revised
under the same title

* the presentation of the requirements between 10 and 11 (linking back
to req 6) is a bit confusing; I would simply put a sentence saying that
the said aspect is covered by req 6

* there should probably be ref to the TAG finding:
http://www.w3.org/2001/tag/doc/alternatives-discovery.html

* all the requirements are of the "must" form (although it's not clear
whether that's meant in the RFC2119 sense); I'm not sure imposing so
many must can leave any space for a real-world solution :)

* the requirements all apply to servers/proxies/browsers/etc, while I
think what is meant is requirements on what the guidelines document
would address; e.g. I would rephrase:

"Origin servers must be able to selectively enable or disable features
of transforming proxies." in
"The guidelines should address how origin servers can enable or disable
features of transforming proxies"

HTH,

Dom

Received on Tuesday, 30 October 2007 09:50:44 UTC