- From: Michael Rys <mrys@microsoft.com>
- Date: Thu, 12 Feb 2004 12:15:00 -0800
- To: <jwrobie@mindspring.com>
- Cc: "Michael Kay" <mhk@mhk.me.uk>, "Jonathan Robie" <jonathan.robie@datadirect.com>, "XML Query Comments" <public-qt-comments@w3.org>
You are now starting to special case. This makes the language design non-orthogonal and hard to teach and understand. Best regards Michael > -----Original Message----- > From: Jonathan Robie [mailto:jwrobie@mindspring.com] > Sent: Thursday, February 12, 2004 12:05 PM > To: Michael Rys > Cc: Michael Kay; Jonathan Robie; XML Query Comments > Subject: Re: [DM] Typed value for elements > > Michael Rys wrote: > > >Contains expects a string typed value. The semantic rules of atomization > >will employ fn:data()/dm:typed-value(). Even for fn:contains(). > > > >Your proposal is going to either remove useful functionality or add > >additional complexity in the atomization process. Neither of which I am > >in favor of. > > > > > Or redefine xslt:value-of() and fn:contains(), acknowledging that they > are text-oriented. For instance, fn:contains() could be defined using > the following signatures: > > fn:contains($arg1 as item(), $arg2 as xs:string?) as xs:boolean > > fn:contains( $arg1 as item(), > $arg2 as xs:string?, > $collation as xs:string) as xs:boolean > > fn:contains() would return true if $arg2 occurs in fn:string($arg1). We > probably would have to look carefully at our function signatures if we > adopted my proposal, but I think this is a significantly cleaner and > simpler proposal than the status quo. > > What useful functionality do you think this would remove? > > Jonathan
Received on Thursday, 12 February 2004 15:15:02 UTC