Peter Ansell created ANY23-83:
---------------------------------
Summary: 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
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
