Skip to content

Clarify the use of ldes:sequencePath in tree:path in addition to ldes:timestampPath #111

@rorlic

Description

@rorlic

It's a detail, but in section 3.5.2. Ordered it says:

The client in ordered mode MUST check, during the initialization phase, whether ldes:timestampPath and/or ldes:sequencePath is set. If not, it MUST return an error, as order cannot be guaranteed.

but further down there is no more mentioning of ldes:sequencePath:

A client MUST check whether the ldes:timestampPath is used in the tree:path. Only then can the relation be used for ordering.

Maybe add and/or ldes:sequencePath again?

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