Au contraire! DTD generation is working now (at least, I don't get any invalid DTDs in my tiny tests). I'm not sure it would make sense to issue a pull request for a change that would make things worse. I'm hoping it makes things better. But Elisa has made an important point. There are 4 pull requests from contributors who are not on Council pending. 1) Do we have a procedure for honoring or rejecting such pull requests? 2) Who among us has the GitHub authority to make such a pull? 3) Who among us has the TEI authority to make such a pull? 4) Who among us has the technical chops to be sure such a pull is the right thing to do? 1) I don't think we do have a process, but I think we should. I don't know enough about git to be confident of what it should be, though. Ideally it would boil down to something like "Councilor volunteers for, or is assigned the pull (by Council Chair); Councilor creates a copy of repo that reflects the pull, and tests it locally; Councilor posts results of test to rest of us with a recommendation; 1 week later Councilor executes recommendation (either pulling in or declining to do so, explaining why to requester), unless there has been discussion to the contrary.". 2) Idunno. Back in the Sourceforge days Lou and I both had such authority. James, too, IIRC. Maybe anyone can do it? What's the difference between a "contributor" and a "member", anyway? 3) At first crack, I would say all members of Council. 4) This one's easy -- no one. :-|
Sorry--I'm not awake yet...Of course, now that I reread all the posts, I guess we're not ready to commit these branches to Stylesheets dev. (Of course we haven't resolved the minOccurs/maxOccurs discussion and DTD processing doesn't work yet, though I think if we have to ignore DTDs the latest solution ought to be fine generally). But hope we're testing stuff against the branches.