W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > October to December 2002

RE: gte vs. numerical property values

From: Wallmer, Martin <Martin.Wallmer@softwareag.com>
Date: Mon, 25 Nov 2002 08:31:37 +0100
Message-ID: <DFF2AC9E3583D511A21F0008C7E6210602D90687@daemsg02.software-ag.de>
To: "'Julian Reschke'" <julian.reschke@gmx.de>, www-webdav-dasl@w3.org

Hi,

see intermixed

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Mittwoch, 20. November 2002 22:49
To: www-webdav-dasl@w3.org
Subject: RE: gte vs. numerical property values



Hi,

for the next draft (that I'll try to submit soon) I really need feedback on
this issue. Unless somebody strongly disagress, what I'll add is the
following syntax:

> > <gte xmlns="DAV:">
> >   <prop><foo xmlns=""/></prop>
> >   <literal xsi:type="xs:long">3</literal>
> > </gte>

and then require servers to

- compare according to the datatype when the type was recognized or to
<martin> agree </martin>

- reject the query if the type is unknown to the server.
<martin> 
What about existing implmentations? Currently a server might react with 
"xsi:type unknown entity" or just ignore it (which would mean: String
comparison)
</martin>

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: www-webdav-dasl-request@w3.org
> [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Julian Reschke
> Sent: Wednesday, October 23, 2002 12:49 PM
> To: Wallmer, Martin; 'Julian Reschke'; www-webdav-dasl@w3.org
> Subject: RE: gte vs. numerical property values
>
>
>
> > From: www-webdav-dasl-request@w3.org
> > [mailto:www-webdav-dasl-request@w3.org]On Behalf Of Wallmer, Martin
> > Sent: Tuesday, October 22, 2002 4:35 PM
> > To: 'Julian Reschke'; www-webdav-dasl@w3.org
> > Subject: RE: gte vs. numerical property values
> >
> >
> >
> > Hi,
> >
> > good idea to deal with datatypes :-)
> >
> > some questions
> > a:)
> > how the server may happen to have information about the type of a dead
> > property?
>
> For instance, using:
>
> http://greenbytes.de/tech/webdav/draft-reschke-webdav-property-dat
> atypes-lat
> est.html
>
> Similar type systems exist in MS Exchange and MS Sharepoint.
>
> > b:)
> > what if the server knows about the datatype, and the type in the
> > query does
> > not match?
>
> Then it should fall back to a string comparison.
>
> > Extended proposal:
> >
> > b) A client can enforce comparison using a specific data type by
> > specifying
> > the type in the query, for instance using:
> >
> > <gte xmlns="DAV:">
> >   <prop><foo xmlns=""/></prop>
> >   <literal xsi:type="xs:long">3</literal>
> > </gte>
>
> Another proposal that may be easier to grok for people that don't want to
> use XSD data types:
>
> <gte xmlns="DAV:">
>   <prop><foo xmlns=""/></prop>
>   <literal-number>3</literal-number>
> </gte>
>
> This has the advantage of simplicity (do we more than
> boolean/string/number/date in basicsearch?), but wouldn't be
> backward-compatible with older drafts.
>
> Julian
>
> --
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
>
>
Received on Monday, 25 November 2002 02:31:49 GMT

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