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

using parameters in the templates #9

Open
seralf opened this issue Nov 30, 2016 · 4 comments
Open

using parameters in the templates #9

seralf opened this issue Nov 30, 2016 · 4 comments

Comments

@seralf
Copy link
Contributor

seralf commented Nov 30, 2016

Hi

I have a case in which I need to provide at runtime certain parameters, in order to select the correct source from a collection of similar sources, and at the same time this should reflect on the generated uri.

Considering the following snippet from an example mapping based on some of the provided ones:

<#AirportMapping>
    rml:logicalSource [
		rml:source "{date}/airport.csv";
		rml:referenceFormulation ql:CSV
    ];
    rr:subjectMap [
	 rr:template "http://airport.example.com/{date}/{id}";
	 rr:class transit:Stop ;
    ];

I can correctly run

java ... RML-Mapper.jar -m my_mapping.ttl -o my_dump.ttl -p date=2016

then the processor correctly search for /2016/airport.csv, but it did not create (as I was wrongly expected) the subject(s) for http://airport.example.com/2016/...
In other terms my question is: Is there any way to interfere on the uri templates using parameters passed at runtime?
I think once a parameter is passed from command line as a key/value pair, it could be helpful and very natural to have it available for templating.

@canarvaeza
Copy link

Hi,

Did you solve this?

@seralf
Copy link
Contributor Author

seralf commented Apr 9, 2018

no, I didn't sorry

@canarvaeza
Copy link

I think this option should be really usefull.

@chiarisilver
Copy link

It would be very useful also for me!

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

3 participants