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:39:49 GMT

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

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

"- About the suggested RDFParserTripleHandler: the RDFParserTripleHandler is a TripleHandler
meant to serialize the received messages
  so it has to accept an RDFWriter, despite the current small difference between an RDFHandler
and an RDFWriter it is cleaner to use the first,
  also keeping in mind future evolutions of such interface. "

The RDFParserTripleHandler code only uses the RDFHandler API currently. I don't have a use
case for it currently, but I think it would be nice to allow any RDFHandlers even if they
do not implement the full RDFWriter API. if you want to allow the future possibility of using
the RDFWriter API in addition to the RDFHandler API then it would be best for API stability
to leave it at the more restrictive RDFWriter.

                
> 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