A working session on IAO is organized on Friday July 29th, 3.30-4.30pm during the ICBO conference.

See announcement here

• OBO to OWL conversion annotation properties tracker 90, tracker 92, tracker 93, tracker 100, tracker 103, tracker 104, tracker 105, tracker 106, tracker 107, tracker 110, tracker 111.

• textual entity/document/document part overlap tracker 33, tracker 85, tracker 42.

• plan specification documentation tracker 112 Mathias Brochhausen
  see this wiki page

• Names, parts of names, and whether it's worth differentiating names on the basis of the type of entity the name refers to (person, physical location where mail is delivered, physical location where someone lives, building, software application, instance of software application) Bill Hogan

1. question of what is an IAO release - addition of curation statuses + announce of deprecation + sent around for review IAO-core - 'joint core release' would show how 'plan specification' would work with 'plan' and 'planned process', something that was raised by Matthias to be confusing right now. When we mentioned that part of the confusion was due to parts being in OBI and parts in IAO, Alan suggested (and there was no disagreement), that we should be working on a 'core release' that merges the things in OBI and IAO that build on each other. Bjoern will put together a minimal list of terms to that effect.

2. plan specification

Every plan is a concretization of its plan specification A plan can form the basis of an intentional action

Many protocols are plan specification that never become plan. example: any grant XX writes -> he never intends on doing what he says

DIE (directive information entity) is_about plan : not sufficient: many entities are about plan but are not DIE e.g., "this plan is in the corner of the room"

model: clinical study design written down somewhere (MB). Study design is subtype of plan specification which needs to be concretized but will never happen on piece of paper

=> proposal: has to be concretized as plan or sthg else. Only plan specification (no other information artifact) can be concretized as a plan import plan from OBI

3. OBO2OWL annotation properties

=> mapping problem with IAO, large community of OBO users

Barry: will define what is a synonym in an ontology

BS: First steps: To define a synonym we need to define what it is for one term to be similar in meaning to another term. Approaches: 1. postulate meanings (in IAO?) and define a similarity relation. 2. conceive meaning in terms of the context of a term in a wider system of terms (for example corresponding to a specific discipline, and define similarity in relation to these contexts and systems).

(in alphabetical order)

• Tomasz Adamusiak
• Matthias Brochhausen
• Melanie Courtot
• Bill Duncan
• Kerstin Forsberg
• Bill Hogan
• Lawrence Hunter
• James Malone
• Chris Mungall
• David Osumi-Sutherland
• Bjoern Peters
• Alan Ruttenberg
• Satya Sahoo
• Barry Smith
• Jie Zheng