• The URL in inventory for the XMI file does not have a complete filename. I would expect something line http://www.omg.org/spec/ARCH/20170801/archimate3.xmi

• The language in bullet 6 is “A model…is producing an artefact not a tool” – in fact it’s an organization that is producing the artifact which is a model: the “model” is not producing anything.

• Unclear why there are normative references to ArchiMate® 2.1

• The normative reference to ArchiMate® 3.0 actually takes you to 3.0.1

• It’s not clear to me that the specification itself adheres to the following licensing requirement (I have already make this comment several times)
  o In any derivative work, Licensee Organization shall always fully acknowledge the right, title and interest of The Open Group in the original Documentation, and shall not claim or imply that any derivative work of the Documentation is the official ArchiMate Documentation.
• With respect to the above quote, bullet 7 in section 2.1 should make it clear that this specification, while Documentation, is not the “original” or the “official” Documentation.

in 7.7 Plateau is a composite rather than a Passive structure

. in 7.8 the abstract syntax and concrete syntax are swapped

in 7.9,2 shouldn't Access have a tagged value of AccessType enumeration with the values None, Read, Write, ReadWrite

in 7.9.4 shouldn't ArchiMate_Junction have a tagged value using JunctionKindType enumeration

in 7.5, Technology Object is abstract so should not be in the Profile

. in 7.3.3 you switch from <<stereotype>> notation to the symbol notation in the corner... which might be very confusing for people reading the standard.
(also 7.4.3,7.5.1,7.5.3, 7.6.1)

location is no longer in the Business Layer... it is now just a composite... if you have to place it somewhere... it is grouped with the Core...

one other thing that really needs to be put into this UML Profile... is the restriction on relationships... somewhere in the profile there needs to be a statement like

"The ArchiMate relationships are constrained as to what Elements (source and target) to which they can be applied. These constraints are detailed in Appendix B of the standard in two tables there (http://pubs.opengroup.org/architecture/archimate3-doc/apdxb.html#_Toc489946155)".

why are only the strategy elements marked as _strictness = profile ... this is purely a Sparx thing correct?... not sure it needs to be in the spec... why would we restrict things to only being able to be stereotyped once?... that is not what the ArchiMate spec allows (it says anything can be stereotyped as much as you
want)