-
Notifications
You must be signed in to change notification settings - Fork 1
BFFI modelling principles and decisions
We strive to use FAIR principles in our modelling work to ensure that BFFI data model will be findable, accessible, interoperable and re-usable.
The BFFI data model is available in a human readable format at http://schema.finto.fi/bffi as well as in a RDF format. All versions of the model and its corresponding conversion software are stored in a Github repository at https://github.com/NatLibFi/lkd. The data model employs dereferenceable and persistent identifiers, well-known modelling languages, mappings to other data models, and well-defined principles for deprecating removed parts of the data model.
We mint our own URIs for all classes and properties in our data model. This is done in order for us to be able to direct the user to our own data model and its documentation for the full context information. This also allows us more freedom to adjust BIBFRAME resources as needed.
As our data model is an extension for BIBFRAME we have chosen the namespace prefix BFFI (formed similarly to BFLC).
The URI scheme we employ is based to the URN standard and the persistent identifiers are registered and can be resolved at the Finnish urn.fi service operated by the National Library of Finland.
The naming of identifiers for the classes and properties follows the BIBFRAME model and the RDA registry's lexical aliases.
To provide interoperability with other linked library data sources we aim to map all entities of the BFFI model to external data models, primarily to BIBFRAME and RDA.
We have used OWL and RDFS mapping properties as well as made our own set of mapping properties for more specific needs. For more information on these, see XX (Mapping).
The Finnish Metadata Thesaurus (URN:NBN:fi:au:mts:) will be used as a base for controlled lists of values for many properties. Most of the value vocabularies in the Metadata Thesaurus are based on the RDA Value Vocabularies and the vocabularies in the Library of Congress Linked Data Service, the latter especially for various values lists used in the MARC format.
We have used bffi-meta:relatedValueVocabulary for mapping a Class to a value vocabulary in the Metadata Thesaurus containing the instances of said class.
If BFFI classes or properties need to be removed from the data model, the original entity will be kept in the model, but its status will be marked with owl:deprecated "true"^^xsd:boolean. A skos:ChangeNote will be added with the string value "Deprecated". An explanation may be added in parentheses. When removing an entity, all triples where this is the predicate or object, also are checked and corrected or removed as needed. When appropriate, the property [dct:isReplacedBy](https://workgroups.helsinki.fi/(http:/purl.org/dc/terms/isReplacedBy) may be added to show a replacing resource. The labels will be kept but all other properties will be removed.
The removed entites are listed at the bottom of the human readable listing of the model.
BFFI Data Model documentation -- Draft in progress