28.02.2013 Views

Bio-medical Ontologies Maintenance and Change Management

Bio-medical Ontologies Maintenance and Change Management

Bio-medical Ontologies Maintenance and Change Management

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Towards <strong>Bio</strong>informatics Resourceomes 23<br />

present an example showing how a reader currently approaches the papers<br />

of an issue of a typical bioinformatics journal (e.g. Journal Of <strong>Bio</strong><strong>medical</strong><br />

Informatics 21 , volume 39, year 2006, issue 4). Figure 2 part a), presentsthe<br />

Web page hosting the index of the journal issue with a “flat” list of the<br />

articles. The only information that can help the reader to decide if a paper<br />

can be interesting for his/her research, are its title <strong>and</strong> authors. Not any<br />

classification is provided for the articles <strong>and</strong> in any case it is rather difficult<br />

to summarize the content in the title. Furthermore, the reader could have not<br />

any idea of how this knowledge domain is organized <strong>and</strong> where the papers<br />

could be located in an ideal map of the domain. So we can state that this list<br />

of papers weakly assists in their retrieval, because of the lack of a semantical<br />

approach to the classification of papers.<br />

In Figure 2 part b), we tried to organize the same set of papers in a<br />

hierarchy that can intuitively describe the topics treated by the papers. In this<br />

way the user is able to recognize the resources (in this example only papers)<br />

of interest at first glance, without opening other documents for reading their<br />

abstracts in order to underst<strong>and</strong> their content.<br />

This vision is the beginning of a bigger one, that sees the topics the resources<br />

concern organized through an ontology. In this way it is possible to<br />

give a more underst<strong>and</strong>able description of the domains the papers describe.<br />

Another feature of this intuitive vision is the possibility of extending the field<br />

of bioinformatics resources also to other kind of entities. In this manner also<br />

e.g. programs, databases, scientists, universities, books, <strong>and</strong> other resources<br />

can be clearly described <strong>and</strong> retrieved. Like the domains, also the different<br />

kinds of bioinformatics resources can be described through the hierarchical<br />

formalism of ontologies. Besides a perceptible presentation of the reality, this<br />

kind of classification is able to be machine-underst<strong>and</strong>able <strong>and</strong> consequently<br />

“reasonable” from “in-silico” scientists [68].<br />

3.2 What Is a Resourceome?<br />

In order to help both scientists <strong>and</strong> software agents in their awareness of the<br />

domain, we raised the exigence of classifying the huge world of bioinformatics<br />

resources (resourceome) [16] building a general machine-underst<strong>and</strong>able<br />

index. This could emerge bottom-up from the creation of - probably overlapping<br />

- Resourceomes (please note here the capital “R”). Organizations,<br />

individual scientist <strong>and</strong> other Resourceomes creators could share, merge <strong>and</strong><br />

integrate their Resourceomes aiming to a general one. But in any case a Resourceome<br />

represents the vision of scientific domain as it is perceived by its<br />

creator. We define a Resourceome as structurally composed of two ontologies.<br />

One ontology is for the description of the kinds of bioinformatics resources<br />

(left side of figure 3) <strong>and</strong> the other is for the description of the topics that<br />

the resources concern (right side of figure 3).<br />

21 www.sciencedirect.com/science/journal/15320464

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!