Open natuk opened 6 years ago
I understand the usefulness of this feature. Technically this can be supported.
However, imho this is a feature that does not fit in a generic transformation engine, in the sense that doing that makes the engine bound to a particular format (RDF, OWL) and it makes it schema dependent.
You might wonder about the first claim (i.e. bound to a particular format such as RDF). It is true that for the moment X3ML engine supports this type of output format, however, it has been designed to support (and it will in future releases) other formats as well (i.e. XML)
Absolutely, I appreciate that this is a feature that only applies to RDF. And it probably breaks the backward compatible transformations as well. I am just highlighting it as an extremely useful feature for one of the main workflows that the X3ML engine serves. I was hoping that it would require relatively little effort to implement.
During mapping the inverse properties (PXXi) can be used depending on the nature of the data. Generic Linked data implementation searching the resulting triples may not be able to pick up inverse properties. Would it be possible to add an option in the command line tool to convert all triples with inverse properties to their forward equivalents?