Closed mchlrch closed 4 years ago
@mchlrch ready to play with.
what about SourceType.RDB? see InputOutputCompatibility:37
InputOutputCompatibility is now configured as follows:
@ktk What do you think, does that make sense to you or should the rules be different?
I tested this feature manually, it works as requested. The comments in the mapping files of runtime-EclipseXtext/editor-test were helpful for doing the manual testing.
I will keep this issue open until we have also added unit-tests for the new validations (see RdfMappingValidator.xtend)
I tested this feature manually, it works as requested. The comments in the mapping files of runtime-EclipseXtext/editor-test were helpful for doing the manual testing.
I will keep this issue open until we have also added unit-tests for the new validations (see RdfMappingValidator.xtend)
added missing tests validations for these issues:
all validations seems to be covered by tests now.
Currently, the three output formats
r2rml
,rml
andcsvw
are generated opportunistically. The user cannot choose the desired output.There is interdependence of the output format with the source and the mapping, for example:
csvw
output requirescsv
sourcer2rml
orrml
output require respective specification in the mapping but is irrelevant forcsvw
outputThe DSL user currently has no guidance and needs to rely on (inexistant) documentation to handle the variability. Instead of that, the DSL should support the user with code-assist and validation that is aware of the output format.
Solution proposal:
output r2rml
output csvw
from mappings onxml
sources