[
https://issues.apache.org/jira/browse/ANY23-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637158#comment-16637158
]
ASF GitHub Bot commented on ANY23-396:
--------------------------------------
Github user lewismc commented on the issue:
https://github.com/apache/any23/pull/122
> The only reason I've hesitated so far about merging this PR is that once
new interfaces are introduced as part of the core API, I'd prefer to never
change them again--so I want to get it right the first time!
Totally understandable
I really like the idea of improving the interoperability logic here.
> The reason being: shouldn't all return types...be, preferably, part of
our own API, rather than RDF4J's?
Yes that is a very fair statement. What, for example happens if and when
the RDF4J project ceases to exist? Then of course we would end up implementing
exactly what you are suggesting.
I am certainly +1 to a TripleFormat API which is somewhat analogous and
certainly interoperable with RDF4J's
[RDFFormat](http://docs.rdf4j.org/javadoc/latest/index.html?org/eclipse/rdf4j/rio/RDFFormat.html).
Very nice @HansBrende
> 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)
