W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2005

Re: new stuff in draft edits

From: Jim Whitehead <ejw@soe.ucsc.edu>
Date: Wed, 19 Oct 2005 11:39:39 -0700
Message-Id: <A6CFADCD-83EC-4E17-84F2-0B4A4AAC32AF@cs.ucsc.edu>
To: WebDav <w3c-dist-auth@w3.org>

> We can get a reasonable diff (now that we have XML version of  
> both), see for instance <http://greenbytes.de/tech/webdav/draft- 
> ietf-webdav-rfc2518bis-latest-from-rfc2518.diff.html>.  I guess  
> this is the format people should be reviewing.

That's very nice! Are you planning on consistently producing this  
page (or is it created automatically)?

Since it's easy to see the differences using this tool, it seems to  
me the concern about seeing changes from draft to daft is reduced. Is  
this true?

> Well, sounds like pre-generated HTML with change tracking (hyper- 
> linked to an issues list) is a good thing. It's not like it's  
> impossible to get that with XML (check the drafts I've been  
> editing, for instance <http://greenbytes.de/tech/webdav/draft-ietf- 
> webdav-bind-12.html>).

This also sounds like a plus. Is there some place that documents how  
to do this?
> Right now we have the situation that feedback to previous drafts  
> usually was ignored, thus the long backlog on issues we now have to  
> go through. This definitively is frustrating, and please don't  
> blame people when they start considering how to invest their time  
> in a more efficient way.

My feeling is the modification process is now back on track, and we  
have a responsive document editor.

> IMHO, it's definitively not XML which is the problem. In the end,  
> we need to provide an ASCII version, and that works *much* better  
> using xml2rfc. Last time we produced a draft with Word (RFC3744)  
> it's formatting was so bad that we had to go through an additional  
> edit/submission cycle to get it right.

I agree that's a pain, and a big advantage of XML. But, if the lack  
of change awareness from draft to draft frustrates people so much we  
never create a final draft, the ability to convert to text isn't  
super important. But, perhaps it's easy to create a cron job that  
automatically creates an HTML diff between revisions of 2518bis?  
Also, automatically converting the latest draft to HTML would also be  
a plus.

Making it easier to see the latest draft might improve participation.

- Jim
Received on Wednesday, 19 October 2005 18:39:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:33 UTC