Re: ID: draft-ietf-webdav-bind-05

Julian wrote on 06/23/2004 03:51:33 AM:

> Joe Hildebrand wrote:
> > Meta:
> >  - Who is maintaining the site for specs?  The latest draft 

> > for bind there is -02.

That would be me ... it should be up-to-date now (with the latest 
from Julian's site).  In particular, I've linked the issues list directly
to Julian's issues list, since he's maintaining that document.  Also, I've
made a copy of Julian's "latest" and made it version 05.1.

> > 1.3
> >  - Second paragraph: how might I otherwise negotiate?  The DAV:bind 
> Good point. As far as I can tell, this text was inherited from RFC3253 
> (<>). 
> Geoff, do you remember what this is supposed to mean? Can/should we 
> clarify that?

This is just a placeholder for our deciding to marshal things differently.
In particular, suppose we had a request header that specified "return 
information in html format" (that was contemplated at one time).  Then the
error info would be marshalled as html in the response body, rather than 
in the xml format that is used by default.

> > 7.1.1
> >  - I think this would be clearer if it included D:resource-id in the 
> > request and response, so you could tell where the loop happened.  Are 
> > resource-id's likely to be costly to return?
> No, they should be cheap. I think we should update the example 

I agree.

> > Sorry some of these are nit-picky.
> No reason to. As a matter of fact, this kind of review is what we need. 

Definitely.  Since we are (or should be) at last call, now's the time
to nit-pick.

> Let's try to get things moving so that we can get back on track (BIND 
> was supposed to be last-called in May according to the just updated 
> working group charter).



Received on Wednesday, 23 June 2004 07:13:25 UTC