[ https://issues.apache.org/jira/browse/JENA-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183414#comment-13183414 ]
Andy Seaborne edited comment on JENA-193 at 9/15/13 8:50 AM: ------------------------------------------------------------- * xsd:String and plain-literals without a language tag will be the same RDF literal. Output should be in the (old) plain literal, no language tag form. Affects Node and writers. May affect persistent data. *Application visible, * * The datatype of a literal with language tag is defined to be rdf:langString. Literals are not written with this datatype explicitly. Affects Node and writers. Application visible. * Turtle standardization [DONE] * TriG [DONE] * N-Quads [DONE] * N-triples/UTF-8 [DONE] * Skolemization http://www.w3.org/2011/rdf-wg/wiki/Skolemization "official" way to round-trip bNodes. was (Author: andy.seaborne): * xsd:String and plain-literals without a language tag will be the same RDF literal. Output should be in the (old) plian literal, no language tag form. Affects Node, readers and writers. Affect storage sub-systems. *Application visible* * The datatype of a literal with language tag is defined to be rdf;langString. Literals are not written with this datatype explicitly. Affects Node and writers. Affect storage sub-systems. Application visible. * Turtle standardisation [DONE] * TriG [DONE] * NQuads [DONE] * N-triples/UTF-8 [DONE] * Skolemization http://www.w3.org/2011/rdf-wg/wiki/Skolemization "official" way to round-trip bNodes. > Changes needed, or desirable, for RDF 1.1 > ----------------------------------------- > > Key: JENA-193 > URL: https://issues.apache.org/jira/browse/JENA-193 > Project: Apache Jena > Issue Type: Umbrella > Components: ARQ, Jena, RIOT > Reporter: Andy Seaborne > > This issue collects changes we might wish to make to Jena for RDF 1.1. > RDF 1.1 is work-in-progress so until specs are formally deined and frozen, > things may change. -- 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