Expose data package (frictionless data) endpoint

[dafeder]

Having a datapackage.json endpoint for every dataset, especially as we integrate Data Dictionaries at the resource level using the tabular data schema, will open up a universe of tooling that exists for this standard (including easy integration with Good Tables)).

[kimwdavidson]

@dafeder: should i add this to the data dictionaries epic or no?

[erogray]

@dafeder is this still a planned ticket?

[dafeder]

Need to follow up with the Frictionless project about combining dcat-us and data package standards...

[dafeder]

Update - this is still something I'd like to see added, along with a general pattern for mapping the core storage schema -- which is likely to be something DCAT-like -- to an arbitrary second schema to help integrate catalogs with wider ecosystems. This might look like

• A template for the output JSON using JSON Path strings as values?
• A jq expression.. either for each property or for the whole object?
• A lightweight implementation of Jolt or some similar spec?

So we could ship with a data package mapping but it would only be guaranteed to work with the default schema; it would need to be straightforward to extend/alter the mapping if you override the default schemas.

This is an old issue but I think worth keeping open; we are likely to be doing related work in the next few months that may unblock this.