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

Hudson commented on ANY23-83:
-----------------------------

Integrated in Any23-trunk #489 (See 
[https://builds.apache.org/job/Any23-trunk/489/])
    ANY23-83 : Remove fixme note that is now fixed (Revision 1448890)
ANY23-83 : Support arbitrary RDFFormats for VocabPrinter without being manually 
added to the list (Revision 1448888)

     Result = ABORTED
ansell : 
Files : 
* /any23/trunk/core/src/main/java/org/apache/any23/vocab/RDFSchemaUtils.java

ansell : 
Files : 
* /any23/trunk/core/src/main/java/org/apache/any23/cli/VocabPrinter.java
* /any23/trunk/core/src/main/java/org/apache/any23/vocab/RDFSchemaUtils.java
* /any23/trunk/core/src/test/java/org/apache/any23/vocab/RDFSchemaUtilsTest.java

                
> Remove hardcoded formats throughout Any23 to make it useful as a library
> ------------------------------------------------------------------------
>
>                 Key: ANY23-83
>                 URL: https://issues.apache.org/jira/browse/ANY23-83
>             Project: Apache Any23
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.0
>            Reporter: Peter Ansell
>            Assignee: Michele Mostarda
>             Fix For: 0.8.0
>
>         Attachments: any23-rdfwritertriplehandler.diff, 
> any23-rio-naive-mime-detector.diff
>
>
> Many classes inside of Any23 seem to hardcode restrictions on the supported 
> formats, making it difficult to utilise Any23 as an extensible library. 
> One example of this are RDFSchemaUtils that artificially restricts itself to 
> three formats using an enum mapping, where it could easily accept any 
> RDFHandler, even if it were not an RDFWriter. 
> Another example is RDFUtils where the list of RDFParser's is hardcoded in, 
> and enforced using an enum.
> What was the reasoning for creating artificial format classes and manually 
> mapping them to writers/parsers instead of using either allowing any 
> RDFHandler in the first case, or allowing any accessible RDFParser in the 
> second case, using Rio.getParser() to avoid hardcoding anything.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to