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

Re: casting literal values

From: Javier Godoy <rjgodoy@fich.unl.edu.ar>
Date: Mon, 18 Feb 2008 13:17:27 -0200
Message-ID: <001401c87241$a3da69e0$017ba8c0@Javier>
To: "Julian Reschke" <julian.reschke@gmx.de>, <www-webdav-dasl@w3.org>


Julian Reschke wrote:
>
> The one I implemented tries to cast, but if it's not possible compares
> string representation. I think that's consistent with the grammar; the
> client did not ask for a typed comparison, after all.
>
> The "MAY do typed comparison" case mainly is for those servers that know
> about property types, but do not support DAV:typed-literal.
>
> So it seems we should change
>
> "when operand for a comparison with a property for which the type is
> known, it MAY be treated according to this type."
>
> to
>
> "when operand for a comparison with a property for which the type is known
> and when compatible with that type, it MAY be treated according to this
> type."

+1, I think it is clear and concise.

Even though rejection was never allowed for DAV:literal, the former text did 
not state an explicit behaviour for type incompatibilities. Now, by 
disallowing casting when the DAV:literal values are not compatible with the 
property type, the possibility of casting errors disappears.

It follows that the server MUST accept it and do its best (for instance, it 
may treat the property as xs:string for that expression, or it may do so for 
each occurence of the property within the search condition).


Best Regards,

Javier 
Received on Monday, 18 February 2008 15:19:42 GMT

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