One day, metacatalog needs a fourth top-level module: a REST server. Besides the fact that REST is the most appropriate tech to exchange information and expose metacatalog publicly, this is also needed to implement a very simple UUID query service. One endpoint needs to be able to look up UUIDs in Entry and EntryGroups. The URI of that endpoint, together with a description is needed to expose a codeList for UUID references e.g. in ISO 19115 or DataCite.
The Rest client will be added after the API is more or less stable.
One day, metacatalog needs a fourth top-level module: a REST server. Besides the fact that REST is the most appropriate tech to exchange information and expose metacatalog publicly, this is also needed to implement a very simple UUID query service. One endpoint needs to be able to look up UUIDs in
Entry
andEntryGroups
. The URI of that endpoint, together with a description is needed to expose a codeList for UUID references e.g. in ISO 19115 or DataCite. The Rest client will be added after the API is more or less stable.