[
https://issues.apache.org/jira/browse/JENA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719497#comment-13719497
]
Alexander Dutton commented on JENA-493:
---------------------------------------
http://www.w3.org/TeamSubmission/turtle/#prefixName
My reading of that is that '.' is not allowed in a prefixName. rapper tends to
agree:
{code}
$ rapper -i turtle courses.ttl
rapper: Parsing URI file:///home/alex/courses.ttl with parser turtle
rapper: Serializing with serializer ntriples
rapper: Error - URI file:///home/alex/courses.ttl:22 - syntax error at 'j'
rapper: Failed to parse file courses.ttl turtle content
rapper: Parsing returned 0 triples
{code}
Line 22 is:
{code}
@prefix j.0: <http://data.ordnancesurvey.co.uk/ontology/spatialrelations/> .
{code}
And the file was the result of a DESCRIBE query with "Accept: text/turtle".
> "j.0" prefix remembered by TDB; breaks Turtle output.
> -----------------------------------------------------
>
> Key: JENA-493
> URL: https://issues.apache.org/jira/browse/JENA-493
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki, RIOT, TDB
> Affects Versions: Fuseki 0.2.7
> Reporter: Alexander Dutton
>
> I'm using TDB with Fuseki, and the TDB prefixes table contains an entry for
> 'j.0'. This is then being used when serializing as Turtle, making a
> downstream RDF library upset.
> I suspect it found its way in after I fed it the result of a CONSTRUCT query
> serialized as RDF/XML.
> The options as far as I can see:
> * TDB doesn't make a note of prefixes that can't be used in all
> serializations (or just the "j.x" ones created by the RDF/XML serializer)
> * The Turtle serializer ignores prefixes it can't use
> * Both of the above
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
