EDM – FRBRoo Application Profile
This Task Force focused on an application profile that would allow a better representation of the FRBR group 1 entities: work, expression, manifestation and item.
The EDM – FRBRoo Application Profile Task Force (EFAP-TF) was launched in response to the recommendations from the deliverable D3.4 from Europeana V1.0. This deliverable asked for an application profile that would allow a better representation of the FRBR group 1 entities: work, expression, manifestation, and item. Additionally, it was to be conceived as an application profile of FRBRoo where each intellectual contribution (e.g., in the publication process) and the related activity are treated as entities in their own right and do not depend too much on the notion of a bibliographic record. As a starting point, they suggested the mapping of FRBRoo and EDM offered by the CIDOC CRM working group. The aim of the EFAP-TF was to extend, correct or restrict this suggested mapping and provide examples for the use of the combined EDM and FRBRoo namespaces.
This report delivers combined models in terms of properties and classes of EDM and FRBRoo illustrated by sample data. Smaller groups have worked on three different examples. The report also provides principles for modeling and mapping rules based on the experiments of the working groups.
Find the report and its annexes below:
Details of the annexes:
- Hamlet examples
- Musical work examples
- Don Quixote example Available at http://november.idi.ntnu.no/frbrized/rest/db/edm/index.html and archived here
The deliverable Final Technical & Logical Architecture and future work recommendations (D3.4) from Europeana V1.0, WP3 makes the following statement:
"The distinction between the work, expression, manifestation, and item will be relevant for the resources that are aggregated in Europeana. Functionality may be required to group results under the work level (e.g. all copies of all digital files in any format that contain all performances of a composition), under the expression level (e.g. all digital files in any format of a particular performance of a composition), or under the manifestation level (e.g. all digital files in a particular format of a particular performance of a composition). The framework of reference, however, should not so much be the original FRBR specification (which still is too much depending on the notion of a bibliographic record!) but rather the FRBRoo approach, in which each aggregate is treated as an entity in its own right. Note that a mapping of FRBRoo and EDM is offered by CIDOC."
The creation of this Task Force (EFAP-TF) reacted to this statement and is intended to start from the mapping provided by CIDOC eventually extending, correcting or restricting it and providing examples for the use of the combined EDM and FRBRoo namespace clusters.
- Checking the mapping proposed by CIDOC available at http://www.cidoc-crm.org/docs/EDM-DC-ORE-CRM-FRBR_Integration_ORE_fix.ppt
- Collecting data samples illustrating the possible use of the combined namespaces
- Identifying a relevant subset of classes and properties for the information integration scenario characteristic for Europeana, possibly a core set.
- Providing use cases for the combined namespaces
The group did not work on primary cataloging in whatever format which is regarded as a provider task. Therefore, the group only dealt with the mapping of existing data formats into an extended EDM model, and at most with guidelines to use a core set of properties.
The Task Force on the EDM FRBRoo extension successfully delivered a report on:
- Combined model in terms of properties and classes including sample data
- Principles for modeling and mapping rules
This deliverable benefits all those wishing to model derivative relations in EDM and may also help to clarify a future strategy regarding RDA compliant metadata and the way these are mapped to EDM.