GKS Core 1.2.0 Community Review Ballot

[korikuzma]

This is the ballot pre-release of v1.2 of the GKS Core models, open for community review following the GA4GH Product Development and Approval process.

Important Links

Release log: https://github.com/ga4gh/gks-core/releases/tag/1.2.0-ballot.2026-07.1
Schemas: https://github.com/ga4gh/gks-core/blob/v1/schema/gks-core/gks-core-source.yaml
Discussion: this page!

Full Changelog: 1.1.0...1.2.0-ballot.2026-07.1

---

This discussion was created from the release 1.2.0-ballot.2026-07.1.

What's Changed

• feat: MappableConcept and ConceptSet inherit Entity by @korikuzma in feat: MappableConcept and ConceptSet inherit Entity #129
• feat: prepare 1.2.0-ballot.2026-07.1 release by @korikuzma in feat: prepare 1.2.0-ballot.2026-07.1 release #130

[larrybabb]

Rebrand gks-core to gkm-core now vs later. #133

[korikuzma]

I'm in favor of this

[larrybabb]

This will be done in 1.1 release.

[kattaylor511]

Epic approves :)

[tnavatar]

This is getting a little meta--but I don't understand why MappableConcept inherits Entity. Entity brings along with it a set of attributes, including Aliases, which MappableConcept shadows with attributes like Mappings. On the surface this change seems to muddy the semantics of an already complicated class.

[larrybabb]

aliases and mappings are semantically different.
Aliases are alternative labels or strings that may be used to name an entity.
Mappings are coded concepts that are more formally authorized codings that relate to the primary coding.

MappableConcept has grown to take on the concept of "any" domain-like concept that VA or GKM has yet to define. It is a complicated class in that it is a generalized way to represent concepts that we don't have in GKM (e.g. Disease, Condition, Phenotype, Gene, Therapy, ModeOfInheritance, etc.).

[korikuzma]

Is it possible to address this issue in the ballot? #134 It would be needed for the GKM Starter Kit

[larrybabb]

Not addressed in 1.1 see issue for details.