anchor.diff:  <1> depends on the rest of the application's modules
   <2> XSD generation, to run the `xsd` goal and then assemble into a zip file; within a profile for modularity
   <3> XJC generation, to run the `xjc` to generate Java DTO classes from XSDs; within a profile for modularity
  +
  +
  +
   
   
   
  
positive.code: +
  These are _not_ the same as the original view models; they are provided as a convenience for subscribers to marshall XML documents into Java classes, but running as a standalone process (not part of the Isis app)
  
  
  For example, here is the `pom.xml` file for the (non-ASF)
  http://github.com/isisaddons/isis-app-todoapp[Isis addons' todoapp] example app's `todoapp-xsd` submodule.
  
negative.code: within the Isis application (they may reference underlying domain entities) whereas the DTO classes generated from the
  XSDs can be used standalone, eg by a Java subscriber running on an ESB such as Apache Camel.
  
  The rest of this section explains how to configure a new `xsd` submodule that uses the `isis-maven-plugin` along with
  other standard plugins in order to generate both XSDs and DTOs.  The `pom.xml` described below uses Maven profiles
  to separate out these two responsibilities.
  
  
  [[_cg_isis-maven-plugin_xsd]]
  == `xsd` submodule
  