Hi Ivan,

Thanks!

We have a tough schedule now so we'll try to test the patch later. But it will 
safe time if we don't need to build sedna from sources but test a night build 
instead. Is this available by any chance?

Please let us know when you publish an official bug-fix release.

Best regards,
Ivan Lagunov

From: Ivan Shcheklein [mailto:[email protected]]
Sent: Thursday, December 20, 2012 11:29 AM
To: Robby Pelssers
Cc: [email protected]; Ivan Lagunov
Subject: Re: [Sedna-discussion] FW: [xquery-talk] The value does not conform to 
the lexical constraints defined for the xs:anyURI type

Hi Ivan, Robby,

Try to run with the following patch. It will be in master ASAP.

Ivan Shcheklein,
Sedna Team

On Wed, Dec 19, 2012 at 6:27 PM, Robby Pelssers 
<[email protected]<mailto:[email protected]>> wrote:
Thx Ivan for the quick response !!

@Ivan Lagunov...   please keep track of this !!

Robby

From: Ivan Shcheklein [mailto:[email protected]<mailto:[email protected]>]
Sent: Wednesday, December 19, 2012 1:07 PM
To: Robby Pelssers
Cc: 
[email protected]<mailto:[email protected]>
Subject: Re: [Sedna-discussion] FW: [xquery-talk] The value does not conform to 
the lexical constraints defined for the xs:anyURI type

Hi Robby,

Sedna allows spaces. It's a bug.

I've already fixed it and let you know when patch and/or new development build 
is available.

BTW, you should be aware that Sedna (and Zorba too) performs 
space-normalization:

xs:anyURI("    http://example.com/aa      aa    ") gives "http://example.com/aa 
aa"

Ivan Shcheklein,
Sedna Team





On Wed, Dec 19, 2012 at 2:42 PM, Robby Pelssers 
<[email protected]<mailto:[email protected]>> wrote:
Hi all,

Do you think Sedna should loosen up the xs:anyURI lexical constraints?

Thx in advance,
Robby

-----Original Message-----
From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]<mailto:[email protected]>] On Behalf Of 
Michael Kay
Sent: Wednesday, December 19, 2012 10:31 AM
To: [email protected]<mailto:[email protected]>
Subject: Re: [xquery-talk] The value does not conform to the lexical 
constraints defined for the xs:anyURI type

The validation rules for xs:anyURI in the XSD 1.0 specification are notoriously 
troublesome, and it is not surprising that different implementors interpret 
them differently.

This is what XSD 1.0 says:

<quote>
The *lexical space* of anyURI is finite-length character sequences which, when 
the algorithm defined in Section 5.4 of [XML Linking Language] is applied to 
them, result in strings which are legal URIs according to [RFC 2396], as 
amended by [RFC 2732].

Note:  Spaces are, in principle, allowed in the *lexical space* of anyURI, 
however, their use is highly discouraged (unless they are encoded by %20).
</quote>

The "Note" here suggests that Sedna is wrong to reject the value (it also 
suggests that your query is wrong to supply it, but that you should be able to 
get away with it).

The "algorithm" referred to in this rule is basically the escaping of special 
characters such as space.

Note that in XSD 1.1, the spec gives up trying to define what's valid in an 
xs:anyURI and what isn't - all strings are now valid in the lexical space of 
xs:anyURI.

Michael Kay
Saxonica

On 19/12/2012 09:11, Robby Pelssers wrote:
> Hi all,
>
>
> I tested following Xquery with Sedna and Zorba:
>
> declare function local:getPipUri($id as xs:string) as xs:anyURI {
>     xs:anyURI(concat("http://www.nxp.com/pip/";, $id)) };
>
> local:getPipUri("CX24483 14LZ")
>
>
> Sedna throws an exception:
> 2012/12/19 10:07:09 database query/update failed (SEDNA Message: ERROR
> FORG0001 Invalid value for cast/constructor.
> Details: The value does not conform to the lexical constraints defined for 
> the xs:anyURI type.
> Query line: 6, column:4
> )
>
>
> http://www.zorba-xquery.com/html/demo happy returns 
> "http://www.nxp.com/pip/CX24483 14LZ"
>
> So how does the xs:anyURI cast work? Is the developer supposed to encode the 
> String before passing it to xs:anyURI or is the anyURI function supposed to 
> do this?
>
> Thx in advance,
> Robby
>
> _______________________________________________
> [email protected]<mailto:[email protected]>
> http://x-query.com/mailman/listinfo/talk
>

_______________________________________________
[email protected]<mailto:[email protected]>
http://x-query.com/mailman/listinfo/talk

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Sedna-discussion mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/sedna-discussion


------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Sedna-discussion mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/sedna-discussion

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Sedna-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sedna-discussion

Reply via email to