Extra structure endpoints in the api specification @ odbx

[fekad]

https://odbx.science/optimade/v0/extensions/docs#/Structure

The section structure is not related to optimade. As far as I see it two API has been merged into one. Of course, it is reasonable but if the client code wants to use the openapi.json file it might hit some endpoints without knowing how to handle them.
For example, in the case of '/structures' endpoint, the response is an HTML page, not even a valid JSON data.

As a workaround, it is possible to ignore all the extra/unknown endpoints in the code of the client.

If you think it is not an issue or it has been discussed before please feel free to close it anytime.

[fekad]

The API implementation MAY provide other entry types than the ones standardized in this specification, but such entry types MUST be prefixed by a database-provider-specific prefix.

https://github.com/Materials-Consortia/OPTIMADE/blob/develop/optimade.rst#51entry-listing-endpoints

To be honest I think this is too restricted...

[ml-evs]

Hey @fekad, thanks for checking this out. I'm in the process of separating my JSON REST and HTML API so I can be more free with the HTML. Does your complaint also apply to https://optimade.odbx.science/v0/extensions/docs#/Structure? I think I have sorted out SSL etc. on this new subdomain so just need to update the link in the providers repo.

[ml-evs]

I'm going to close this here and make the PR to providers so that the link can be updated. If you find any issues with http://optimade.odbx.science please do report them @fekad! Thanks again.

[ml-evs]

Feel free to review Materials-Consortia/providers#22 ;)