Search (3 results, page 1 of 1)

0.026028758 = product of:
  0.052057516 = sum of:
    0.05064729 = weight(_text_:von in 3732) [ClassicSimilarity], result of:
      0.05064729 = score(doc=3732,freq=10.0), product of:
        0.12806706 = queryWeight, product of:
          2.6679487 = idf(docFreq=8340, maxDocs=44218)
          0.04800207 = queryNorm
        0.39547473 = fieldWeight in 3732, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          2.6679487 = idf(docFreq=8340, maxDocs=44218)
          0.046875 = fieldNorm(doc=3732)
    0.001410227 = product of:
      0.004230681 = sum of:
        0.004230681 = weight(_text_:a in 3732) [ClassicSimilarity], result of:
          0.004230681 = score(doc=3732,freq=2.0), product of:
            0.055348642 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.04800207 = queryNorm
            0.07643694 = fieldWeight in 3732, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=3732)
      0.33333334 = coord(1/3)
  0.5 = coord(2/4)

Abstract

Seit einiger Zeit stellen Bibliotheken ihre bibliografischen Metadadaten verstärkt offen in Form von Linked Data zur Verfügung. Dabei kommen jedoch ganz unterschiedliche Modelle für die Strukturierung der bibliografischen Daten zur Anwendung. Manche Bibliotheken verwenden ein auf FRBR basierendes Modell mit mehreren Schichten von Entitäten, während andere flache, am Datensatz orientierte Modelle nutzen. Der Wildwuchs bei den Datenmodellen erschwert die Nachnutzung der bibliografischen Daten. Im Ergebnis haben die Bibliotheken die früheren MARC-Silos nur mit zueinander inkompatiblen Linked-Data-Silos vertauscht. Deshalb ist es häufig schwierig, Datensets miteinander zu kombinieren und nachzunutzen. Kleinere Unterschiede in der Datenmodellierung lassen sich zwar durch Schema Mappings in den Griff bekommen, doch erscheint es fraglich, ob die Interoperabilität insgesamt zugenommen hat. Der Beitrag stellt die Ergebnisse einer Studie zu verschiedenen veröffentlichten Sets von bibliografischen Daten vor. Dabei werden auch die unterschiedlichen Modelle betrachtet, um bibliografische Daten als RDF darzustellen, sowie Werkzeuge zur Erzeugung von entsprechenden Daten aus dem MARC-Format. Abschließend wird der von der Finnischen Nationalbibliothek verfolgte Ansatz behandelt.

Type

a

9.97181E-4 = product of:
  0.003988724 = sum of:
    0.003988724 = product of:
      0.011966172 = sum of:
        0.011966172 = weight(_text_:a in 1323) [ClassicSimilarity], result of:
          0.011966172 = score(doc=1323,freq=16.0), product of:
            0.055348642 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.04800207 = queryNorm
            0.2161963 = fieldWeight in 1323, product of:
              4.0 = tf(freq=16.0), with freq of:
                16.0 = termFreq=16.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046875 = fieldNorm(doc=1323)
      0.33333334 = coord(1/3)
  0.25 = coord(1/4)

Abstract

Maintaining a library of digital objects of necessaryy requires maintaining metadata about those objects. The metadata necessary for successful management and use of digital objeets is both more extensive than and different from the metadata used for managing collections of printed works and other physical materials. While a library may record descriptive metadata regarding a book in its collection, the book will not dissolve into a series of unconnected pages if the library fails to record structural metadata regarding the book's organization, nor will scholars be unable to evaluate the book's worth if the library fails to note that the book was produced using a Ryobi offset press. The Same cannot be said for a digital version of the saure book. Without structural metadata, the page image or text files comprising the digital work are of little use, and without technical metadata regarding the digitization process, scholars may be unsure of how accurate a reflection of the original the digital version provides. For internal management purposes, a library must have access to appropriate technical metadata in order to periodically refresh and migrate the data, ensuring the durability of valuable resources.

9.19731E-4 = product of:
  0.003678924 = sum of:
    0.003678924 = product of:
      0.011036771 = sum of:
        0.011036771 = weight(_text_:a in 5896) [ClassicSimilarity], result of:
          0.011036771 = score(doc=5896,freq=10.0), product of:
            0.055348642 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.04800207 = queryNorm
            0.19940455 = fieldWeight in 5896, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5896)
      0.33333334 = coord(1/3)
  0.25 = coord(1/4)

Abstract

This paper proposes the use of the Unified Modeling Language (UML) as a language for modelling ontologies for Web resources and the knowledge contained within them. To provide a mechanism for serialising and processing object diagrams representing knowledge, a pair of XSI-T stylesheets have been developed to map from XML Metadata Interchange (XMI) encodings of class diagrams to corresponding RDF schemas and to Java classes representing the concepts in the ontologies. The Java code includes methods for marshalling and unmarshalling object-oriented information between in-memory data structures and RDF serialisations of that information. This provides a convenient mechanism for Java applications to share knowledge on the Web

Type

a