> I am not going > to support an IETF working group that says "nobody is allowed > to do a better job describing HTTP than what is in our charter." that's your choice, of course. but the charter wording is up to the IESG, and they have the authority to make decisions about what kinds of activities are in scope and which kinds of activities are out of scope. (the draft charter being discussed is just someone's idea of a proposal to be given to IESG and it's reasonable to debate it, or to suggest your own draft charter to the applications ADs) for better or worse, there's a lot of investment in the current prose. a drastic rewrite might remove some ambiguities but would certainly create others - and also create questions about exactly what was changed. if HTTP is updated by making relatively minor tweaks where possible, and major changes to text only when necessary, it's much clearer what was changed than if there's a major restructuring/rewriting of the document. that, and rewriting would force a reset to Proposed Standard and create an ambiguity over whether the Proposed or Draft version were authoritative. KeithReceived on Friday, 1 June 2007 14:48:56 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 4 October 2011 12:13:58 GMT