[
https://issues.apache.org/jira/browse/JENA-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-318.
--------------------------------
Resolution: Fixed
Fix Version/s: Fuseki 0.2.5
TDB 0.9.4
The Turtle/NTriples routers would have not allowed the lang tag at the parsing
stage.
RDF/XML just has uninterpreted strings for lang tags so needs checking.
1/ Add mode to RIOT to generate a parse error for bad lang tags
2/ Make Fuseki protect against errors when inserting bad data (PUT, POST,
Upload)
> Illegal language tags (in RDF/XML) can cause exceptions in Fuseki+TDB.
> ----------------------------------------------------------------------
>
> Key: JENA-318
> URL: https://issues.apache.org/jira/browse/JENA-318
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
> Fix For: TDB 0.9.4, Fuseki 0.2.5
>
> Attachments: JENA-318-data-bad-lang.rdf
>
>
> (split from JENA-163)
> Alexander Dutton writes:
> It seems to be the following language tags in the data that cause this issue:
> * i18n
> * sr@latin
> Both have invalid syntax as per BCP 47, but it might be worth catching this a
> little earlier and throwing a more appropriate error:
> [alex@lucy jena-fuseki-0.2.4]$ curl -XPUT
> "http://localhost:3030/public/data?graph=http://creativecommons.org/publicdomain/zero/1.0/rdf";
> -d@rdf -H"Content-type: application/rdf+xml" -i
> HTTP/1.1 100 Continue
> HTTP/1.1 500 Different ids for http://xmlns.com/foaf/0.1/logo: allocated:
> expected [000000000000041D], got [000000000000041A]
> Access-Control-Allow-Origin: *
> Server: Fuseki (0.2.4)
> Content-Length: 0
--
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
