Search (2 results, page 1 of 1)

0.004655886 = product of:
  0.018623544 = sum of:
    0.018623544 = weight(_text_:information in 1154) [ClassicSimilarity], result of:
      0.018623544 = score(doc=1154,freq=10.0), product of:
        0.06134496 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.034944877 = queryNorm
        0.3035872 = fieldWeight in 1154, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1154)
  0.25 = coord(1/4)

Abstract

We examined how data provenance and additional information of element values including nomens, and administrative information on the metadata should be modeled and represented in the Resource Description Framework (RDF) for linked data of library catalogs. First, we classified such information types into categories and organized the combination with recording-units, i.e., a description statement or description set. Next, we listed the appropriate RDF representation patterns for each recording-unit. Then, we reviewed the methods to examine such information in Resource Description and Access (RDA) in RDF, BIBFRAME, and Wikidata, and pointed out the issues involved in them.

0.0021033147 = product of:
  0.008413259 = sum of:
    0.008413259 = weight(_text_:information in 1760) [ClassicSimilarity], result of:
      0.008413259 = score(doc=1760,freq=4.0), product of:
        0.06134496 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.034944877 = queryNorm
        0.13714671 = fieldWeight in 1760, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1760)
  0.25 = coord(1/4)

Abstract

Purpose - The purpose of this paper is to present functional requirements for bibliographic records (FRBR)-based model and functional requirements for authority data (FRAD)-based model; both of which incorporate an event concept that transforms FRBR and FRAD with minimal modification. Design/methodology/approach - Relationships between the entities defined in FRBR/FRAD are transformed into event entities and relationships with other kinds of entities. The cardinality of those relationships is also examined. In addition, a comparison of the proposed FRBR-based model with the object-oriented FRBR (FRBROO) is conducted. Findings - In the proposed event-aware FRBR model, an event and its output resource are dependent on each other and necessary information about an event can be expressed with information about its output resource, and vice versa. Therefore, the usefulness and expressiveness of the proposed model is limited. In the FRBROO model, dependency between an event and its output resource is not observed, except in a few cases, since a different resource and event modeling was adopted there. The event-aware FRAD model proposed is useful - but also the scope of its usefulness limited since dependency between an event and its input/output resource is not observed on some event entities. Originality/value - The proposed models are meaningful in terms of understanding the basic structure and features of a model that incorporates an event concept. The usefulness and limitation of event modeling have been clarified through such model building. The proposed models provide a stable basis for examining FRBR/FRAD further.