<div class="gmail_quote">On Sun, Jul 26, 2009 at 7:16 PM, Manu Sporny <span dir="ltr"><<a href="mailto:msporny@digitalbazaar.com">msporny@digitalbazaar.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm not proposing that we allow people to directly stomp all over Ian's<br>
specification - that wouldn't help anything. I am also not suggesting<br>
that Ian should change how he authors his HTML5 specification.<br>
<br>
What I'm proposing is that others should be able to easily create<br>
lasting alternate language, modified sections, remove sections or add<br>
sections IN THEIR OWN SANDBOX and generate alternate specifications<br>
based on Ian's HTML5 specification. We should provide the tools to<br>
enable that.<br></blockquote><div><br></div><div>OK, this clarifies some of my confusion in my last response.</div><div><br></div><div>I do not understand what advantages this would provide over the current system. Here are some use cases:</div>
<div><br></div><div>* If one simply wants an easy way to comment, one can now use the new comment-in-the-spec-itself tool Ian has added.</div><div>* If one wants to share a more detailed proposal for discussion, one can post it on this email list.</div>
<div>* If one wants to broaden discussion beyond this list or post long, detailed proposals, one can put up the proposal on the web and link to it (here and elsewhere).</div><div>* If one wants the proposal to mirror the language of the spec, one can copy and paste language from the spec to edit.</div>
<div><br></div><div>What use case outside these are you seeking to aid? What would the tool do that copy-and-paste will not do? How is (whatever it is that tool does) critical to the use case, such that it cannot be well-solved now?</div>
<div><br></div><div>So far you have not given a use case (that I've seen) so much as a vague assertion that because the number of spec contributors is in the hundreds rather than tens of thousands, there is some not-well-defined barrier to entry in the above list.</div>
<div><br></div><div>PK</div></div>