Closed bblfish closed 2 years ago
We are working on this and we will solve it in the following iterations: https://github.com/kg-construct/rml-fno-spec/issues/30 In any case, there are other engines (such as R2RML-f) that take as input the base IRI as a parameter in the execution. I don't see any issue here, and this repo is not though for issues but for discussions/questions.
We are working on this and we will solve it in the following iterations: kg-construct/rml-fno-spec#30
great. thanks for the pointer.
In any case, there are other engines (such as R2RML-f) that take as input the base IRI as a parameter in the execution.
Actually rmlmapper-java
does too. That is what the -b
flag is for. The problem it seems is that it also requires. Mhhh. I see the -b flag is for the base URL of the template URLS....
rmlmapper -b http://dodo.org/ -m all_data.csv-rml.ttl -s turtle | head -n 40
[...]
<http://dodo.org/all#m_0> a sosa:Observation .
<http://dodo.org/all#m_1> a sosa:Observation .
<http://dodo.org/all#m_10> a sosa:Observation .
Ok, that was not clear to me. I'll check their documentation. I guess it's a bit new to me to have two different relative URLs to deal with. Perhaps they should call -b
, --template-url
instead...
I don't see any issue here, and this repo is not though for issues but for discussions/questions.
Btw. I found it difficult to find the right place to report questions on the spec itself.
I suggest that the spec itself ( https://rml.io/specs/rml/ ) point to the github repo where it is being developed, and that in the front README of that repository, the various entry points for discussion are linked to.
Ok, that was not clear to me. I'll check their documentation. I guess it's a bit new to me to have two different relative URLs to deal with. Perhaps they should call
-b
,--template-url
instead...
This is an implementation-related issue, so nothing to do here ;-)
Btw. I found it difficult to find the right place to report questions on the spec itself.
I suggest that the spec itself ( https://rml.io/specs/rml/ ) point to the github repo where it is being developed, and that in the front README of that repository, the various entry points for discussion are linked to.
Please move this suggestion to the discussions section. Although it's something that we are currently doing, see for example the RML-star spec: https://w3id.org/kg-construct/rml-star and https://github.com/kg-construct/rml-star-spec
I have the following template
For data such as
The need for a @base is a bug in https://github.com/RMLio/rmlmapper-java/issues/178 I believe. More tricky is the behavior of rr:template.
Currently
rmlmapper-java
transforms that to full urls using the base of the mapping document in which it appears. But that is rarely going to be what one wants: one does not want to place the potentially huge instance data in the file in which the mapped data goes: especially when mapping data from many different files.So there needs to be a way to spacify the base for the template in the RDF document, or if not set, it should be left as a relative URL in the generated document.
For the moment the output is