W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2004

Re: Remaining issues with the bind draft -- process

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Mon, 5 Apr 2004 23:22:41 -0400
To: Webdav WG <w3c-dist-auth@w3c.org>
Message-ID: <OF4DBEAE3D.7E19989C-ON85256E6E.0011E91E-85256E6E.00127D47@us.ibm.com>

Hi Antony,

Thanks for speaking up!  It's folks that aren't part of the
design team whose feedback on this point is most valuable.

I agree that comprehensibility is more important than
axiomatic minimality, but we do try to avoid duplicating
normative information from other specs, to avoid confusion
when those other specs are revised.

Were there specific parts about the BIND spec that you felt
merited/required additional explanation?

Thanks,
Geoff


Antony wrote on 04/05/2004 10:03:33 PM:

> I'm a (lurking) WebDAV implementer, and I'm waiting for BIND. I think 
> it's bizarre to propose publishing BIND when understanding it depends 
> on RFC2518bis, that has an indeterminate publish schedule and may never 
> happen. IMO the only thing that makes sense is to publish locking 
> separately, and only then publish BIND. I've been hoping this would 
> happen ever since I saw GULP, so for what it's worth, I request 
> Julian's point 3.
> 
> As an aside, I think the BIND spec should err on the side of ease of 
> comprehension, rather than being axiomatically minimal. I think the 
> process of writing such explanatory content is more likely to bring to 
> light misunderstandings that illustrate ambiguity or incomplete 
> coverage. Developing such non-normative explanatory content is a 
> time-honoured and very effective mechanism to avoid that.
> 
> Just my $0.02
> 
> On 06/04/2004, at 7:43 AM, Julian Reschke wrote:
> 
> > 3) A drastic approach would be to de-couple locking entirely from
> > RFC2518 ("updating" RFC2518 again). That would look similar to how
> > RFC3253 is organized (locking would become an optional module, and
> > everything that needs to be said about locking would reside in that
> > separate document). Of course that approach would have a significant
> > impact on RFC2518bis, because optimally, it wouldn't say anything 
about
> > locking anymore either.
> 
> Antony Blakey
> -------------
> Some defeats are installments to victory.
>    --Jacob Riis
> 
Received on Monday, 5 April 2004 23:23:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:06 GMT