<mscottm> Just got off the metro connected via my droid

nice

Dr. Xue Webster new member of the group

Chemist, PhD in medical informatic; work at Lily is to try and uncover novel hypothesis through data and text mining

start with disease of interest, try to identify novel targets - problem of ranking, designing in vivo/in vitro tests

uses semweb technologies to represent and work with data

excited to participate, learn and contribute

<mscottm> Welcome Xue!

<Christi> Welcome Yue!

<yue> thanks

https://docs.google.com/document/d/1XoRj-Ysxa0xOX2n3MBNcG7_dT7cEA4C3ITKn3z1rCPc/edit?hl=en&authkey=CJXJhtsP#

<epichler> manuscript: https://docs.google.com/document/d/1sh0lttGpqXZuQL-WxTSqj5ZjMRFeYUciHhkHfqRSrTk/edit?hl=en&authkey=CK7D5YYO#

<epichler> supplement: https://docs.google.com/document/d/1rxLEXSa0E_5GmjYpDvGOs7yNENcBICKvQco8ecaywOg/edit?hl=en&authkey=CI3-m6oE#

now going over the action items

suggest Deb McGuiness for R1.2

synthetic patient data

https://dvcs.w3.org/hg/TMO-Indivo/file/3334734509e9/syntheticPatients/

joanne: searching for much more impressive functionality
... question answering is ok, but we need more

chris: genotype-phenotype data will bring insights

joanne: news article shows that open data allows for future use

chris: think of easy to hard questions; could we actually get that out of the data?

http://esw.w3.org/HCLSIG/PharmaOntology/Roles

joanne: what's the role of tmo-external.owl

michel: snapshot of the dependencies at that time - we can ensure consistency with what we develop at that time

elgar: important practical consideration
... we also did this with the data

michel: problem with the google doc manuscript

use case reworking

bosse - took content from wiki; better to summarize; add to supplement

elgar: supplementary materials - do we want queries in the paper or in the supplementary
... more readable if we take out the queries and refer to supplementary material

<mscottm> What about putting the quarries into a separate section like the pendix I'm not sure if that was discussed as an option?

<mscottm> That's from voice recognition

elgar: problems with the queries - will fix

michel: scott -> we agreed that we would put queries + answers in the supplementary material

<mscottm> Tx

joanne: AMIA - need to create a demonstration - focus on this after the paper
... how can we demo the value of this work
... so that it gains exposure and importance in that community

scott: will be in the bay area, but can we schedule it so that he can present it

This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: michel
Inferring Scribes: michel

WARNING: No "Topic:" lines found.

Default Present: +1.518.915.aacc, +46.4.63.3.aadd, +1.617.993.aaee, michel, +1.781.431.aaff, +1.302.598.aagg, matthias_samwald, mscottm, Christi, yue, +31.62.427.aaii
Present: +1.518.915.aacc +46.4.63.3.aadd +1.617.993.aaee michel +1.781.431.aaff +1.302.598.aagg matthias_samwald mscottm Christi yue +31.62.427.aaii

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Got date from IRC log name: 27 Jan 2011
Guessing minutes URL: http://www.w3.org/2011/01/27-hcls2-minutes.html
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report