Search (6 results, page 1 of 1)

  • × author_ss:"Panzer, M."
  1. Green, R.; Panzer, M.: Relations in the notational hierarchy of the Dewey Decimal Classification (2011) 0.03 
    0.027574293 = product of:
  0.055148587 = sum of:
    0.055148587 = product of:
      0.11029717 = sum of:
        0.11029717 = weight(_text_:2011 in 4823) [ClassicSimilarity], result of:
          0.11029717 = score(doc=4823,freq=5.0), product of:
            0.25410342 = queryWeight, product of:
              4.9694557 = idf(docFreq=834, maxDocs=44218)
              0.051133048 = queryNorm
            0.4340641 = fieldWeight in 4823, product of:
              2.236068 = tf(freq=5.0), with freq of:
                5.0 = termFreq=5.0
              4.9694557 = idf(docFreq=834, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4823)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Source
    Classification and ontology: formal approaches and access to knowledge: proceedings of the International UDC Seminar, 19-20 September 2011, The Hague, The Netherlands. Eds.: A. Slavic u. E. Civallero
    Year
    2011
  2. Baker, T.; Bermès, E.; Coyle, K.; Dunsire, G.; Isaac, A.; Murray, P.; Panzer, M.; Schneider, J.; Singer, R.; Summers, E.; Waites, W.; Young, J.; Zeng, M.: Library Linked Data Incubator Group Final Report (2011) 0.03 
    0.026101073 = product of:
  0.052202147 = sum of:
    0.052202147 = product of:
      0.10440429 = sum of:
        0.10440429 = weight(_text_:2011 in 4796) [ClassicSimilarity], result of:
          0.10440429 = score(doc=4796,freq=7.0), product of:
            0.25410342 = queryWeight, product of:
              4.9694557 = idf(docFreq=834, maxDocs=44218)
              0.051133048 = queryNorm
            0.41087323 = fieldWeight in 4796, product of:
              2.6457512 = tf(freq=7.0), with freq of:
                7.0 = termFreq=7.0
              4.9694557 = idf(docFreq=834, maxDocs=44218)
              0.03125 = fieldNorm(doc=4796)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    The mission of the W3C Library Linked Data Incubator Group, chartered from May 2010 through August 2011, has been "to help increase global interoperability of library data on the Web, by bringing together people involved in Semantic Web activities - focusing on Linked Data - in the library community and beyond, building on existing initiatives, and identifying collaboration tracks for the future." In Linked Data [LINKEDDATA], data is expressed using standards such as Resource Description Framework (RDF) [RDF], which specifies relationships between things, and Uniform Resource Identifiers (URIs, or "Web addresses") [URI]. This final report of the Incubator Group examines how Semantic Web standards and Linked Data principles can be used to make the valuable information assets that library create and curate - resources such as bibliographic data, authorities, and concept schemes - more visible and re-usable outside of their original library context on the wider Web. The Incubator Group began by eliciting reports on relevant activities from parties ranging from small, independent projects to national library initiatives (see the separate report, Library Linked Data Incubator Group: Use Cases) [USECASE]. These use cases provided the starting point for the work summarized in the report: an analysis of the benefits of library Linked Data, a discussion of current issues with regard to traditional library data, existing library Linked Data initiatives, and legal rights over library data; and recommendations for next steps. The report also summarizes the results of a survey of current Linked Data technologies and an inventory of library Linked Data resources available today (see also the more detailed report, Library Linked Data Incubator Group: Datasets, Value Vocabularies, and Metadata Element Sets) [VOCABDATASET].
    Issue
    W3C Incubator Group Report 25 October 2011.
    Year
    2011
  3. Panzer, M.: Two tales of a concept : aligning FRSAD with SKOS (2011) 0.03 
    0.025630746 = product of:
  0.051261492 = sum of:
    0.051261492 = product of:
      0.102522984 = sum of:
        0.102522984 = weight(_text_:2011 in 4789) [ClassicSimilarity], result of:
          0.102522984 = score(doc=4789,freq=3.0), product of:
            0.25410342 = queryWeight, product of:
              4.9694557 = idf(docFreq=834, maxDocs=44218)
              0.051133048 = queryNorm
            0.4034695 = fieldWeight in 4789, product of:
              1.7320508 = tf(freq=3.0), with freq of:
                3.0 = termFreq=3.0
              4.9694557 = idf(docFreq=834, maxDocs=44218)
              0.046875 = fieldNorm(doc=4789)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Year
    2011
  4. Panzer, M.: Cool URIs for the DDC : towards Web-scale accessibility of a large classification system (2008) 0.01 
    0.0138556445 = product of:
  0.027711289 = sum of:
    0.027711289 = product of:
      0.055422578 = sum of:
        0.055422578 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
          0.055422578 = score(doc=2629,freq=2.0), product of:
            0.17905922 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133048 = 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.5 = coord(1/2)
    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
  5. Panzer, M.: Designing identifiers for the DDC (2007) 0.01 
    0.0116183115 = product of:
  0.023236623 = sum of:
    0.023236623 = product of:
      0.046473246 = sum of:
        0.046473246 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
          0.046473246 = score(doc=1752,freq=10.0), product of:
            0.17905922 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133048 = 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.5 = coord(1/2)
    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?"
  6. Panzer, M.: Dewey: how to make it work for you (2013) 0.01 
    0.008659778 = product of:
  0.017319556 = sum of:
    0.017319556 = product of:
      0.034639113 = sum of:
        0.034639113 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
          0.034639113 = score(doc=5797,freq=2.0), product of:
            0.17905922 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133048 = 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.5 = coord(1/2)
    Source
    Knowledge quest. 42(2013) no.2, S.22-29

Authors

Years

Types

Themes