Establish convention for GA4GH Schema persistent URLs

[ahwagner]

Problem Statement

The GKS Work Stream is trying to align conventions for resolving persistent URLs (pURLs) for schemas maintained by GA4GH.

Impact of alignment between standards

Consistency in the structure of pURLs drives consistency and cohesion across products, and makes it easier to document and describe GA4GH schema resources at a high level.

Background research and landscape analysis

GA4GH already uses w3id.org as a persistent URL resolver for GA4GH products, including VRS 1.3 definitions. The need for persistent URLs is important for use of online JSON Schema documents that should be resolvable by an $id attribute.

Proposed solution

We would like to establish a convention for registering GA4GH schema resolution at w3id.org, and propose the following syntax:

In this proposal, the product specific section may be variable from product to product, but otherwise all components are consistent across specifications.

This solution requires:

1. TASC to register GKS schemas under the /ga4gh/schema/ path
2. TASC to review requests for other GA4GH schema registrations at w3id.org and enforce consistent pURL patterns under the /ga4gh/schema/ path

[ahwagner]

This has been implemented, only outstanding task is documentation (this is on me).

[ahwagner]

We should add process document to github.com/ga4gh/TASC, similar to the service-info request documentation.