Skip to content

Add GeneDiseaseValidityProposition#406

Open
tnavatar wants to merge 7 commits into
ga4gh:v1from
tnavatar:v1
Open

Add GeneDiseaseValidityProposition#406
tnavatar wants to merge 7 commits into
ga4gh:v1from
tnavatar:v1

Conversation

@tnavatar

@tnavatar tnavatar commented May 12, 2026

Copy link
Copy Markdown

Per the PR, a GeneDiseaseValidityProposition is used as a subject of a statement about the level of evidence supporting a gene disease association of the type curated by ClinGen, and reported by GenCC.

While the incorporation of all the evidence contributing to these types of statements is a major project likely requiring a new community profile, this proposition is a start, and will enable the production of standard gene disease validity statements leveraging the rest of VA-Spec.

Comment thread schema/va-spec/base/va-core-source.yaml Outdated
type:
extends: type
const: GeneValidityProposition
default: GeneValidityProposition

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there's a fairly consistent convention to add a description parameter like so

        description: MUST be "GeneValidityProposition".

it feels kind of redundant to me but it's employed elsewhere in the schema

@larrybabb larrybabb left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is a fine starting draft PR. I made a couple of comments, but nothing that should slow things down. those items can be addressed anytime in the future.

Comment thread schema/va-spec/base/va-core-source.yaml
Comment thread schema/va-spec/base/va-core-source.yaml
@jsstevenson

Copy link
Copy Markdown
Contributor

@korikuzma notes that we also need to run make all in the schema/ directory to ensure schema artifacts are generated

I think the note about intended proposition scope would be good context to add in docs, but that could be postponed if the goal is to get this merged in time for a new schema release

@tnavatar

Copy link
Copy Markdown
Author

I think I remember having a bit of a discussion with @mbrush about including an example of the intended use case in the description (specifically citing the 2015 ACMG criteria, for instance), and that it was not preferred to do so, but I might be making that up. I don't disagree that making the scope clearer would be a good idea though, and it's a little hard to do without using those references.

Can see about generating those artifacts. My machine isn't set up to run those, would someone have documentation available of requirements for running a build? (or submit a PR to my PR with the appropriate artifacts?)

@jsstevenson

Copy link
Copy Markdown
Contributor

Can see about generating those artifacts. My machine isn't set up to run those, would someone have documentation available of requirements for running a build? (or submit a PR to my PR with the appropriate artifacts?)

Most definitely -- tnavatar#1

required:
- predicate
- subjectGene
- objectCondition

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tnavatar just double checking because I believe the GenCC requires MOI on their GDV classifications. Does the GCI or the ClinGen GDV SOP require MOI to be declared on every classification? The fallback is that some folks do put in the moi term "unknown" which I agree is a cop out. Just wondering if you considered this.

@larrybabb larrybabb added the public review ready The PR has been vetted by the GKS leads and is ready for public review label Jun 23, 2026
@larrybabb

Copy link
Copy Markdown
Contributor

TODO: fix tests

@jsstevenson

Copy link
Copy Markdown
Contributor

TODO: fix tests

Don't quote me on this, but i believe this is an upstream test failure, and that Kori has a PR for fixing it

@korikuzma

Copy link
Copy Markdown
Contributor

TODO: fix tests

Don't quote me on this, but i believe this is an upstream test failure, and that Kori has a PR for fixing it

Correct. #404

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

public review ready The PR has been vetted by the GKS leads and is ready for public review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants