Search (128 results, page 1 of 7)

0.0038025428 = product of:
  0.038025428 = sum of:
    0.011706693 = weight(_text_:und in 539) [ClassicSimilarity], result of:
      0.011706693 = score(doc=539,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.24487628 = fieldWeight in 539, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.078125 = fieldNorm(doc=539)
    0.011706693 = weight(_text_:und in 539) [ClassicSimilarity], result of:
      0.011706693 = score(doc=539,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.24487628 = fieldWeight in 539, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.078125 = fieldNorm(doc=539)
    0.0146120405 = product of:
      0.029224081 = sum of:
        0.029224081 = weight(_text_:22 in 539) [ClassicSimilarity], result of:
          0.029224081 = score(doc=539,freq=2.0), product of:
            0.07553371 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.021569785 = queryNorm
            0.38690117 = fieldWeight in 539, 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=539)
      0.5 = coord(1/2)
  0.1 = coord(3/30)

Date

26.12.2011 13:22:07

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.00326992 = product of:
  0.024524398 = sum of:
    0.008194685 = weight(_text_:und in 4644) [ClassicSimilarity], result of:
      0.008194685 = score(doc=4644,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 4644, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4644)
    0.0053462577 = weight(_text_:in in 4644) [ClassicSimilarity], result of:
      0.0053462577 = score(doc=4644,freq=6.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.1822149 = fieldWeight in 4644, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4644)
    0.008194685 = weight(_text_:und in 4644) [ClassicSimilarity], result of:
      0.008194685 = score(doc=4644,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 4644, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4644)
    0.0027887707 = weight(_text_:s in 4644) [ClassicSimilarity], result of:
      0.0027887707 = score(doc=4644,freq=4.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.118916616 = fieldWeight in 4644, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4644)
  0.13333334 = coord(4/30)

Abstract

This paper describes a method for converting existing thesauri and related resources from their native format to RDF(S) and OWL. The method identifies four steps in the conversion process. In each step, decisions have to be taken with respect to the syntax or semantics of the resulting representation. Each step is supported through a number of guidelines. The method is illustrated through conversions of two large thesauri: MeSH and WordNet.

Pages

S.17-31

Series

Lecture notes in computer science; no.3298

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0029625234 = product of:
  0.022218924 = sum of:
    0.0070240153 = weight(_text_:und in 4641) [ClassicSimilarity], result of:
      0.0070240153 = score(doc=4641,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.14692576 = fieldWeight in 4641, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.046875 = fieldNorm(doc=4641)
    0.0064806426 = weight(_text_:in in 4641) [ClassicSimilarity], result of:
      0.0064806426 = score(doc=4641,freq=12.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.22087781 = fieldWeight in 4641, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=4641)
    0.0070240153 = weight(_text_:und in 4641) [ClassicSimilarity], result of:
      0.0070240153 = score(doc=4641,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.14692576 = fieldWeight in 4641, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.046875 = fieldNorm(doc=4641)
    0.0016902501 = weight(_text_:s in 4641) [ClassicSimilarity], result of:
      0.0016902501 = score(doc=4641,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.072074346 = fieldWeight in 4641, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.046875 = fieldNorm(doc=4641)
  0.13333334 = coord(4/30)

Abstract

This paper presents an overview of the work in progress at the W3C to produce a standard conversion of WordNet to the RDF/OWL representation language in use in the SemanticWeb community. Such a standard representation is useful to provide application developers a high-quality resource and to promote interoperability. Important requirements in this conversion process are that it should be complete and should stay close to WordNet's conceptual model. The paper explains the steps taken to produce the conversion and details design decisions such as the composition of the class hierarchy and properties, the addition of suitable OWL semantics and the chosen format of the URIs. Additional topics include a strategy to incorporate OWL and RDFS semantics in one schema such that both RDF(S) infrastructure and OWL infrastructure can interpret the information correctly, problems encountered in understanding the Prolog source files and the description of the two versions that are provided (Basic and Full) to accommodate different usages of WordNet.

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0022562696 = product of:
  0.022562696 = sum of:
    0.008194685 = weight(_text_:und in 572) [ClassicSimilarity], result of:
      0.008194685 = score(doc=572,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 572, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=572)
    0.0061733257 = weight(_text_:in in 572) [ClassicSimilarity], result of:
      0.0061733257 = score(doc=572,freq=8.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.21040362 = fieldWeight in 572, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0546875 = fieldNorm(doc=572)
    0.008194685 = weight(_text_:und in 572) [ClassicSimilarity], result of:
      0.008194685 = score(doc=572,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 572, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=572)
  0.1 = coord(3/30)

Abstract

We consider use of ontological background knowledge in intelligent information systems and analyze directions of their reduction in compliance with specifics of particular user task. Such reduction is aimed at simplification of knowledge processing without loss of significant information. We propose methods of generation of task thesauri based on domain ontology that contain such subset of ontological concepts and relations that can be used in task solving. Combinatorial optimization is used for minimization of task thesaurus. In this approach, semantic similarity estimates are used for determination of concept significance for user task. Some practical examples of optimized thesauri application for semantic retrieval and competence analysis demonstrate efficiency of proposed approach.

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0021588372 = product of:
  0.021588372 = sum of:
    0.0052914224 = weight(_text_:in in 4649) [ClassicSimilarity], result of:
      0.0052914224 = score(doc=4649,freq=8.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.18034597 = fieldWeight in 4649, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=4649)
    0.007529726 = product of:
      0.022589177 = sum of:
        0.022589177 = weight(_text_:l in 4649) [ClassicSimilarity], result of:
          0.022589177 = score(doc=4649,freq=2.0), product of:
            0.0857324 = queryWeight, product of:
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.021569785 = queryNorm
            0.26348472 = fieldWeight in 4649, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.046875 = fieldNorm(doc=4649)
      0.33333334 = coord(1/3)
    0.008767224 = product of:
      0.017534448 = sum of:
        0.017534448 = weight(_text_:22 in 4649) [ClassicSimilarity], result of:
          0.017534448 = score(doc=4649,freq=2.0), product of:
            0.07553371 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.021569785 = queryNorm
            0.23214069 = fieldWeight in 4649, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=4649)
      0.5 = coord(1/2)
  0.1 = coord(3/30)

Abstract

More and more cultural heritage institutions publish their collections, vocabularies and metadata on the Web. The resulting Web of linked cultural data opens up exciting new possibilities for searching and browsing through these cultural heritage collections. We report on ongoing work in which we investigate the estimation of relevance in this Web of Culture. We study existing measures of semantic distance and how they apply to two use cases. The use cases relate to the structured, multilingual and multimodal nature of the Culture Web. We distinguish between measures using the Web, such as Google distance and PMI, and measures using the Linked Data Web, i.e. the semantic structure of metadata vocabularies. We perform a small study in which we compare these semantic distance measures to human judgements of relevance. Although it is too early to draw any definitive conclusions, the study provides new insights into the applicability of semantic distance measures to the Web of Culture, and clear starting points for further research.

Date

26.12.2011 13:40:22

0.0021044814 = product of:
  0.01578361 = sum of:
    0.004682677 = weight(_text_:und in 4639) [ClassicSimilarity], result of:
      0.004682677 = score(doc=4639,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.09795051 = fieldWeight in 4639, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.03125 = fieldNorm(doc=4639)
    0.0052914224 = weight(_text_:in in 4639) [ClassicSimilarity], result of:
      0.0052914224 = score(doc=4639,freq=18.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.18034597 = fieldWeight in 4639, product of:
          4.2426405 = tf(freq=18.0), with freq of:
            18.0 = termFreq=18.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.03125 = fieldNorm(doc=4639)
    0.004682677 = weight(_text_:und in 4639) [ClassicSimilarity], result of:
      0.004682677 = score(doc=4639,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.09795051 = fieldWeight in 4639, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.03125 = fieldNorm(doc=4639)
    0.0011268335 = weight(_text_:s in 4639) [ClassicSimilarity], result of:
      0.0011268335 = score(doc=4639,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.048049565 = fieldWeight in 4639, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.03125 = fieldNorm(doc=4639)
  0.13333334 = coord(4/30)

Abstract

This thesis focuses on conversion of vocabularies for representation and integration of collections on the Semantic Web. A secondary focus is how to represent metadata schemas (RDF Schemas representing metadata element sets) such that they interoperate with vocabularies. The primary domain in which we operate is that of cultural heritage collections. The background worldview in which a solution is sought is that of the Semantic Web research paradigmwith its associated theories, methods, tools and use cases. In other words, we assume the SemanticWeb is in principle able to provide the context to realize interoperable collections. Interoperability is dependent on the interplay between representations and the applications that use them. We mean applications in the widest sense, such as "search" and "annotation". These applications or tasks are often present in software applications, such as the E-Culture application. It is therefore necessary that applications requirements on the vocabulary representation are met. This leads us to formulate the following problem statement: HOW CAN EXISTING VOCABULARIES BE MADE AVAILABLE TO SEMANTIC WEB APPLICATIONS?
We refine the problem statement into three research questions. The first two focus on the problem of conversion of a vocabulary to a Semantic Web representation from its original format. Conversion of a vocabulary to a representation in a Semantic Web language is necessary to make the vocabulary available to SemanticWeb applications. In the last question we focus on integration of collection metadata schemas in a way that allows for vocabulary representations as produced by our methods. Academisch proefschrift ter verkrijging van de graad Doctor aan de Vrije Universiteit Amsterdam, Dutch Research School for Information and Knowledge Systems.

Pages

IV, 186 S

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0020754572 = product of:
  0.020754572 = sum of:
    0.008194685 = weight(_text_:und in 4656) [ClassicSimilarity], result of:
      0.008194685 = score(doc=4656,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 4656, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4656)
    0.004365201 = weight(_text_:in in 4656) [ClassicSimilarity], result of:
      0.004365201 = score(doc=4656,freq=4.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.14877784 = fieldWeight in 4656, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4656)
    0.008194685 = weight(_text_:und in 4656) [ClassicSimilarity], result of:
      0.008194685 = score(doc=4656,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 4656, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4656)
  0.1 = coord(3/30)

Abstract

This document describes in brief how to express the content and structure of a thesaurus, and metadata about a thesaurus, in RDF. Using RDF allows data to be linked to and/or merged with other RDF data by semantic web applications. The Semantic Web, which is based on the Resource Description Framework (RDF), provides a common framework that allows data to be shared and reused across application, enterprise, and community boundaries.

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0019476034 = product of:
  0.019476034 = sum of:
    0.008194685 = weight(_text_:und in 604) [ClassicSimilarity], result of:
      0.008194685 = score(doc=604,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 604, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=604)
    0.0030866629 = weight(_text_:in in 604) [ClassicSimilarity], result of:
      0.0030866629 = score(doc=604,freq=2.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.10520181 = fieldWeight in 604, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0546875 = fieldNorm(doc=604)
    0.008194685 = weight(_text_:und in 604) [ClassicSimilarity], result of:
      0.008194685 = score(doc=604,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 604, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=604)
  0.1 = coord(3/30)

Abstract

iQvoc is a new open source SKOS-XL vocabulary management tool developed by the Federal Environment Agency, Germany, and innoQ Deutschland GmbH. Its immediate purpose is maintaining and publishing reference vocabularies in the upcoming Linked Data cloud of environmental information, but it may be easily adapted to host any SKOS- XL compliant vocabulary. iQvoc is implemented as a Ruby on Rails application running on top of JRuby - the Java implementation of the Ruby Programming Language. To increase the user experience when editing content, iQvoc uses heavily the JavaScript library jQuery.

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0018823948 = product of:
  0.018823948 = sum of:
    0.008366474 = weight(_text_:in in 2655) [ClassicSimilarity], result of:
      0.008366474 = score(doc=2655,freq=20.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.28515202 = fieldWeight in 2655, product of:
          4.472136 = tf(freq=20.0), with freq of:
            20.0 = termFreq=20.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=2655)
    0.0016902501 = weight(_text_:s in 2655) [ClassicSimilarity], result of:
      0.0016902501 = score(doc=2655,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.072074346 = fieldWeight in 2655, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.046875 = fieldNorm(doc=2655)
    0.008767224 = product of:
      0.017534448 = sum of:
        0.017534448 = weight(_text_:22 in 2655) [ClassicSimilarity], result of:
          0.017534448 = score(doc=2655,freq=2.0), product of:
            0.07553371 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.021569785 = queryNorm
            0.23214069 = fieldWeight in 2655, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=2655)
      0.5 = coord(1/2)
  0.1 = coord(3/30)

Abstract

The term "facet" was introduced into the field of library classification systems by Ranganathan in the 1930's [Ranganathan, 1962]. A facet is a viewpoint or aspect. In contrast to traditional classification systems, faceted systems are modular in that a domain is analyzed in terms of baseline facets which are then synthesized. In this paper, the term "facet" is used in a broader meaning. Facets can describe different aspects on the same level of abstraction or the same aspect on different levels of abstraction. The notion of facets is related to database views, multicontexts and conceptual scaling in formal concept analysis [Ganter and Wille, 1999], polymorphism in object-oriented design, aspect-oriented programming, views and contexts in description logic and semantic networks. This paper presents a definition of facets in terms of faceted knowledge representation that incorporates the traditional narrower notion of facets and potentially facilitates translation between different knowledge representation formalisms. A goal of this approach is a modular, machine-aided knowledge base design mechanism. A possible application is faceted thesaurus construction for information retrieval and data mining. Reasoning complexity depends on the size of the modules (facets). A more general analysis of complexity will be left for future research.

Date

22. 1.2016 17:30:31

0.0018361328 = product of:
  0.018361328 = sum of:
    0.008194685 = weight(_text_:und in 4329) [ClassicSimilarity], result of:
      0.008194685 = score(doc=4329,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 4329, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4329)
    0.008194685 = weight(_text_:und in 4329) [ClassicSimilarity], result of:
      0.008194685 = score(doc=4329,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.17141339 = fieldWeight in 4329, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4329)
    0.0019719584 = weight(_text_:s in 4329) [ClassicSimilarity], result of:
      0.0019719584 = score(doc=4329,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.08408674 = fieldWeight in 4329, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4329)
  0.1 = coord(3/30)

Content

Enthält einen Überblick über Modelle, Systeme und Projekte

Pages

S.252-257

0.0017789633 = product of:
  0.017789632 = sum of:
    0.0070240153 = weight(_text_:und in 4642) [ClassicSimilarity], result of:
      0.0070240153 = score(doc=4642,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.14692576 = fieldWeight in 4642, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.046875 = fieldNorm(doc=4642)
    0.003741601 = weight(_text_:in in 4642) [ClassicSimilarity], result of:
      0.003741601 = score(doc=4642,freq=4.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.12752387 = fieldWeight in 4642, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=4642)
    0.0070240153 = weight(_text_:und in 4642) [ClassicSimilarity], result of:
      0.0070240153 = score(doc=4642,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.14692576 = fieldWeight in 4642, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.046875 = fieldNorm(doc=4642)
  0.1 = coord(3/30)

Abstract

Thesauri can be useful resources for indexing and retrieval on the Semantic Web, but often they are not published in RDF/OWL. To convert thesauri to RDF for use in Semantic Web applications and to ensure the quality and utility of the conversion a structured method is required. Moreover, if different thesauri are to be interoperable without complicated mappings, a standard schema for thesauri is required. This paper presents a method for conversion of thesauri to the SKOS RDF/OWL schema, which is a proposal for such a standard under development by W3Cs Semantic Web Best Practices Working Group. We apply the method to three thesauri: IPSV, GTAA and MeSH. With these case studies we evaluate our method and the applicability of SKOS for representing thesauri.

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0017630312 = product of:
  0.017630313 = sum of:
    0.0052914224 = weight(_text_:in in 4646) [ClassicSimilarity], result of:
      0.0052914224 = score(doc=4646,freq=8.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.18034597 = fieldWeight in 4646, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=4646)
    0.010648641 = product of:
      0.03194592 = sum of:
        0.03194592 = weight(_text_:l in 4646) [ClassicSimilarity], result of:
          0.03194592 = score(doc=4646,freq=4.0), product of:
            0.0857324 = queryWeight, product of:
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.021569785 = queryNorm
            0.37262368 = fieldWeight in 4646, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.046875 = fieldNorm(doc=4646)
      0.33333334 = coord(1/3)
    0.0016902501 = weight(_text_:s in 4646) [ClassicSimilarity], result of:
      0.0016902501 = score(doc=4646,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.072074346 = fieldWeight in 4646, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.046875 = fieldNorm(doc=4646)
  0.1 = coord(3/30)

Abstract

In this article we describe a SemanticWeb application for semantic annotation and search in large virtual collections of cultural-heritage objects, indexed with multiple vocabularies. During the annotation phase we harvest, enrich and align collection metadata and vocabularies. The semantic-search facilities support keyword-based queries of the graph (currently 20M triples), resulting in semantically grouped result clusters, all representing potential semantic matches of the original query. We show two sample search scenario's. The annotation and search software is open source and is already being used by third parties. All software is based on establishedWeb standards, in particular HTML/XML, CSS, RDF/OWL, SPARQL and JavaScript.

Source

Web Semantics: Science, Services and Agents on the WorldWideWeb 6(2008) no.4, S.243-249

0.0016565587 = product of:
  0.016565587 = sum of:
    0.004365201 = weight(_text_:in in 2654) [ClassicSimilarity], result of:
      0.004365201 = score(doc=2654,freq=4.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.14877784 = fieldWeight in 2654, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2654)
    0.0019719584 = weight(_text_:s in 2654) [ClassicSimilarity], result of:
      0.0019719584 = score(doc=2654,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.08408674 = fieldWeight in 2654, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2654)
    0.010228428 = product of:
      0.020456856 = sum of:
        0.020456856 = weight(_text_:22 in 2654) [ClassicSimilarity], result of:
          0.020456856 = score(doc=2654,freq=2.0), product of:
            0.07553371 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.021569785 = 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.1 = coord(3/30)

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.0016373465 = product of:
  0.016373465 = sum of:
    0.005915991 = weight(_text_:in in 4820) [ClassicSimilarity], result of:
      0.005915991 = score(doc=4820,freq=10.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.20163295 = fieldWeight in 4820, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=4820)
    0.0016902501 = weight(_text_:s in 4820) [ClassicSimilarity], result of:
      0.0016902501 = score(doc=4820,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.072074346 = fieldWeight in 4820, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.046875 = fieldNorm(doc=4820)
    0.008767224 = product of:
      0.017534448 = sum of:
        0.017534448 = weight(_text_:22 in 4820) [ClassicSimilarity], result of:
          0.017534448 = score(doc=4820,freq=2.0), product of:
            0.07553371 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.021569785 = queryNorm
            0.23214069 = fieldWeight in 4820, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=4820)
      0.5 = coord(1/2)
  0.1 = coord(3/30)

Abstract

One of the major problems facing systems for Computer Aided Design (CAD), Architecture Engineering and Construction (AEC) and Geographic Information Systems (GIS) applications today is the lack of interoperability among the various systems. When integrating software applications, substantial di culties can arise in translating information from one application to the other. In this paper, we focus on semantic di culties that arise in software integration. Applications may use di erent terminologies to describe the same domain. Even when appli-cations use the same terminology, they often associate di erent semantics with the terms. This obstructs information exchange among applications. To cir-cumvent this obstacle, we need some way of explicitly specifying the semantics for each terminology in an unambiguous fashion. Ontologies can provide such specification. It will be the task of this paper to explain what ontologies are and how they can be used to facilitate interoperability between software systems used in computer aided design, architecture engineering and construction, and geographic information processing.

Date

3.12.2016 18:39:22

0.0015135966 = product of:
  0.015135966 = sum of:
    0.005915991 = weight(_text_:in in 4645) [ClassicSimilarity], result of:
      0.005915991 = score(doc=4645,freq=10.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.20163295 = fieldWeight in 4645, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=4645)
    0.007529726 = product of:
      0.022589177 = sum of:
        0.022589177 = weight(_text_:l in 4645) [ClassicSimilarity], result of:
          0.022589177 = score(doc=4645,freq=2.0), product of:
            0.0857324 = queryWeight, product of:
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.021569785 = queryNorm
            0.26348472 = fieldWeight in 4645, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.046875 = fieldNorm(doc=4645)
      0.33333334 = coord(1/3)
    0.0016902501 = weight(_text_:s in 4645) [ClassicSimilarity], result of:
      0.0016902501 = score(doc=4645,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.072074346 = fieldWeight in 4645, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.046875 = fieldNorm(doc=4645)
  0.1 = coord(3/30)

Abstract

Evaluation of ontology alignments is in practice done in two ways: (1) assessing individual correspondences and (2) comparing the alignment to a reference alignment. However, this type of evaluation does not guarantee that an application which uses the alignment will perform well. In this paper, we contribute to the current ontology alignment evaluation practices by proposing two alternative evaluation methods that take into account some characteristics of a usage scenario without doing a full-fledged end-to-end evaluation. We compare different evaluation approaches in three case studies, focussing on methodological issues. Each case study considers an alignment between a different pair of ontologies, ranging from rich and well-structured to small and poorly structured. This enables us to conclude on the use of different evaluation approaches in different settings.

0.0013313338 = product of:
  0.013313337 = sum of:
    0.0040973425 = weight(_text_:und in 2362) [ClassicSimilarity], result of:
      0.0040973425 = score(doc=2362,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.085706696 = fieldWeight in 2362, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.02734375 = fieldNorm(doc=2362)
    0.0051186522 = weight(_text_:in in 2362) [ClassicSimilarity], result of:
      0.0051186522 = score(doc=2362,freq=22.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.17445749 = fieldWeight in 2362, product of:
          4.690416 = tf(freq=22.0), with freq of:
            22.0 = termFreq=22.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.02734375 = fieldNorm(doc=2362)
    0.0040973425 = weight(_text_:und in 2362) [ClassicSimilarity], result of:
      0.0040973425 = score(doc=2362,freq=2.0), product of:
        0.04780656 = queryWeight, product of:
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.021569785 = queryNorm
        0.085706696 = fieldWeight in 2362, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.216367 = idf(docFreq=13101, maxDocs=44218)
          0.02734375 = fieldNorm(doc=2362)
  0.1 = coord(3/30)

Abstract

The paper analysed here is a kind of position paper. In order to get a better under-standing of the reported work I used the retrieval interface of the thesaurus, the so-called NCI DTS Browser accessible via the Web3, and I perused the cited OWL file4 with numerous "Find" and "Find next" string searches. In addition the file was im-ported into Protégé 2000, Release 2.0, with OWL Plugin 1.0 and Racer Plugin 1.7.14. At the end of the paper's introduction the authors say: "In the following sections, this paper will describe the terminology development process at NCI, and the issues associated with converting a description logic based nomenclature to a semantically rich OWL ontology." While I will not deal with the first part, i.e. the terminology development process at NCI, I do not see the thesaurus as a description logic based nomenclature, or its cur-rent state and conversion already result in a "rich" OWL ontology. What does "rich" mean here? According to my view there is a great quantity of concepts and links but a very poor description logic structure which enables inferences. And what does the fol-lowing really mean, which is said a few lines previously: "Although editors have defined a number of named ontologic relations to support the description-logic based structure of the Thesaurus, additional relation-ships are considered for inclusion as required to support dependent applications."
According to my findings several relations available in the thesaurus query interface as "roles", are not used, i.e. there are not yet any assertions with them. And those which are used do not contribute to complete concept definitions of concepts which represent thesaurus main entries. In other words: The authors claim to already have a "description logic based nomenclature", where there is not yet one which deserves that title by being much more than a thesaurus with strict subsumption and additional inheritable semantic links. In the last section of the paper the authors say: "The most time consuming process in this conversion was making a careful analysis of the Thesaurus to understand the best way to translate it into OWL." "For other conversions, these same types of distinctions and decisions must be made. The expressive power of a proprietary encoding can vary widely from that in OWL or RDF. Understanding the original semantics and engineering a solution that most closely duplicates it is critical for creating a useful and accu-rate ontology." My question is: What decisions were made and are they exemplary, can they be rec-ommended as "the best way"? I raise strong doubts with respect to that, and I miss more profound discussions of the issues at stake. The following notes are dedicated to a critical description and assessment of the results of that conversion activity. They are written in a tutorial style more or less addressing students, but myself being a learner especially in the field of medical knowledge representation I do not speak "ex cathedra".

Theme

Konzeption und Anwendung des Prinzips Thesaurus

0.0013083849 = product of:
  0.013083849 = sum of:
    0.0054005357 = weight(_text_:in in 231) [ClassicSimilarity], result of:
      0.0054005357 = score(doc=231,freq=12.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.18406484 = fieldWeight in 231, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0390625 = fieldNorm(doc=231)
    0.006274772 = product of:
      0.018824315 = sum of:
        0.018824315 = weight(_text_:l in 231) [ClassicSimilarity], result of:
          0.018824315 = score(doc=231,freq=2.0), product of:
            0.0857324 = queryWeight, product of:
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.021569785 = queryNorm
            0.2195706 = fieldWeight in 231, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.0390625 = fieldNorm(doc=231)
      0.33333334 = coord(1/3)
    0.0014085418 = weight(_text_:s in 231) [ClassicSimilarity], result of:
      0.0014085418 = score(doc=231,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.060061958 = fieldWeight in 231, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.0390625 = fieldNorm(doc=231)
  0.1 = coord(3/30)

Abstract

As an extension to the current Web, Semantic Web will not only contain structured data with machine understandable semantics but also textual information. While structured queries can be used to find information more precisely on the Semantic Web, keyword searches are still needed to help exploit textual information. It thus becomes very important that we can combine precise structured queries with imprecise keyword searches to have a hybrid query capability. In addition, due to the huge volume of information on the Semantic Web, the hybrid query must be processed in a very scalable way. In this paper, we define such a hybrid query capability that combines unary tree-shaped structured queries with keyword searches. We show how existing information retrieval (IR) index structures and functions can be reused to index semantic web data and its textual information, and how the hybrid query is evaluated on the index structure using IR engines in an efficient and scalable manner. We implemented this IR approach in an engine called Semplore. Comprehensive experiments on its performance show that it is a promising approach. It leads us to believe that it may be possible to evolve current web search engines to query and search the Semantic Web. Finally, we briefy describe how Semplore is used for searching Wikipedia and an IBM customer's product information.

Pages

S.652-665

Series

Lecture notes in computer science; 4825

0.001150207 = product of:
  0.011502069 = sum of:
    0.0038187557 = weight(_text_:in in 5864) [ClassicSimilarity], result of:
      0.0038187557 = score(doc=5864,freq=6.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.1301535 = fieldWeight in 5864, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5864)
    0.006274772 = product of:
      0.018824315 = sum of:
        0.018824315 = weight(_text_:l in 5864) [ClassicSimilarity], result of:
          0.018824315 = score(doc=5864,freq=2.0), product of:
            0.0857324 = queryWeight, product of:
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.021569785 = queryNorm
            0.2195706 = fieldWeight in 5864, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5864)
      0.33333334 = coord(1/3)
    0.0014085418 = weight(_text_:s in 5864) [ClassicSimilarity], result of:
      0.0014085418 = score(doc=5864,freq=2.0), product of:
        0.023451481 = queryWeight, product of:
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.021569785 = queryNorm
        0.060061958 = fieldWeight in 5864, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.0872376 = idf(docFreq=40523, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5864)
  0.1 = coord(3/30)

Abstract

Current retrieval and recommendation approaches rely on hard-wired data models. This hinders personalized cus-tomizations to meet information needs of users in a more flexible manner. Therefore, the paper investigates how similarity-basedretrieval strategies can be combined with graph queries to enable users or system providers to explore repositories in the LinkedOpen Data (LOD) cloud more thoroughly. For this purpose, we developed novel content-based recommendation approaches.They rely on concept annotations of Simple Knowledge Organization System (SKOS) vocabularies and a SPARQL-based querylanguage that facilitates advanced and personalized requests for openly available knowledge graphs. We have comprehensivelyevaluated the novel search strategies in several test cases and example application domains (i.e., travel search and multimediaretrieval). The results of the web-based online experiments showed that our approaches increase the recall and diversity of rec-ommendations or at least provide a competitive alternative strategy of resource access when conventional methods do not providehelpful suggestions. The findings may be of use for Linked Data-enabled recommender systems (LDRS) as well as for semanticsearch engines that can consume LOD resources. (PDF) Similarity-based knowledge graph queries for recommendation retrieval. Available from: https://www.researchgate.net/publication/333358714_Similarity-based_knowledge_graph_queries_for_recommendation_retrieval [accessed May 21 2020].

Source

Semantic Web. 10(2019) 6, S.1007-1037

0.0011043089 = product of:
  0.016564632 = sum of:
    0.005915991 = weight(_text_:in in 4648) [ClassicSimilarity], result of:
      0.005915991 = score(doc=4648,freq=10.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.20163295 = fieldWeight in 4648, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.046875 = fieldNorm(doc=4648)
    0.010648641 = product of:
      0.03194592 = sum of:
        0.03194592 = weight(_text_:l in 4648) [ClassicSimilarity], result of:
          0.03194592 = score(doc=4648,freq=4.0), product of:
            0.0857324 = queryWeight, product of:
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.021569785 = queryNorm
            0.37262368 = fieldWeight in 4648, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.9746525 = idf(docFreq=2257, maxDocs=44218)
              0.046875 = fieldNorm(doc=4648)
      0.33333334 = coord(1/3)
  0.06666667 = coord(2/30)

Abstract

The main objective of the MultimediaN E-Culture project is to demonstrate how novel semantic-web and presentation technologies can be deployed to provide better indexing and search support within large virtual collections of culturalheritage resources. The architecture is fully based on open web standards in particular XML, SVG, RDF/OWL and SPARQL. One basic hypothesis underlying this work is that the use of explicit background knowledge in the form of ontologies/vocabularies/thesauri is in particular useful in information retrieval in knowledge-rich domains. This paper gives some details about the internals of the demonstrator.

0.0010934502 = product of:
  0.016401753 = sum of:
    0.0061733257 = weight(_text_:in in 4330) [ClassicSimilarity], result of:
      0.0061733257 = score(doc=4330,freq=8.0), product of:
        0.029340398 = queryWeight, product of:
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.021569785 = queryNorm
        0.21040362 = fieldWeight in 4330, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.3602545 = idf(docFreq=30841, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4330)
    0.010228428 = product of:
      0.020456856 = sum of:
        0.020456856 = weight(_text_:22 in 4330) [ClassicSimilarity], result of:
          0.020456856 = score(doc=4330,freq=2.0), product of:
            0.07553371 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.021569785 = queryNorm
            0.2708308 = fieldWeight in 4330, 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=4330)
      0.5 = coord(1/2)
  0.06666667 = coord(2/30)

Abstract

One vision of the Semantic Web is that it will be much like the Web we know today, except that documents will be enriched by annotations in machine understandable markup. These annotations will provide metadata about the documents as well as machine interpretable statements capturing some of the meaning of document content. We discuss how the information retrieval paradigm might be recast in such an environment. We suggest that retrieval can be tightly bound to inference. Doing so makes today's Web search engines useful to Semantic Web inference engines, and causes improvements in either retrieval or inference to lead directly to improvements in the other.

Date

12. 2.2011 17:35:22