Search (8 results, page 1 of 1)

0.0131395515 = product of:
  0.10511641 = sum of:
    0.10511641 = weight(_text_:supported in 4644) [ClassicSimilarity], result of:
      0.10511641 = score(doc=4644,freq=2.0), product of:
        0.22949564 = queryWeight, product of:
          5.9223356 = idf(docFreq=321, maxDocs=44218)
          0.03875087 = queryNorm
        0.45803228 = fieldWeight in 4644, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.9223356 = idf(docFreq=321, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4644)
  0.125 = coord(1/8)

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.

0.004325858 = product of:
  0.034606863 = sum of:
    0.034606863 = weight(_text_:work in 4641) [ClassicSimilarity], result of:
      0.034606863 = score(doc=4641,freq=2.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.2433148 = fieldWeight in 4641, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.046875 = fieldNorm(doc=4641)
  0.125 = coord(1/8)

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.

0.0036048815 = product of:
  0.028839052 = sum of:
    0.028839052 = weight(_text_:work in 3695) [ClassicSimilarity], result of:
      0.028839052 = score(doc=3695,freq=2.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.20276234 = fieldWeight in 3695, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.0390625 = fieldNorm(doc=3695)
  0.125 = coord(1/8)

Abstract

The concepts of simplicity and complexity play major roles in information storage and retrieval in knowledge organizations. This paper reports an investigation of these concepts in the structure of descriptors. The main purpose of simplicity is to decrease the number of words in the construction of descriptors as this idea affects semantic relations, recall and precision. ISO 25964 has affirmed the purpose of simplicity by requiring splitting compound terms into simpler concepts. This work aims to elaborate the standard methods of evaluation by providing a more detailed evaluation of the descriptors structure and identifying effective factors in simplicity and complexity results in the structure of thesauri descriptors. The research population is taken from the descriptors of the Commonwealth Agricultural Bureaux (CAB) Thesaurus, the Persian Cultural Thesaurus (ASFA) and the Chemical Thesaurus. This research was conducted using the statistical and content analysis method. In this research we propose a new quantitative approach as well as novel indicators and indices involving Simplicity and Factoring Ratios to evaluate the descriptors structure. The results will be useful in the verification, selection and maintenance purposes in knowledge organizations and the inquiry method can be further developed in the field of ontology evaluation.

0.00328138 = product of:
  0.02625104 = sum of:
    0.02625104 = product of:
      0.05250208 = sum of:
        0.05250208 = weight(_text_:22 in 539) [ClassicSimilarity], result of:
          0.05250208 = score(doc=539,freq=2.0), product of:
            0.13569894 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03875087 = 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.125 = coord(1/8)

Date

26.12.2011 13:22:07

0.002523417 = product of:
  0.020187335 = sum of:
    0.020187335 = weight(_text_:work in 2362) [ClassicSimilarity], result of:
      0.020187335 = score(doc=2362,freq=2.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.14193363 = fieldWeight in 2362, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.02734375 = fieldNorm(doc=2362)
  0.125 = coord(1/8)

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

0.002296966 = product of:
  0.018375728 = sum of:
    0.018375728 = product of:
      0.036751457 = sum of:
        0.036751457 = weight(_text_:22 in 4792) [ClassicSimilarity], result of:
          0.036751457 = score(doc=4792,freq=2.0), product of:
            0.13569894 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03875087 = queryNorm
            0.2708308 = fieldWeight in 4792, 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=4792)
      0.5 = coord(1/2)
  0.125 = coord(1/8)

Source

Wissensspeicher in digitalen Räumen: Nachhaltigkeit - Verfügbarkeit - semantische Interoperabilität. Proceedings der 11. Tagung der Deutschen Sektion der Internationalen Gesellschaft für Wissensorganisation, Konstanz, 20. bis 22. Februar 2008. Hrsg.: J. Sieglerschmidt u. H.P.Ohly

0.002162929 = product of:
  0.017303431 = sum of:
    0.017303431 = weight(_text_:work in 1169) [ClassicSimilarity], result of:
      0.017303431 = score(doc=1169,freq=2.0), product of:
        0.14223081 = queryWeight, product of:
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.03875087 = queryNorm
        0.1216574 = fieldWeight in 1169, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6703904 = idf(docFreq=3060, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1169)
  0.125 = coord(1/8)

Abstract

T.2: The ability to identify and locate relevant information among vast collections and other resources is a major and pressing challenge today. Several different types of vocabulary are in use for this purpose. Some of the most widely used vocabularies were designed a hundred years ago and have been evolving steadily. A different generation of vocabularies is now emerging, designed to exploit the electronic media more effectively. A good understanding of the previous generation is still essential for effective access to collections indexed with them. An important object of ISO 25964 as a whole is to support data exchange and other forms of interoperability in circumstances in which more than one structured vocabulary is applied within one retrieval system or network. Sometimes one vocabulary has to be mapped to another, and it is important to understand both the potential and the limitations of such mappings. In other systems, a thesaurus is mapped to a classification scheme, or an ontology to a thesaurus. Comprehensive interoperability needs to cover the whole range of vocabulary types, whether young or old. Concepts in different vocabularies are related only in that they have the same or similar meaning. However, the meaning can be found in a number of different aspects within each particular type of structured vocabulary: - within terms or captions selected in different languages; - in the notation assigned indicating a place within a larger hierarchy; - in the definition, scope notes, history notes and other notes that explain the significance of that concept; and - in explicit relationships to other concepts or entities within the same vocabulary. In order to create mappings from one structured vocabulary to another it is first necessary to understand, within the context of each different type of structured vocabulary, the significance and relative importance of each of the different elements in defining the meaning of that particular concept. ISO 25964-1 describes the key characteristics of thesauri along with additional advice on best practice. ISO 25964-2 focuses on other types of vocabulary and does not attempt to cover all aspects of good practice. It concentrates on those aspects which need to be understood if one of the vocabularies is to work effectively alongside one or more of the others. Recognizing that a new standard cannot be applied to some existing vocabularies, this part of ISO 25964 provides informative description alongside the recommendations, the aim of which is to enable users and system developers to interpret and implement the existing vocabularies effectively. The remainder of ISO 25964-2 deals with the principles and practicalities of establishing mappings between vocabularies.

0.00164069 = product of:
  0.01312552 = sum of:
    0.01312552 = product of:
      0.02625104 = sum of:
        0.02625104 = weight(_text_:22 in 1670) [ClassicSimilarity], result of:
          0.02625104 = score(doc=1670,freq=2.0), product of:
            0.13569894 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03875087 = queryNorm
            0.19345059 = fieldWeight in 1670, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1670)
      0.5 = coord(1/2)
  0.125 = coord(1/8)

Date

26. 9.2006 21:00:22