Changes between Version 7 and Version 8 of MeetingReport
- Timestamp:
- 2010/02/12 18:15:41 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MeetingReport
v7 v8 20 20 Conclusions: 21 21 * Data exchange: 22 * *Current systems are arbitrary but work well.23 * *A namespace for file formats would be useful.24 * *A namespace for column of tabular data would be useful. Could22 * Current systems are arbitrary but work well. 23 * A namespace for file formats would be useful. 24 * A namespace for column of tabular data would be useful. Could 25 25 also be used to describe data in other formats e.g. XML, 26 26 though this could be rather verbose. 27 27 28 * *At the moment namespaces for columns is probably more important28 * At the moment namespaces for columns is probably more important 29 29 than URIs for each data element in a column. 30 30 31 * *Maybe are applicable to the above:31 * Maybe are applicable to the above: 32 32 Ontology Lookup Service ( 33 33 http://www.ebi.ac.uk/ontology-lookup) and/orLife Science 34 34 Resource Name Project ( http://www.lsrn.org) 35 35 36 * *Agreed that worthwhile to pass URIs to describe columns for36 * Agreed that worthwhile to pass URIs to describe columns for 37 37 tabular data. Agreed that arbitrary human-friendly names are 38 38 also good. 39 39 40 * *Agreed to dump all BioMart/ InterMine column headings out, find40 * Agreed to dump all BioMart/ InterMine column headings out, find 41 41 the common/commonly-used ones and work on naming. 42 42 43 43 * Genome Builds: 44 * *Investigate whether is there a standard available for describing44 * Investigate whether is there a standard available for describing 45 45 genome versions/ genome annotation versions. 46 * *Consider whether to base naming on ensembl as planning to cover46 * Consider whether to base naming on ensembl as planning to cover 47 47 all genomes 48 48
