21.01.2014 Views

Semantic Annotation for Process Models: - Department of Computer ...

Semantic Annotation for Process Models: - Department of Computer ...

Semantic Annotation for Process Models: - Department of Computer ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

52 CHAPTER 3. STATE OF THE ART<br />

providing unified structured metadata. Emerging semantic annotation <strong>of</strong> Web services<br />

is relating concepts in Web services to domain specific ontologies, such as MWSAF<br />

(METEOR-S Web Service <strong>Annotation</strong> Framework) [133].<br />

Manual annotation is a tedious work. Semi-automatic and automatic annotation<br />

can facilitate this task. Some ef<strong>for</strong>ts on automatic and semi-automatic semantic annotation<br />

<strong>of</strong> textual documents have already done in [32] and [70]. Usually, the text<br />

extraction using some lexical analysis and grammatical functions is applied to achieve<br />

the semi-automatic annotation. AI technologies and semantic mapping are <strong>of</strong>ten used<br />

in Web services <strong>for</strong> the semi-automatic semantic annotation.<br />

3.4.1 MnM<br />

MnM [184] is an annotation tool to support both automated and semi-automated semantic<br />

markup <strong>of</strong> Web pages. MnM integrates a Web browser with an ontology editor<br />

and provides open APIs to link to ontology servers and <strong>for</strong> integrating in<strong>for</strong>mation<br />

extraction tools [193]. With the browser, users can have an overview <strong>of</strong> the knowledge<br />

models which are stored on the ontology server. A set <strong>of</strong> tags defined in the ontology<br />

are selected to annotate segments <strong>of</strong> text on web pages. MnM uses SGML/XML <strong>for</strong>mat<br />

tags and inserts them into the document.<br />

A machine learning technique is applied <strong>for</strong> in<strong>for</strong>mation extraction in MnM. The<br />

manual tagged documents are treated as training corpus over which a learning algorithm<br />

is run to learn the extraction rules. Learning can result in a library <strong>of</strong> induced rules<br />

which can be used to extract in<strong>for</strong>mation from texts. The extracted in<strong>for</strong>mation is<br />

sent to the ontology server and fills predefined slots associated with an extraction<br />

template. The slots are the properties <strong>of</strong> a particular class defined in the ontology.<br />

MnM can handle multiple ontologies at the same time and allows inherited definitions<br />

to be displayed <strong>for</strong> ontology editing and browsing. Moreover, MnM can access ontology<br />

servers through APIs, and also access ontologies specified in a markup <strong>for</strong>mat, such as<br />

RDF and DAML+OIL [193].<br />

3.4.2 KIM (Knowledge & In<strong>for</strong>mation Management)<br />

KIM [127] is a knowledge and in<strong>for</strong>mation management plat<strong>for</strong>m <strong>for</strong> automatic semantic<br />

annotation, indexing and retrieval <strong>of</strong> Web documents. The automatic semantic<br />

annotation in KIM can be seen as a classical named-entity recognition (NER) and<br />

annotation process. The NE (Named-Entity) type is specified through a reference to<br />

the KIMO (KIM Ontology) with the focus on named entity classes. KIMO is a lightweight<br />

top-level ontology including some basic distinctions between entity types (such<br />

as locations, agents, events, situations), real-world entity types <strong>of</strong> general importance<br />

(e.g. mettings, employment positions, commercial, government), and characteristic attributes<br />

and relations <strong>for</strong> featured entity types. The KIM KB (Knowledge Base) aims<br />

to provide quasi exhaustive coverage <strong>of</strong> the most important entities in the world. The<br />

entities stored in KB are instances with their proper classes and aliases. The entity<br />

descriptions in KB and the KIM ontology are stored in the same RDF(S) repository.<br />

Thus, KIM provides <strong>for</strong> each entity reference in the document (i) a link (URI) to the<br />

specific class in the ontology, and (ii) a link to the specific instance in the KB [136].

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!