You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GKS VA-Spec, Cat-VRS and VRS all work together on a GKS-Core set of schemas.
Would we create a namespace for GKS, or would we create one for each product (including the shared one)? Is there going to be a "best practice" within GA4GH schema registry to define namespaces that make sense?
gks-core
vrs
cat-vrs
va-spec
are the 4 repos we have right now that each have their own schemas, some of which depend on others. VA-Spec is the most complex since it has sub-namespaces for community guidelines. And there's some degree of volatility around the fact that we may change the way we group or namespace things.
I think we would need to work with you guys to figure out how you envision all this working in the registry.
The text was updated successfully, but these errors were encountered:
GKS VA-Spec, Cat-VRS and VRS all work together on a GKS-Core set of schemas.
Would we create a namespace for GKS, or would we create one for each product (including the shared one)? Is there going to be a "best practice" within GA4GH schema registry to define namespaces that make sense?
gks-core
vrs
cat-vrs
va-spec
are the 4 repos we have right now that each have their own schemas, some of which depend on others. VA-Spec is the most complex since it has sub-namespaces for community guidelines. And there's some degree of volatility around the fact that we may change the way we group or namespace things.
I think we would need to work with you guys to figure out how you envision all this working in the registry.
The text was updated successfully, but these errors were encountered: