We discussed on the list about the need of node_id for primitive contraints in the AOM to allow referencing alternatives in a constraint for ELEMENT.value.
That seems to be solved in the AOM 2, but was an issue from AOM 1.4.
If we need to create paths for an specific part of the structure that points to one of the alternatives, e.g. for querying, we don't have a place in the IM to store the node_id that will be one of the right-most ids in the path.
What we talked about, and most agreed, is to add a node_id to the DATA_VALUE class, or (my preference) to make DATA_VALUE inherit from LOCATABLE to have the archetype_node_id attribute in DATA_VALUE.