One more wrench to throw in here. Once in awhile there is a <gi> that is from the TEI scheme, but probably should not point directly to the vanilla P5 version in the vault. The (only) specific example I've seen is: The content model of http://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-affiliation.html"
<gi>affiliation</gi></ref> in the jTEI schema ...
Should that <ref> point to the jTEI documentation, not vanilla TEI? Should that <gi> have a scheme="jTEI"? My instinct for right now is not to worry about it, as the result of the new system won't make it any worse than it is now. But we should do something to allow a <gi> to purposefully point somewhere other than auto-generated. For now, having a @scheme other than 'TEI' or 'tei' would do the trick. But maybe James' idea of ignoring a <gi> that is already inside a <ref> should be implemented, too. Am I good to go checking this in? And while I'm at it, gitsters, how do I do that? I did the work in a local copy that was checked out to dev. I have not committed it, let alone pushed, yet. I could, of course, * clone a new copy of repo * check out release branch in that new repo * copy my modified pgm to new repo copy release branch * commit it * push it * warn release techs about it * revert my dev directory with `git checkout -- profiles/readme/html/to.xsl` But there's probably a better GIT way to do this, eh?