Central Metadata Registry for approved standards

[MKonopko]

Per M Haendel:

I think we need a central, computable metadata registry for approved standards. This information can then be automatically ingested by other systems. For example, we have a really nice metadata registry for the OBO ontology standards here. Here is an example for HPO: https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/ontology/hp.md

[jb-adams]

@MKonopko @mellybelly great idea, I think this is similar to something I had in mind, essentially a registry and API for GA4GH standards so they can be looked up in a programmatic way. I wrote a document outlining some use cases for such an application.

I plan to bring this up as a project proposal once the TASC meetings start.

[mcupak]

@jb-adams Very nice! I wonder if we can repurpose the Service Registry format for this.

[jb-adams]

@mcupak I think this would integrate well with Service Registry and Service Info. For example, each item returned from /services/types could be passed to the "Standards API," letting the registry master node access the OpenAPI spec and informing them on what client requests each service could be expected to handle. Could be useful for networks of diverse service types.

[mamanambiya]

@jb-adams this sounds like this would be more useful for external use (GA4GH standards consumers) than for GA4GH internal use, right?

[mellybelly]

yes, this ensures that journals and other standards registries can easily ingest the released GA4GH standards metadata and recommend them ;-).

[jb-adams]

yes, I'm largely seeing it as a way for newcomers and other consumers to explore our available standards, and be able to locate all of our outputs from a central resource or service.