Globally unique, persistent and resolvable identifier schemas
Identifier schemas within FAIRsharing must be persistent to be in scope for our standards registry, but there is an extra attribute that shows whether or not the schema is also a GUPRI.
This feature is in active development.
FAIRsharing allows the registration of any community-relevant persistent identifiers (PIDs), whether or not they are also globally-unique and resolvable (a.k.a. GUPRIs, see our section on identifier schema records). FAIRsharing simplifies the EOSC PID Policy to determine if an identifier schema is also a GUPRI:
A Persistent Identifier (PID) policy for the European Open Science Cloud (EOSC), Publications Office, 2020, https://data.europa.eu/doi/10.2777/926037
If your identifier schema is a GUPRIs as defined below, then enable the tickbox within the Additional Information tab that asks "Is this identifier schema a GUPRI as defined by FAIRsharing?".
How do I tell if my identifier schema conforms to the FAIRsharing GUPRI policy?
While the requirements for being a FAIRsharing GUPRI are closely aligned with the EOSC PID policy document linked above, there are some differences. Firstly, some aspects of the EOSC PID policy are beyond the scope of the curation team to assess; as such, some attributes defined as mandatory by EOSC may be optional for FAIRsharing to provide flexibility with regards to what is publicly available for these standards. Secondly, some aspects of the EOSC PID policy are not appropriate to a globally-relevant resource such as FAIRsharing. For example, FAIRsharing does not require or check that an identifier schema integrates with the European Research Infrastructures (EOSC PID 7.1).
The following conditions must be met for your identifier schema to be considered globally unique, persistent and resolvable as per FAIRsharing requirements. The identifier schema:
should be mature, and the id providers should show a commitment to sustaining the infrastructures and the minted identifiers for the long term (similar to EOSC PID policy principles 2.7 and 2.8).
must be globally unique, persistent, and resolvable (similar to EOSC PID section 3).
Global uniqueness: must use a controlled syntax/namespaces to avoid clashes.
Persistence : Must have clear community backing for the schema. The syntax of the schema must be stable. The referred object should itself be stable, though there are various ways to show this (e.g., a dataset might be completely immutable, while a record describing an organisation is likely to change as the organisations homepage, name or other attributes change).
Resolvable: humans and machines must be able to use the identifier to access information on the digital object, how the object can be accessed, or the object itself. There should be an established tombstoning or equivalent procedure.
It must be clear who the maintaining organisation for the identifier schema is (similar to EOSC PID 5.3).
There should be a clear preservation policy / exit plan, should the original provider shut down (similar to EOSC PID 8.4).
Last updated
Was this helpful?
