JT and I worked on a system loosely based on what the TEI does, but actually simpler, to validate the content of egXML elements in our praxis documents. What happens is that each child node of an egXML element (assuming it's an element) is copied out into a separate temporary document, transformed back into the main TEI namespace; and each child text node is pushed out into a separate document wrapped in a p element; then our rng schema is transformed to add as start elements all the elements that occur as children of egXML (along with p); then the fragment documents are all validated three ways, using our new RNG, using our standard Schematron, and using the extracted TEI Schematron. This has thrown up lots of lovely errors in our examples, which JT is now fixing, before we make this process part of the main build.

I've also added jing to the utilities folder so that we don't have to depend on its being in a known location on a build host.