Feature: Translation service for UUID <-> name.trio convention identifiers

[dang03]

Implementation of a service on the Catalogues that enables the transalation of a UUID to the name.trio convention identifier and viceversa through each descriptor API.

[jbonnet]

@dang03 Should this be available in the GKs API? Or is it simply an internal API?

[dang03]

@jbonnet I'm not sure of what/who could use this service. It was a suggestion from @mbredel to have a service that translates UUIDs to name.trio and viceversa.
Most probably this should be available in the GKs API, then GK communicating to the service in the Catalogue.
What do you think?

[jbonnet]

@dang03 Well, I think it makes sense to have it on the GK API, controlling who can access it, etc.

[dang03]

With the one Catalogues concept, external platform users should not interact with the Catalogues using UUIDs (of internal usage, e.g: 65b416a6-46c0-4596...), instead they should interact with using the name.trio identifier (external usage, e.g: sonata-eu.firewall.1.0).
This is applicable to descriptors, however son-package files currently only use UUIDs.

[jbonnet]

Why not supporting both?

…

On 20 Jan 2017, at 12:35, Daniel ***@***.***> wrote: With the one Catalogues concept, external platform users should not interact with the Catalogues using UUIDs (of internal usage, e.g: 65b416a6-46c0-4596...), instead they should interact using the name.trio identifier (external usage, e.g: sonata-eu.firewall.1.0). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.