But, in a special case like Accessport2LtpTranslator, the uuid prefix is generated as "alt" as per the existing logic. But as per the application's specification, the application-id shall be generated as "atlt". This is contradicting to "ApplicationLayerTopology" (alt).
The current logic implemented for generating uuid for the applications is as per https://github.com/openBackhaul/ApplicationPattern/blob/develop/doc/ElementsApplicationPattern/Names/StructureOfUuids/StructureOfUuids.md.
But, in a special case like Accessport2LtpTranslator, the uuid prefix is generated as "alt" as per the existing logic. But as per the application's specification, the application-id shall be generated as "atlt". This is contradicting to "ApplicationLayerTopology" (alt).
As a temporary solution, a workaround has been requested in A2LT https://github.com/openBackhaul/Accessport2LtpTranslator/issues/130.
Kindly let us know how this situation shall be handled so that a unique uuid is generated for applications