W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > January to March 2008

casting literal values

From: Javier Godoy <rjgodoy@fich.unl.edu.ar>
Date: Thu, 14 Feb 2008 16:02:10 -0200
Message-ID: <003101c86f33$c14b9370$017ba8c0@Javier>
To: <www-webdav-dasl@w3.org>, "Julian Reschke" <julian.reschke@gmx.de>

Julian Reschke wrote:
> Subject: Re: QSD description for DAV:contains in DAV:basicsearchschema
> If nothing else comes up I intend to submit a new draft (-15) early next 
> week.

A short comment about casting literal values:

(Section 5.11)  [[
The comparison evaluates to UNDEFINED if the property value can not be cast 
to the specified datatype.

What happens if the property value can not be cast to the specified 
- when casting a literal value (DAV:literal) if the property type is known 
and the server chooses to treat the literal according to this type,
- when casting typed literal values.

Failing with 422 seems logical, though it is not explicitly stated. IMHO, it 
may help to recommend servers not to be lenient about this.

Btw, the uppercase keyword UNDEFINED is never used in the document but in 
Section 5.11 ("The comparison evaluates to UNDEFINED"). Should it be UNKNOWN 

Best Regards

Received on Thursday, 14 February 2008 18:02:40 UTC

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