In splitting out the client components (#9) for chop-dbhi/data-models-validator#1 I need resources for performing simple validation (e.g. is a model and version available?) and more granular access to the content itself, such as a list of versions for particular model.
I propose the following to start:
/models - List of models with basic information with their respective list of versions (no tables or fields) and links to related resources (minor and patch releases depend on #7).
/models/:name - Single model with the same representation above.
/models/:name/:version - Same as it is now.
/models/:name/:version/schema - Schema information for the model. This replaces the /schemata endpoint.
Another change will be including URLs in the Link-Template header (for collection-based resources) and in the Link header (for object-based resource).
gracebrownecodes
commented
9 years ago
In splitting out the client components (#9) for chop-dbhi/data-models-validator#1 I need resources for performing simple validation (e.g. is a model and version available?) and more granular access to the content itself, such as a list of versions for particular model.
I propose the following to start:
/models- List of models with basic information with their respective list of versions (no tables or fields) and links to related resources (minor and patch releases depend on #7)./models/:name- Single model with the same representation above./models/:name/:version- Same as it is now./models/:name/:version/schema- Schema information for the model. This replaces the/schemataendpoint.Another change will be including URLs in the
Link-Templateheader (for collection-based resources) and in theLinkheader (for object-based resource)./cc @aaron0browne