UAF13 — 9.1.1 ArchitecturalReference - Incorrect Name (Not a Reference to Architecture), Not a Tuple, Incorrect Definition. Not Needed - Use a Trace

9.1.1 Domain Metamodel::Architecture Management - Architectural Reference. p128 , Fig 9:125

ArchitecturalReference defined as 'A tuple that specifies that one architectural description refers to another.'

1) The name of the element should be 'ArchitectureDescriptionReference' as it isn't 'architecture' that's being referred to - it's an ArchitectureDescription element
2) ArchitecturalReference isn't a tuple. The shortest possible tuple, a triple, is either node - relationship - node or node - relationship - (same) node if reflexicve. ArchitecturalReference is a relationship.
3) The definition of a metamodel element must define the concept itself. This must be atomic. The 'one architectural description refers to another' defines how it may be connected - it doesn't define what 'ArchitecturalReference' is. If the element were defined you'd probably correctly decided that it isn't a concept for a metamodel because there is no atomic definition other than 'undefined' because it's semantically equivalent to the other "universal stuff" releationship, ArbitraryConnector. This sort of error would be much easier to trap if there was rigour in the definition of individual metamodel elements.
4) A 'tuple' does not specify anything. This connector element is purely a description or assertion that there is some unknown relationship between 2 ArchitecturalDescription elements
5) If a reference is required why isn't a trace relationship used? Then we'd have one less arbitrary metamodel element.