Mappings to other models

We have mapped BFFI to BIBFRAME and RDA.

Mapping properties

We use owl:equivalentClass and owl:equivalentProperty for mapping when we consider the classes and properties the same. For more nuanced mappings, we followed the example given by Share-VDE taking inspiration from SKOS mapping properties. SVDE introduced https://svde.org/ontology/closeMatch and we expanded this idea to include the other three SKOS mapping properties.

• bffi-meta:exactMatch
  • Semantically exactly matching class or property in another ontology or scheme.
• bffi-meta:closeMatch
  • Semantically similar class or property in another ontology or scheme.
• bffi-meta:narrowMatch
  • Semantically narrower class or property in another ontology or scheme.
• bffi-meta:broadMatch
  • Semantically broader class or property in another ontology or scheme.

Mapping to BIBFRAME

Whenever possible, we have used owl:equivalentClass and owl:equivalentProperty for mapping to BIBFRAME. In some cases, a BFFI data model entity is directly a subclass or subproperty of a BIBFRAME entity, in which case no extra mappings were used. Finally, in some cases we have used our own mapping properties (see above). All of the BFFI entities have some type of a mapping to BIBFRAME.

The mapping is strongly tied to the conversion from BIBFRAME to BFFI. However, the mapping is not enough for a full conversion which requires a more comprehensive set of rules.

For the BIBFRAME classes and properties omitted from BFFI, we have created a separate mapping file from BIBFRAME to BFFI.

Mapping to RDA

The Finnish library data description is based on the RDA description rules. Many of the specific RDA properties did not have direct counterparts in the BIBFRAME data model or are available only with a broader semantic meaning so we added them when required by the RDA rules. We have mapped BFFI entities to RDA when possible using our own mapping properties (see above). For some classes we also refer to RDA value vocabularies using a rdfs:seeAlso relation.