[ 
https://issues.apache.org/jira/browse/ANY23-396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646843#comment-16646843
 ] 

ASF GitHub Bot commented on ANY23-396:
--------------------------------------

Github user HansBrende commented on the issue:

    https://github.com/apache/any23/pull/122
  
    **Implementation note:** I considered using the existing `Configuration` 
interface to construct `TripleWriter` instances, but it seemed rather limited, 
in that settings are only validated when they are first used, rather than 
*failing fast*, and they are all stored as strings rather than the actual 
parsed objects they represent. This is good for settings imported from a config 
file or loaded from the command line, but not very easy, type-safe, or 
performant for programmatic configuration.
    
    So instead, I created `Settings`, which could be considered a type-safe 
version of `Configuration`, or a *parsed* configuration. In the future, we 
could add the ability to create a `Settings` object *from* a `Configuration` 
object, given a set of supported settings and a configuration parser. In a 
future PR, I'm planning to implement a similar concept for `Rover`, so that a 
`Settings` object can be parsed from the command line for each writer. E.g., 
instead of having, simply:
    
    ```
    --format mycustomdecorator,notrivial,turtle
    ```
    we could do something like:
    ```
    --format 
mycustomdecorator,notrivial;alwayssuppresscsstriples=true,turtle;prettyprint=true
    ```


> 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)

Reply via email to