Dataset specifications usually contain a number of schemas. However, for the data publisher user there are 2 different types of schema:
- schemas they need to create data for, for example, development-plans
- schemas they need to refer to. These are schemas that we (MHCLG/Digital land) have created data for, and the data becomes the values the data publisher can use. For example, for the [contribution-purpose schema] we have created the contribution purpose data that data publishes need to refer to when they are creating their developer-agreement-contribution data.
As the image below shows, we just list the schemas as one list.
We need to make the separation clearer.
However, currently there is no way for the rendering code to determine which type a schema is. And in the case of reference schemas there is no way to point to the actual data the user needs to refer to.
What mechanism should we use to improve this?
Dataset specifications usually contain a number of schemas. However, for the data publisher user there are 2 different types of schema:
As the image below shows, we just list the schemas as one list.
We need to make the separation clearer.
However, currently there is no way for the rendering code to determine which type a schema is. And in the case of reference schemas there is no way to point to the actual data the user needs to refer to.
What mechanism should we use to improve this?