Search (5 results, page 1 of 1)

0.017622467 = product of:
  0.1057348 = sum of:
    0.1057348 = weight(_text_:21st in 538) [ClassicSimilarity], result of:
      0.1057348 = score(doc=538,freq=2.0), product of:
        0.2381352 = queryWeight, product of:
          5.74105 = idf(docFreq=385, maxDocs=44218)
          0.041479383 = queryNorm
        0.44401163 = fieldWeight in 538, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.74105 = idf(docFreq=385, maxDocs=44218)
          0.0546875 = fieldNorm(doc=538)
  0.16666667 = coord(1/6)

Content

Präsentation während der Veranstaltung "Networked Knowledge Organization Systems and Services: The 6th European Networked Knowledge Organization Systems (NKOS) Workshop, Workshop at the 11th ECDL Conference, Budapest, Hungary, September 21st 2007".

0.014263492 = product of:
  0.08558095 = sum of:
    0.08558095 = sum of:
      0.05748153 = weight(_text_:century in 5797) [ClassicSimilarity], result of:
        0.05748153 = score(doc=5797,freq=2.0), product of:
          0.20775084 = queryWeight, product of:
            5.0085325 = idf(docFreq=802, maxDocs=44218)
            0.041479383 = queryNorm
          0.27668494 = fieldWeight in 5797, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.0085325 = idf(docFreq=802, maxDocs=44218)
            0.0390625 = fieldNorm(doc=5797)
      0.02809942 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
        0.02809942 = score(doc=5797,freq=2.0), product of:
          0.14525373 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.041479383 = queryNorm
          0.19345059 = fieldWeight in 5797, 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=5797)
  0.16666667 = coord(1/6)

Content

"As knowledge brokers, we are living in interesting times for libraries and librarians. We wonder sometimes if our traditional tools like the Dewey Decimal Classification (DDC) system can cope with the onslaught of information. The categories provided don't always seem adequate for the knowledge-discovery habits of today's patrons. They have grown accustomed to new ways for their information needs to be met, from the fire-and-forget style of a hard-to-control classic Google search to the pervasive, always-on style of Google Now, anticipating users' information needs without their having even asked a verbal question. Contrariwise, I believe that we, as librarians, could be making better use of our tools. Many (like the DDC) are a reflection of the same social and epistemological forces that brought about modernity at the turn of the last century. We as librarians are in the unique position of providing services that are as ground-breaking as these tools. As we see the need to provide unique and cutting-edge knowledge discovery to our users, I argue in this article that the DDC can play a key role in fulfilling this purpose."

Source

Knowledge quest. 42(2013) no.2, S.22-29

0.008264797 = product of:
  0.049588777 = sum of:
    0.049588777 = weight(_text_:history in 305) [ClassicSimilarity], result of:
      0.049588777 = score(doc=305,freq=2.0), product of:
        0.19296135 = queryWeight, product of:
          4.6519823 = idf(docFreq=1146, maxDocs=44218)
          0.041479383 = queryNorm
        0.25698814 = fieldWeight in 305, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.6519823 = idf(docFreq=1146, maxDocs=44218)
          0.0390625 = fieldNorm(doc=305)
  0.16666667 = coord(1/6)

Abstract

This paper explores the history, uses cases, and future plans associated with availability of the Dewey Decimal Classification (DDC) system as linked data. Parts of the Dewey Decimal Classification (DDC) system have been available as linked data since 2009. Initial efforts included the DDC Summaries (the top three levels of the DDC) in eleven languages exposed as linked data in dewey.info. In 2010, the content of dewey.info was further extended by the addition of assignable numbers and captions from the Abridged Edition 14 data files in English, Italian, and Vietnamese. During 2012, we will add assignable numbers and captions from the latest full edition database, DDC 23. In addition to the "old friends" of different Dewey language versions, institutions such as the British Library and Deutsche Nationalbibliothek have made use of Dewey linked data in bibliographic records and authority files, and AGROVOC has linked to our data at a general level. We expect to extend our linked data network shortly to "new acquaintances" such as GeoNames, ISO 639-3 language codes, and Mathematics Subject Classification. In particular, we will examine the linking process to GeoNames as an example of cross-domain vocabulary alignment. In addition to linking plans, we report on use cases that facilitate machine-assisted categorization and support discovery in the Semantic Web environment.

0.0037465894 = product of:
  0.022479536 = sum of:
    0.022479536 = product of:
      0.044959072 = sum of:
        0.044959072 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
          0.044959072 = score(doc=2629,freq=2.0), product of:
            0.14525373 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.041479383 = queryNorm
            0.30952093 = fieldWeight in 2629, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2629)
      0.5 = coord(1/2)
  0.16666667 = coord(1/6)

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.0031416109 = product of:
  0.018849665 = sum of:
    0.018849665 = product of:
      0.03769933 = sum of:
        0.03769933 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
          0.03769933 = score(doc=1752,freq=10.0), product of:
            0.14525373 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.041479383 = queryNorm
            0.2595412 = fieldWeight in 1752, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1752)
      0.5 = coord(1/2)
  0.16666667 = coord(1/6)

Content

Some examples of identifiers for concepts follow: <http://dewey.info/concept/338.4/en/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the English-language version of Edition 22. <http://dewey.info/concept/338.4/de/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the German-language version of Edition 22. <http://dewey.info/concept/333.7-333.9/> This identifier is used to retrieve or identify the 333.7-333.9 concept across all editions and language versions. <http://dewey.info/concept/333.7-333.9/about.skos> This identifier is used to retrieve a SKOS representation of the 333.7-333.9 concept (using the "resource" element). There are several open issues at this preliminary stage of development: Use cases: URIs need to represent the range of statements or questions that could be submitted to a Dewey web service. Therefore, it seems that some general questions have to be answered first: What information does an agent have when coming to a Dewey web service? What kind of questions will such an agent ask? Placement of the {locale} component: It is still an open question if the {locale} component should be placed after the {version} component instead (<http://dewey.info/concept/338.4/edn/22/en>) to emphasize that the most important instantiation of a Dewey class is its edition, not its language version. From a services point of view, however, it could make more sense to keep the current arrangement, because users are more likely to come to the service with a present understanding of the language version they are seeking without knowing the specifics of a certain edition in which they are trying to find topics. Identification of other Dewey entities: The goal is to create a locator that does not answer all, but a lot of questions that could be asked about the DDC. Which entities are missing but should be surfaced for services or user agents? How will those services or agents interact with them? Should some entities be rendered in a different way as presented? For example, (how) should the DDC Summaries be retrievable? Would it be necessary to make the DDC Manual accessible through this identifier structure?"