W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > July to September 1999

RE: DASL Protocol Nits

From: Slein, Judith A <JSlein@crt.xerox.com>
Date: Fri, 2 Jul 1999 13:51:58 -0400
Message-ID: <201BB34B3A73D1118C1F00805F1582E801BA4E80@x-wb-0128-nt8.wrc.xerox.com>
To: "'Jim Davis'" <jrd3@alum.mit.edu>, "Slein, Judith A" <JSlein@crt.xerox.com>, www-webdav-dasl@w3.org
> -----Original Message-----
> From: Jim Davis [mailto:jrd3@alum.mit.edu]
> Sent: Friday, July 02, 1999 1:22 PM
> To: Slein, Judith A; www-webdav-dasl@w3.org
> Subject: Re: DASL Protocol Nits
> 
> 
> >2.  In section 2.5.1 the last sentence before the example -- 
> is this saying
> >that even if the results are ordered, I may not be getting 
> back the first n
> >results, but any arbitrary n results (though the ones I get 
> will be sorted
> >according to the sortby clause)?
> 
> No.  the paragraph before that covers this case.  Care to 
> suggest better
> wording?

Then I don't know what it is trying to say.  Maybe it just isn't needed, and
is confusing me because it isn't really saying anything new?  If the set is
truncated, doesn't that just mean that you are getting some subset of the
results that satisfy the search criteria?  And then the fact that it comes
right after the paragraph on ordering suggests that it's some special remark
about that.


> >6.  In the example at the end of section 5.19.8, 
> "<D:propdesc>" should be
> >"<D:opdesc>".
> 
> Eh? the properties element contains propdesc elements, and 
> the operators
> contains opdesc elements.  Is there a propdesc that should be 
> an opdesc?
> 

Well, section 5.19.8 is about operator descriptions, not about property
descriptions, and the example (the last line of section 5.19.8) is
describing the DAV:like operator, so it should be a DAV:opdesc element.

--Judy
Received on Friday, 2 July 1999 13:52:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:04 GMT