SchemaBlocks{S}[B] Mission Statement

SchemaBlocks aims to translate the work of the workstreams into data models that:

• Are usable by other internal GA4GH deliverables, such as the Search API.
• Are usable by Driver Projects as an exchange format.
• Aid in aligning the work streams across GA4GH.
• Do not create a hindrance in development work by other work streams.

ga4gh Namespace and Prefix

In a “GA4GH Namespace Discussion” telecon on 2019-08-22, initiated by GKS and with the participation of different work stream and project leads, it was agreed that newly generated identifiers created and maintained in the “GA4GH ecosystem” should use a general ga4gh prefix, and not create scoped prefixes.

Current {S}[B] Repository Status

Recently, repository structure, schema formats and the amount of schema blocks represented in the repositories have seen some maturation and expansion. The current setup is closing in on moving from an “experimental state” towards production readiness, i.e. a stable format for general document structure, canonical links and also frozen representation of first core schemas.

SchemaBlocks Repositories

The SchemaBlocks Github organisation contains several specifically scoped repositories. Please use the relevant Github Issues to and/or GH pull requests comment and contribute there.

SchemaBlocks “Status” Levels

SchemaBlocks schemas (“blocks”) provide recommended blueprints for schema parts to be re-used for the development of code based “products” throughout the GA4GH ecosystem. We propose a labeling system for those schemas, to provide transparency about the level of support those schemas have from {S}[B] participants and observers.