Xavier Sosnovsky

Received via the SDMX mailbox and related to this issue: "There is my view a feature that would be nice to have for avoiding possible timeout and improving the responsiveness...

This might be useful for item schemes too (cf. [initial request](https://github.com/sdmx-twg/sdmx-rest/issues/173) from @buhaiovos)

Re. item schemes, there are some rather large codelists (with up to 1 million codes for example). See [related discussion](https://github.com/sdmx-twg/sdmx-rest/discussions/175).

Was possible with SOAP but SOAP has been deprecated

(Note to self before the analysis starts: This is not trivial for the structure specific formats)

Let's take the attached fictive DSD as example (and let's ignore OBS_COM):  And let's take the following dataset:  If I query for `D.CHF.`, I would expect it to...

Thanks, @dosse The reference metadata is the part of the spec I know the least, so I would prefer to forward the question to @agent96 :-). It definitely looks useful...

Fixed in the `develop` branch

Good point indeed! It sounds logical to me that updatedAfter applies to anything matching the query. On the other hand, asking for a *datastructure* resource and then getting a response...

We might want to rethink the use cases again and see whether existing HTTP features (like conditional GET requests) might be sufficient.