Search (5 results, page 1 of 1)

0.01678804 = product of:
  0.08394019 = sum of:
    0.08394019 = sum of:
      0.046302408 = weight(_text_:german in 1752) [ClassicSimilarity], result of:
        0.046302408 = score(doc=1752,freq=2.0), product of:
          0.24051933 = queryWeight, product of:
            5.808009 = idf(docFreq=360, maxDocs=44218)
            0.041411664 = queryNorm
          0.19251013 = fieldWeight in 1752, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.808009 = idf(docFreq=360, maxDocs=44218)
            0.0234375 = fieldNorm(doc=1752)
      0.037637785 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
        0.037637785 = score(doc=1752,freq=10.0), product of:
          0.1450166 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.041411664 = 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.2 = coord(1/5)

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

0.009260482 = product of:
  0.046302408 = sum of:
    0.046302408 = product of:
      0.092604816 = sum of:
        0.092604816 = weight(_text_:german in 2127) [ClassicSimilarity], result of:
          0.092604816 = score(doc=2127,freq=8.0), product of:
            0.24051933 = queryWeight, product of:
              5.808009 = idf(docFreq=360, maxDocs=44218)
              0.041411664 = queryNorm
            0.38502026 = fieldWeight in 2127, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              5.808009 = idf(docFreq=360, maxDocs=44218)
              0.0234375 = fieldNorm(doc=2127)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Content

What are those "other" relationships that Dewey possesses and that seem so important to surface? Firstly, there is the relationship of concepts to resources. Dewey has been used for a long time, and over 200,000 numbers are assigned to information resources each year and added to WorldCat by the Library of Congress and the German National Library alone. Secondly, we have relationships between concepts in the scheme itself. Dewey provides a rich set of non-hierarchical relations, indicating other relevant and related subjects across disciplinary boundaries. Thirdly, perhaps most importantly, there is the relationship between the same concepts across different languages. Dewey has been translated extensively, and current versions are available in French, German, Hebrew, Italian, Spanish, and Vietnamese. Briefer representations of the top-three levels (the DDC Summaries) are available in several languages in the DeweyBrowser. This multilingual nature of the scheme allows searchers to access a broader range of resources or to switch the language of--and thus localize--subject metadata seamlessly. MelvilClass, a Dewey front-end developed by the German National Library for the German translation, could be used as a common interface to the DDC in any language, as it is built upon the standard DDC data format. It is not hard to give an example of the basic terminology of a class pulled together in a multilingual way: <class/794.8> a skos:Concept ; skos:notation "794.8"^^ddc:notation ; skos:prefLabel "Computer games"@en ; skos:prefLabel "Computerspiele"@de ; skos:prefLabel "Jeux sur ordinateur"@fr ; skos:prefLabel "Juegos por computador"@es .

0.007717067 = product of:
  0.038585335 = sum of:
    0.038585335 = product of:
      0.07717067 = sum of:
        0.07717067 = weight(_text_:german in 4335) [ClassicSimilarity], result of:
          0.07717067 = score(doc=4335,freq=2.0), product of:
            0.24051933 = queryWeight, product of:
              5.808009 = idf(docFreq=360, maxDocs=44218)
              0.041411664 = queryNorm
            0.3208502 = fieldWeight in 4335, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.808009 = idf(docFreq=360, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4335)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Source

Kompatibilität, Medien und Ethik in der Wissensorganisation - Compatibility, Media and Ethics in Knowledge Organization: Proceedings der 10. Tagung der Deutschen Sektion der Internationalen Gesellschaft für Wissensorganisation Wien, 3.-5. Juli 2006 - Proceedings of the 10th Conference of the German Section of the International Society of Knowledge Organization Vienna, 3-5 July 2006. Ed.: H.P. Ohly, S. Netscher u. K. Mitgutsch

0.0044885674 = product of:
  0.022442836 = sum of:
    0.022442836 = product of:
      0.044885673 = sum of:
        0.044885673 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
          0.044885673 = score(doc=2629,freq=2.0), product of:
            0.1450166 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.041411664 = 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.2 = coord(1/5)

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.0028053545 = product of:
  0.014026772 = sum of:
    0.014026772 = product of:
      0.028053544 = sum of:
        0.028053544 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
          0.028053544 = score(doc=5797,freq=2.0), product of:
            0.1450166 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.041411664 = 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.5 = coord(1/2)
  0.2 = coord(1/5)

Source

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