Just to report that Kingsley has nailed the problem. It looks as though
the RDF Browser is getting to the RDF via the HTML page, relying on a
<link rel="alternate" ...> entry in the head of the HTML page, rather
than using a 303 redirection strategy to access the RDF directly.
I have added a suitable <link> element to my HTML pages and the Browser
now works fine.
Richard
In message <[EMAIL PROTECTED]>, Kingsley Idehen
<[EMAIL PROTECTED]> writes
Richard,
The output below indicates we have something to look into re. our Browser.
curl -I -H "Accept: application/rdf+xml"
http://collections.wordsworth.org.uk/object/1993.25
HTTP/1.1 303 See Other
Date: Thu, 12 Jun 2008 02:10:54 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Location: http://collections.wordsworth.org.uk/object/data/1993.25
Connection: close
Accept-Ranges: bytes
Vary: accept
Content-Length: 0
Content-Type: application/rdf+xml;qs=1
Set-Cookie: ASPSESSIONIDSCSAQRAR=FAKPBAEADBPFBFAMOPLBPOAM; path=/
Cache-control: private
--
Richard Light
XML/XSLT and Museum Information Consultancy
[EMAIL PROTECTED]
