incubator-any23-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Ansell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ANY23-83) Remove hardcoded formats throughout Any23 to make it useful as a library
Date Sun, 13 May 2012 23:43:49 GMT

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

Peter Ansell commented on ANY23-83:
-----------------------------------

"- I've improved the NaiveMIMETypeDetector logic as suggested by the submitted patch. See
r1337905. "

I think there is also the possibility of an equivalent patch for the TikaMIMETypeDetector
as a backup for cases where Tika doesn't reveal a MIME-type but Rio might provide it. See
https://github.com/ansell/any23/commit/6da60d6b92932f08a7ca9f08a3cdf9aa74615bb2


                
> 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.7.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message