Domain specific language in technical solution documents: Discussion of two approaches to improve the semi-automated annotation

Helena X. Schmidt, Andreas Kohn, Udo Lindemann

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

2 Scopus citations

Abstract

The efficient search for existing solutions in mechanical engineering is a key-factor for successful product development. Ontology-based knowledge systems can support the semi-automated annotation of documents about existing solutions and enable the retrieval of those documents. However, the use of different wordings for similar products and a generally heterogeneous domain-specific language hinder the efficient annotation process. In this paper, two approaches to improve the semi-automatic annotation of documents by adding terms to the ontology are described. We evaluate the two approaches by analysing the industry sector-specific and company-specific languages used in documents in the field of mechanical engineering.

Original languageEnglish
Title of host publicationKEOD 2011 - Proceedings of the International Conference on Knowledge Engineering and Ontology Development
Pages159-166
Number of pages8
StatePublished - 2011
EventInternational Conference on Knowledge Engineering and Ontology Development, KEOD 2011 - Paris, France
Duration: 26 Oct 201129 Oct 2011

Publication series

NameKEOD 2011 - Proceedings of the International Conference on Knowledge Engineering and Ontology Development

Conference

ConferenceInternational Conference on Knowledge Engineering and Ontology Development, KEOD 2011
Country/TerritoryFrance
CityParis
Period26/10/1129/10/11

Keywords

  • Annotation
  • Domain specific language
  • Mechanical engineering
  • Ontology-based knowledge system
  • Solution knowledge
  • Sublanguage

Fingerprint

Dive into the research topics of 'Domain specific language in technical solution documents: Discussion of two approaches to improve the semi-automated annotation'. Together they form a unique fingerprint.

Cite this