Changes between Version 1 and Version 2 of Data_exchange
- Timestamp:
- 2010/02/12 16:46:19 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Data_exchange
v1 v2 2 2 Wednesday 10th February p.m. - Room 516 3 3 4 Semantic Data Exchange 5 6 Gos Micklem 7 Richard Smith 8 James Taylor 9 Arek Kasprzyk 10 Soichi Ogishima 11 Brad Chapman 12 Christian Zmasek 13 Peter Cock 14 Hideyuki Morita 15 Ryosuke Ishiwata 16 Kei Ono 17 Shinobu Okamoto 18 Alberto Labarga 19 20 ------------------------------------------------------------------------------ 21 Discussion on possibilities/need for improving data exchange between 22 e.g. InterMine, Galaxy, BioMart, Cytoscape... 4 ''' Semantic Data Exchange''' 5 6 * Gos Micklem 7 * Richard Smith 8 * James Taylor 9 * Arek Kasprzyk 10 * Soichi Ogishima 11 * Brad Chapman 12 * Christian Zmasek 13 * Peter Cock 14 * Hideyuki Morita 15 * Ryosuke Ishiwata 16 * Kei Ono 17 * Shinobu Okamoto 18 * Alberto Labarga 19 20 '''Discussion on possibilities/need for improving data exchange between 21 e.g. InterMine, Galaxy, BioMart, Cytoscape...''' 23 22 24 23 Would typing of arbitrary data exchange improve communication between … … 27 26 28 27 29 Current situation: 28 '''Current situation:''' 30 29 31 30 It was felt that the current situation wasn't so bad: however it would … … 42 41 needed> 43 42 44 Cytoscape (http://www.cytoscape.org) /BioMart: REST API used. Perhaps SOAP would be better but43 Cytoscape (http://www.cytoscape.org) & BioMart: REST API used. Perhaps SOAP would be better but 45 44 this still requires some development. REST was fine for data 46 45 retrieval. … … 141 140 large-scale users/providers can start to comply. 142 141 143 144 Data exchange conclusions: 145 *** A namespace for file formats would be useful. 146 147 *** A namespace for column of tabular data would be useful. Could 142 '''Data exchange conclusions:''' 143 * A namespace for file formats would be useful. 144 145 * A namespace for column of tabular data would be useful. Could 148 146 also be used to describe data in other formats e.g. XML, though 149 147 this could be rather verbose. 150 *** Investigate whether the above exist.148 * Investigate whether the above exist. 151 149 Ontology Lookup Service (http://www.ebi.ac.uk/ontology-lookup) 152 150 and/orLife Science Resource Name Project (http://www.lsrn.org) 153 151 applicable ? 154 152 155 *** At the moment namespaces for columns is probably more important153 * At the moment namespaces for columns is probably more important 156 154 than URIs for each data element in a column. 157 155 158 Agreed that worthwhile to pass URIs to describe columns. Agreed that159 arbitrary human-friendly names are also good.160 161 *** Agreed to dump all BioMart/ InterMine column headings out, find156 * Agreed that worthwhile to pass URIs to describe columns. Agreed that 157 arbitrary human-friendly names are also good. 158 159 * Agreed to dump all BioMart/ InterMine column headings out, find 162 160 the common/commonly-used ones and work on naming. 163 161 164 162 165 163 166 ========== Discussion turned to genome builds: 164 '''Discussion turned to genome builds:''' 167 165 168 166 There is no-where to go to find out if entities/ coordinates come from … … 201 199 version. 202 200 203 Genome version summary: 204 * Investigate whether is there a standard available for describing genome version * 205 * Consider whether to base naming on ensembl genome/ annotation versions * 206 207 208 209 =========== Thoughts on RDF: 201 '''Genome version summary:''' 202 * Investigate whether is there a standard available for describing genome version 203 * Consider whether to base naming on ensembl genome/ annotation versions 204 205 206 207 '''Thoughts on RDF:''' 210 208 211 209 If everyone is expressing their data in RDF with a common underlying