Ability to provide base IRI for parsing relative IRIs in input files #129

tpluscode · 2025-01-26T21:24:28Z

When an input has no @base, the file's URL is used to parse relative references.

I would like to ask for a --base or --base-iri CLI option to set the base for parsing if the base directive is missing.

The text was updated successfully, but these errors were encountered:

josd · 2025-01-27T12:57:44Z

For eye you can use

--wcache <uri> <file>           to tell that <uri> is cached as <file>

tpluscode · 2025-01-27T13:29:37Z

Hm, that did not work.

I have a base.n3 file:

PREFIX ex: <http://example.org/>

<foobar> a ex:Foo .

{
  <http://localhost/foobar> a ex:Foo .
} => {
  <http://localhost/foobar> a ex:Bar .
} .

I expected that calling with --wcache http://localhost/ base.n3 would do the trick but it still parses the relative reference as file:// URL

> eye --nope --quiet --pass --wcache http://localhost/ base.n3 base.n3  
@prefix ex: <http://example.org/>.

<file:///absolute/path/foobar> a ex:Foo.

tpluscode · 2025-01-27T13:47:37Z

I'm also unsure how this is going to work when there are multiple files like that. Consider foo.n3 and bar.n3

eye --nope --quiet --pass --wcache http://localhost/ foo.n3 foo.n3 --wcache http://localhost/ bar.n3 bar.n3

The description of --wcache suggests that this is not valid usage and each usage should have a different value of <uri>?

josd · 2025-01-27T14:28:58Z

It works as follows:

$ eye --nope --quiet --pass --wcache http://localhost . http://localhost/base.n3
@prefix ex: <http://example.org/>.

<http://localhost/foobar> a ex:Foo.
<http://localhost/foobar> a ex:Bar.

and we use it all the time for multiple files, either by specifying a "directory", like the above . or by multiple --wcache options

josd · 2025-01-27T14:31:45Z

for examples see all test files in the subdirectories of https://github.com/eyereasoner/eye/tree/master/reasoning

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ability to provide base IRI for parsing relative IRIs in input files #129

Ability to provide base IRI for parsing relative IRIs in input files #129

Ability to provide base IRI for parsing relative IRIs in input files #129

Ability to provide base IRI for parsing relative IRIs in input files #129

Comments