[
https://issues.apache.org/jira/browse/JENA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719578#comment-13719578
]
Andy Seaborne commented on JENA-493:
------------------------------------
I'll check sometime (not right at this moment ...) but IIRC it implicitly does
because it takes the prefixes from the model and they are XML-legal. I don't
think it checks itself in anyway. The Turtle reader (again IIRC) is very
liberal, as it needs to be.
At some time, might be worth revisiting prefix handling details end-to-end
(e.g. the RDF/XML checks prefixes, not assume the modle ones are XML-legal).
At the moment, the fact there is common use of RDF/XML means the current
restrictions are probably adequate.
> "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
