1 / 13

Harmonizing the Semantics of Technical Terms by the Generic Component Model

This paper explores the harmonization of technical terms through the Generic Component Model. It discusses concepts such as terminology, vocabulary, ontology, classification, and relationships. The paper also emphasizes the importance of aligning technical terms with the GCM to improve interoperability and provide intelligent support.

davidcano
Download Presentation

Harmonizing the Semantics of Technical Terms by the Generic Component Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Harmonizing the Semantics of Technical Terms by the Generic Component Model Frank Oemig, Bernd Blobel EFMI STC 2010 Reykjavik, Iceland June 3rd+4th, 2010

  2. What does this mean? Terminology Vocabulary Concept Catalog Term Rules Grammar Ontology Classification Nomenclature Taxonomy Thesaurus Value Set Relationship Pre-Coordination Post-Coordination causal Partonomy Rule Set sequential Harmonizing the Semantic of Technical Terms

  3. The Generic Component Modell Domain n Domain 2 Domain Perspective Domain 1 Business Concepts System's Architectural Perspective System Domains Relations Network System Compnent Composition Development Process Perspective Aggregations (e.g. Basic Services) Details (e.g. Basic Concepts) System Viewpoints Enterprise View Engineering View Technology View Information View Computational View Harmonizing the Semantic of Technical Terms

  4. Alignment with GCM (a specific view) Domains Views Business Concepts Relations Network Composition/ Decomposition Basic Services/ Functions Relationships Basic Concepts Domain 1 Domain 2 Domain 3 Domain n Catalogs Catalog Entries Harmonizing the Semantic of Technical Terms

  5. Alignment with the GCM (a specific domain) Views Domains Business Concepts Relations Network Composition/ Decomposition Basic Services/ Functions Relationships Catalogs Basic Concepts Enterprise View Information View Catalog Entries Harmonizing the Semantic of Technical Terms

  6. Results (i) • A catalogue entry represents an abstract single information item. • A catalogue represents an abstract aggregation of individual information items and is normally identified by a short description. • A vocabulary is a set of items in use in a specific domain. • A specific vocabulary where each entry represents a class of certain elements which in return may have a reduced information quality. • A concept is a specialization of codes by adding the semantics. • An Object-Identifier (OID) is a very special code. • Pre-coordinated concepts are a specialization of concepts in form of new concepts by combining the semantics of two or more other concepts, while post-coordinated concepts just embed other concepts • In principal, the different kinds of catalogues are distinguished by the different specializations of catalogue entries. • A terminology is a very special vocabulary which contains (perhaps standalone) concepts and therefore includes semantics. Harmonizing the Semantic of Technical Terms

  7. Results (ii) • A thesaurus as a catalogue of terms, but it also establishes associative relationships among the terms. • A term is itself a sequence of words. • A nomenclature is differentiated from a thesaurus by using rules out of a set. • A lexicon is an assembly of words. In order to help searching these words are ordered alphabetically, which sequential order. • An ontology makes use of, and embeds, a terminology. In addition, concepts out of a terminology are set into a relationship to each other. A priori, an ontology does not constrain the kind of relationship. • A relationship is a concept because it embeds a specific semantics when combining other catalogue entries. • Relationships can be specialized in order to provide different type of catalogues. • In an is-a relationship, the linked objects form a hierarchic relationship where the second is a specialization of the first. • A part-of relationship defines that the second object is part of the first. • A taxonomy/partonomy is a special ontology only allowing for is-a/part-of relationships in order to establish a hierarchy. Harmonizing the Semantic of Technical Terms

  8. Catalogs Basic Concepts RelationsNetwork Relations Harmonizing the Semantic of Technical Terms

  9. Discussion • Cimino: • „controlled vocabulary“ to avoid discussion • CEN: • „categorical structures“? • Should be mapped to GCM Harmonizing the Semantic of Technical Terms

  10. Conclusion • interoperability between different principals has been considered and standardized from a technology perspective. • use of technical terms must be based on a formally modeled architecture comprehensively meeting the GCM architecture framework • Provide education and intelligent support Harmonizing the Semantic of Technical Terms

  11. Q & A Harmonizing the Semantic of Technical Terms

  12. Thank you For Your Attention! Harmonizing the Semantic of Technical Terms

  13. HL7 Germany: Board Member + TC-chair HL7-USA: Past Int‘l Affiliate Representative to the TSC 2008 HL7 Ambassador Implementation & Conformance Co-Chair Konrad-Zuse-Platz 1-3 53227 Bonn Germany T: +49 (0) 228 2668-4781 M: +49 (0) 151 12668-781 Home: +49 (0) 208 3021 7656 eMail: Frank.Oemig@agfa.com Frank Oemig Agfa HealthCare GmbH Solution Management „Interfaces and Standards“ IHE: Founding Member Caretaker IT-Infrastructure Delegate to epSOS GMDS: AG SIE Co-Chair Harmonizing the Semantic of Technical Terms

More Related