Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RML Reference implementation does not like XRM Turtle output #138

Closed
ktk opened this issue Feb 20, 2021 · 2 comments
Closed

RML Reference implementation does not like XRM Turtle output #138

ktk opened this issue Feb 20, 2021 · 2 comments

Comments

@ktk
Copy link
Member

ktk commented Feb 20, 2021

It looks like the RML reference implementation RML Mapper is using a stricter Turtle parser than pretty much anything I tested so it will not run the mapping. When I convert it, it works.

I tried figuring out what it is but couldn't find a version that worked. Not sure how to proceed.

@mchlrch
Copy link
Member

mchlrch commented Feb 22, 2021

We don't explicitly validate the generated turtle. I think that so far people have used the generated mappings with processors that have tolerant parsers and therefore no issues.

Here are a few places were the generated turtle is lax and might cause validation issues:

<#AirportMapping>
	rml:logicalSource [
		rml:source "http://www.example.com/Airport.csv" ;
		rml:referenceFormulation ql:CSV      <<==
	];
	
	rr:subjectMap [
		rr:template "http://airport.example.com/{id}" ;
		rr:class transit:Stop ;      <<==
	];
	
	rr:predicateObjectMap [
		rr:predicate transit:route ;
		rr:objectMap [
			rml:reference "stop" ;
			rr:datatype xsd:integer ;      <<==
		];      <<==
	];

@mchlrch
Copy link
Member

mchlrch commented Jul 27, 2022

With XRM version 1.2.0, the generated turtle files now have stricter syntax compliance.

@mchlrch mchlrch closed this as completed Jul 27, 2022
@mchlrch mchlrch transferred this issue from zazuko/expressive-rdf-mapper Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants