You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by "Peter Ansell (JIRA)" <ji...@apache.org> on 2013/04/18 01:41:15 UTC

[jira] [Commented] (MARMOTTA-205) Turtle-Exports do not contain any language tags

    [ https://issues.apache.org/jira/browse/MARMOTTA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634615#comment-13634615 ] 

Peter Ansell commented on MARMOTTA-205:
---------------------------------------

I added two issues for this as a sub-task of SES-1720 on the Sesame tracker.

The correct syntax according to the RDF/Turtle working group is to make rdf:langString invisible in the Turtle document and for the parser to create it for recognised language literals if it is in RDF-1.1 mode. Note that SES-1720 has been put on hold until the RDF working group gets RDF-1.1 to Candidate Recommendation status.

One workaround on the Marmotta side may be to make Literal.getDatatype return null if the datatype is rdf:langString, to improve the chances that an RDF-1.0 implementation will skip that step.

I think you already knew, but moving to RDF-1.1 inside of an RDF-1.0 API is a risky business!

You accidentally put *xsd*:langString above by the way!
                
> Turtle-Exports do not contain any language tags
> -----------------------------------------------
>
>                 Key: MARMOTTA-205
>                 URL: https://issues.apache.org/jira/browse/MARMOTTA-205
>             Project: Marmotta
>          Issue Type: Bug
>          Components: Triple Store
>    Affects Versions: 3.0-incubating
>            Reporter: Jakob Frank
>            Assignee: Sebastian Schaffert
>
> When serializing rdf data into turtle, all language tags are discarded.
> This is because Sesame appends language tags only to untyped literals, but we are using the RDF1.1 notation which adds xsd:langString to Literals with lang-tag.

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