Avoiding the pitfalls of ontology development
All,
At my employer (US Government), I'm finding more and more
ontology projects, but I have to wonder about the quality and value of
them. Some start with taxonomies and add some basic OWL relationships.
Others appear to take abstract/complex terms (found in enterprise
architectures) and add relationships. Others are such quick efforts, one
has to wonder. Others are developed with little or no background or
experience in ontology development. Most projects appear to be starting
with terms, not concepts.
Has anyone yet characterized this trend? Are there any names yet
for this? What are the pitfalls? Has anyone written a paper on the 7
pitfalls of ontology development? I need a polite way of helping these
projects avoid such pitfalls.
Jim Schoening