The basic premise is that lizard-structure only shows a data source’s structure. There are no edit actions, so no POST/PUT/DELETE: only GET.
There are several basic ways to deal with naming the views. Especially when you also want POST/PUT/DELETE, having both ObjectList and ObjectDetail makes sense. But we don’t need that. What’s most interesting are the lists, these are also often the most effective. You don’t want to have to grab handfuls of URLs before you can render a page. You want the most useful data right away. So on an Data source page, you want a list of projects. On a Project page, a list of layers. And so on.
We deemed it more useful to call the view with the list of projects the data source view, though. A data source is a list of projects, so it makes sense that way.
But: a project also has information on itself, as has a project, etc.
Information about the data source itself and its list of projects.
Use this to discover the projects you can show in your user interface. The result is a dictionary with the following items:
Information about the feature and most importantly its representations.