You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2015/10/24 12:14:27 UTC

[jira] [Resolved] (JENA-1052) Provide strict compliance with RFC 3986,3987.

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

Andy Seaborne resolved JENA-1052.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Jena 3.0.1

When RIOt is in strict mode (which not the default), absolute URIs will not be normalised.

> Provide strict compliance with RFC 3986,3987.
> ---------------------------------------------
>
>                 Key: JENA-1052
>                 URL: https://issues.apache.org/jira/browse/JENA-1052
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: ARQ, RIOT
>    Affects Versions: Jena 3.0.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>             Fix For: Jena 3.0.1
>
>
> The "RDF tests" Community Group at W3C is providing community maintenance and enhancement of the RDF and SPARQL test suites.
> As part of that, a number of IRI resolution tests are proposed.  They assume minimal compliance with RFC 3986 and 3987. This means base URIs declared in data (i.e. use of {{BASE}} or {{@base}}) do not have URI normalization applied. 
> Normalization is optional in URI processing. Jena normally performs some normalization. This JIRA will add a switch for strict compliance for HTTP URIs and leave normal processing with the additional normalization step. Normalization of explicit use of absolute {{file:}} URIs will always be performed.
> Turtle and TriG are affected.  N-Triples and N-Quads are not affected and remain with no URI processing; all URIs are treated as presented.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)