...
The classes and properties themselves in BIBFRAME, as well as some of their definitions, remain under active discussion on the BIBFRAME mailing list (archives) and in other venues. With our project's strong focus on linking through to real world entities, we remain flexible in our interpretation and application of the BIBFRAME ontology, in some cases electing to use properties and/or classes in an LD4L namespace until such time as consensus has been reached through in later releases or through pilot projects scheduled for 2015 and/or community practice. Fundamental questions will continue about distinctions between information and real world entities and conflicts between a desire to retain all the information encoded in MARC records vs. allowing bibliographic metadata to more freely inter-operate with other Web data.
- Bibliographic Framework Initiative
- Technical site for the Bibliographic Framework Initiative (bibframe.org)
- BIBFRAME primer document (PDF)
- BIBFRAME master RDF file (December 10, 2014)
Addressing complexity
Several levels of complexity may legitimately exist in parallel and be utilized based on the availability of data or the goals of an application. This choice can be seen in PROV-O ontology where direct object properties have been paired with more complex options involving intermediate nodes that add additional temporal or role information. The related PAV (Provenance, Attribution, and Versioning) ontology offers a simpler set of classes and properties sufficient for many applications requiring only simple attribution. Application software can also often mask a more complex underlying data model, and in many cases it may be preferable in production contexts to separate logging and provenance information from user-facing applications entirely.
...