Is there a test case for this problem?
On Mon, Aug 26, 2013 at 9:48 AM, Andy Seaborne <[email protected]> wrote: > On 26/08/13 02:56, Holger Knublauch wrote: > >> On 8/25/2013 3:49, Andy Seaborne wrote: >> >>> On 23/08/13 00:10, Holger Knublauch wrote: >>> >>>> On 8/23/2013 2:06, Andy Seaborne wrote: >>>> >>>>> Based on your experience, when does it make a difference? >>>>> >>>> >>>> A number of our test cases broke, and I tracked it down to the case >>>> where the base URI of a graph ends with something like .owl yet the file >>>> is saved in ttl. >>>> >>> >>> So the specific issue here is about ".owl". >>> >> >> And also about graph URIs ending with .rdf. >> > > .rdf is in the MIME type registration for RDF. > > > Anyway, for a real-world >> example of this look at >> >> http://www.fao.org/**countryprofiles/geoinfo/**geopolitical/resource/** >> geopolitical.owl<http://www.fao.org/countryprofiles/geoinfo/geopolitical/resource/geopolitical.owl> >> > > Did you man /data/? > > /resource/ is HTML + a bit of RDFa. > > The links go to RDF/XML - it does not conneg for any format (actually, you > get a 406 even if you ask for applciation/rdf+xml!) > > Once this file is downloaded to a local file so that owl:imports are >> resolved against that file, it must be saved in RDF/XML serialization >> because RIOT will treat it as an RDF/XML even if saved as >> geopolitical.ttl and even if my call to Model.read tells it to use the >> Turtle reader. >> > > Where does geopolitical.ttl come into it? > Is it something you produced? > Are you using a location mapper or something to redirect to the local TTL > file? > > Andy > > Thanks, >> Holger >> >> > -- I like: Like Like - The likeliest place on the web<http://like-like.xenei.com> Identity: https://www.identify.nu/[email protected] LinkedIn: http://www.linkedin.com/in/claudewarren
