Search (2 results, page 1 of 1)

0.002189429 = product of:
  0.004378858 = sum of:
    0.004378858 = product of:
      0.008757716 = sum of:
        0.008757716 = weight(_text_:a in 3743) [ClassicSimilarity], result of:
          0.008757716 = score(doc=3743,freq=20.0), product of:
            0.043477926 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.037706986 = queryNorm
            0.20142901 = fieldWeight in 3743, product of:
              4.472136 = tf(freq=20.0), with freq of:
                20.0 = termFreq=20.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3743)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

In 2008 the FRBR/CRM Harmonisation Working Group has achieved a major milestone: a complete version of the object-oriented definition of FRBR (FRBRoo) was released for comment. After a brief overview of the history and context of the Working Group, this paper focuses on the primary contributions resulting from this work. - FRBRoo is a self-contained document which expresses the concepts of FRBR using the objectoriented methodology and framework of CIDOC CRM. It is an alternative view on library conceptualisation for a different purpose, not a replacement for FRBR. - This 'translation' process presented an opportunity to verify and confirm FRBR's internal consistency. - FRBRoo offers a common view of library and museum documentation as two kinds of information from memory institutions. Such a common view is necessary to provide interoperable information systems for all users interested in accessing common or related content. - The analysis provided an opportunity for mutual enrichment of FRBR and CIDOC CRM. Examples include: - - Addition of the modelling of time and events to FRBR, which can be seen in its application to the publishing process - - Clarification of the manifestation entity - - Explicit modelling of performances and recordings in FRBR - - Adding the work entity to CRM - - Adding the identifier assignment process to CRM. - Producing a formalisation which is more suited for implementation with object-oriented tools, and which facilitates the testing and adoption of FRBR concepts in implementations with different functional specifications and in different environments.

0.0019970664 = product of:
  0.003994133 = sum of:
    0.003994133 = product of:
      0.007988266 = sum of:
        0.007988266 = weight(_text_:a in 1917) [ClassicSimilarity], result of:
          0.007988266 = score(doc=1917,freq=26.0), product of:
            0.043477926 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.037706986 = queryNorm
            0.18373153 = fieldWeight in 1917, product of:
              5.0990195 = tf(freq=26.0), with freq of:
                26.0 = termFreq=26.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.03125 = fieldNorm(doc=1917)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The models in the FRBR family include ways to document names or terms for all entities defined in the models, with identification as the ultimate aim, i.e., to distinguish entities by unique appellations and to use the most reliable appellations for entities in a given context. The intention in this paper is to explore the interrelationships between these different models with regards to their treatment of names, identifiers and other appellation entities. The specialisation/generalisation structure of the appellation-related entities and the relationships and properties of these entities will be discussed. The paper also tries to clarify the potential confusion of identity itself in this context - when are we talking about an entity via its name, about the name itself, about the name citation in a document and when about a name of name? In FRBR(er), titles for group 1, names for group 2 and terms for group 3 entities are merely defined as attributes of these entities. This serves the basic requirement of associating the appellation (label) with the entity, but does not allow introducing attributes of these appellations or relationships between and among them. FRAD, completed a decade later, defined as entities name, identifier, and controlled access point. Clearly making the distinction between a bibliographic entity and its name is a significant step taken in FRAD. This permits the separate treatment of relationships between the persons, families, and corporate bodies themselves and those relationships which instead operate between their names or between the controlled access points based on those names. In FRSAD, the most recent model, two entities are defined, Thema and Nomen. Again, the bibliographic entity is distinguished from the full range of its appellations. The FRBRoo model expanded on the treatment of appellations and identifiers in CRM by modeling the identifier assignment process. In FRBRoo, F12 Name was defined but identified with the existing CRM entity E41 Appellation. Current development is concentrating on integrating FRAD and FRSAD concepts into FRBRoo, and this is putting a focus on naming and appellations, causing new classes and properties to be defined, and requiring a re-evaluation of some of the decisions previously made in FRBRoo. As naming and appellations are such a significant feature of the FRBR family of conceptual models, this work is an important step in towards the consolidation of the models into a single coherent statement of the bibliographic universe.

Content

Contribution to a special issue "The FRBR family of conceptual models: toward a linked future"

Type

a