Semantic Web-Based Information Systems: State-of-the-Art ...
Semantic Web-Based Information Systems: State-of-the-Art ...
Semantic Web-Based Information Systems: State-of-the-Art ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
0 Cr stan & Cuel<br />
Table 3. Methontology through our framework<br />
Name.<strong>of</strong>.<strong>the</strong>.Phase. Input. Description. Output.<br />
Planning<br />
Specification<br />
Conceptualization<br />
Formalization<br />
Integration<br />
Implementation<br />
Maintenance<br />
Acquisition<br />
Evaluation<br />
Documentation<br />
Nothing: first step<br />
A series <strong>of</strong> question<br />
such as: “Why is this<br />
ontology being built<br />
and what are its<br />
intended uses and endusers?”<br />
A good specification<br />
document<br />
Conceptual model<br />
Existing ontologies and<br />
<strong>the</strong> formal model<br />
Formal model<br />
Computable ontology<br />
Plan <strong>the</strong> main tasks to be done,<br />
<strong>the</strong> way in which <strong>the</strong>y will be<br />
arranged, <strong>the</strong> time and resources<br />
that are necessary to perform<br />
<strong>the</strong>se tasks<br />
Identify ontology’s goals<br />
Conceptualize in a model that<br />
describes <strong>the</strong> problem and its<br />
solution. To identify and ga<strong>the</strong>r<br />
all <strong>the</strong> useful and potentially<br />
usable domain knowledge and its<br />
meanings<br />
Transform conceptual model into<br />
a formal or semi-compatible<br />
model, using frame-oriented or<br />
description logic representation<br />
systems<br />
Processes <strong>of</strong> inclusion,<br />
polymorphic refinement, circular<br />
dependencies, and restriction.<br />
For example, select meta<br />
ontologies that better fit <strong>the</strong><br />
conceptualisation<br />
Select target language<br />
Including, modifying definition<br />
in <strong>the</strong> ontology<br />
Searching and listing knowledge<br />
sources through non-structured<br />
interviews with experts, informal<br />
text analysis, formal text<br />
analysis, structured interviews<br />
with experts to have detailed<br />
information on concepts, terms,<br />
meanings, and so on<br />
Technical judgment with respect<br />
to a frame <strong>of</strong> reference<br />
A project plan<br />
Ontology requirements specification document,<br />
specifying purposes and scopes. Its goal is to produce<br />
ei<strong>the</strong>r an informal, semi-formal, or formal ontology<br />
specification document written in natural language, using<br />
a set <strong>of</strong> intermediate representations or using competency<br />
questions, respectively. The document has to provide at<br />
least <strong>the</strong> following information: <strong>the</strong> purpose <strong>of</strong> <strong>the</strong><br />
ontology (including its intended uses, scenarios <strong>of</strong> use,<br />
end-users, etc.); <strong>the</strong> level <strong>of</strong> formality used to codify<br />
terms and meanings (highly informal, semi-informal,<br />
semi-formal, rigorously formal ontologies); <strong>the</strong> scope; its<br />
characteristics and granularity. Properties <strong>of</strong> this<br />
document are: concision, partial completeness, coverage<br />
<strong>of</strong> terms, <strong>the</strong> stopover problem and level <strong>of</strong> granularity <strong>of</strong><br />
ache and every term, and consistency <strong>of</strong> all terms and<br />
<strong>the</strong>ir meanings.<br />
A complete glossary <strong>of</strong> terms (including concepts,<br />
instances, verbs, and properties). Then, a set <strong>of</strong><br />
intermediate representations such as concepts<br />
classification trees, verb diagram, table <strong>of</strong> formulas, and<br />
table <strong>of</strong> rules. The aim is to allow <strong>the</strong> final user to<br />
ascertain whe<strong>the</strong>r or not an ontology is useful and to<br />
compare <strong>the</strong> scope and completeness <strong>of</strong> several<br />
ontologies, <strong>the</strong>ir reusability, and shareability.<br />
Formal conceptualization<br />
Create a computable ontology<br />
Guidelines for maintaining ontologies<br />
A list <strong>of</strong> <strong>the</strong> sources <strong>of</strong> knowledge and a rough<br />
description <strong>of</strong> how <strong>the</strong> process will be carried out and<br />
what techniques will be used.<br />
A formal and correct ontology<br />
Specification document must have <strong>the</strong> property <strong>of</strong><br />
concision<br />
Copyright © 2007, Idea Group Inc. Copying or distributing in print or electronic forms without written permission <strong>of</strong><br />
Idea Group Inc. is prohibited.