Search (8 results, page 1 of 1)

0.025201196 = product of:
  0.06300299 = sum of:
    0.053677894 = weight(_text_:section in 2362) [ClassicSimilarity], result of:
      0.053677894 = score(doc=2362,freq=2.0), product of:
        0.26305357 = queryWeight, product of:
          5.276892 = idf(docFreq=613, maxDocs=44218)
          0.049850095 = queryNorm
        0.20405689 = fieldWeight in 2362, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.276892 = idf(docFreq=613, maxDocs=44218)
          0.02734375 = fieldNorm(doc=2362)
    0.009325097 = weight(_text_:on in 2362) [ClassicSimilarity], result of:
      0.009325097 = score(doc=2362,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.08505116 = fieldWeight in 2362, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.02734375 = fieldNorm(doc=2362)
  0.4 = coord(2/5)

Abstract

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".

0.024165256 = product of:
  0.060413137 = sum of:
    0.026643137 = weight(_text_:on in 539) [ClassicSimilarity], result of:
      0.026643137 = score(doc=539,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.24300331 = fieldWeight in 539, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.078125 = fieldNorm(doc=539)
    0.03377 = product of:
      0.06754 = sum of:
        0.06754 = weight(_text_:22 in 539) [ClassicSimilarity], result of:
          0.06754 = score(doc=539,freq=2.0), product of:
            0.17456654 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049850095 = 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.4 = coord(2/5)

Abstract

A discussion on current initiatives regarding terminology registries.

Date

26.12.2011 13:22:07

0.017673712 = product of:
  0.04418428 = sum of:
    0.03230309 = weight(_text_:on in 604) [ClassicSimilarity], result of:
      0.03230309 = score(doc=604,freq=6.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.29462588 = fieldWeight in 604, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=604)
    0.011881187 = weight(_text_:information in 604) [ClassicSimilarity], result of:
      0.011881187 = score(doc=604,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.13576832 = fieldWeight in 604, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=604)
  0.4 = coord(2/5)

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.

Source

Proceedings of the Sixth Workshop on Scripting and Development for the Semantic Web, Crete, Greece, May 31, 2010, CEUR Workshop Proceedings, SFSW - http://ceur-ws.org/Vol-699/Paper2.pdf

0.014181092 = product of:
  0.03545273 = sum of:
    0.018650195 = weight(_text_:on in 572) [ClassicSimilarity], result of:
      0.018650195 = score(doc=572,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.17010231 = fieldWeight in 572, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=572)
    0.016802534 = weight(_text_:information in 572) [ClassicSimilarity], result of:
      0.016802534 = score(doc=572,freq=4.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.1920054 = fieldWeight in 572, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=572)
  0.4 = coord(2/5)

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.

0.013157635 = product of:
  0.032894086 = sum of:
    0.026104836 = weight(_text_:on in 4639) [ClassicSimilarity], result of:
      0.026104836 = score(doc=4639,freq=12.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.23809364 = fieldWeight in 4639, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.03125 = fieldNorm(doc=4639)
    0.0067892494 = weight(_text_:information in 4639) [ClassicSimilarity], result of:
      0.0067892494 = score(doc=4639,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.0775819 = fieldWeight in 4639, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.03125 = fieldNorm(doc=4639)
  0.4 = coord(2/5)

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.

0.005275072 = product of:
  0.02637536 = sum of:
    0.02637536 = weight(_text_:on in 4656) [ClassicSimilarity], result of:
      0.02637536 = score(doc=4656,freq=4.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.24056101 = fieldWeight in 4656, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4656)
  0.2 = coord(1/5)

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.

0.0031971764 = product of:
  0.015985882 = sum of:
    0.015985882 = weight(_text_:on in 4642) [ClassicSimilarity], result of:
      0.015985882 = score(doc=4642,freq=2.0), product of:
        0.109641045 = queryWeight, product of:
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.049850095 = queryNorm
        0.14580199 = fieldWeight in 4642, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.199415 = idf(docFreq=13325, maxDocs=44218)
          0.046875 = fieldNorm(doc=4642)
  0.2 = coord(1/5)

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.

0.002036775 = product of:
  0.0101838745 = sum of:
    0.0101838745 = weight(_text_:information in 4641) [ClassicSimilarity], result of:
      0.0101838745 = score(doc=4641,freq=2.0), product of:
        0.08751074 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.049850095 = queryNorm
        0.116372846 = fieldWeight in 4641, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=4641)
  0.2 = coord(1/5)

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.