In the OPT itself, there are archetype roots in place wherever an archetype root is encountered - also a filled slot. That can contain both a node id and an archetype id. In Archie we preserve both when creating an OPT 2.
Then in data of course, that’s the big question. Because we encountered this same problem, and did not want to resort to ADL 1.4 style name-based uniqueness constraints, we did the following in data:
- store the node id in archetype_node_id
- store the archetype id and template id in archetype_details.
That’s a bit non-standard at the moment, but it is also very easily converted back to standard data.
Then we made the path lookup so that it works either on the node id or the archetype id - since both are stored in the data. The node id is always unique and you don’t need an additional archetype id in the path queries.
This approach would require mean minimal adaptations in the specification and no changes the AQL or path queries.