Miro Cupak

I'm all for removing mismatches in the APIs, but this might be jumping the gun a bit. Can we think about this more and involve the Beacon group in the...

Aligning the dataset concepts from the two APIs would be very good. We're looking into this on the beacon side as well: https://github.com/ga4gh/beacon-team/issues/25

Bump, if I may. How far along is this issue? We're working on the new [Beacon schema](https://github.com/ga4gh/beacon-team) release and it would be nice to propagate the artifact to Maven Central...

@kozbo The ticket looks resolved - what's the next step?

As Michael said, we see service-info implemented at the top level of APIs. To elaborate a bit more, since this API has a single endpoint, I think it's your decision...

@jmarshall What makes the most sense to me is: - `https://datahost.example.com/htsget/reads/` - `https://datahost.example.com/htsget/variants/` - `https://datahost.example.com/htsget/service-info` - `https://datahost.example.com/refget/sequence/` - `https://datahost.example.com/refget/service-info` Where `htsget` and `refget` parts are not prescribed by the specs...

Neither option is forbidden or not compliant from service-info perspective. You should go with whatever you think is best for your API, I'm just trying to describe what makes sense...

Thanks, makes sense to me. I filed this https://github.com/ga4gh-discovery/ga4gh-service-info/issues/72.