Refactor Service entity type to not have version as an attribute that is separate from the MRN

maritimeconnectivity / IdentityRegistry

MCP (Maritime Connectivity Platform) Identity Registry API

http://maritimeconnectivity.net/#core_components

Apache License 2.0

16 stars 8 forks source link

Refactor Service entity type to not have version as an attribute that is separate from the MRN #42

Open oliverhaagh opened 8 months ago

oliverhaagh commented 8 months ago

Currently the MIR has a unique constraint on the combination of version and MRN in the Service entity type, which consequently allows several service entities to have the same MCP MRN, which is a violation of the specification.

oliverhaagh commented 1 week ago

In order to not break backwards compatibility for existing services the Service type will continue to have the version field, but for any new services being created it will not be allowed to give this a value.