Skip to content

Clarify time searching? #149

@rorlic

Description

@rorlic

The TREE specification says:

Same as the previous example but with the predicate tree:timeQuery expecting an xsd:dateTime.

This part is clear to me: when filling in the search form, the hydra variable should be provided as a xsd:dateTime literal value and will result in a URL that can be requested.

This time however, when the page itself does not exist, a redirect is doing to happen to the page containing the timestamp. A tree:path can indicate the time predicate which is intended.

I assume there is a typo and should read:

a redirect is going to happen

If a page exists at this URL, the server returns it. That part is clear.
If no page exists at this URL, a redirect happens to the page containing the timestamp. This part is unclear to me.

I understand that because the server offers this search form it knows what predicate path (should it be property path?) to use for comparison. But, what does it compare against? I assume members as it says:

can indicate the time predicate which is intended

What happens if no member matches the given value? A not-found (404) HTTP result?
What happens if multiple members match that value in different pages?

Maybe we can clarify this in the TREE specification?

In addition: if it is a property path instead of a predicate path then the result of applying this property path can be multiple values. Does a member match if ANY of these values match the given timestamp?

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