-
Notifications
You must be signed in to change notification settings - Fork 0
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
Files and carml-jar #143
Comments
I understand this as follows: carml requires different For stream sources:
For file sources:
Using The new requirement is now, that both variations can be generated from xrm. Is that correct @ktk ? |
Correct interpretation. It would be nice as people can use XRM and create carml output without having to interact with streams that way. For those that do not necessarily use a barnard59 pipeline, that's probably a nice thing to have. |
Ran into this again btw. I think for pure carml-cli mode, this feature would be useful. So either have an anonymous (empty) stream or a filename with |
There is a new cli tool for carml available: https://github.com/carml/carml-jar
I could get it to work with XRM
carml
output but I had to figure out how to do it properly. With the current configuration I can only get it to work with piping the file as a stream and I have to do the XRM source like this:source ""
. This generates:I can then run:
cat input/eCH0071.xml| java -jar bin/carml-jar-1.0.0-SNAPSHOT-0.4.4.jar map -m src-gen/mapping.carml.ttl
However, I cannot run it directly from a file, I always have to pipe it. So I checked out the carml docs and it says the name can be left out or empty, so that seems to be correct.
So I checked out the ontology and I found stream:url, so I changed the generated output to this (manually):
And then I can run it directly from file:
java -jar bin/carml-jar-1.0.0-SNAPSHOT-0.4.4.jar map -m src-gen -rsl input -of ttl -P
This probably would work in XRM via
rml
output but I use the XML Namespace extension so I have to stick with carml-syntax.Not sure how to handle that properly in XRM though, would be nice if both options could be generated.
The text was updated successfully, but these errors were encountered: