search

agera-edc / MinimumViableDataspace

Guidance on documentation, scripts and integration steps on using the EDC project results
Apache License 2.0
0 stars 2 forks source link

Rename 'registry' to 'registration service' consistently #196

Closed Izzzu closed 2 years ago

Izzzu commented 2 years ago

Description

A mix of the names 'registry' and 'registration service' to refer to the 'registration service' is confusing.

Especially as deployers need to first deploy an 'azure container registry', which is unrelated.

Therefore, we want to make sure the names are used consistently.

Further notes

Renaming authority_did in terraform files to dataspace_did to not confuse the internal Dataspace DID with the external GAIA-X Authority DID.

linked to #180

pkirch commented 2 years ago

Please make the Flow sequence in docs/developer/decision-records/2022-06-15-registration-service/README.md more consistent for Dataspace Registry and Registration Service as discussed. Thanks!

Izzzu commented 2 years ago

Please make the Flow sequence in docs/developer/decision-records/2022-06-15-registration-service/README.md more consistent for Dataspace Registry and Registration Service as discussed. Thanks!

Changed as discussed

Izzzu commented 2 years ago

@Izzzu, we still have a couple of references that use the term Registry in this repo, including RegistryApi, as well as Dataspace Registry in the Registration Service ADR.

The RegistrationService repo uses the term Registry as well.

Do we want to keep this as is, or would it be worthwhile to use the term Registration Service consistently?

@zeier RegistryApi and also usage of Registry in Registration Service sound reasonable, because Registration Service manages the participants registry and it exposes the Registry API that offers methods to list and register participant. So I'd say we don't ned to get rid of the word 'registry', as it's just one component of the registration service, which is one component of the dataspace auhtority.