[
https://issues.apache.org/jira/browse/JENA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719515#comment-13719515
]
Rob Vesse commented on JENA-493:
--------------------------------
Recent versions of Jena/ARQ have implemented the new W3C Candidate
recommendation for Turtle where the PN_PREFIX rule does explicitly allow for a
. in a prefixed name
http://www.w3.org/TR/turtle/#grammar-production-PN_PREFIX
rapper is written by the author of the original member submission who has been
steadily less active in maintaining it over the past couple of years. So
either rapper may not yet support the new Candidate Recommendation or you are
using an old version prior to support for it being added.
> "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
