VoCamp1/Meeting Notes

Meeting Notes

Second Teleconference

Thursday, October 15 at 10:00 am EDT (8??am PDT, 16:00 CEST, 14:00 UTC). We will begin on time and end promptly at 11:00 EDT.

Agenda and Goals

Same as for Monday's telecon (go there for more detail).

1. Introductions
2. Questions about wiki and mailing list
3. Review of VoCamp schedule and expectations
4. Questions about expectations
5. Further discussion until the hour is used up

Notes

present: Josh Reece, Sheldon MacKay, Arlin Stoltzfus, Rutger Vos, Hilmar Lapp, Bill Piel, Jeff Wilcke, Anne Thessen

Introductions

• RV: treebase, metadata, nexml, phyloWS
• JR: phylogeography,
• AS: evoinfo group, CDAO
• HL: cyberinfrastructure, evoinfo, queries on trees
• BP: treebase, iptol, taxonomic annotations
• JW: SNoMed, vet sci, taxo model in SNoMed, term services lab; align bio-top, snomed and bfo
• AT: eol, marine life, informatics for ecology
• SM: phylogenetics, comparative genomics;

Use of shared resources (wiki, list)

1. RV: OpenID new? separate accounts?
   • HL: yes, yes
2. JR: Acronyms are confusing. How familiar should I get with resources before VoCamp?
   • SM: will expand acronyms. depends on interests
   • HL: focus on your interests

VoCamp schedule and expectations

1. JR: how much focus on programming vs. abstractions?

Training and bootcamps

Participant ownership

Ideas for pitches

1. Rutger: (please put this on the wiki pitch page)

First Teleconference

Monday, October 12 at 4:00 EDT (1pm PDT, 22:00 CEST, 20:00 UTC). We will begin on time and end promptly at 5:00 EDT.

Agenda and goals

1. Introductions
   • Name
   • Disciplinary training ("field")
   • Primary research interest in 6 words or fewer
   • Names of ontology-related projects you have worked on
   • Primary VoCamp interest
2. Questions about wiki and mailing list
3. Review of VoCamp schedule and expectations
4. Questions about expectations
5. Further discussion until the hour is used up

Desired outcomes for today:

• participants are aware of shared information resources, and know how to use them
• participants (including organizers) know each other by name
• participants know what is expected of them
  • they know what is going to happen at the VoCamp event
  • they know what are their roles before, during, & after VoCamp
  • they understand how to take ownership of the event

Notes

present: Sheldon MacKay, Mark Schildhauer, Stan Blum, Dave Thau, Arlin, Joel Sachs, Karen Cranston, Enrico Pontelli, John Wieczorek, Mark Wilkinson, Chris Goddard, Jim Case, Jonathan Rees, Rosemary Shrestha, Ravensara Travilian, Greg Whitbread, Peter Midford

Introductions

• SB: tdwg
• KC: eol
• CG:tolkin
• JC: natl ani health network
• HL: cyberinfrastructure, phyloWS (querying)
• SM: tol, gmod,
• PM: phenoscape, onto alignment
• EP: CDAO
• JR: science commons
• GW: systems to support nomenclature
• RT: vert ontogeny & phylogeny
• MS: nceas, data interop, SONNet
• JS: spire
• AS: cyberinfrastructure, comparative analysis, CDAO,
• RS: crop ontology,
• DT: data integration, aligning taxonomies, TDWG, regnum
• JW: taxonomy, darwincore
• MW: exposing web services on the semantic web

Questions about VoCamp

1. Mark S: Should we look for spontaneous collaborations or delve deeply into pre-existing projects?
   • HL: take advantage of opportunities for unique collaborations is preferable
2. What are some examples of products of a VoCamp?
   • not many to go on
3. Mark S: OK to organize before-hand?
   • yes
   • organizers act as participants during the event
4. Joel S: why vocamp instead of hackathon?
5. Mark S: PATO?
   • Peter, Hilmar

Training and boot camps We need to identify needs for training and information (e.g., how to use Protege, what is PhyloCode, what is CDAO, etc). Stay tuned for further communications on this topic.