W3C home > Mailing lists > Public > www-rdf-validator@w3.org > February 2004

Re: bad uri handling

From: Emmanuel Pietriga <epietriga@nuxeo.com>
Date: Thu, 05 Feb 2004 09:06:31 +0100
Message-ID: <4021F987.5020100@nuxeo.com>
To: Stephen Pollei <stephen_pollei@comcast.net>
Cc: www-rdf-validator@w3.org

This problem seems to be related to ARP's URI parser. I don't know 
whether URI checking can be diasbled or not. Maybe by switching to 
another (more permissive) parsing mode? I guess we would then omit to 
check other important things, so I'm not sure this is a good thing for 
the RDF Validator in the general case.

Unless it is possible to disable this specific feature on demand (URI 
checking).

Jeremy? (I don't know if Jeremy reads this list ; if not, you might want 
to ask on the jena-dev [1] list).

[1] jena-dev@yahoogroups.com

Emmanuel

-- 
Emmanuel Pietriga (epietriga@nuxeo.com)
tel (mobile): +33 6 88 51 94 98
http://claribole.net


Stephen Pollei wrote:

> http://stephen_pollei.home.comcast.net/ gives Error: {W107} Bad URI
> <http://stephen_pollei.home.comcast.net/>: Host is not a well formed
> address!
> 
> It's the underscore, however _'s are good host names according to rfc
> 2181 section 11 and rfc1123 sections 2.1 and 6.1.3.5
> The problem is that rfc2396 section 3.2.2 is unduly restrictive. Also it
> can be argued that it shouldn't be trying to parse the uri, just treat
> it like opaque string at this point.
> 
> 
Received on Thursday, 5 February 2004 03:05:00 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:16:59 UTC