Matches in Nanopublications for { <https://w3id.org/fair/icc/terms/F1-Explanation> ?p ?o ?g. }
Showing items 1 to 15 of
15
with 100 items per page.
- F1-Explanation type Explanation assertion.
- F1-Explanation type Explanation assertion.
- F1-Explanation label "F1 Explanation" assertion.
- F1-Explanation label "Explanation of FAIR principle F1" assertion.
- F1-Explanation isDefinedBy F1-Explanation assertion.
- F1-Explanation isDefinedBy F1-Explanation assertion.
- F1-Explanation comment "Principle F1 states that resources, i.e. data and metadata, should be assigned a globally unique and persistent identifier (GUPID). ..." assertion.
- F1-Explanation comment "Principle F1 states that digital resources, i.e. data and metadata, must be assigned a globally unique and persistent identifier in order to be found and resolved by computers. This is the most fundamental of the FAIR principles, as globally unique and persistent identifiers are essential elements found in all of the other FAIR principles. Globally unique means that the identifier is guaranteed to unambiguously refer to exactly one resource in the world. Therefore, it is insufficient for it to be unique only locally (e.g. unique within a single, local database). Persistence refers to the requirement that this globally unique identifier is never reused in another context, and continues to identify the same resource, even if that resource no longer exists, or moves. In practice, this often involves using a third-party to generate an identifier that has guaranteed longevity and is project/organization-independent." assertion.
- F1-Explanation seeAlso Digital_object_identifier assertion.
- F1-Explanation seeAlso journal.pbio.2001414 assertion.
- F1-Explanation seeAlso zenodo.3267434 assertion.
- F1-Explanation explains-principle F1 assertion.
- F1-Explanation explains-principle F1 assertion.
- F1-Explanation implementation-considerations "Current challenges relate to ensuring the longevity of identifiers - in particular, that identifiers created by a project/community should survive the termination of the project or the dissolution of the community. Obtaining a persistent identifier, therefore, may require reliance on a third-party organization that promises longevity, and maintains these identifiers independently of the project/community. Current choices are for each community to choose, for all appropriate digital resources (i.e. data and metadata), identifier registration service(s) such as these that ensure global uniqueness and that also comply with the community-defined criteria for identifier persistence and resolvability." assertion.
- F1-Explanation implementation-examples "A common example of a useful identifier is the Digital Object Identifier (DOI) which is guaranteed by the DOI specification to be globally unique and persistent. DOIs provide an additional service, under principle A1, of being able to direct calls to the source data to the location of that data, even if the identified data moves. This ensures that identifiers are stable and valid beyond the project that generated them. In some circumstances, again with DOIs being an example, third-party persistent identifiers may also provide support for principle A2 (that metadata exists beyond the lifespan of the data) since these identifiers may still be responsive to Web calls, and be capable of providing metadata, even if the source resource is no longer active. For a discussion on identifiers see doi:10.1371/journal.pbio.2001414 and doi:10.5281/zenodo.3267434 ." assertion.