Customer Experience Management (CXM), Information Management, Social Business
 
 
 

What is an Ontology? And Why We Need Them

Here at the 10th International Protégé Conference in Budapest, Hungary the word of the day is 'ontology'.

Most folks inside these walls know exactly what that means. Most people outside these walls do not. And those of us in the content management space should have a clear idea. Certainly, as the CM and Web technologies around us evolve, we will be left behind if we don't.

Starting at the beginning, an ontology is really such a simple concept that I find it a shame that there are so many definitions which seem to make the idea less rather than more clear, and more rather than less complex sounding. What confuses things further is the fact that the word has its roots in philosophy and that the meaning in the philosophical context tends to differ a bit from what most scientists and industry practitioners mean.

In the philosophical domain, the word ontology tends to mean a branch of metaphysics concerned with the study of existence — the work of trying to understand the basic structure of our world. This definition sheds some light on the what is meant outside of philosophy, but by no means takes us (or at least me) all the way home.

In the scientific and commercial realms, first an ontology tends to mean a thing that is produced rather than a field of study, and then we get a host of rather inaccessible explanations about what that thing is.

Here's one from Tom Gruber for starters: “An ontology is a specification of a conceptualization.” Or how 'bout this: “Ontologies are 'specifications of a relational vocabulary'.”

Here's what Wikipedia says: “An ontology is a data model that represents a set of concepts within a domain and the relationships between those concepts.”

Got it? Right then, can I see yours?

Oh, what, sorry, what's that? Oh, you said “What's a 'conceptualization'? What is a 'domain'? What's a 'relational vocabulary'?” Right well, I thought we all talked like that, but for those who don't, a 'conceptualization' is like a bunch of concepts pertaining to some slice of reality.

A domain is a particular slice of reality — for example your company's Web publishing operations or Joe's pizza restaurant down the block or the human genome. And then that 'specification' word, well we're all at least somewhat familiar with that, but in this context it means that you're defining and documenting some truth about the slice of reality in question. And I don't have any idea what a 'relational vocabulary' is.

But generally, have you got the concept? Kind of? Hmm, OK, let's try this:

An ontology is a detailed model/picture/schema (pick your favorite word) of a slice of reality which is based on the facts that we know about that reality. This model/picture/schema is a description of some of the things and some of the relationships between the things that are known about that reality.

The W3C describes ontology in accessible language: “An ontology defines the terms used to describe and represent an area of knowledge.” That's pretty concise.

Barry Smith, who spoke at the conference yesterday, used the example of a map's legend. His statement was that “ontologies do for data what legends do for maps.” Barry comes from the bio-informatics area and tends to think in terms of things like the Gene Ontology (GO) project.

 

Continue reading this article:

 
 
Useful article?
  Email It      

Related Articles:
Tags: , , , , , , ,
 
 
 

Featured Events  View all | Add event | feed RSS

Who's Hiring?  View all | Post a job | feed RSS


 
Are you hiring?    Post your job today ($45 for 45 days)!