Open jensscheerlinck opened 5 years ago
Hi,
Thanks for reporting this.
In a rr:predicateMap, only an rr:constant
is implemented. rr:column
and rr:template
are not implemented. To implement these would mean parsing them inside the loop in [1], in which only rr:constant
is currently parser. A possible workaround would be creating one rr:predicateObjectMap
per value in the TestColumn
. Since these values are meant to be properties, I would assume their number is manageable?
Hi,
Thanks for the response.
Unfortunately we have some 30 different values in the 'TestColumn'. Currently we have indeed split these up into 30 different maps. Which has a big impact on performance.
Creating different rr:predicateObjectMap elements would also be a possibility. However, we also tried this out before and the result was a very sparse matrix that made overall performance even worse.
Hi there. I was just wondering if you plan to support this feature in the near future? I'm currently running with the workaround mentioned above, but it would greatly simplify my mapping file if I could just use rr:templates in predicate position ;-)
When trying to use a rr:predicateMap with a rr:column or rr:template value, the parsers produces no results.
Example:
I only get the desired triples when using
rr:predicateMap [ rr:constant ex:test ]
orrr:predicate ex:test