Apache Any23
  1. Apache Any23
  2. ANY23-83

Remove hardcoded formats throughout Any23 to make it useful as a library

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.7.0
    • Fix Version/s: 0.8.0
    • Component/s: core
    • Labels:
      None

      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

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Michele Mostarda
              Reporter:
              Peter Ansell
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development