Please refer to my response to Matthew, which I believe also addresses your questions.
I hear this all too often, the problem is that usually ontologies are
just part of a larger system. what is the onto going to be used for?
that will tell u a lot about how to design it, how to build it. what
is the application domain? are there layers of tasks u expect the
ontology to "support"? personally I like it more when the ontology is
understood as part of a well understood larger system. There are of
course cases for which the ontology is the ultimate goal and usability
is some what an abstract consideration.
Can anyone recommend what they feel are the best books that describe how to
Define, Design, and Implement an Ontology? My interests lie within how to
do so for an enterprise but I'll gladly accept any resources that you feel
are worth looking at.
Frank Guerino, Chairman
The International Foundation for Information Technology (IF4IT)