1 summary slides from enhancing organism based disease knowledge using biological taxonomy, and...

3
1 Summary Slides from Enhancing Organism Based Disease Knowledge Using Biological Taxonomy, and Environmental Ontologies Ken Baclawski Northeastern University Neil Sarkar Marine Biological Laboratory These slides are the two summary slides from the talk given on March 27, 2008 at “An Open Ontology Repository: Rationale, Expectations & Requirements – Session- 1.” The slides prioritize the requirements for the OOR, from the point of view of developers and end users, for the projects described in the talk.

Upload: kyle-padilla

Post on 27-Mar-2015

214 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: 1 Summary Slides from Enhancing Organism Based Disease Knowledge Using Biological Taxonomy, and Environmental Ontologies Ken Baclawski Northeastern University

1

Summary Slides fromEnhancing Organism Based Disease Knowledge Using Biological Taxonomy, and Environmental

Ontologies

Ken Baclawski

Northeastern University

Neil Sarkar

Marine Biological Laboratory

These slides are the two summary slides from the talk given on March 27, 2008 at “An Open Ontology Repository: Rationale, Expectations & Requirements – Session-1.” The slides prioritize the requirements for the OOR, from the point of view of developers and end users, for the projects described in the talk.

Page 2: 1 Summary Slides from Enhancing Organism Based Disease Knowledge Using Biological Taxonomy, and Environmental Ontologies Ken Baclawski Northeastern University

2

Developer Requirements

Must have the ability to browse and query small segments of an ontology.

Good to have the ability to dynamically curate and suggest changes via the user community.

Ideally, it can be used to navigate across inferred information that is associated with a small set of terms and that comes from many ontologies.

Page 3: 1 Summary Slides from Enhancing Organism Based Disease Knowledge Using Biological Taxonomy, and Environmental Ontologies Ken Baclawski Northeastern University

3

End User Requirements

Must have– Ability to efficiently navigate multiple hierarchies– Consistency across multiple ontologies

Good to have– Ability to provide live feedback– Allow annotating relationships or propose new terms

Ideally, it can– Support scientific hypothesis testing