Simplifying language and shortening sections [TAG feedback - editorial] #815
Labels
defer to arch 2.0
tag-needs-resolution
Issue the Technical Architecture Group has raised and looks for a response on.
From an editorial perspective, implementers who are approaching this set of specifications for the first time may be deterred by the volume of text. In particular where sections or paragraphs do not relate to specific, implementable requirements. The specification abstracts are all rather long and we think all of the specs would benefit from a thorough proof-read, with an eye to removing redundant text, simplifying language, removing filler, and overall shortening throughout. While background and context are useful, we would encourage containing such sections in their own documents, which may be optionally read, and keeping only the informative language that is really crucial for implementation in the specifications themselves.
(from w3ctag/design-reviews#736)
The text was updated successfully, but these errors were encountered: