You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that it does not mention constant-valued term maps.
My interpretation is therefore that that rr:termType is not intended to alter the value of an rr:constant.
Obviously, the mapping can be simply written as
:om_0 a rr:ObjectMap;
rr:constant <http://vocab.gtfs.org/terms#StopTime>.
I am raising this issue because we stated evaluation of another R(2R)ML system which complained about some of the mapping files for the described reason.
The text was updated successfully, but these errors were encountered:
Thanks for using the benchmark and also pointing this!
Indeed, it's a bug during the translation from YARRRML to RML with YARRRML-parser. See this issue.
I took the gtfs-csv.yaml and translate it with our new translator https://github.com/oeg-upm/yatter. Can you take a look and see if it resolves your current problem? mapping.txt
dachafra
changed the title
Mixing rr:constant "string" with rr:termType rr:IRI seems to violate R2RML spec.
Change YARRRML translator to yatter
Feb 28, 2023
We just used a simple sparql update statement to fix it.
I just tested with your mapping.txt file and it looks fine. If with yatter in the future the mappings work out of the box then just the better :)
First of all, thanks for the work of providing this excellent resource.
Describe the bug
The mapping files such as
gtfs-bench/mappings/gtfs-csv.rml.ttl
Line 35 in ad19b9b
7.1 Constant RDF Terms states:
7.4 IRIs, Literal, Blank Nodes states:
Note that it does not mention constant-valued term maps.
My interpretation is therefore that that rr:termType is not intended to alter the value of an rr:constant.
Obviously, the mapping can be simply written as
I am raising this issue because we stated evaluation of another R(2R)ML system which complained about some of the mapping files for the described reason.
The text was updated successfully, but these errors were encountered: