Skip to content

Have separate client algorithms in different documents #115

Description

@pietercolpaert

At this moment there are 2 different client algorithms specified with the ordered mode and the unordered mode. I think it would make sense to have this in 2 separate documents: a simple and straightforward to implement document for the simple use cases, and a more elaborate specification for ordered traversal. This would probably make it much clearer and simpler on how to implement this, and would probably also open a clearer avenue to in the future evolve the client algorithms to for example RDF-Message based designs.

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