[JENA-1713] Riot emits a WARN on valid IRI data

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Jena 3.10.0
• Fix Version/s: Jena 3.12.0
• Component/s: IRI
• Assignee: Andy Seaborne
• Reporter: Gregory Williams
• Created: 24/May/19 19:33
• Updated: 01/Jun/19 15:03
• Resolved: 27/May/19 14:44

Description

 

riot 3.10.0 emits a NON_INITIAL_DOT_SEGMENT warning on data that I believe if valid:

 

$ cat test.ttl
@base <http://example.org/foo/bar/> .
<./../../../useless/../../../still-root> <> "not ok" .

$ riot -q test.ttl
10:56:50 WARN riot :: [line: 2, col: 1 ] Bad IRI: <http://example.org/still-root> Code: 8/NON_INITIAL_DOT_SEGMENT in PATH: The path contains a segment /../ not at the beginning of a relative reference, or it contains a /./ These should be removed.
<http://example.org/still-root> <http://example.org/foo/bar/> "not ok" .

 

The resulting IRI is what I expect, but the warning seems spurious. The cited ref text in the definition of that warning suggests that it should only be warning if the dot segments are used outside of a relative IRI:

The complete path segments "." and ".." are intended <em>only</em> for use within relative references

In this example, however, they are being used in a relative IRI, and seem to be successfully removed during resolution against the base IRI to produce the expected output.

 

Issue Links

• links to: GitHub Pull Request #570