Github user HansBrende commented on the issue:
https://github.com/apache/any23/pull/121
Another thought:
Using the TripleHandler interface (as intended) to transform triples,
rather than a separate ModelExtractor, has the added advantage that the triples
might not necessarily need to be stored in memory during the transformation
process. The user could implement either a "collecting" triple handler which
stores statements in memory prior to transforming them, or a "streaming" triple
handler for transformation-on-the-fly (e.g., if mapping some predicate A to
some other predicate B), or some combination of these two concepts. The
"collecting" ability could be easily supplemented with a `ModelWriter` or
equivalent, as in [ANY23-397](https://issues.apache.org/jira/browse/ANY23-397).
But adding a separate "ModelExtractor" concept only muddles this
already-existing ability to transform triples with TripleHandlers by
introducing a redundant construct of more limited abstraction power than what
already exists.
So for me:
-1 for ANY23-396
+1 for ANY23-397
@lewismc any thoughts?
---
