[
https://issues.apache.org/jira/browse/ANY23-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16612705#comment-16612705
]
ASF GitHub Bot commented on ANY23-396:
--------------------------------------
Github user HansBrende commented on the issue:
https://github.com/apache/any23/pull/121
@jgrzebyta But as far as rover goes, you're right: we currently don't have
support for using an arbitrary triple handler. Looks like it expects an
RDFFormat and then finds a triple handler based on that.
I wonder if it would be possible to allow a more flexible way to specify
triple handlers as rover arguments to fix this problem? While I don't think
that creating a `ModelExtractor` as currently defined in this PR is the way to
go, I do think that rover needs to be improved in this respect.
I will think on this.
> 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)
