We haven't run into any issues that seem related to this. When compiling
MEI, we always set the localsource parameter to our base ODD declaration,
so there won't be any elementSpecs creating elements in the TEI ns, they're
all in the MEI ns.
Feel free to give it a try by cloning the MEI repo, running ./teitorelaxng
with --localsource set to mei-source.xml
https://github.com/music-encoding/music-encoding/blob/develop/source/mei-sou...
and
using the mei-all customization
https://github.com/music-encoding/music-encoding/blob/develop/customizations...
.
Raff
On Mon, Jan 1, 2018 at 10:08 PM, Syd Bauman
In odds/odd2odd.xsl (in the dev branch) we find several keys into the <*Spec> elements (e.g., "odd2odd-CHANGE") which use as their key (i.e., their @use) the value of tei:uniqueName(). That function (defined on line 279 of the same file) returns the @ident of the node passed to it, with the namespace in which the thing being specified is declared iff said namespace is not the TEI namespace.
BUT, a few of the calls to those keys use @ident, not tei:uniqueName(). In particular, those in the mode "pass0" template for *Spec elements in mode "change" (which starts on line 510) and those in the mode "pass1" template for *Spec elements in mode "delete" (which starts on line 587).
I don't see how these would ever work if the base ODD being customized is not a TEI ODD. In which case, isn't this a bug?
I wonder, does this work for MEI at all? -- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived