AMEFF - ID's of objects and attributes

Using different ID's of objects and attributes in each tool leads to inconsistency issues: In case of objects, we solved it with adding new attribute with our own tool ID, which can't be done with attributes. Each tool uses it's own ID format and usually deletes old one with their own. We can't expect unification here (to kkep the original one) - it gets usually deep in tools coding, so my suggestion (just an idea) is to create 3 ID slots where second tool can use own ID and so on, or use one slot as it is in TOGAMEFF now, where second tool can extend the id with it's own (separated with ";" for example). I see this as a major issue for interoperability now, but it definitely needs a deeper discussion and consensus with tool vendors as it has to be included in tool certification.