??? Also we summarize the guidelines
for organizing ontologies, that is, different information should be put at different
hierarchies of ontologies. Furthermore, different from primitives in ontology languages,
which will not change, the concepts in ontologies will change. When inserting
or deleting a concept in ontologies, we should keep the ontologies consistent,
otherwise it will hurt the ontologies to provide sharing information. Hence, we also
discuss how to resolve the conflicts in ontology organizations.
Architecture
To make easy the use of inheritance, block, atavism, and mutation operations
discussed in the ???Ontology Language Organization??? section, we build a graphical
tool to implement these operations in ontology building. This tool can be applied
to ontologies as well as ontology languages.
Example.8. Figure 7 shows that, there exists a Person_Ontology, and we need to
build a Student_Ontology. Then in the ???Parent Ontologies??? frame, we select the
???Person_Ontology???, and in the ???Child or grandchild Ontologies??? frame, we input
the ontology name ???Student??? and the namespace ???stu??? for this Student_Ontology.
Pages:
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477