Unique ID - should it require a URI?

[hkdctol]

Hyon Kim
Data.gov
GSA

Requirement(s)

Current DCAT US 1.1 requires each dataset to have a unique ID, the ID is to be unique across the agency’s catalog and remain fixed
The notes for this field state It is highly recommended that a URI (preferably an HTTP URL) be used to provide a globally unique identifier.

Target Audience / Stakeholders

Stakeholders are agencies and users of federal data

Additional context, comments, or links - Optional

Question for the metadata schema update -- should the schema REQUIRE a URI? This would have many benefits, but also have resource implications.

[hkdctol]

Cross referencing an issue from Project Open Data repository at project-open-data/project-open-data.github.io#627

[hkdctol]

Also referencing project-open-data/project-open-data.github.io#614

[hkdctol]

another reference at project-open-data/project-open-data.github.io#592

[fellahst]

Kim,

Thank you for your inquiry about the unique identifier requirements in the DCAT-US specification. You are correct in noting that DCAT-US mandates that each resource, be it a dataset, data service, data series, or catalog, must be identified by a URI. This requirement is enforced through the SHACL (Shapes Constraint Language) profile, ensuring strict adherence to the standard.

The use of URIs as unique identifiers for each resource aligns with the broader principles of data management and interoperability. By enforcing this through the SHACL profile, DCAT-US 3.0 ensures that resources are not only uniquely identifiable but also easily accessible and linkable across different systems and platforms.

This approach underlines the commitment to creating a standardized, interoperable, and FAIR-compliant data ecosystem, enhancing the usability and effectiveness of federal data resources.

Please refer the usage guideline Deferenceable Identifiers in the specification for more details.
If you have any further questions or require additional guidance on implementing this aspect of the DCAT-US 3.0 specification, please feel free to reach out.

[ShaferAC]

+1

[mrratcliffe]

+1