node_id on C_OBJECT should be optional when sibling nodes are unambiguous


Currently the AOM says that the node_id attribute of the C_OBJECT class is mandatory (1..1). However, node_ids are not used on object nodes that are only children of single-valued attributes, or in some cases multiple alternatives of single-valued attributes (needs checking).

Node identifiers should not be needed on nodes unambiguously identifiable by paths, and if we look at Xpath, it does not expect them either - predicates are only used to distinguish when there are multiple sibling objects below an attribute.


Diego Bosca
May 18, 2015, 6:36 PM

Arguably the ability of specialize any data type implies that every node of every archetype could be ambiguous when specializing that archetype (at least to know which constraint is that node following)

Thomas Beale
September 30, 2015, 8:48 AM

This CR can now be rejected since in ADL2 the approach is to define a code on every node, with some of those codes being defined in the terminology as nedeed.


Thomas Beale

Raised By

Sistine Barretto


Affects versions