After a long discussion with Jerome we determined that three changes might satisfy his requirements. Those changes are:
In a record collection (aka a catalog) allow records to be encoded in-line or by reference. This would allows a static catalog to be set up with paging.
Make the query parameters in the Local Resources Catalog requirements class optional like the sorting and advanced filtering query parameters.
Make the geometry member in the record optional in the building block but mandatory in the GeoJSON encoding of the record. This is actually consistent with csw:Record where the geometry is optional.
This PR is an exploration to capture all these changes. This allows us to keep the current organization but still satisfy the use cases that Jerome had in mind in relatation to issue #300.
After a long discussion with Jerome we determined that three changes might satisfy his requirements. Those changes are:
geometrymember in the record optional in the building block but mandatory in the GeoJSON encoding of the record. This is actually consistent with csw:Record where the geometry is optional.This PR is an exploration to capture all these changes. This allows us to keep the current organization but still satisfy the use cases that Jerome had in mind in relatation to issue #300.
Closes #300.