In most common scenarios, a GET on the resource URL returns an RDF response with information about this resource.
I have a scenario where the server expects some parameters from the client, in order to return a correct response.
For example, depending on “startTime” & “endTime” parameters, the value of a certain property - say dcterms:description will differ.
The properties startTime & endTime are themselves not necessarily even part of the resource description.
The client needs to link to a specific resource description that is parameterized.
How can I best model this using OSLC?
I am thinking of the approach below. I wonder if anyone can identify any problem with that? Is there any other way I can solve this?
Define the resource URL with query parameters (http://example.com/resource/r1?start_time=20201101&end_time=20201201) or path paramters (http://example.com/resource/r1/start_time/20201101/end_time/20201201).
I suspect this ought to be fine, since the query part is a valid part of the resource URL?
But then it looks like there is an endless set of resources, since the paramters can be of any value.
With this approach, I am also thinking that the base “http://example.com/resource/r1” can be seen as a ServiceProvider, with an OSLC Query service that can return all possible resources (with URLs with query/path parameters)
Can anyone see a problem with this approach? Is there any other way I can solve this?