Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guidance and migration pathway for globally unique IDs #592

Open
philipashlock opened this issue May 12, 2017 · 0 comments
Open

Guidance and migration pathway for globally unique IDs #592

philipashlock opened this issue May 12, 2017 · 0 comments
Labels

Comments

@philipashlock
Copy link
Contributor

philipashlock commented May 12, 2017

It was recommended that globally unique values for identifier should be specified way back with #69 and the guidance was updated to make this a recommendation (using a URL) with the update to v1.1, but it was not a strict requirement. After several years of this metadata making its way across the internet ecosystem it's now more clear than ever that this needs to transition to a hard requirement. The case for this was already made pretty sufficiently within #69. This issue is meant to lead both to final guidance on that as a hard requirement, but also to more immediately develop a migration pathway to transition current non-global values for identifier to proper URLs.

One migration option may be to define a convention where a unique ID for each agency is paired with the non-global identifier for the dataset and then have that appended to the end of a URL, potentially using a similar approach as W3ID to help maintain persistence.

For instance, if GSA has a metadata entry with a non global identifier like GSA-2016-01-22-01 then that could be represented as a more global URI like dcat-us:federal/gsa/GSA-2016-01-22-01 but ultimately it would appended on to a URL for a final value of something like https://id.data.gov/dcat-us/federal/gsa/GSA-2016-01-22-01. We'd also need to consider URL encoding as part of this transformation since there aren't any restrictions on the current values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants