Skip to content

Confusing API for parsing and serializing #57

@renyuneyun

Description

@renyuneyun

The library doesn't have a consistent API for use in parsing and serializing RDF files (currently only Turtle, if I understand correctly), also without clear/correct documents.

For example:

  • parseTurtle() and parse() both exist
    • parse() is marked deprecated, which makes sense
    • However, their internals are different, leading to different parsed results, and how the Graph object should be used subsequently
    • A cleaner way is to provide a NewGraph class for the new parsing method, if it's not stable enough, and then fully replace the old one after mature; or use a different branch, etc
  • graph.serialize() and graph.serializedString both exist, without clear documentation
  • graph.serialize() has an optional parameter that is confusing, and also leading to inconsistent behaviours

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions