Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sample JSON output using ONS data available here: https://api.beta.ons.gov.uk/v1/datasets/ashe-table-7-hours/editions/time-series/versions/1/metadata
We envisage a link to this JSON will be served as one of the distribution/download options from the above link, and that when the
downloads.ons....file.jsonlink is accessed the appropriate media type headers will be set on that response.Questions on what we have done:
Questions on what we haven't:
I've tried to use DCAT vocabulary where applicable in this example. It seems that Schema.org might hold more value in a strictly web setting, but as our current intention is that this file is downloaded DCAT seemed more fitting. Is it even appropriate for this JSON file to be a download, or must it be redirected to as a page/endpoint in its own right?