RML-Core test cases are too dependent on RML-IO #87
Labels
documentation
Improvements or additions to documentation
help wanted
Extra attention is needed
pending
Waiting for another spec or issue to be ready
proposal
issue has a proposal to be solved
test-cases
Test cases need to be updated
Problem
Engines implementing RML-Core should no bother with all different Source descriptions like CSV, XML, JSON, RDB, SPARQL, etc.
to be RML-Core compliant. However, the current test-cases exist in the different Source descriptions. Thus if an engine would cover RML-Core and do not support a certain format, it's coverage would drastically fall, even though it may have perfect RML-Core support.
Moreover, different source support is out of scope of RML-Core as it is part of RML-IO.
Proposal
Drop all source specific test-cases in RML-Core and add the different sources to RML-IO.
RML-IO currently focus on RML Logical Target tests, Logical Source is missing as it is covered by RML-Core.
Keep the CSV variant for all test-cases in RML-Core because we cannot test anything without input data. CSV is the easiest to support (no iterator) and can be loaded easily into a RDB. For RDB support loading the CSV + updating the Logical Source suffice.
Special features like datatype extraction from RDBs and possible other formats like integer, floats in JSON, could be added as specific test-cases in RML-IO.
Discussion
Let's discuss this properly! This is not a blocker for the KGCW Challenge as it does not involve a specification change, only a move and refactoring of the test-cases. Engines supporting RML-Core and RML-IO should still have the same coverage like now.
The text was updated successfully, but these errors were encountered: