Dereferenceabilty of Music Ontology terms

[Hogan, Aidan]

Hi folks,

I've been wrong about dereferenceability issues in the past ;), but it
seems that there's a problem with some of the terms in the Music
Ontology in this regard?

For terms like mo:Composer, they seem to redirect fine in a browser, but
not so with "Accept: application/rdf+xml": after the initial 302 to
http://pingthesemanticweb.com/ontology/mo/musicontology.rdfs, a 406 is
returned [1].

For terms like mo:MusicArtist, dereferencing seems fine [2] (the
original redirect is to a different namespace).

Cheers,
Aidan

======================================================

[1]

$ curl -I -H "Accept: application/rdf+xml"
http://purl.org/ontology/mo/Composer -L

HTTP/1.1 302 Moved Temporarily
Date: Sun, 09 Jan 2011 22:48:19 GMT
Server: 1060 NetKernel v3.3 - Powered by Jetty
Location: http://pingthesemanticweb.com/ontology/mo/musicontology.rdfs
Content-Type: text/html; charset=iso-8859-1
X-Purl: 2.0; http://localhost:8080
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Length: 293

HTTP/1.1 406 Unacceptable
Server: Virtuoso/05.12.3041 (Solaris) x86_64-pc-solaris2.10-32 VDB
Connection: Keep-Alive
Content-Type: text/html; charset=ISO-8859-1
Date: Sun, 09 Jan 2011 22:48:19 GMT
Accept-Ranges: bytes
Alternates: {"musicontology.rdfs" 1 {type application/octet-stream}
{charset ISO-8859-1} {length 141599}}
Content-Length: 418

======================================================

[2]

$ curl -I -H "Accept: application/rdf+xml"
http://purl.org/ontology/mo/MusicArtist -L

HTTP/1.1 302 Moved Temporarily
Date: Sun, 09 Jan 2011 22:45:51 GMT
Server: 1060 NetKernel v3.3 - Powered by Jetty
Location: http://motools.sourceforge.net/mo/MusicArtist
Content-Type: text/html; charset=iso-8859-1
X-Purl: 2.0; http://localhost:8080
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Content-Length: 278

HTTP/1.1 303 See Other
Server: nginx/0.7.63
Date: Sun, 09 Jan 2011 22:45:52 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
Location: http://motools.sourceforge.net/doc/musicontology.rdfs
Cache-Control: max-age=172800
Expires: Tue, 11 Jan 2011 22:45:52 GMT

HTTP/1.1 200 OK
Server: nginx/0.7.63
Date: Sun, 09 Jan 2011 22:45:52 GMT
Content-Type: application/rdf+xml
Connection: keep-alive
Last-Modified: Sun, 28 Nov 2010 15:50:10 GMT
ETag: "2463d-4961ee90d7422"
Accept-Ranges: bytes
Content-Length: 149053
Cache-Control: max-age=172800
Expires: Tue, 11 Jan 2011 22:45:52 GMT

========================================================

[Damian Steer]

On 9 Jan 2011, at 22:57, Hogan, Aidan wrote:

> Hi folks,
>
> I've been wrong about dereferenceability issues in the past ;), but it
> seems that there's a problem with some of the terms in the Music
> Ontology in this regard?
>
> For terms like mo:Composer, they seem to redirect fine in a browser, but
> not so with "Accept: application/rdf+xml": after the initial 302 to
> http://pingthesemanticweb.com/ontology/mo/musicontology.rdfs, a 406 is
> returned [1].

It seems like it only responds to application/octet-stream (or wildcards).

Damian

[Yves Raimond]

Hello!

Looks like it might be due to a rogue Purl (which I thought was
removed) that overrides our domain - thanks for spotting that, I will
look into it!

Cheers,
y

[Yves Raimond]

Arg - In fact, I don't have the rights to remove those rogue PURLs -
only Fred is allowed to. Fred, could you delete them? I suppose
there's not only Composer in there, but a few others - looking for
PURL registered by you and starting with /ontology/mo/ would do, I
think

Best,
y