That paper below was written by Doug Foxvog (of this list)
among others; it has an interesting overview algorithm section around the third
page or so:
Building Application Ontologies
order to build meaningful a (AO),
a knowledge base,
thesaurus or dictionary is necessary. WordNet is a quite
conceptual thesaurus with hierarchally structured
and multiple semantic relations between concepts.
is a good choice also due to its broad concept structure
Process of Building (AO)
assume there are k
semantic services from the same
domain as the inputs of (AO) builder.
Fig. 4, the building process is iterative including
Initialize AO0 as
an empty set, ;.
Import a SOi; 1 · i · k; re-organise it into
[ my note: 1 <= i <= k
defined by Definition 1.
For each concept of SOi, extract its relative
from WordNet by the WCEA
6.2; add the retrieved information to SOi, then
a new SO0i with more concept
Merge SO0i and AOi¡1 using
in Section 6.3 to obtain a new AOi.
including cleaning concept conflicts,
and storing (see Section 6.4).
Repeat steps 2 to 5, until i = k, then stop.
output of this process is an application ontology AOk,
can be referred to by other service providers or users
create new applications as depicted in Fig. 4.
This algorithm seems like a very useful
place to start from if the list wants to consider how ontologies might be
merged in daily practice.
Rich AT EnglishLogicKernel DOT com