Search (553 results, page 1 of 28)

0.16856344 = sum of:
  0.13791059 = product of:
    0.41373175 = sum of:
      0.41373175 = weight(_text_:3a in 1826) [ClassicSimilarity], result of:
        0.41373175 = score(doc=1826,freq=2.0), product of:
          0.4416923 = queryWeight, product of:
            8.478011 = idf(docFreq=24, maxDocs=44218)
            0.052098576 = queryNorm
          0.93669677 = fieldWeight in 1826, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            8.478011 = idf(docFreq=24, maxDocs=44218)
            0.078125 = fieldNorm(doc=1826)
    0.33333334 = coord(1/3)
  0.030652853 = product of:
    0.061305705 = sum of:
      0.061305705 = weight(_text_:web in 1826) [ClassicSimilarity], result of:
        0.061305705 = score(doc=1826,freq=2.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.36057037 = fieldWeight in 1826, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.078125 = fieldNorm(doc=1826)
    0.5 = coord(1/2)

Source

http://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=5&ved=0CDQQFjAE&url=http%3A%2F%2Fdigbib.ubka.uni-karlsruhe.de%2Fvolltexte%2Fdocuments%2F3131107&ei=HzFWVYvGMsiNsgGTyoFI&usg=AFQjCNE2FHUeR9oQTQlNC4TPedv4Mo3DaQ&sig2=Rlzpr7a3BLZZkqZCXXN_IA&bvm=bv.93564037,d.bGg&cad=rja

0.092324466 = product of:
  0.18464893 = sum of:
    0.18464893 = sum of:
      0.08582799 = weight(_text_:web in 8365) [ClassicSimilarity], result of:
        0.08582799 = score(doc=8365,freq=2.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.50479853 = fieldWeight in 8365, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.109375 = fieldNorm(doc=8365)
      0.09882093 = weight(_text_:22 in 8365) [ClassicSimilarity], result of:
        0.09882093 = score(doc=8365,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.5416616 = fieldWeight in 8365, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.109375 = fieldNorm(doc=8365)
  0.5 = coord(1/2)

Date

22. 6.2015 16:08:38

0.092324466 = product of:
  0.18464893 = sum of:
    0.18464893 = sum of:
      0.08582799 = weight(_text_:web in 4643) [ClassicSimilarity], result of:
        0.08582799 = score(doc=4643,freq=2.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.50479853 = fieldWeight in 4643, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.109375 = fieldNorm(doc=4643)
      0.09882093 = weight(_text_:22 in 4643) [ClassicSimilarity], result of:
        0.09882093 = score(doc=4643,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.5416616 = fieldWeight in 4643, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.109375 = fieldNorm(doc=4643)
  0.5 = coord(1/2)

Date

22. 9.2007 15:41:14

Theme

Semantic Web

0.08558736 = product of:
  0.17117472 = sum of:
    0.17117472 = sum of:
      0.060689554 = weight(_text_:web in 1936) [ClassicSimilarity], result of:
        0.060689554 = score(doc=1936,freq=4.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.35694647 = fieldWeight in 1936, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0546875 = fieldNorm(doc=1936)
      0.11048517 = weight(_text_:22 in 1936) [ClassicSimilarity], result of:
        0.11048517 = score(doc=1936,freq=10.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.6055961 = fieldWeight in 1936, product of:
            3.1622777 = tf(freq=10.0), with freq of:
              10.0 = termFreq=10.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=1936)
  0.5 = coord(1/2)

Abstract

Dewey Decimal Classification and Relative Index, Edition 22 (DDC 22) will be issued simultaneously in print and web versions in July 2003. The new edition is the first full print update to the Dewey Decimal Classification system in seven years-it includes several significant updates and many new numbers and topics. DDC 22 also features some fundamental structural changes that have been introduced with the goals of promoting classifier efficiency and improving the DDC for use in a variety of applications in the web environment. Most importantly, the content of the new edition has been shaped by the needs and recommendations of Dewey users around the world. The worldwide user community has an important role in shaping the future of the DDC.

Object

DDC-22

0.08428172 = sum of:
  0.068955295 = product of:
    0.20686588 = sum of:
      0.20686588 = weight(_text_:3a in 4388) [ClassicSimilarity], result of:
        0.20686588 = score(doc=4388,freq=2.0), product of:
          0.4416923 = queryWeight, product of:
            8.478011 = idf(docFreq=24, maxDocs=44218)
            0.052098576 = queryNorm
          0.46834838 = fieldWeight in 4388, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            8.478011 = idf(docFreq=24, maxDocs=44218)
            0.0390625 = fieldNorm(doc=4388)
    0.33333334 = coord(1/3)
  0.015326426 = product of:
    0.030652853 = sum of:
      0.030652853 = weight(_text_:web in 4388) [ClassicSimilarity], result of:
        0.030652853 = score(doc=4388,freq=2.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.18028519 = fieldWeight in 4388, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0390625 = fieldNorm(doc=4388)
    0.5 = coord(1/2)

Footnote

Vgl. unter: https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=2ahUKEwizweHljdbcAhVS16QKHXcFD9QQFjABegQICRAB&url=https%3A%2F%2Fwww.researchgate.net%2Fpublication%2F271200105_Die_Autonomie_des_Menschen_und_der_Maschine_-_gegenwartige_Definitionen_von_Autonomie_zwischen_philosophischem_Hintergrund_und_technologischer_Umsetzbarkeit_Redigierte_Version_der_Magisterarbeit_Karls&usg=AOvVaw06orrdJmFF2xbCCp_hL26q.

0.08306804 = product of:
  0.16613609 = sum of:
    0.16613609 = sum of:
      0.10966698 = weight(_text_:web in 4331) [ClassicSimilarity], result of:
        0.10966698 = score(doc=4331,freq=10.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.6450079 = fieldWeight in 4331, 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=4331)
      0.056469105 = weight(_text_:22 in 4331) [ClassicSimilarity], result of:
        0.056469105 = score(doc=4331,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.30952093 = fieldWeight in 4331, 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=4331)
  0.5 = coord(1/2)

Abstract

Das Semantic Web - bzw. Linked Data - hat das Potenzial, die Verfügbarkeit von Daten und Wissen, sowie den Zugriff darauf zu revolutionieren. Einen großen Beitrag dazu können Wissensorganisationssysteme wie Thesauri leisten, die die Daten inhaltlich erschließen und strukturieren. Leider sind immer noch viele dieser Systeme lediglich in Buchform oder in speziellen Anwendungen verfügbar. Wie also lassen sie sich für das Semantic Web nutzen? Das Simple Knowledge Organization System (SKOS) bietet eine Möglichkeit, die Wissensorganisationssysteme in eine Form zu "übersetzen", die im Web zitiert und mit anderen Resourcen verknüpft werden kann.

Date

15. 3.2011 19:21:22

Theme

Semantic Web

0.08306804 = product of:
  0.16613609 = sum of:
    0.16613609 = sum of:
      0.10966698 = weight(_text_:web in 4685) [ClassicSimilarity], result of:
        0.10966698 = score(doc=4685,freq=10.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.6450079 = fieldWeight in 4685, 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=4685)
      0.056469105 = weight(_text_:22 in 4685) [ClassicSimilarity], result of:
        0.056469105 = score(doc=4685,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.30952093 = fieldWeight in 4685, 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=4685)
  0.5 = coord(1/2)

Abstract

This document contains and presents test cases for the Web Ontology Language (OWL) approved by the Web Ontology Working Group. Many of the test cases illustrate the correct usage of the Web Ontology Language (OWL), and the formal meaning of its constructs. Other test cases illustrate the resolution of issues considered by the Working Group. Conformance for OWL documents and OWL document checkers is specified.

Date

14. 8.2011 13:33:22

Theme

Semantic Web

0.07913525 = product of:
  0.1582705 = sum of:
    0.1582705 = sum of:
      0.07356684 = weight(_text_:web in 6048) [ClassicSimilarity], result of:
        0.07356684 = score(doc=6048,freq=2.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.43268442 = fieldWeight in 6048, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.09375 = fieldNorm(doc=6048)
      0.084703654 = weight(_text_:22 in 6048) [ClassicSimilarity], result of:
        0.084703654 = score(doc=6048,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.46428138 = fieldWeight in 6048, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.09375 = fieldNorm(doc=6048)
  0.5 = coord(1/2)

Date

22. 9.2007 15:41:14

Theme

Semantic Web

0.07913525 = product of:
  0.1582705 = sum of:
    0.1582705 = sum of:
      0.07356684 = weight(_text_:web in 100) [ClassicSimilarity], result of:
        0.07356684 = score(doc=100,freq=2.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.43268442 = fieldWeight in 100, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.09375 = fieldNorm(doc=100)
      0.084703654 = weight(_text_:22 in 100) [ClassicSimilarity], result of:
        0.084703654 = score(doc=100,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.46428138 = fieldWeight in 100, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.09375 = fieldNorm(doc=100)
  0.5 = coord(1/2)

Date

22. 9.2007 15:41:14

Theme

Semantic Web

0.07726393 = product of:
  0.15452786 = sum of:
    0.15452786 = sum of:
      0.10511739 = weight(_text_:web in 6122) [ClassicSimilarity], result of:
        0.10511739 = score(doc=6122,freq=12.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.6182494 = fieldWeight in 6122, product of:
            3.4641016 = tf(freq=12.0), with freq of:
              12.0 = termFreq=12.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0546875 = fieldNorm(doc=6122)
      0.049410466 = weight(_text_:22 in 6122) [ClassicSimilarity], result of:
        0.049410466 = score(doc=6122,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.2708308 = fieldWeight in 6122, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=6122)
  0.5 = coord(1/2)

Abstract

Noch ist nicht entschieden mit welcher Vehemenz das sogenannte Web 2.0 die Bibliotheken verändern wird. Allerdings wird hier und da bereits mit Bezugnahme auf das sogenannte Semantic Web von einer dritten und mancherorts von einer vierten Generation des Web gesprochen. Der Vortrag hinterfragt kritisch, welche Konzepte sich hinter diesen Bezeichnungen verbergen und geht der Frage nach, welche Herausforderungen eine Übernahme dieser Konzepte für die Bibliothekswelt mit sich bringen würde. Vgl. insbes. Folie 22 mit einer Darstellung von der Entwicklung vom Web 1.0 zum Web 4.0

Object

Web 2.0

0.07726393 = product of:
  0.15452786 = sum of:
    0.15452786 = sum of:
      0.10511739 = weight(_text_:web in 4330) [ClassicSimilarity], result of:
        0.10511739 = score(doc=4330,freq=12.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.6182494 = fieldWeight in 4330, product of:
            3.4641016 = tf(freq=12.0), with freq of:
              12.0 = termFreq=12.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0546875 = fieldNorm(doc=4330)
      0.049410466 = weight(_text_:22 in 4330) [ClassicSimilarity], result of:
        0.049410466 = score(doc=4330,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.2708308 = fieldWeight in 4330, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=4330)
  0.5 = coord(1/2)

Abstract

One vision of the Semantic Web is that it will be much like the Web we know today, except that documents will be enriched by annotations in machine understandable markup. These annotations will provide metadata about the documents as well as machine interpretable statements capturing some of the meaning of document content. We discuss how the information retrieval paradigm might be recast in such an environment. We suggest that retrieval can be tightly bound to inference. Doing so makes today's Web search engines useful to Semantic Web inference engines, and causes improvements in either retrieval or inference to lead directly to improvements in the other.

Date

12. 2.2011 17:35:22

Theme

Semantic Web

0.07635105 = product of:
  0.1527021 = sum of:
    0.1527021 = sum of:
      0.110350266 = weight(_text_:web in 4649) [ClassicSimilarity], result of:
        0.110350266 = score(doc=4649,freq=18.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.64902663 = fieldWeight in 4649, product of:
            4.2426405 = tf(freq=18.0), with freq of:
              18.0 = termFreq=18.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.046875 = fieldNorm(doc=4649)
      0.042351827 = weight(_text_:22 in 4649) [ClassicSimilarity], result of:
        0.042351827 = score(doc=4649,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.23214069 = fieldWeight in 4649, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=4649)
  0.5 = coord(1/2)

Abstract

More and more cultural heritage institutions publish their collections, vocabularies and metadata on the Web. The resulting Web of linked cultural data opens up exciting new possibilities for searching and browsing through these cultural heritage collections. We report on ongoing work in which we investigate the estimation of relevance in this Web of Culture. We study existing measures of semantic distance and how they apply to two use cases. The use cases relate to the structured, multilingual and multimodal nature of the Culture Web. We distinguish between measures using the Web, such as Google distance and PMI, and measures using the Linked Data Web, i.e. the semantic structure of metadata vocabularies. We perform a small study in which we compare these semantic distance measures to human judgements of relevance. Although it is too early to draw any definitive conclusions, the study provides new insights into the applicability of semantic distance measures to the Web of Culture, and clear starting points for further research.

Date

26.12.2011 13:40:22

Theme

Semantic Web

0.0629143 = product of:
  0.1258286 = sum of:
    0.1258286 = sum of:
      0.06935949 = weight(_text_:web in 3478) [ClassicSimilarity], result of:
        0.06935949 = score(doc=3478,freq=4.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.4079388 = fieldWeight in 3478, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0625 = fieldNorm(doc=3478)
      0.056469105 = weight(_text_:22 in 3478) [ClassicSimilarity], result of:
        0.056469105 = score(doc=3478,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.30952093 = fieldWeight in 3478, 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=3478)
  0.5 = coord(1/2)

Abstract

Web 2.0 in just under 5 minutes.

Date

5. 1.2008 19:22:48

0.0629143 = product of:
  0.1258286 = sum of:
    0.1258286 = sum of:
      0.06935949 = weight(_text_:web in 1679) [ClassicSimilarity], result of:
        0.06935949 = score(doc=1679,freq=4.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.4079388 = fieldWeight in 1679, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0625 = fieldNorm(doc=1679)
      0.056469105 = weight(_text_:22 in 1679) [ClassicSimilarity], result of:
        0.056469105 = score(doc=1679,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.30952093 = fieldWeight in 1679, 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=1679)
  0.5 = coord(1/2)

Abstract

Durch den neuen Erschließungsstandard "Resource Description and Access" (RDA) lassen sich bibliografische Daten sowie Normdaten Semantic-Web-konform repräsentieren. Der Vortrag soll aufzeigen, welche Auswirkungen RDA auf die Katalogisierung in Bibliotheken und den Zugang zu den erschlossenen Ressourcen im Semantic Web hat. Anhand erster Erfahrungen aus praktischen Umsetzungen wird erläutert, wie bibliografische Daten durch RDA und Linked-Data-Technologien besser zugänglich gemacht und vor allem nachgenutzt werden können.

Date

13. 2.2011 20:22:23

0.061869845 = product of:
  0.12373969 = sum of:
    0.12373969 = sum of:
      0.07432922 = weight(_text_:web in 759) [ClassicSimilarity], result of:
        0.07432922 = score(doc=759,freq=6.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.43716836 = fieldWeight in 759, product of:
            2.4494898 = tf(freq=6.0), with freq of:
              6.0 = termFreq=6.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0546875 = fieldNorm(doc=759)
      0.049410466 = weight(_text_:22 in 759) [ClassicSimilarity], result of:
        0.049410466 = score(doc=759,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.2708308 = fieldWeight in 759, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=759)
  0.5 = coord(1/2)

Abstract

XML will have a profound impact on the way data is exchanged on the Internet. An important feature of this language is the separation of content from presentation, which makes it easier to select and/or reformat the data. However, due to the likelihood of numerous industry and domain specific DTDs, those who wish to integrate information will still be faced with the problem of semantic interoperability. In this paper we discuss why this problem is not solved by XML, and then discuss why the Resource Description Framework is only a partial solution. We then present the SHOE language, which we feel has many of the features necessary to enable a semantic web, and describe an existing set of tools that make it easy to use the language.

Date

11. 5.2013 19:22:18

Theme

Semantic Web

0.055164233 = product of:
  0.110328466 = sum of:
    0.110328466 = product of:
      0.3309854 = sum of:
        0.3309854 = weight(_text_:3a in 230) [ClassicSimilarity], result of:
          0.3309854 = score(doc=230,freq=2.0), product of:
            0.4416923 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.052098576 = queryNorm
            0.7493574 = fieldWeight in 230, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.0625 = fieldNorm(doc=230)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)

Source

https%3A%2F%2Ftannerlectures.utah.edu%2F_documents%2Fa-to-z%2Fp%2Fpopper80.pdf&usg=AOvVaw3f4QRTEH-OEBmoYr2J_c7H

0.055050008 = product of:
  0.110100016 = sum of:
    0.110100016 = sum of:
      0.060689554 = weight(_text_:web in 40) [ClassicSimilarity], result of:
        0.060689554 = score(doc=40,freq=4.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.35694647 = fieldWeight in 40, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0546875 = fieldNorm(doc=40)
      0.049410466 = weight(_text_:22 in 40) [ClassicSimilarity], result of:
        0.049410466 = score(doc=40,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.2708308 = fieldWeight in 40, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0546875 = fieldNorm(doc=40)
  0.5 = coord(1/2)

Abstract

Conclusion There is a reason why Google Scholar and Web of Science/Scopus are kings of the hills in their various arenas. They have strong brand recogniton, a head start in development and a mass of eyeballs and users that leads to an almost virtious cycle of improvement. Competing against such well established competitors is not easy even when one has deep pockets (Microsoft) or a killer idea (scite). It will be interesting to see how the landscape will look like in 2030. Stay tuned for part II where I review each particular index.

Date

17.11.2020 12:22:59

Object

Web of Science

0.053031296 = product of:
  0.10606259 = sum of:
    0.10606259 = sum of:
      0.063710764 = weight(_text_:web in 2118) [ClassicSimilarity], result of:
        0.063710764 = score(doc=2118,freq=6.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.37471575 = fieldWeight in 2118, product of:
            2.4494898 = tf(freq=6.0), with freq of:
              6.0 = termFreq=6.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.046875 = fieldNorm(doc=2118)
      0.042351827 = weight(_text_:22 in 2118) [ClassicSimilarity], result of:
        0.042351827 = score(doc=2118,freq=2.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.23214069 = fieldWeight in 2118, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=2118)
  0.5 = coord(1/2)

Abstract

Während das Internet vor noch nicht allzu langer Zeit hauptsächlich ein weiteres Informationsmedium darstellte, so explodieren die technischen Möglichkeiten derzeit förmlich. Diese stärken nicht nur den gegenseitigen Austausch der Nutzer. Sie alle vermessen unsere täglichen Gewohnheiten - auf sehr vielfältige Art und Weise. Die Mechanismen, die das gekaufte Web ausmachen, werden hierdurch komplexer. In den meisten neuen Technologien und Anwendungen verbergen sich Wege, die Verbraucherverführung zu perfektionieren. Nicht wenige davon dürften zudem für die Politik und andere Interessensverbände von Bedeutung sein, als alternativer Kanal, um Wählergruppen und Unterstützer zu mobilisieren. Das nachfolgende Kapitel nennt die wichtigsten Trends der nächsten Jahre, mitsamt ihren möglichen manipulativen Auswirkungen. Nur wenn wir beobachten, von wem die Zukunftstechniken wie genutzt werden, können wir kommerziellen Auswüchsen vorbeugen.

Content

Mit Verweis auf das Buch: Firnkes, M.: Das gekaufte Web: wie wir online manipuliert werden. Hannover : Heise Zeitschriften Verlag 2015. 220 S.

Date

5. 7.2015 22:02:31

Theme

Semantic Web

0.049685203 = product of:
  0.099370405 = sum of:
    0.099370405 = sum of:
      0.052019615 = weight(_text_:web in 1752) [ClassicSimilarity], result of:
        0.052019615 = score(doc=1752,freq=16.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.3059541 = fieldWeight in 1752, product of:
            4.0 = tf(freq=16.0), with freq of:
              16.0 = termFreq=16.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.0234375 = fieldNorm(doc=1752)
      0.047350787 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
        0.047350787 = score(doc=1752,freq=10.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = 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)

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

0.048338976 = product of:
  0.09667795 = sum of:
    0.09667795 = sum of:
      0.03678342 = weight(_text_:web in 1967) [ClassicSimilarity], result of:
        0.03678342 = score(doc=1967,freq=2.0), product of:
          0.17002425 = queryWeight, product of:
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.052098576 = queryNorm
          0.21634221 = fieldWeight in 1967, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.2635105 = idf(docFreq=4597, maxDocs=44218)
            0.046875 = fieldNorm(doc=1967)
      0.059894532 = weight(_text_:22 in 1967) [ClassicSimilarity], result of:
        0.059894532 = score(doc=1967,freq=4.0), product of:
          0.18244034 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.052098576 = queryNorm
          0.32829654 = fieldWeight in 1967, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046875 = fieldNorm(doc=1967)
  0.5 = coord(1/2)

Abstract

This paper reports on the second part of an initiative of the authors on researching classification systems with the conceptual model defined by the Functional Requirements for Subject Authority Data (FRSAD) final report. In an earlier study, the authors explored whether the FRSAD conceptual model could be extended beyond subject authority data to model classification data. The focus of the current study is to determine if classification data modeled using FRSAD can be used to solve real-world discovery problems in multicultural and multilingual contexts. The paper discusses the relationships between entities (same type or different types) in the context of classification systems that involve multiple translations and /or multicultural implementations. Results of two case studies are presented in detail: (a) two instances of the DDC (DDC 22 in English, and the Swedish-English mixed translation of DDC 22), and (b) Chinese Library Classification. The use cases of conceptual models in practice are also discussed.

Source

Beyond libraries - subject metadata in the digital environment and semantic web. IFLA Satellite Post-Conference, 17-18 August 2012, Tallinn