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 10:26:24 +0100
Message-ID: <DFF2AC9E3583D511A21F0008C7E6210602D9068E@daemsg02.software-ag.de>
To: "'Julian Reschke'" <julian.reschke@gmx.de>, "Wallmer, Martin" <Martin.Wallmer@softwareag.com>, www-webdav-dasl@w3.org


I agree with DAV:typed-literal.
We have not yet implemented QSD.


-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Montag, 25. November 2002 09:51
To: Wallmer, Martin; 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: Monday, November 25, 2002 8:32 AM
> To: 'Julian Reschke'; www-webdav-dasl@w3.org
> Subject: RE: gte vs. numerical property values
> ...
> 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>

OK, I'll add that as a clarification.

> - 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>

(side remark: technically, this shouldn't be a problem -- after all, it's
just an Internet Draft.)

OK, how about *adding* an alternative to DAV:literal? Therfore:

DAV:literal: untyped, server can compare according to it's internal
knowledge of types (with the clarification above)
DAV:typed-literal: typed according to the xsi:type attribute -- "new"
servers can implement this without affecting any existing code.

We'll need to think abut discovery of this feature, though. It might be
possible to do this with QSD (in the meantime, are there any QSD
implementations except ours?)


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Monday, 25 November 2002 04:26:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:43 UTC