RE: DASL and DELTA-V properties

"Clemm, Geoff" <[email protected]>
Newsgroups gmane.ietf.deltav
Message-ID <3906C56A7BD1F54593344C05BD1374B107D7B82B@SUS-MA1IT01>
I was assuming that you were referring to a DAV:allprop in the
"WHERE" clause (i.e. find this string in all properties).
Thus my statement that "DAV:allprop SEARCH should not search
RFC-3253 properties".

If you were referring to the use of DAV:allprop in the "SELECT" clause,
then as Julian points out, it should not report RFC-3253 properties
(but should search whatever is specified in the WHERE clause).

And Julian's sed statement is of course correct (thanks, Julian!).

Cheers,
Geoff

-----Original Message-----
From: Julian Reschke [mailto:[email protected]]
Sent: Monday, August 12, 2002 8:28 AM
To: Clemm, Geoff; [email protected]; [email protected]
Cc: Kazeroni, Ladan; Nevermann, Dr., Peter; Wallmer, Martin
Subject: RE: DASL and DELTA-V properties


Wait-a-minute :-)

> From: [email protected]
> [mailto:[email protected]]On Behalf Of Clemm, Geoff
> Sent: Monday, August 12, 2002 2:19 PM
> To: [email protected]; [email protected]
> Cc: Kazeroni, Ladan; Nevermann, Dr., Peter; Wallmer, Martin
> Subject: RE: DASL and DELTA-V properties
>
>
>
> I agree with Julian.  DAV:allprop SEARCH should be defined to
> have the same behavior as DAV:allprop.  In particular, it
> should not search RFC-3253 properties.

Yes, it should SEARCH them (if used in the where clause). No, it shouldn't
report them (when select uses allprop).

> The current proposal for the next revision of 2518 is that
> it should only search dead properties and properties
> defined in RFC-2518.

sed s/search/report/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.