UAF14 — ServiceArchitecture Defined as AD, ServiceArchitecture Is not a Service as Stated

ServiceArchitecture is defined as 'An element used to denote a model of the Architecture, described from the Services perspective.'

1) This doesn't define what service architecture is
2) ... denote a model ... almost everything in the UAF metamodel is an AD Element i.e. something that describes some real world concept and forms part of an AD (a model). The definition is supposed to define the real world thing that it is used to represent not itself.
3) Architecture is essentially the set of temporal, spatial, functional etc relationships that something has [internally and with anything external]. ServiceArchitecture is not a specialisation of Service ie it is not true to state that 'ServiceArchitecture is a Service'. The class structure is not therefore correct. I suspect what has happened is that this is a bottom-up derivation which enables behaviours and or properties to be inherited that are useful in a UML implementation. That doesn't make it correct however. Occam's razor should apply in these cases.