From: Race, A. <Ala...@un...> - 2017-03-20 15:53:19
|
Hello, I have a question regarding the intent for the MUST, SHOULD, MAY requirement levels within the mapping file that I couldn't find a clear definition of online. The question relates to determination of a valid mzML file. With MAY, is the intent that: a) A set of terms that may be included, but is not exhaustive. I.e. The MAY rules are for guidance only. b) Only terms mentioned here may be included within the defined scope, any others would render the mzML technically invalid. c) Something else? On a related note, the analyzer_may rule states that any child of MS:1000480 (mass analyser attribute) can be included. However, one of the children is MS:1000021 (reflectron state) - so inclusion of this 'parent' term (whose child terms define on and off) would satisfy the validity of mzML, but including the MS:1000021 term makes no sense. Is there anything within the obo/mapping file that I'm missing that would enable filtering/checking of these parent terms that ideally shouldn't be allowed to be included? Thank you for your help, Alan |