Thanks @skyleryoung here’s the definitions - I can incorporate these into the proposal doc if needed.
| term | definition |
|---|---|
| publisher | the organisation responsible for publishing the entire data set/API. This could be an organisation who are publishing data about their own services or it could be an organisation combining data from various sources |
| developer | the organisation developing the API. This could be the same as the publisher if they have in house capacity to do this. Or it could be an organisation that has been contracted by the publisher. |
| provenance | in this case refers to the overall responsibility for a whole data set, rather than the original source of each record which could vary across records. We aren’t provididing information about how the data has potentially been collected/transformed to get to the current state. |
As @MikeThacker has found an alternative way to feed this info into the UK dashboard I would be interested to hear thoughts about whether the developer information is still useful to include.
It could be (e.g. if someone noticed common issues across APIs made by a particular developer) but perhaps the publisher info is the most important thing.
Where exactly in the JSON schema will these fields be located? Are they sent once at the top-level for each API? Or are they sent with each record?
They would be sent once at the top level GET/ alongside the fields version, profile and openapi_url