Include spec major version in URL paths
This was suggested multiple times and I cannot remember why specifically I did not put this in initially
Allow specifications without capabilities + Allow for dependencies between specifications
Versioning is currently per-specification, so if you include many capabilities into a single specification it makes it harder to evolve individual capabilities (see #31). That is why we decided to split the discovery-related specifications into separate documents, one of them describing the data ingestion which only consists of shared APIs that are relevant to all discovery capabilities but not user-facing capabilities.
Please note that I welcome comments and feedback, even though I will merge this right away as I would otherwise be blocked.
Three changes, two of them related:
Please note that I welcome comments and feedback, even though I will merge this right away as I would otherwise be blocked.