Search (6 results, page 1 of 1)

0.015701342 = product of:
  0.031402685 = sum of:
    0.031402685 = product of:
      0.06280537 = sum of:
        0.06280537 = weight(_text_:cataloging in 5478) [ClassicSimilarity], result of:
          0.06280537 = score(doc=5478,freq=4.0), product of:
            0.20397975 = queryWeight, product of:
              3.9411201 = idf(docFreq=2334, maxDocs=44218)
              0.051756795 = queryNorm
            0.3079 = fieldWeight in 5478, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.9411201 = idf(docFreq=2334, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5478)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This exploratory study examined Linked Data (LD) schemas/ontologies and data models proposed or in use by libraries around the world using MAchine Readable Cataloging (MARC) as a basis for comparison of the scope and extensibility of these potential new standards. The researchers selected 14 libraries from national libraries, academic libraries, government libraries, public libraries, multi-national libraries, and cultural heritage centers currently developing Library Linked Data (LLD) schemas. The choices of models, schemas, and elements used in each library's LD can create interoperability issues for LD services because of substantial differences between schemas and data models evolving via local decisions. The researchers observed that a wide variety of vocabularies and ontologies were used for LLD including common web schemas such as Dublin Core (DC)/DCTerms, Schema.org and Resource Description Framework (RDF), as well as deprecated schemas such as MarcOnt and rdagroup1elements. A sharp divide existed as well between LLD schemas using variations of the Functional Requirements for Bibliographic Records (FRBR) data model and those with different data models or even with no listed data model. Libraries worldwide are not using the same elements or even the same ontologies, schemas and data models to describe the same materials using the same general concepts.

Source

Cataloging and classification quarterly. 57(2019) no.5, S.261-277

0.0133230295 = product of:
  0.026646059 = sum of:
    0.026646059 = product of:
      0.053292118 = sum of:
        0.053292118 = weight(_text_:cataloging in 241) [ClassicSimilarity], result of:
          0.053292118 = score(doc=241,freq=2.0), product of:
            0.20397975 = queryWeight, product of:
              3.9411201 = idf(docFreq=2334, maxDocs=44218)
              0.051756795 = queryNorm
            0.26126182 = fieldWeight in 241, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9411201 = idf(docFreq=2334, maxDocs=44218)
              0.046875 = fieldNorm(doc=241)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Cataloging and classification quarterly. 43(2006) nos.3/4, S.161-189

0.012271579 = product of:
  0.024543159 = sum of:
    0.024543159 = product of:
      0.049086317 = sum of:
        0.049086317 = weight(_text_:22 in 4184) [ClassicSimilarity], result of:
          0.049086317 = score(doc=4184,freq=2.0), product of:
            0.18124348 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051756795 = queryNorm
            0.2708308 = fieldWeight in 4184, 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=4184)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 1.2011 10:38:28

0.012271579 = product of:
  0.024543159 = sum of:
    0.024543159 = product of:
      0.049086317 = sum of:
        0.049086317 = weight(_text_:22 in 759) [ClassicSimilarity], result of:
          0.049086317 = score(doc=759,freq=2.0), product of:
            0.18124348 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051756795 = 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)
  0.5 = coord(1/2)

Date

11. 5.2013 19:22:18

0.012271579 = product of:
  0.024543159 = sum of:
    0.024543159 = product of:
      0.049086317 = sum of:
        0.049086317 = weight(_text_:22 in 3283) [ClassicSimilarity], result of:
          0.049086317 = score(doc=3283,freq=2.0), product of:
            0.18124348 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051756795 = queryNorm
            0.2708308 = fieldWeight in 3283, 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=3283)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.0077717677 = product of:
  0.015543535 = sum of:
    0.015543535 = product of:
      0.03108707 = sum of:
        0.03108707 = weight(_text_:cataloging in 5903) [ClassicSimilarity], result of:
          0.03108707 = score(doc=5903,freq=2.0), product of:
            0.20397975 = queryWeight, product of:
              3.9411201 = idf(docFreq=2334, maxDocs=44218)
              0.051756795 = queryNorm
            0.15240273 = fieldWeight in 5903, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.9411201 = idf(docFreq=2334, maxDocs=44218)
              0.02734375 = fieldNorm(doc=5903)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

RDF - the Resource Description Framework - is a foundation for processing metadata; it provides interoperability between applications that exchange machine-understandable information on the Web. RDF emphasizes facilities to enable automated processing of Web resources. RDF metadata can be used in a variety of application areas; for example: in resource discovery to provide better search engine capabilities; in cataloging for describing the content and content relationships available at a particular Web site, page, or digital library; by intelligent software agents to facilitate knowledge sharing and exchange; in content rating; in describing collections of pages that represent a single logical "document"; for describing intellectual property rights of Web pages, and in many others. RDF with digital signatures will be key to building the "Web of Trust" for electronic commerce, collaboration, and other applications. Metadata is "data about data" or specifically in the context of RDF "data describing web resources." The distinction between "data" and "metadata" is not an absolute one; it is a distinction created primarily by a particular application. Many times the same resource will be interpreted in both ways simultaneously. RDF encourages this view by using XML as the encoding syntax for the metadata. The resources being described by RDF are, in general, anything that can be named via a URI. The broad goal of RDF is to define a mechanism for describing resources that makes no assumptions about a particular application domain, nor defines the semantics of any application domain. The definition of the mechanism should be domain neutral, yet the mechanism should be suitable for describing information about any domain. This document introduces a model for representing RDF metadata and one syntax for expressing and transporting this metadata in a manner that maximizes the interoperability of independently developed web servers and clients. The syntax described in this document is best considered as a "serialization syntax" for the underlying RDF representation model. The serialization syntax is XML, XML being the W3C's work-in-progress to define a richer Web syntax for a variety of applications. RDF and XML are complementary; there will be alternate ways to represent the same RDF data model, some more suitable for direct human authoring. Future work may lead to including such alternatives in this document.