One of the benefits of the visual approach to XML in CAM templates is that it makes it easy to compare two schema.
By ingesting one or more XSD schema into CAM templates - it is then easy to use a standard compare tool (such as KDiff open source) - to review the changes and differences in the structure and rules separately.
By contrast the complexity of XSD schema syntax makes direct comparison of two XSD schema problematic - especially if the changes are buried in import or include files.
Using the CAM approach solves that by making templates that can be simply compared. Of this works for CAM templates themselves - and this was a design intent - to make it easy to review changes between versions of partners exchange schema templates.
Thanks, DW