DI_21OCT09

Action items from previous meeting

ACTION ITEM: Sheldon will follow up with core software development team to to see whether they have interest in the Crimson.
ACTION ITEM: Sheldon and Bill will prepare some outlines on high level plan for taxonomic intelligence for next WG meeting.
- https://pods.iplantcollaborative.org/wiki/display/iptol/Name_Resolution_Prototype
ACTION ITEM: Bill, Sheldon and Jerry will follow up on building the prototye of service.
ACTION ITEM: Bill will attend other WG's meeting a week from next Monday. (Data Assembly, possible also Tree Evolution and Tree Reconciliation)

Attendees: Scott Menor, Steve, Jerry Lu, Bill Piel, Val Tannen, Michael Gonzales, Natalie Henriques

Review Action Items from Previous Meeting

Val attended presentation that was given to developers, he sent Sheldon the literature pointers and the URL to the Crimson website to be posted so that core developers will have access to the information. ACTION: Find the location of the information on the wiki
On the wiki Bill posted Name Resolution Prototype information https://pods.iplantcollaborative.org/wiki/display/iptol/Name_Resolution_Prototype which includes two relevant links to Nadia Anwar’s Ph.D. thesis and Roger Hyam’s discussion of taxonomy and the semantic web.
Bill noted that Nadia combines resolution of taxonomic labels with classifications and although we may not be using much classification data, we need to resolve diversity of names, synonyms and other lexicons in how people express species names.
The website also shows a Proposed Schema, Bill will start loading plant information from the USDA’s PLANTS database which largely covers the USA and Canada. Once the input is extensive the list will be run through uBio. The three tables capture data from the various resources and fuse them together.

Detailed Planning for the Prototype

Working on the design of the prototype.
The target delivery date of the prototype demo would be at the Phoenix meeting. Other participants will be there and it will be a good time to have discussions.
There are several cross cutting issues and it would be very helpful to have a systematic way to ask them.
We need to facilitate communication across the group, for the different working groups to be aware of what is going on.
Access to use cases that relate to cross cutting problems.
Michael stated that it is the role of the Engagement Team to facilitate communication between the groups.

Develop Milestones and a Timeline for the Next Six Months

Michael – we need a timeline of where we are going and expectations. Finite ideas we want to try out, a clear outline of where we want to do and how soon to get there.
Deliverable – requirements of the prototype and execution in time for the Phoenix meeting.

Open Discussion

Bill – the demo prototype will stimulate people to consider the possibilities. We could have a Perl script that takes XML documents with trees send to the taxonomic web service. This Perl script would fuse trees in a matrix representation.
Get people to give us use cases so we can go ahead and develop them.
Val – I have a set of use cases for free manipulation who do I send the document to? Brian already has use cases but I cannot find them on the wiki, I would prefer if someone form the engagement team tell us where to go.
Michael – The engagement team’s role is to make sure all the cases gel and we interface to core services. The engagement team needs to look at - Where is the information on the wiki? How is the information organized? The job is to make sure it is communicated effectively.
Tactical Items
Working groups mailing lists – ACTION: Michael will send out the mailing list of who is in the group. Please review and let him know if anyone has been missed.
Jerry suggested that the use case information from the DI group be put on the wiki for the core development group to start reviewing.