trouble de-referencing bibo: URI
Dan Brickley
I'm using a script to programmatically fetch a lot of common RDF
namespaces, ... and Bibo is proving different to most of them.
Log copied below. Basically for most I am sending an accept: header
asking for application/rdf+xml, and apart from RDFa from Creative
Commons, I get it.
For bibo for some reason I get an error about unescaped hash. Maybe
some interaction between the Purl setup and your hosting provider?
No big deal, I have the schema now, but thought I'd mention it. Maybe
removing the final # in Purl control panel settings would help?
cheers,
Dan
danbri$ curl http://purl.org/ontology/bibo/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML>
<HEAD>
<TITLE>302 Found</TITLE>
</HEAD>
<BODY>
<H1>Found</H1>
The resource requested is available <A
HREF="http://bibotools.googlecode.com/svn/bibo-ontology/tags/1.3/bibo.xml.owl#">here</A>.<P>
</BODY>
</HTML>
ajbim:zoo danbri$ curl -L http://purl.org/ontology/bibo/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>The request was invalid: the URI included an un-escaped hash character</p>
</body></html>
ajbim:zoo danbri$ curl -H "Accept: application+rdf/xml" -L
http://purl.org/ontology/bibo/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>The request was invalid: the URI included an un-escaped hash character</p>
</body></html>
ajbim:zoo danbri$ curl -H "Accept: application+rdf/xml" -L
http://bibotools.googlecode.com/svn/bibo-ontology/tags/1.3/bibo.xml.owl
<?xml version="1.0"?>
<!DOCTYPE rdf:RDF [
...success :)
Frederick Giasson
> I'm using a script to programmatically fetch a lot of common RDF
> namespaces, ... and Bibo is proving different to most of them.
>
> Log copied below. Basically for most I am sending an accept: header
> asking for application/rdf+xml, and apart from RDFa from Creative
> Commons, I get it.
>
> For bibo for some reason I get an error about unescaped hash. Maybe
> some interaction between the Purl setup and your hosting provider?
>
> No big deal, I have the schema now, but thought I'd mention it. Maybe
> removing the final # in Purl control panel settings would help?
Yes, apparently that it had some issues with the hash. Retry it now, I
just removed it in the purl redirect.
Thanks for reporting the issue!
Take care,
Fred
Dan Brickley
>> No big deal, I have the schema now, but thought I'd mention it. Maybe
>> removing the final # in Purl control panel settings would help?
>
> Yes, apparently that it had some issues with the hash. Retry it now, I just
> removed it in the purl redirect.
Great, that seems to have fixed it. I can remove the special case
treatment from my Perl script, thanks :)
Dan
Frederick Giasson
> Great, that seems to have fixed it. I can remove the special case
> treatment from my Perl script, thanks :)
Good perfect :)
Simpler code is better :D
Take care,
Fred