With respect to writing a new, simple, well-behaved, PureODD customization file, are the following correct? If the issues I raise in the footnotes are problems (as I think they are) I will be happy to create issues in GitHub and fix 'em, but I want to make sure they are problems, first. * macroRef/@key should always refer to a TEI macro, not a TEI datatype (i.e., should start with "macro." not "data." or "teidata.")[1,2] * dataRef/@key should always refer to a TEI tei-datatype, not a TEI datatype or a macro (i.e., should start with "teidata.")[3] * classRef/@key should always refer to a class, i.e. should start with "att." or "model." Notes ----- [1] In which case the only example of a <macroRef> in the Guidelines is problematic, as its @key is "data.text". [2] We use macroRef/@key that starts with "data." 3 times in the Guidelines. [3] In which case the 1st example of <dataRef> in the tagdoc, while not incorrect (it refers to 1.5.1), is a bit disingenuous.