W3C home > Mailing lists > Public > xproc-dev@w3.org > September 2009

RE: make-absolute-uris may match strings which are not of type anyURI ...

From: <Toman_Vojtech@emc.com>
Date: Mon, 21 Sep 2009 06:11:56 -0400
Message-ID: <6E216CCE0679B5489A61125D0EFEC78710DBAF5B@CORPUSMX10A.corp.emc.com>
To: <xproc-dev@w3.org>
Actually, RFC2373 (which updates RFC2396) includes "[" and "]" in the
"reserved characters" category, but java.net.URI does not seem to
reflect this change in the actual implementation.

Regards,
Vojtech

--
Vojtech Toman
Principal Software Engineer
EMC Corporation
toman_vojtech@emc.com
http://developer.emc.com/xmltech


> -----Original Message-----
> From: xproc-dev-request@w3.org 
> [mailto:xproc-dev-request@w3.org] On Behalf Of Toman_Vojtech@emc.com
> Sent: Monday, September 21, 2009 11:24 AM
> To: xproc-dev@w3.org
> Subject: RE: make-absolute-uris may match strings which are 
> not of type anyURI ...
> 
> I can't speak for Calabash, but in Calumet, the problem is 
> caused by the
> subtleties of the java.net.URI class. It seems the API 
> documentation for
> java.net.URI is misleading in that it includes the characters "[" and
> "]" in the "reserved characters" (which, acording to the API doc are
> among the legal URI characters) - while in fact they are not (both in
> the java.net.URI implementation and in RFC2396).
> 
> This is a more general issue with other "excluded characters" (to use
> the RFC2396 terminology), such as "{", "<", "|" etc. I will see what I
> can do about this in Calumet.
> 
> Thanks for reporting this.
> 
> Regards,
> Vojtech Toman
> 
> --
> Vojtech Toman
> Principal Software Engineer
> EMC Corporation
> toman_vojtech@emc.com
> http://developer.emc.com/xmltech
> 
> 
> 
Received on Monday, 21 September 2009 10:12:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 21 September 2009 10:12:47 GMT