Excellent work, Peter. Martin and I just started where you left off and discovered that P5/Exemplars/tei_simplePrint.odd contains two <classSpec ident="att.global.rendition" mode="change"> elements (right next to each other: lines 3514 and 3539). If these are merged, this particular problem goes away. Begs the question of what the BLEEP did we do to the stylesheets in DC that would cause this side effect. Just as importantly, this raises a big, hairy question: is it legal to have two <*Spec> elements in the same ODD with the same @ident? (I have always told people that it is _legal_ but *won't work*.) Martin thinks one of the footnotes in USE implies that it is not: An ODD processor should recognize as erroneous such obvious inconsistencies as an attempt to include an elementSpec in add mode for an element which is already present in an imported module. We will need to hash this out (in both respects -- the Stylesheets and the issue of duplcate <*Spec>s), but I will not be able to contribute any time to this until after MarkupUK next week.

we had an efficient Stylesheets meeting today and tackled issue #375 which I think we fixed. (NB, the Stylesheets were not flagged as broken but the issue only surfaced in the subsequent Guidelines builds.)

Yet, the Guidelines build is still broken due to another issue with the exemplars (I believe) we introduced in [1]. The tei_simplePrint.odd does feature multiple <elementSpec> with the same @ident and relies on the ODD processing to resolve these properly. But it seems the ODD processing now(?) duplicates some of the information, leading to the error message "reference to undefined pattern „att.global.rendition.attribute.rendition““. [2] In fact, the schema it complains about has two of those attribute references:

``` <define name="att.global.rendition.attributes"> <ref name="att.global.rendition.attribute.rendition"/> <ref name="att.global.rendition.attribute.rendition"/> </define> ```

That’s how far I got with debugging today …

Best Peter

[1] https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com... [2] https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjenkins.te...