[
https://issues.apache.org/jira/browse/ANY23-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612407#comment-16612407
]
ASF GitHub Bot commented on ANY23-396:
--------------------------------------
Github user HansBrende commented on the issue:
https://github.com/apache/any23/pull/121
Aside from the comments I've made on this PR, I'm still not convinced that
having a ModelExtractor is a good idea in the first place. Why not just create
a ModelWriter (as in ANY23-397) or an equivalent "collecting" TripleHandler,
and then allow the end user to transform the collected statements however they
wish?
Having a ModelExtractor creates additional questions & complexities: in
what order are the extractors executed? (Certainly the ModelExtractors would
have to be executed last in order to have access to all previously collected
statements.) What if multiple ModelExtractors are declared? Which ones have
higher precedence in the extraction order?
I'm not sure that having a dedicated ModelExtractor is worth the trouble of
dealing with these complexities, when a user could accomplish the same thing by
simply transforming the statements collected by a ModelWriter or equivalent, or
defining their own filtering and/or mapping TripleHandler.
> Add ability to run extractors in flow
> -------------------------------------
>
> Key: ANY23-396
> URL: https://issues.apache.org/jira/browse/ANY23-396
> Project: Apache Any23
> Issue Type: Improvement
> Components: core
> Affects Versions: 2.2
> Reporter: Jacek Grzebyta
> Assignee: Jacek Grzebyta
> Priority: Minor
>
> Currently extractors do not work in flows. I.E. Next extractor has no any
> access to triples made by previous one.
> It would be useful if an extractor has possibility to modify triples created
> by another extractor.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
