Document (#33753)

Author
Panzer, M.
Title
Designing identifiers for the DDC
Source
025.431: The Dewey blog: September 04, 2007
Year
2007
Content
"Although the Dewey Decimal Classification is currently available on the web to subscribers as WebDewey and Abridged WebDewey in the OCLC Connexion service and in an XML version to licensees, OCLC does not provide any "web services" based on the DDC. By web services, we mean presentation of the DDC to other machines (not humans) for uses such as searching, browsing, classifying, mapping, harvesting, and alerting. In order to build web-accessible services based on the DDC, several elements have to be considered. One of these elements is the design of an appropriate Uniform Resource Identifier (URI) structure for Dewey. The design goals of mapping the entity model of the DDC into an identifier space can be summarized as follows: * Common locator for Dewey concepts and associated resources for use in web services and web applications * Use-case-driven, but not directly related to and outlasting a specific use case (persistency) * Retraceable path to a concept rather than an abstract identification, reusing a means of identification that is already present in the DDC and available in existing metadata. We have been working closely with our colleagues in the OCLC Office of Research (especially Andy Houghton as well as Eric Childress, Diane Vizine-Goetz, and Stu Weibel) on a preliminary identifier syntax. The basic identifier format we are currently exploring is: http://dewey.info/{aspect}/{object}/{locale}/{type}/{version}/{resource} where * {aspect} is the aspect associated with an {object}-the current value set of aspect contains "concept", "scheme", and "index"; additional ones are under exploration * {object} is a type of {aspect} * {locale} identifies a Dewey translation * {type} identifies a Dewey edition type and contains, at a minimum, the values "edn" for the full edition or "abr" for the abridged edition * {version} identifies a Dewey edition version * {resource} identifies a resource associated with an {object} in the context of {locale}, {type}, and {version}
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?"
Footnote
Vgl.: http://ddc.typepad.com/025431/2007/09/designing-ident.html.
Object
DDC

Similar documents (author)

  1. Panzer, M.: From heteroglossiato polyglottism : Multilingual MelvilClass (2008) 5.35
    5.3508706 = sum of:
      5.3508706 = weight(author_txt:panzer in 5764) [ClassicSimilarity], result of:
        5.3508706 = fieldWeight in 5764, product of:
          1.0 = tf(freq=1.0), with freq of:
            1.0 = termFreq=1.0
          8.561393 = idf(docFreq=22, maxDocs=44218)
          0.625 = fieldNorm(doc=5764)
    
  2. Panzer, M.: Dewey Web services : overview (2009) 5.35
    5.3508706 = sum of:
      5.3508706 = weight(author_txt:panzer in 7190) [ClassicSimilarity], result of:
        5.3508706 = fieldWeight in 7190, product of:
          1.0 = tf(freq=1.0), with freq of:
            1.0 = termFreq=1.0
          8.561393 = idf(docFreq=22, maxDocs=44218)
          0.625 = fieldNorm(doc=7190)
    
  3. Panzer, M.: Ontological representation of the DDC : Brainstorming, May 6th 2008 (2008) 5.35
    5.3508706 = sum of:
      5.3508706 = weight(author_txt:panzer in 2465) [ClassicSimilarity], result of:
        5.3508706 = fieldWeight in 2465, product of:
          1.0 = tf(freq=1.0), with freq of:
            1.0 = termFreq=1.0
          8.561393 = idf(docFreq=22, maxDocs=44218)
          0.625 = fieldNorm(doc=2465)
    
  4. Panzer, M.: DDC, SKOS, and linked data on the Web (2008) 5.35
    5.3508706 = sum of:
      5.3508706 = weight(author_txt:panzer in 4478) [ClassicSimilarity], result of:
        5.3508706 = fieldWeight in 4478, product of:
          1.0 = tf(freq=1.0), with freq of:
            1.0 = termFreq=1.0
          8.561393 = idf(docFreq=22, maxDocs=44218)
          0.625 = fieldNorm(doc=4478)
    
  5. Panzer, M.: Taxonomies as resources identification, location and access of a »Webified« Dewey (2008) 5.35
    5.3508706 = sum of:
      5.3508706 = weight(author_txt:panzer in 5471) [ClassicSimilarity], result of:
        5.3508706 = fieldWeight in 5471, product of:
          1.0 = tf(freq=1.0), with freq of:
            1.0 = termFreq=1.0
          8.561393 = idf(docFreq=22, maxDocs=44218)
          0.625 = fieldNorm(doc=5471)
    

Similar documents (content)

  1. Tillett, B.B.: Numbers to identify entities (ISADN's-International Standard Authority Data Numbers) (2007) 0.66
    0.6593443 = sum of:
      0.6593443 = product of:
        1.3186886 = sum of:
          1.3186886 = weight(abstract_txt:identifiers in 792) [ClassicSimilarity], result of:
            1.3186886 = score(doc=792,freq=4.0), product of:
              0.8154248 = queryWeight, product of:
                1.1868724 = boost
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.092932925 = queryNorm
              1.6171799 = fieldWeight in 792, product of:
                2.0 = tf(freq=4.0), with freq of:
                  4.0 = termFreq=4.0
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.109375 = fieldNorm(doc=792)
        0.5 = coord(1/2)
    
  2. Lynch, C.: Identifiers and their role in networked information applications (1998) 0.57
    0.5710089 = sum of:
      0.5710089 = product of:
        1.1420178 = sum of:
          1.1420178 = weight(abstract_txt:identifiers in 1768) [ClassicSimilarity], result of:
            1.1420178 = score(doc=1768,freq=3.0), product of:
              0.8154248 = queryWeight, product of:
                1.1868724 = boost
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.092932925 = queryNorm
              1.4005189 = fieldWeight in 1768, product of:
                1.7320508 = tf(freq=3.0), with freq of:
                  3.0 = termFreq=3.0
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.109375 = fieldNorm(doc=1768)
        0.5 = coord(1/2)
    
  3. Serra, L.G.; Schneider, J.A.; Santarém Segundo, J.E.: Person identifiers in MARC 21 records in a semantic environment (2020) 0.49
    0.48943618 = sum of:
      0.48943618 = product of:
        0.97887236 = sum of:
          0.97887236 = weight(abstract_txt:identifiers in 127) [ClassicSimilarity], result of:
            0.97887236 = score(doc=127,freq=3.0), product of:
              0.8154248 = queryWeight, product of:
                1.1868724 = boost
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.092932925 = queryNorm
              1.2004447 = fieldWeight in 127, product of:
                1.7320508 = tf(freq=3.0), with freq of:
                  3.0 = termFreq=3.0
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.09375 = fieldNorm(doc=127)
        0.5 = coord(1/2)
    
  4. Lee, H.; Park, Z.: FRBRizing bibliographic records focusing on identifiers and role indicators in the Korean cataloging environment (2012) 0.47
    0.4709602 = sum of:
      0.4709602 = product of:
        0.9419204 = sum of:
          0.9419204 = weight(abstract_txt:identifiers in 1927) [ClassicSimilarity], result of:
            0.9419204 = score(doc=1927,freq=4.0), product of:
              0.8154248 = queryWeight, product of:
                1.1868724 = boost
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.092932925 = queryNorm
              1.1551285 = fieldWeight in 1927, product of:
                2.0 = tf(freq=4.0), with freq of:
                  4.0 = termFreq=4.0
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.078125 = fieldNorm(doc=1927)
        0.5 = coord(1/2)
    
  5. Beynon-Davies, P.: Form-ing institutional order : the scaffolding of lists and identifiers (2016) 0.41
    0.4078635 = sum of:
      0.4078635 = product of:
        0.815727 = sum of:
          0.815727 = weight(abstract_txt:identifiers in 3156) [ClassicSimilarity], result of:
            0.815727 = score(doc=3156,freq=3.0), product of:
              0.8154248 = queryWeight, product of:
                1.1868724 = boost
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.092932925 = queryNorm
              1.0003706 = fieldWeight in 3156, product of:
                1.7320508 = tf(freq=3.0), with freq of:
                  3.0 = termFreq=3.0
                7.3928223 = idf(docFreq=73, maxDocs=44218)
                0.078125 = fieldNorm(doc=3156)
        0.5 = coord(1/2)