[ANY23-83] Remove hardcoded formats throughout Any23 to make it useful as a library

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7.0
• Fix Version/s: 0.8.0
• Component/s: core
• Assignee: Michele Mostarda
• Reporter: Peter Ansell
• Created: 09/May/12 06:26
• Updated: 01/May/13 23:06
• Resolved: 22/Jan/13 03:40

Description

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.

Issue Links

• is blocked by: ANY23-119 Split extractor implementations out into a new module