You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Alexander Dutton (JIRA)" <ji...@apache.org> on 2013/07/25 11:43:55 UTC

[jira] [Updated] (JENA-493) "j.0" prefix remembered by TDB; breaks Turtle output.

     [ https://issues.apache.org/jira/browse/JENA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Dutton updated JENA-493:
----------------------------------

    Description: 
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

  was:
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
* The Turtle serializer ignores prefixes it can't use
* Both of the above

    
> "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