-
Notifications
You must be signed in to change notification settings - Fork 12
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
Input file path and type not abstracted from rml mapping #10
Comments
Reckon it's something we could work on @anuzzolese? Also are there any tests? |
Hi @henrieglesorotos, if i got the problem you are referring to correctly I would say that it is somehow implemented (maybe not the best solution, but we can discuss about improvements). In fact, pyrml supports the parametrisation of RML mapping files by relying on Jinja2. RML files processed by pyrml can accepts parameters as Jinja2 does, e.g.:
Than when you instantiate your mapper in the Python code you can do something like this:
|
This is excellent news! Can we add to the docs? Also - shall we create some simple tests if they don't exist? |
Yes, controbuting in documenting and providing how-to guides would be utmost helpful. |
Having some issues. See example below: We have some pre-existing rml rules in
Input file:
I am getting:
Any ideas? |
Btw - we generally work in yarrrml so it's simpler, and then convert using https://github.com/RMLio/yarrrml-parser |
FYI:
|
Did you manage to replicate this @anuzzolese ? |
Currently the input file can't be parameterised via cli or api. It is hardcoded into the mapping file. Eg:
It would be more flexible to be able to provide this as a parameter.
The text was updated successfully, but these errors were encountered: