remove /service-info endpoint (for now)

[dglazer]

Addresses DRS v1 PRC #11 /service-info items

Per PRC discussion, the GA4GH-wide /service-info spec isn't yet ready for use.

[susheel]

I don't think this endpoint needs deletion for DRS v1, as points raised need to be addressed by Discovery and future inclusion post v1

[dglazer]

I'm personally fine either way, so unless the PRC has a strong opinion, I defer to the group. The best argument for deleting it now is that, once there's a GA4GH-blessed cross-API /service-info definition, we can add it to DRS without a backwards-incompatible breaking change.

[susheel]

I'd keep the /service-info endpoint to at least provide users links to the documentation and contact points of the service, including being consistent with all other GA4GH APIs. Not a strongly held opinion and happy to defer to the community.

Once we get a GA4GH blessed /service-info spec, I suspect this will be a breaking change for all GA4GH APIs.

[susheel]

+0 ELIXIR

[ddietterich]

+1 Terra
We'll support it as an extension and then totally replace it when the real thing comes along. No backward compatibility.

[Avantol13]

+1 from DCF/UChicago/CTDS/Gen3/

[mattions]

+0 from Seven Bridges (CGC, Cavatica)
(Agreed that vocabulary should be shared among other Cloud WS APIs. Currently it might be useful to link to doc pages)

[briandoconnor]

Farewell /service-info, I'm sure we will see you again soon!

Seriously, though, I think it's best to remove it for now and I suspect it will be added in very late in the game before Oct's meeting. Implementers, I think it's fine to keep this in your implementations and tweak when the final version comes out.