Open jqnatividad opened 1 month ago
Having Digital Object Identifiers (DOIs) for datasets is "a foundational requirement to unambiguously identify and access resources."
In the Usage Guidelines, the topic is thoroughly covered
https://doi-do.github.io/dcat-us/#deferenceable-identifiers
However, there is no specific guidance on how to get DOIs.
In section 6.1.3 Identifier Resolution Service, several well known services are listed.
Is a standard Identifier Resolution Service (like purl.org, or DataCite, which is not listed) being considered?
Is the US government considering standing up its own Registry?
Will there be best practice guidance beyond using RFC 3986 IETF standard for URIs? (https://doi-do.github.io/dcat-us/#generating-resolvable-urls)?
Specific guidance would be much appreciated as we prepare CKAN to support DCAT-US v3 and to architect a Federal Data Usage platform.
Perhaps a reference to OSTI, which is I believe the main registry for DOIs for government research data?
dafeder
commented
4 weeks ago
Having Digital Object Identifiers (DOIs) for datasets is "a foundational requirement to unambiguously identify and access resources."
In the Usage Guidelines, the topic is thoroughly covered
https://doi-do.github.io/dcat-us/#deferenceable-identifiers
However, there is no specific guidance on how to get DOIs.
In section 6.1.3 Identifier Resolution Service, several well known services are listed.
Is a standard Identifier Resolution Service (like purl.org, or DataCite, which is not listed) being considered?
Is the US government considering standing up its own Registry?
Will there be best practice guidance beyond using RFC 3986 IETF standard for URIs? (https://doi-do.github.io/dcat-us/#generating-resolvable-urls)?
Specific guidance would be much appreciated as we prepare CKAN to support DCAT-US v3 and to architect a Federal Data Usage platform.