Hi Marcos, It was actually linked to the HTML WG issue tracker, but bugs would be good too. I agree about filing bugs from within the spec: we are using a script by d glazkov on HTML to Platform Accessibility APIs Implementation Guide http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html whereby you can select text and press the button and it opens a bug against the spec with the selected text added in the comment. You should also note we are using some UI that you don't see in specs to provide customizable views of the spec content. regards stevef On 22 March 2012 15:43, Marcos Caceres <w3c@marcosc.com> wrote: > > > On Thursday, 22 March 2012 at 15:38, Steve Faulkner wrote: > > > Hi marco, > > > What about having a disclaimer in the SoTD that states "Caution, this > is an Editor's draft and hence may contain changes not yet agreed to by the > WG"... or some such. > > > > > > I don't think thats enough, what the HTML5 spec had before last call was > markers on any parts of the spec that had an issue raised against it with a > link to the issue. this was achieved using a script. > That would be great, actually. Linking specs to bugzilla would be awesome. > It would also be great to be able to file bugs from within the spec, as > HTML5 currently does. > > > > I think that having an indicator for any non editorial change that has > not been agreed by a working group would be useful. > > > > That might be a challenge - but as long as it's done in a sane way, it > might be doable. Otherwise, it becomes annoying record keeping and gets in > the way of "the creative process" that is spec writing. > > -- > Marcos Caceres > http://datadriven.com.au > > > > -- with regards Steve Faulkner Technical Director - TPG www.paciellogroup.com | www.HTML5accessibility.com | www.twitter.com/stevefaulkner HTML5: Techniques for providing useful text alternatives - dev.w3.org/html5/alt-techniques/ Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html
Received on Thursday, 22 March 2012 15:53:53 UTC