-
Notifications
You must be signed in to change notification settings - Fork 8
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 in test cases #83
Comments
Here are some suggestions for simple datatype tests:
The last one assumes In other words, the datatype map "behaves" like a IRI generating term map. |
The ones covered by shapes are listed in tests.py:
These should already raise an error by the engine if they use the SHACL shapes to validate the mapping. Regarding 19a, that one might be a bit in the flux. Regarding 19b, is on purpose with a data error. The test-cases currently assume 'best-effort' in that case. Regarding 20b, why is that an error? The RFC for URIs (https://www.rfc-editor.org/rfc/rfc3986#section-4.1) says that it can be resolved if needed. It is a valid IRI. Datatype maps are missing yes, feel free to put it in a PR, thanks a lot! If you don't have time, I can do it as well, let me know. |
Aha! Okay, I understood that the test cases (for engines) assume valid mappings. In other words, you now assume that each engine uses the shapes (or something else) to cover all cases. Which is OK, but I misinterpreted that. 19a --> Assuming the base IRI of the mapping is the same as the output is a dangerous assumption. You could leave it for the tests for backward compatibility with previous engines, but I would propose to document it as (either 19b --> "best effort" contradicts with "generating no file" so you want to be strict. You retain partial results of the same triples map. 20b --> Based on R2RML --> the string is tested for being an absolute IRI and does not mention anything about trying to compute the absolute IRI where possible. RML can propose this, but I have yet to find this mentioned in the spec. RDF does allow one to store information about |
Well not required but engines should not crash with invalid mappings. Thry can make their life ewsy by using the shapes or do it manually.
I agree here. I just need a way forward. Dropping the testcase seems the best way, we don't want engines to support this behavior. Do you agree?
Agreed! Especially this kind of stuff needs to go, the test cases must always follow the same paradigm. Let's change it to an error.
Exactly! This is a whole can of worms so we need to pick a side here. These URIs are valid ones because they are in the end absolute. So not resolving? But if not resolving we can allow this case right? |
Agree to drop the case. Well, turning
|
I think this is all resolved? @chrdebru |
Yup! |
IDs
does not exist in the source and the mapping should not generate an output5*8ALPHA
(src: https://www.rfc-editor.org/rfc/rfc5646). I would not vouch for using a lit of valid tags, but may restrict the spec in explicitly referring to the first language rule:language = 2*3ALPHA["-" extlang]
http://example.com/base/path/../Danny
is not an absolute IRI."\\{\\{\\{ {$.['ISO 3166']} \\}\\}\\}"
The text was updated successfully, but these errors were encountered: