Hello Bob, > Dumb question: An Annotation Type such as "Age(hours)" or "body mass(kg)" when > applied to a biosource will be exported as a BioMaterialCharacteristic, right? > Yes, they will. Also an important point: since tab2mage specifications only allow for BioMaterialCharacteristics to be attached to BioSources, all annotations attached to items other than BioSource are not exported. This issue will be solved when implementing the MAGE-TAB specifications which are more flexible.
> We don't have to mark/tag the Annotation Type as a 'BioMaterialCharacteristic' > in some way? I guess it would be good to put all of these in an Annotation > Type Category (called BioMaterialCharacteristic, for example), but that's just > for convenience? > AnnotationType can be marked as Parameter (which then excludes them to be used as BiomaterialCharacteristics). In that respect, the default assumption is that if AnnotationTypes are used to annotate Biomaterials then they are considered as BioMaterialCharacteristics. > And a related question: we (base admins) should create Annotation Types just > for the 'leaves' in the MGED ontology, is that correct? > > Is there a convention for capitalisation, spaces etc? e.g. > 1. DevelopmentalStage > 2. Developmental Stage > 3. developmental stage > > Thanks for pointing this out, I will fix this. To be compliant with tab2mage parser, case1 is the valid one (MGED ontology use CamelCase convention for its classes.) the list of valid 'leaves' is available here: http://mged.sourceforge.net/ontologies/MGEDontology.php#BioMaterialCharacteristics > It's not consistent in the manual (see link above) e.g. > > "Age(week)" - capitalised > "body mass(kg)" - lower case > "body temperature (degree_C)" - an extra space before the units > > The tab2mage specs are clearer when it comes to declaration of parameters. Please see http://tab2mage.sourceforge.net/docs/detail.html#protoparams And there are notes regarding declaration of FactorValue, here: /'FactorValues may be linked to either "Values" or "Measurements"/. As a rule of thumb, Tab2MAGE currently assumes that a purely numerical value in a FactorValue column should be encoded as a Measurement. In such situations the /<category>/ field should indicate the class and name of the measurement unit, in the form: FactorValue[<unit class>(<unit name>)] For example: FactorValue[Temperature(degree_C)] Again will fix the doc. > Has anyone made any progress importing MGED or other ontologies as a whole? > Not yet :( > While we're at it, a more advanced question: say we have a Biosource > Annotation Type called OrganismPart, which is free text (or a text enum). How > could you enter values from a separate anatomy ontology, so that it goes into > tab2mage correctly (or perhaps MAGE-TAB at a later date)? > I am still exploring using several different sets of annotations that would be shared on specific projects to answer that use case. This could solve the problem of users being confronted with AnnotationTypes and values which are not relevant to them . But this does not solve the pb of mixing and matching within one Ontology Category. A work around would be some convention for specifying Source Ontology and value. Again this is suboptimal but might a necessary evil to be able to support MAGE-TAB specifications. Or more drastically, only stick to using OBO foundry ontologies and if terms are missing from those resources, contact the editors and submit the missing terms. All OBO foundry ontologies are very reactive and will advise for alternate terms. thanks for your input. Philippe **************************************************************** Philippe Rocca-Serra (Ph.D) NET Project - Technical Coordinator http://www.ebi.ac.uk/net-project EBI- The European Bioinformatics Institute EMBL Outstation Hinxton Wellcome Trust Genome Campus CB10 1SD Cambridge, UK email: [EMAIL PROTECTED] Tel: +44 (0) 1223 492 553 Fax: +44 (0) 1223 494 468 European Nutrigenomics Organization http://www.nugo.org **************************************************************** ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ The BASE general discussion mailing list basedb-users@lists.sourceforge.net unsubscribe: send a mail with subject "unsubscribe" to [EMAIL PROTECTED]
