Search (56 results, page 1 of 3)

0.33914855 = product of:
  0.5935099 = sum of:
    0.059350993 = product of:
      0.17805298 = sum of:
        0.17805298 = weight(_text_:3a in 400) [ClassicSimilarity], result of:
          0.17805298 = score(doc=400,freq=2.0), product of:
            0.31681007 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.037368443 = queryNorm
            0.56201804 = fieldWeight in 400, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.046875 = fieldNorm(doc=400)
      0.33333334 = coord(1/3)
    0.17805298 = weight(_text_:2f in 400) [ClassicSimilarity], result of:
      0.17805298 = score(doc=400,freq=2.0), product of:
        0.31681007 = queryWeight, product of:
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.037368443 = queryNorm
        0.56201804 = fieldWeight in 400, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.046875 = fieldNorm(doc=400)
    0.17805298 = weight(_text_:2f in 400) [ClassicSimilarity], result of:
      0.17805298 = score(doc=400,freq=2.0), product of:
        0.31681007 = queryWeight, product of:
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.037368443 = queryNorm
        0.56201804 = fieldWeight in 400, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.046875 = fieldNorm(doc=400)
    0.17805298 = weight(_text_:2f in 400) [ClassicSimilarity], result of:
      0.17805298 = score(doc=400,freq=2.0), product of:
        0.31681007 = queryWeight, product of:
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.037368443 = queryNorm
        0.56201804 = fieldWeight in 400, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.478011 = idf(docFreq=24, maxDocs=44218)
          0.046875 = fieldNorm(doc=400)
  0.5714286 = coord(4/7)

Content

Vgl.: https%3A%2F%2Faclanthology.org%2FD19-5317.pdf&usg=AOvVaw0ZZFyq5wWTtNTvNkrvjlGA.

0.032156922 = product of:
  0.112549216 = sum of:
    0.09482904 = weight(_text_:interpretation in 2654) [ClassicSimilarity], result of:
      0.09482904 = score(doc=2654,freq=2.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.4430163 = fieldWeight in 2654, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2654)
    0.017720178 = product of:
      0.035440356 = sum of:
        0.035440356 = weight(_text_:22 in 2654) [ClassicSimilarity], result of:
          0.035440356 = score(doc=2654,freq=2.0), product of:
            0.13085791 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.037368443 = queryNorm
            0.2708308 = fieldWeight in 2654, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2654)
      0.5 = coord(1/2)
  0.2857143 = coord(2/7)

Abstract

Faceted Knowledge Representation provides a formalism for implementing knowledge systems. The basic notions of faceted knowledge representation are "unit", "relation", "facet" and "interpretation". Units are atomic elements and can be abstract elements or refer to external objects in an application. Relations are sequences or matrices of 0 and 1's (binary matrices). Facets are relational structures that combine units and relations. Each facet represents an aspect or viewpoint of a knowledge system. Interpretations are mappings that can be used to translate between different representations. This paper introduces the basic notions of faceted knowledge representation. The formalism is applied here to an abstract modeling of a faceted thesaurus as used in information retrieval.

Date

22. 1.2016 17:30:31

0.019352864 = product of:
  0.13547005 = sum of:
    0.13547005 = weight(_text_:interpretation in 2097) [ClassicSimilarity], result of:
      0.13547005 = score(doc=2097,freq=8.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.6328804 = fieldWeight in 2097, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2097)
  0.14285715 = coord(1/7)

Abstract

Interpretation of semantic propositions in free-text documents such as MEDLINE citations would provide valuable support for biomedical applications, and several approaches to semantic interpretation are being pursued in the biomedical informatics community. In this paper, we describe a methodology for interpreting linguistic structures that encode hypernymic propositions, in which a more specific concept is in a taxonomic relationship with a more general concept. In order to effectively process these constructions, we exploit underspecified syntactic analysis and structured domain knowledge from the Unified Medical Language System (UMLS). After introducing the syntactic processing on which our system depends, we focus on the UMLS knowledge that supports interpretation of hypernymic propositions. We first use semantic groups from the Semantic Network to ensure that the two concepts involved are compatible; hierarchical information in the Metathesaurus then determines which concept is more general and which more specific. A preliminary evaluation of a sample based on the semantic group Chemicals and Drugs provides 83% precision. An error analysis was conducted and potential solutions to the problems encountered are presented. The research discussed here serves as a paradigm for investigating the interaction between domain knowledge and linguistic structure in natural language processing, and could also make a contribution to research on automatic processing of discourse structure. Additional implications of the system we present include its integration in advanced semantic interpretation processors for biomedical text and its use for information extraction in specific domains. The approach has the potential to support a range of applications, including information retrieval and ontology engineering.

0.013684542 = product of:
  0.09579179 = sum of:
    0.09579179 = weight(_text_:interpretation in 2661) [ClassicSimilarity], result of:
      0.09579179 = score(doc=2661,freq=4.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.44751403 = fieldWeight in 2661, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2661)
  0.14285715 = coord(1/7)

Abstract

Research on semantic web services promises greater interoperability among software agents and web services by enabling content-based automated service discovery and interaction and by utilizing. Although this is to be based on use of shared ontologies published on the semantic web, services produced and described by different developers may well use different, perhaps partly overlapping, sets of ontologies. Interoperability will depend on ontology mappings and architectures supporting the associated translation processes. The question we ask is, does the traditional approach of introducing mediator agents to translate messages between requestors and services work in such an open environment? This article reviews some of the processing assumptions that were made in the development of the semantic web service modeling ontology OWL-S and argues that, as a practical matter, the translation function cannot always be isolated in mediators. Ontology mappings need to be published on the semantic web just as ontologies themselves are. The translation for service discovery, service process model interpretation, task negotiation, service invocation, and response interpretation may then be distributed to various places in the architecture so that translation can be done in the specific goal-oriented informational contexts of the agents performing these processes. We present arguments for assigning translation responsibility to particular agents in the cases of service invocation, response translation, and match- making.

0.01161172 = product of:
  0.081282035 = sum of:
    0.081282035 = weight(_text_:interpretation in 229) [ClassicSimilarity], result of:
      0.081282035 = score(doc=229,freq=2.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.37972826 = fieldWeight in 229, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.046875 = fieldNorm(doc=229)
  0.14285715 = coord(1/7)

Abstract

While much of a company's knowledge can be found in text repositories, current content management systems have limited capabilities for structuring and interpreting documents. In the emerging Semantic Web, search, interpretation and aggregation can be addressed by ontology-based semantic mark-up. In this paper, we examine semantic annotation, identify a number of requirements, and review the current generation of semantic annotation systems. This analysis shows that, while there is still some way to go before semantic annotation tools will be able to address fully all the knowledge management needs, research in the area is active and making good progress.

0.01161172 = product of:
  0.081282035 = sum of:
    0.081282035 = weight(_text_:interpretation in 1122) [ClassicSimilarity], result of:
      0.081282035 = score(doc=1122,freq=2.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.37972826 = fieldWeight in 1122, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.046875 = fieldNorm(doc=1122)
  0.14285715 = coord(1/7)

0.01161172 = product of:
  0.081282035 = sum of:
    0.081282035 = weight(_text_:interpretation in 2280) [ClassicSimilarity], result of:
      0.081282035 = score(doc=2280,freq=2.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.37972826 = fieldWeight in 2280, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.046875 = fieldNorm(doc=2280)
  0.14285715 = coord(1/7)

Abstract

A faceted ontology consists of a set of facets, where each facet consists of a predefined set of terms structured by a subsumption relation. We propose two extensions of faceted ontologies, which allow inferring conjunctions of terms that are valid in the underlying domain. We give a model-theoretic interpretation to these extended faceted ontologies and we provide mechanisms for inferring the valid conjunctions of terms. This inference service can be exploited for preventing errors during the indexing process and for deriving navigation trees that are suitable for browsing. The proposed scheme has several advantages by comparison to the hierarchical classification schemes that are currently used, namely: conceptual clarity: it is easier to understand, compactness: it takes less space, and scalability: the update operations can be formulated easier and be performed more efficiently.

0.009676432 = product of:
  0.067735024 = sum of:
    0.067735024 = weight(_text_:interpretation in 4705) [ClassicSimilarity], result of:
      0.067735024 = score(doc=4705,freq=2.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.3164402 = fieldWeight in 4705, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.0390625 = fieldNorm(doc=4705)
  0.14285715 = coord(1/7)

Abstract

Companies, governmental agencies and scientists produce a large amount of quantitative (research) data, consisting of measurements ranging from e.g. the surface temperatures of an ocean to the viscosity of a sample of mayonnaise. Such measurements are stored in tables in e.g. spreadsheet files and research reports. To integrate and reuse such data, it is necessary to have a semantic description of the data. However, the notation used is often ambiguous, making automatic interpretation and conversion to RDF or other suitable format diffiult. For example, the table header cell "f(Hz)" refers to frequency measured in Hertz, but the symbol "f" can also refer to the unit farad or the quantities force or luminous flux. Current annotation tools for this task either work on less ambiguous data or perform a more limited task. We introduce new disambiguation strategies based on an ontology, which allows to improve performance on "sloppy" datasets not yet targeted by existing systems.

0.0077411463 = product of:
  0.05418802 = sum of:
    0.05418802 = weight(_text_:interpretation in 4402) [ClassicSimilarity], result of:
      0.05418802 = score(doc=4402,freq=2.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.25315216 = fieldWeight in 4402, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.03125 = fieldNorm(doc=4402)
  0.14285715 = coord(1/7)

Abstract

Support for evolving ontologies is required in almost all situations where ontologies are used in real-world applications. In those cases, ontologies are often developed by several persons and will continue to evolve over time, because of changes in the real world, adaptations to different tasks, or alignments to other ontologies. To prevent that such changes will invalidate existing usage, a change management methodology is needed. This involves advanced versioning methods for the development and the maintenance of ontologies, but also configuration management, that takes care of the identification, relations and interpretation of ontology versions. All these aspects come together in integrated ontology library systems. When the number of different ontologies is increasing, the task of storing, maintaining and re-organizing them to secure the successful re-use of ontologies is challenging. Ontology library systems can help in the grouping and reorganizing ontologies for further re-use, integration, maintenance, mapping and versioning. Basically, a library system offers various functions for managing, adapting and standardizing groups of ontologies. Such integrated systems are a requirement for the Semantic Web to grow further and scale up. In this chapter, we describe a number of results with respect to the above mentioned areas. We start with a description of the alignment task and show a meta-ontology that is developed to specify the mappings. Then, we discuss the problems that are caused by evolving ontologies and describe two important elements of a change management methodology. Finally, in Section 4.4 we survey existing library systems and formulate a wish-list of features of an ontology library system.

0.0077411463 = product of:
  0.05418802 = sum of:
    0.05418802 = weight(_text_:interpretation in 4404) [ClassicSimilarity], result of:
      0.05418802 = score(doc=4404,freq=2.0), product of:
        0.21405315 = queryWeight, product of:
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.037368443 = queryNorm
        0.25315216 = fieldWeight in 4404, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.7281795 = idf(docFreq=390, maxDocs=44218)
          0.03125 = fieldNorm(doc=4404)
  0.14285715 = coord(1/7)

Abstract

Significant progress has been made in technologies for publishing and distributing knowledge and information on the web. However, much of the published information is not organized, and it is hard to find answers to questions that require more than a keyword search. In general, one can say that the web is organizing itself. Information is often published in relatively ad hoc fashion. Typically, concern about the presentation of content has been limited to purely layout issues. This, combined with the fact that the representation language used on the World Wide Web (HTML) is mainly format-oriented, makes publishing on the WWW easy, giving it an enormous expressiveness. People add private, educational or organizational content to the web that is of an immensely diverse nature. Content on the web is growing closer to a real universal knowledge base, with one problem relatively undefined; the problem of the interpretation of its contents. Although widely acknowledged for its general and universal advantages, the increasing popularity of the web also shows us some major drawbacks. The developments of the information content on the web during the last year alone, clearly indicates the need for some changes. Perhaps one of the most significant problems with the web as a distributed information system is the difficulty of finding and comparing information.

0.005530036 = product of:
  0.03871025 = sum of:
    0.03871025 = product of:
      0.0774205 = sum of:
        0.0774205 = weight(_text_:anwendung in 4695) [ClassicSimilarity], result of:
          0.0774205 = score(doc=4695,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.42793027 = fieldWeight in 4695, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.0625 = fieldNorm(doc=4695)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0048387814 = product of:
  0.03387147 = sum of:
    0.03387147 = product of:
      0.06774294 = sum of:
        0.06774294 = weight(_text_:anwendung in 4644) [ClassicSimilarity], result of:
          0.06774294 = score(doc=4644,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.37443897 = fieldWeight in 4644, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4644)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0048387814 = product of:
  0.03387147 = sum of:
    0.03387147 = product of:
      0.06774294 = sum of:
        0.06774294 = weight(_text_:anwendung in 604) [ClassicSimilarity], result of:
          0.06774294 = score(doc=604,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.37443897 = fieldWeight in 604, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.0546875 = fieldNorm(doc=604)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0048387814 = product of:
  0.03387147 = sum of:
    0.03387147 = product of:
      0.06774294 = sum of:
        0.06774294 = weight(_text_:anwendung in 572) [ClassicSimilarity], result of:
          0.06774294 = score(doc=572,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.37443897 = fieldWeight in 572, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.0546875 = fieldNorm(doc=572)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0041475273 = product of:
  0.029032689 = sum of:
    0.029032689 = product of:
      0.058065377 = sum of:
        0.058065377 = weight(_text_:anwendung in 5448) [ClassicSimilarity], result of:
          0.058065377 = score(doc=5448,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.3209477 = fieldWeight in 5448, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.046875 = fieldNorm(doc=5448)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0041475273 = product of:
  0.029032689 = sum of:
    0.029032689 = product of:
      0.058065377 = sum of:
        0.058065377 = weight(_text_:anwendung in 2176) [ClassicSimilarity], result of:
          0.058065377 = score(doc=2176,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.3209477 = fieldWeight in 2176, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.046875 = fieldNorm(doc=2176)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0041475273 = product of:
  0.029032689 = sum of:
    0.029032689 = product of:
      0.058065377 = sum of:
        0.058065377 = weight(_text_:anwendung in 756) [ClassicSimilarity], result of:
          0.058065377 = score(doc=756,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.3209477 = fieldWeight in 756, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.046875 = fieldNorm(doc=756)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0041475273 = product of:
  0.029032689 = sum of:
    0.029032689 = product of:
      0.058065377 = sum of:
        0.058065377 = weight(_text_:anwendung in 4729) [ClassicSimilarity], result of:
          0.058065377 = score(doc=4729,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.3209477 = fieldWeight in 4729, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.046875 = fieldNorm(doc=4729)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.003616363 = product of:
  0.02531454 = sum of:
    0.02531454 = product of:
      0.05062908 = sum of:
        0.05062908 = weight(_text_:22 in 6089) [ClassicSimilarity], result of:
          0.05062908 = score(doc=6089,freq=2.0), product of:
            0.13085791 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.037368443 = queryNorm
            0.38690117 = fieldWeight in 6089, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=6089)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Pages

S.11-22

0.0034562727 = product of:
  0.024193907 = sum of:
    0.024193907 = product of:
      0.048387814 = sum of:
        0.048387814 = weight(_text_:anwendung in 3695) [ClassicSimilarity], result of:
          0.048387814 = score(doc=3695,freq=2.0), product of:
            0.1809185 = queryWeight, product of:
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.037368443 = queryNorm
            0.2674564 = fieldWeight in 3695, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8414783 = idf(docFreq=948, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3695)
      0.5 = coord(1/2)
  0.14285715 = coord(1/7)

Theme

Konzeption und Anwendung des Prinzips Thesaurus