Changes between Version 5 and Version 6 of UseCases

Show
Ignore:
Timestamp:
2010/02/09 09:33:27 (8 years ago)
Author:
gaou
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • UseCases

    v5 v6  
    1313  * Yasunori Yamamoto 
    1414  * Akira R. KINJO 
     15  * Gos Micklem 
    1516 
    1617== Summary == 
    17 - [ ] use cases 
    18     - [ ] myexperiment - flymine 
    19         - [ ] any questions can be more efficient 
    20 - [ ] questions that queries over separated DBs 
    21     - [ ] using in-house data -> NGS 
    22     - [ ] can be in different sources - less cost of integration 
    23 - [ ] querying the predicates 
    24     - [ ] discovery of DBs 
    25     - [ ] hypothesis generation 
    26 - [ ] compare how data can be published with existing & SW technology 
    27 - [ ] interpreted knowledge 
    28     - [ ] not numerical? 
    29     - [ ] not too raw? 
    30     - [ ] linked by predicates (even if numerical) 
    31 - [ ] data are linked 
    32 - [ ] migrate SQL to simple SPARQL endpoints 
    33     - [ ] easy to convert 20 lines? 
    34     - [ ] convert PDB relational to Sparql (kinjo-san, Fransois) 
    35     - [ ] miRbase (raoul) 
    36 - [ ] users do not have to know the entire schema 
    37 - [ ] Paul 
    38     - [ ] predict PPI using homologs (PPI in yeast -> homolog in human) 
    39 - [ ] formulation of SPARQL queries -> RDFscape 
    40     - [ ] can be GUI. 
    4118 
    42 quick note copied from OmniOutliner. will make it prettier later (gaou) 
     19Lots of use cases in data and service integrations are available in websites such as [http://www.myexperiment.org/ myExperiment] and [http://www.flymine.org/ FlyMine]. Using semantic web, any of the existing questions and use cases can be more efficient. 
     20 
     21So one use case/demonstration would be to compare how data can be published with existing & SW technology. 
     22 
     23 
     24  * questions that queries over separated DBs 
     25    * using in-house data -> NGS 
     26    * can be in different sources - less cost of integration 
     27  * querying the predicates 
     28    * discovery of DBs 
     29    * hypothesis generation 
     30  * interpreted knowledge 
     31    * not numerical? 
     32    * not too raw? 
     33    * linked by predicates (even if numerical) 
     34  * data are linked 
     35  * migrate SQL to simple SPARQL endpoints 
     36    * easy to convert 20 lines? 
     37    * convert PDB relational to Sparql (kinjo-san, Fransois) 
     38    * miRbase (raoul) 
     39  * users do not have to know the entire schema 
     40  * Paul 
     41    * predict PPI using homologs (PPI in yeast -> homolog in human) 
     42  * formulation of SPARQL queries -> RDFscape 
     43    * can be GUI. 
     44 
     45 - gaou (Kazuharu Arakawa)