FWIW, you seem to have reintroduced a nonsensical content model fvLib (prior to your merge) <content> <zeroOrMore xmlns="http://relaxng.org/ns/structure/1.0"> <ref name="model.featureVal"/> </zeroOrMore> </content> fvLib (after your merge) <content> <zeroOrMore xmlns="http://relaxng.org/ns/structure/1.0"> <choice> <ref name="model.featureVal"/> </choice> </zeroOrMore> </content> This doesnt affect schema production, and is thus benign. But, if for some reason we have to rerun the purification of content models script again before I merge in the pure ODD branch, this one will need hand fixing again. And I don't understand (never have) what @preDeclare is doing. On 02/10/15 01:39, Syd Bauman wrote:
That looks a bit terrifying. Are you sure you’re working off the right copy of the repo? No, I'm not at all sure; did I do it wrong? I'm was trying to request that someone merge syd-xenodata into master. But the commit messages below make it look like it's the right branch. They list everything that happened before it was branched off, too, but it does list up to the latest change in sydb-xenodata, which was to predeclare macro.anyXML.
From where was this mail sent, and to where is it going? I'm CCing the council list in case it winds up in a bit bucket.