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
The statementText property captures a human-readable free text expression of what a Statement is putting forth as true. e.g. for a VarPath statement, it might read:
“VariantX is causal for autosomal-dominant ConditionY with high penetrance, as mediated by its effects on GeneZ ‘.
This clearly expresses what a Statement data structure reports to be true, in plain language (so that it is unambiguous even if they do not understand SPOQ paradigm). And it provides a translation that reinforces / educates users on the SPOQ pattern for expressing Statement semantics.
This is not necessary of course, but IMO this is a valuable addition that achieves several benefits . . . might be a good to explore the utility/appetite for this early on, but including this property in Statement Profiles, and authoring 'templates' to help automatically generate the values of this property from the data (see comment below)
The text was updated successfully, but these errors were encountered:
Note that it would be simple to author templates for assembling these sentences using values of specific properties. e.g.
[subjectVariant] is causal for [modeOfInheritanceQualifier] [objectCondition] with [penetranceQualifier] penetrance, as mediated by its effects on the [geneContextQualifier] gene.
. . . which would give sentences like the example above.
Or, if direction and/or strength is provided:
This statement reports [strength] evidence/confidence [direction] the claim that [subjectVariant] is causal for [modeOfInheritanceQualifier] [objectCondition] with [penetranceQualifier] penetrance, as mediated by its effects on the [geneContextQualifier] gene.
. . . which would give sentences like:
"This statement reports moderate evidence supporting the claim that VariantX is causal for autosomal-dominant ConditionY with high penetrance, as mediated by its effects on GeneZ ".
A simple script could be written to instantiate these templates in the data, and/or in a user interface.
mbrush
changed the title
Add/extend the core-im statementText property in Statement profiles
Author templates for the core-im statementText property in Statement profiles
Jul 4, 2024
mbrush
changed the title
Author templates for the core-im statementText property in Statement profiles
Add/estend the core-im statementText property in Statement profiles
Jul 4, 2024
mbrush
changed the title
Add/estend the core-im statementText property in Statement profiles
Add/extend the core-im statementText property in Statement profiles
Jul 4, 2024
The
statementText
property captures a human-readable free text expression of what a Statement is putting forth as true. e.g. for a VarPath statement, it might read:“VariantX is causal for autosomal-dominant ConditionY with high penetrance, as mediated by its effects on GeneZ ‘.
This clearly expresses what a Statement data structure reports to be true, in plain language (so that it is unambiguous even if they do not understand SPOQ paradigm). And it provides a translation that reinforces / educates users on the SPOQ pattern for expressing Statement semantics.
This is not necessary of course, but IMO this is a valuable addition that achieves several benefits . . . might be a good to explore the utility/appetite for this early on, but including this property in Statement Profiles, and authoring 'templates' to help automatically generate the values of this property from the data (see comment below)
The text was updated successfully, but these errors were encountered: