- From: Peter F. Patel-Schneider <pfps@research.bell-labs.com>
- Date: Mon, 22 Oct 2007 10:41:10 -0400 (EDT)
- To: hendler@cs.rpi.edu
- Cc: public-owl-wg@w3.org
From: Jim Hendler <hendler@cs.rpi.edu> Subject: Re: comments on WDs and non-published WG documents Date: Mon, 22 Oct 2007 09:54:24 -0400 > > In any case, all we need to overcome this particular problem is to > > make > > an internal editor's draft immediately after the WD and have WG member > > organizations make comments against that inside the WG. > > why do it ass-backwards like that? Why not do an internal editors > draft NOW and then get the WG comments registered BEFORE we represent > it as a consensus document of the WG? That would have the nice > feature of being able to answer questions from people in our > organizations and elsewhere with solid answers instead of "Oh, we > haven't discussed that yet", "Oh, that might get taken out later," > "Gee, I never realized that" and other such helpful things... > Probably wouldn't delay things much, and would make it clear we are > publishing in good faith (and we wouldn't need a State of the > Document that was full of weasel words). > I don't see where taking due caution within the WG is a bad thing, > and still would like to hear a good argument for doing things > differently in this case. > -JH Well, *the* reason to publish a WD now is to get comments from outside the WG quickly. WD publication does do this. Making an internal draft does not do nearly as good a job. Yes, publication of the current documents may produce comments that mirror what we would do in the WG anyway, but I am in favour of getting outside comments soon. How little delay do you think producing an internal document first would produce? Would we be able to go this route quickly enough that we could publish WDs and have some comments before the first F2F? peter
Received on Monday, 22 October 2007 14:49:23 UTC