Create standard glossary of terms

[ahwagner]

V1 document is here: https://docs.google.com/document/d/1xPFXRF7_Ppe5SDBHTBa1E-MBHHNtoc1Q-jZ1olOrtc4/edit?tab=t.0

Expansion to follow.

[ahwagner]

@larrybabb:

terms to define: "Breaking Change: A change to an existing feature that is NOT backward compatible. For example, removing anything, adding required values or updating the form or output to something that was previously released is "breaking". Adding optional values or attributes would be "non-breaking".

@kreinold:

request to revisit the "Data Model" definition

[ajhpage]

how comprehensive is this document supposed to be? particularly in the "roles" section I can see a number of missing definitions. there have been many calls for a GA4GH glossary and I'm wondering if this is supposed to be answering all of them, in which case the scope should be expanded. If not, the scope should be defined at the top so we know what's in and what's out, and it should point to any other glossaries that are developed already or in the future.

[ahwagner]

agree @ajhpage! My notes from the TASC meeting about this were terse, but the "Expansion to follow" comment reflects the group's consensus that there are quite a few additional terms we would want to include here across GA4GH. This terminology is what we started with due to its operational basis in active Work Stream processes from GKS.

Would love to have the folks interested in the glossary effort engage with TASC on this.

[ajhpage]

ah - great to hear! I'll try to dig up all the different threads I have about this and direct people here going forward.