Set up "hydra:search" endpoints to filter items/ids (IRITemplate)

I’m submitting a

• feature request.

Current Behaviour:

As discussed in this issue in the Specs https://github.com/HydraCG/Specifications/issues/168#issuecomment-404415370 hydrus should provide an endpointbased on hydra:search to introspect/filter items and ids. In particular:

Expected Behaviour:

As described in the issue mentioned above:

A better way for the client to discover the ID of an object would be, IMHO, to query the server for that object based on functional dependencies. E.g.: find the book with ISBN 123456 ; find all sensors on network X with serial number Y. That way, the client does not have to know how the server generates ID, and the server does not have to commit forever to a given way of generating IDs. All the server has to do is to provide the “search” functionality described above.

[Mec-iS]

This is an advanced topic and this issue will be part of the Summer Of Code (see label). hydra:search is in the spec: https://github.com/HydraCG/Specifications/blob/master/spec/latest/core/core.jsonld#L404

First of all you should understand what an IRITemplate is, we are having a conversation about here: https://github.com/HTTP-APIs/http-apis.github.io/issues/7 If you want you can contribute by writing a page that explains what it is needed to know.

[knakul853]

@Mec-iS can you explore bit more : )