Refresh htsget interop site

[brainstorm]

The other endpoints seem to be either old (htsget ~0.2) or having SSL certificate issues. So this site needs a bit of a refresh in order to have htsget developers interact with endpoints that are up to date (i.e: supporting /service-info).

Might be useful to have the administrative contact info for those endpoints handy somewhere (perhaps on that same page?).

/cc @mlin @jb-adams @ohofmann

[brainstorm]

There are some asset retrieval issues too:

[jb-adams]

Thanks @brainstorm !

Additionally, I'd like to get the currently running servers registered on the GA4GH service registry. It's a general-purpose registry of web services implementing GA4GH standards using the service registry specification. OpenAPI

example requests:
https://registry.ga4gh.org/v1/services
https://registry.ga4gh.org/v1/services?type=org.ga4gh:htsget:*

For htsget, only the GA4GH server is currently registered. But I'd like to get multiple servers registered for interop, testing, FASP, visibility, etc.

Any chance we could work on this?

[brainstorm]

Better than additionally, wouldn't it make sense to have this interop page just pointing exclusively to the GA4GH service registry for htsget? Perhaps cleaner to not update the same things on several places? :)

[jb-adams]

@brainstorm I like that idea! Let's discuss at the next htsget meeting

[mlin]

@jb-adams @brainstorm Yea, this interop page was created before service registry existed, and can now be largely retired as vestigial

[jmarshall]

👍 to just delete this page.

[brainstorm]

Done.