-
Notifications
You must be signed in to change notification settings - Fork 2
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
Issues with test cases #33
Comments
I proposed a PR for the second issue. |
I fixed the third issue in #37 |
Added a suggestion for the first issue in #38 , but in this stage I prefer not to replace existing test cases but rather create more if it's an alternative instead of a bugfix, hence the |
made a suggestion for the 4th and 5th issue in #39 |
made a suggestion for the 6th issue in #40 |
made a suggestion for 7th issue in #41 |
added test case 0010 for last issue in #42 |
All looks good. There is just one problem with
But:
And this one has both a returnMap and rml:FunctionExecution. |
yeah I made kg-construct/rml-core#142, so then all tasks of this issue are done |
rml:constant "name" ;
in 0002 not be changed torml:reference "name" ;
The test description states that it tests whether the "false reference" is caught, but the test uses a constant and I do not see what is wrong with this mapping. The spec does not specify that constant expression maps are not allowed for input value maps.id-lab:toUpperCaseURL
a good function for test case 0004? It is underspecified and it does not play nicely with the usual behavior of trying to generate an absolute IRI. I would have understood it the test data contained a IRI, but the test case now assumes that the values is put next tohttp://
http://VENUS
is not a valid absolute IRIhttp:\\
(lower case) when it is missing, but transformshttp://
intoHTTP://
when it is provided.rml:return
other than the nested function call. Maybe 0001?The text was updated successfully, but these errors were encountered: