Search (4 results, page 1 of 1)

0.0641097 = product of:
  0.14958929 = sum of:
    0.022337925 = weight(_text_:world in 1956) [ClassicSimilarity], result of:
      0.022337925 = score(doc=1956,freq=2.0), product of:
        0.13150178 = queryWeight, product of:
          3.8436708 = idf(docFreq=2573, maxDocs=44218)
          0.03421255 = queryNorm
        0.16986786 = fieldWeight in 1956, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.8436708 = idf(docFreq=2573, maxDocs=44218)
          0.03125 = fieldNorm(doc=1956)
    0.029682916 = weight(_text_:wide in 1956) [ClassicSimilarity], result of:
      0.029682916 = score(doc=1956,freq=2.0), product of:
        0.15158753 = queryWeight, product of:
          4.4307585 = idf(docFreq=1430, maxDocs=44218)
          0.03421255 = queryNorm
        0.1958137 = fieldWeight in 1956, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.4307585 = idf(docFreq=1430, maxDocs=44218)
          0.03125 = fieldNorm(doc=1956)
    0.022773797 = weight(_text_:web in 1956) [ClassicSimilarity], result of:
      0.022773797 = score(doc=1956,freq=4.0), product of:
        0.11165301 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03421255 = queryNorm
        0.2039694 = fieldWeight in 1956, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03125 = fieldNorm(doc=1956)
    0.022337925 = weight(_text_:world in 1956) [ClassicSimilarity], result of:
      0.022337925 = score(doc=1956,freq=2.0), product of:
        0.13150178 = queryWeight, product of:
          3.8436708 = idf(docFreq=2573, maxDocs=44218)
          0.03421255 = queryNorm
        0.16986786 = fieldWeight in 1956, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.8436708 = idf(docFreq=2573, maxDocs=44218)
          0.03125 = fieldNorm(doc=1956)
    0.029682916 = weight(_text_:wide in 1956) [ClassicSimilarity], result of:
      0.029682916 = score(doc=1956,freq=2.0), product of:
        0.15158753 = queryWeight, product of:
          4.4307585 = idf(docFreq=1430, maxDocs=44218)
          0.03421255 = queryNorm
        0.1958137 = fieldWeight in 1956, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.4307585 = idf(docFreq=1430, maxDocs=44218)
          0.03125 = fieldNorm(doc=1956)
    0.022773797 = weight(_text_:web in 1956) [ClassicSimilarity], result of:
      0.022773797 = score(doc=1956,freq=4.0), product of:
        0.11165301 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03421255 = queryNorm
        0.2039694 = fieldWeight in 1956, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03125 = fieldNorm(doc=1956)
  0.42857143 = coord(6/14)

Abstract

Things change. Words change, meaning changes and use changes both words and meaning. In information access systems this means concept schemes such as thesauri or classification schemes change. They always have. Concept schemes that have survived have evolved over time, moving from one version, often called an edition, to the next. If we want to manage how words and meanings - and as a consequence use - change in an effective manner, and if we want to be able to search across versions of concept schemes, we have to track these changes. This paper explores how we might expand SKOS, a World Wide Web Consortium (W3C) draft recommendation in order to do that kind of tracking. The Simple Knowledge Organization System (SKOS) Core Guide is sponsored by the Semantic Web Best Practices and Deployment Working Group. The second draft, edited by Alistair Miles and Dan Brickley, was issued in November 2005. SKOS is a "model for expressing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, folksonomies, other types of controlled vocabulary and also concept schemes embedded in glossaries and terminologies" in RDF. How SKOS handles version in concept schemes is an open issue. The current draft guide suggests using OWL and DCTERMS as mechanisms for concept scheme revision. As it stands an editor of a concept scheme can make notes or declare in OWL that more than one version exists. This paper adds to the SKOS Core by introducing a tracking system for changes in concept schemes. We call this tracking system vocabulary ontogeny. Ontogeny is a biological term for the development of an organism during its lifetime. Here we use the ontogeny metaphor to describe how vocabularies change over their lifetime. Our purpose here is to create a conceptual mechanism that will track these changes and in so doing enhance information retrieval and prevent document loss through versioning, thereby enabling persistent retrieval.

0.020576308 = product of:
  0.14403415 = sum of:
    0.07201707 = weight(_text_:web in 4939) [ClassicSimilarity], result of:
      0.07201707 = score(doc=4939,freq=10.0), product of:
        0.11165301 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03421255 = queryNorm
        0.6450079 = fieldWeight in 4939, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0625 = fieldNorm(doc=4939)
    0.07201707 = weight(_text_:web in 4939) [ClassicSimilarity], result of:
      0.07201707 = score(doc=4939,freq=10.0), product of:
        0.11165301 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03421255 = queryNorm
        0.6450079 = fieldWeight in 4939, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0625 = fieldNorm(doc=4939)
  0.14285715 = coord(2/14)

Abstract

This paper describes a conceptual framework and methodology for managing scheme versioning for the Semantic Web. The first part of the paper introduces the concept of vocabulary encoding schemes, distinguished from metadata schemas, and discusses the characteristics of changes in schemes. The paper then presents a proposal to use a value record-similar to a term record in thesaurus management techniques-to manage scheme versioning challenges for the Semantic Web. The conclusion identifies future research directions.

Footnote

Simultaneously published as Knitting the Semantic Web

Theme

Semantic Web

0.009760199 = product of:
  0.06832139 = sum of:
    0.034160696 = weight(_text_:web in 1337) [ClassicSimilarity], result of:
      0.034160696 = score(doc=1337,freq=4.0), product of:
        0.11165301 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03421255 = queryNorm
        0.3059541 = fieldWeight in 1337, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.046875 = fieldNorm(doc=1337)
    0.034160696 = weight(_text_:web in 1337) [ClassicSimilarity], result of:
      0.034160696 = score(doc=1337,freq=4.0), product of:
        0.11165301 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03421255 = queryNorm
        0.3059541 = fieldWeight in 1337, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.046875 = fieldNorm(doc=1337)
  0.14285715 = coord(2/14)

Abstract

In this article, we describe the development of an extension to the Simple Knowledge Organization System (SKOS) to accommodate the needs of vocabulary development applications (VDA) managing metadata schemes and requiring close tracking of change to both those schemes and their member concepts. We take a neopragmatic epistemic stance in asserting the need for an entity in SKOS modeling to mediate between the abstract concept and the concrete scheme. While the SKOS model sufficiently describes entities for modeling the current state of a scheme in support of indexing and search on the Semantic Web, it lacks the expressive power to serve the needs of VDA needing to maintain scheme historical continuity. We demonstrate preliminarily that conceptualizations drawn from empirical work in modeling entities in the bibliographic universe, such as works, texts, and exemplars, can provide the basis for SKOS extension in ways that support more rigorous demands of capturing concept evolution in VDA.

Theme

Semantic Web

0.0092020035 = product of:
  0.064414024 = sum of:
    0.032207012 = weight(_text_:web in 2638) [ClassicSimilarity], result of:
      0.032207012 = score(doc=2638,freq=2.0), product of:
        0.11165301 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03421255 = queryNorm
        0.2884563 = fieldWeight in 2638, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0625 = fieldNorm(doc=2638)
    0.032207012 = weight(_text_:web in 2638) [ClassicSimilarity], result of:
      0.032207012 = score(doc=2638,freq=2.0), product of:
        0.11165301 = queryWeight, product of:
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.03421255 = queryNorm
        0.2884563 = fieldWeight in 2638, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2635105 = idf(docFreq=4597, maxDocs=44218)
          0.0625 = fieldNorm(doc=2638)
  0.14285715 = coord(2/14)