> How can anyone make technical commentary if they have not read the > spec? sometimes you can make useful commentary about the overall approach even without knowledge of the details. but it's risky. mainly this is an argument for limiting the number of specs that people are expected to read, perhaps in the WG charter.