search

GenomicsStandardsConsortium / mixs

Minimum Information about any (X) Sequence” (MIxS) specification
https://w3id.org/mixs
Creative Commons Zero v1.0 Universal
38 stars 21 forks source link

which attributes of a term are invariant in MIxS6 packages - Final_clean #438

Open turbomam opened 2 years ago

turbomam commented 2 years ago

4thOct2022-CIH edited ticket for clarity: In the packages table listing all the terms there are 12 columns, the question is which of those columns are FIXED accross all packages and which are allowed to vary depending on which package its part of?

MIxS invariant? comment
Environmental package FIXED MAM: this is the secondary key
Structured comment name FIXED MAM: yes
Package item FIXED MAM: yes
Definition FIXED decided at 2022-07-?? meeting)
Expected value FIXED
Value syntax FIXED MAM: yes, databases need to know how to validate entries, regardless of the Environmental package
Example VARIABLE MAM: no
Requirement VARIABLE MAM: no
Preferred unit FIXED discussed 2022-10-04
Occurrence FIXED MAM: yes, databases need to know if a field is single-valued or multi-valued, regardless of the Environmental package
MIXS ID FIXED MAM: this is the primary key
github ticket VARIABLE its for internal use only and not meant for display to external users

original wording from Marks post: Disclaimer: I believe we have an imminent plan to retire the Google sheets as a source of truth, but provide tools for round tripping between the LinkML model and "throwaway" sheets

What's the primary key for rows on MIxS6 packages - Final_clean?

It's probably a compound key, based on MIXS ID and Environmental package

Does that mean that the values in all other columns are allowed to vary? Can a MIXS ID have different Structured comment names or different Package items?

Based on an accounting of columns in MIxS6 Core- Final_clean

only1chunts commented 2 years ago

TWG group discussed this issue, the consensus was that "Example" and "Requirement" are the only two columns that should be variable. Units was voiced as an option but definitively rebutted as a bad idea for a Standard, the fact that its pretty simple to convert between different units means that the stored value should always be the same, if particular providers want to present in different units then they can convert it from the standard unit.