incubator-any23-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michele Mostarda (JIRA)" <>
Subject [jira] [Commented] (ANY23-83) Remove hardcoded formats throughout Any23 to make it useful as a library
Date Sun, 13 May 2012 16:54:47 GMT


Michele Mostarda commented on ANY23-83:

Hi Guys,
about #ANY23-19: I don't like the idea to add an abstraction library, it would add useless
complexity and compromise performances.
Furthermore we would be conditioned to wait the update of the abstraction library to access
any evolution of the underlying libraries.

About patches:
- I've improved the NaiveMIMETypeDetector logic as suggested by the submitted patch. See r1337905.
- I've improved the RDFUtils library renaming/adding/refactoring methods to improve flexibility
and usability. See r1337919, rr1337933.
- 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.
- I've improved the NQuads Parser/Writer integration with Sesame RIO registering all via SPI.
See r1337933.

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