Hello all,

I have imported a turtle file into a RDF graph in Virtuoso and I have 
made a rewrite rule for dereferencing the URIs. I notice strange 
behaviour with some of the URIs in this graph. For those URIs, the data 
format when directly dereferencing the URI always seems to be Turtle. 
This is noticeable by just opening a URI in a web browser. An example of 
a URI that resolves to HTML (as it should) is:
(A) http://lod.geodan.nl/hhnk/zoneringen/zonering.
An example of a URI that should resolve to HTML but turns out as Turtle is:
  (B) http://lod.geodan.nl/hhnk/zoneringen/hhnk.

I have spent quite some time trying to find out the cause of this 
difference. I think there is nothing wrong the rewrite rule. It rewrites 
the URI to a SPARQL DESCRIBE query with a format specification. When I 
issue a request in that shape I notice the same difference in content 
type. The following command (A) gets a HTML response:
curl -g -i 
"http://lod.geodan.nl/sparql?query=DESCRIBE+<http://lod.geodan.nl/hhnk/zoneringen/zonering>+FROM+<http://lod.geodan.nl/hhnk/zoneringen/>&format=text/html"

But this one (B) gets a Turtle response:
curl -g -i 
"http://lod.geodan.nl/sparql?query=DESCRIBE+<http://lod.geodan.nl/hhnk/zoneringen/hhnk>+FROM+<http://lod.geodan.nl/hhnk/zoneringen/>&format=text/html"

The funny thing is that in both cases the HTTP response header claims 
the format to be text/html.

How could this behaviour be explained? I have tried to look at the 
problem from different angles but I am stumped now.

Regards,
Frans




------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Reply via email to