incubator-any23-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Ansell (JIRA)" <>
Subject [jira] [Updated] (ANY23-83) Remove hardcoded formats throughout Any23 to make it useful as a library
Date Fri, 11 May 2012 01:05:50 GMT


Peter Ansell updated ANY23-83:

    Attachment: any23-rdfwritertriplehandler.diff

Patch to make RDFWriterTripleHandler accept any RDFHandler instead of RDFWriter to make it
more generic
> Remove hardcoded formats throughout Any23 to make it useful as a library
> ------------------------------------------------------------------------
>                 Key: ANY23-83
>                 URL:
>             Project: Apache Any23
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.0
>            Reporter: Peter Ansell
>         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
> 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:!default.jspa
For more information on JIRA, see:


View raw message