FAIR Mapping Recommendations¶
FAIR Mapping recommendations were created as part of the the FAIR-IMPACT project (2022-2025). One of the goals of the RDA FAIR Mappings working group is to solicit feedback for the recommendations to improve them.
To formulate these recommendations, we conceptually divided the domain of mapping and crosswalks into four parts: Format & Model, Mappings Metadata, PID, and Service & API. The recommendations were formulated based on brainstorming sessions focusing on each part using gathered community requirements and feedback collected during various events. The recommendations are broken down as “generic recommendations” and “technical recommendations”. The technical recommendations are technical implementation aspects that will ensure the machine execution of the generic recommendation that are human readable guidances.
Rec 1. Model & Format¶
Generic recommendation¶
G-Rec.1 Use a model to represent mappings with explicit links between the mapped entities and metadata for the crosswalk and the individual mappings that can be serialised in various formats (discussion#75)
Technical recommendation¶
T-Rec 1.1 Use the SSSOM model to structure and share your mappings (discussion#59)
T-Rec 1.2 Provide the mappings with different serialisations including LD standards (RDF/XML, OWL/XML, JSON-LD) (discussion#61)
T-Rec 1.3 Make sure the metadata describing the crosswalks and the individual mappings are aligned with standards and FAIR vocabularies to structure the metadata (e.g. Dublin Core, DCAT, …) (discussion#62)
Rec 2. Mapping Metadata¶
Generic recommendation¶
G-Rec 2. Provide metadata to describe the crosswalks and individual mappings (discussion#76)
Technical recommendation¶
T-Rec 2.1 Use the minimum SSSOM metadata schema defined by the FAIR IMPACT project to document mappings and crosswalks (discussion#63)
T-Rec 2.2 If the mappings are separated from the associated metadata, Include an additional metadata field containing the PID pointing to the mapping or crosswalk (discussion#64)
Rec 3. PID¶
Generic recommendation¶
G-Rec 3 Crosswalks (collections of mappings), individual mappings, and their versions must be identified with a GUPRI (discussion#65)
Technical recommendation¶
T-Rec 3.1 Use web-based GUPRIs that enable the access to the SSSOM mapping metadata and data (e.g. PURL, W3id,...) (discussion#66)
T-Rec 3.2 Establish and publish a PID policy describing the approach for versioning and explicitly describe the preservation policies(discussion#67)
Rec 4. Service & API¶
Generic recommendation¶
G-Rec 4 Publish your collection of mappings or crosswalks and the associated metadata into a specialized repository such as MSCR that provides access for humans and machines (discussion#77)
Technical recommendation¶
T-Rec 4.1 Mapping repositories must extract and publish the metadata records for the crosswalk and each of the individual mappings (discussion#68)
T-Rec 4.2 Metadata records describing collections of mappings, individual mappings, as well as their versions must be identified with a GUPRI (discussion#69)
T-Rec 4.3 Mapping repositories may allow procedure of authorisation and authentication(discussion#70)
T-Rec 4.4 Mapping repositories should allow accessibility to mapping metadata even when the mapping is no longer available (discussion#71)
T-Rec 4.5 Mapping repositories must provide search functionality for mappings and collections of mappings (discussion#72)
T-Rec 4.6 Mapping repositories must use open standards and machine readable descriptions to publish API description (e.g. OpenAPI, smartAPI) (discussion#73)