I am getting the above error again (see earlier mail exchange at https://listserv.brown.edu/archives/cgi-bin/wa?A2=TEI-L;72ebf1f5.1512) when I generate a schema with elements in our own namespace. This time around, I do need the xenoData element, so the workaround of removing that element doesn’t work. Nor do I want to use the workaround of telling oXygen not to do ID/IDREF checking, because then it would still regularly pop-up for new encoders.
From the references to the council mailing list and the github issue in the previous mail round, I understand that I should redefine the content of xenoData to exclude anything that is in our own (non-TEI) namespace.
So, given that the actual work for defining xenoData happens in anyElement-xenoData, I need to redefine that in my ODD.
This is where I get stuck, because I have no idea what sort of thing anyElement-xenoData is, and how it would fit in an ODD. Is it a macro? I don’t see it on http://www.tei-c.org/release/doc/tei-p5-doc/en/html/REF-MACROS.html. I see a definition in the generated rng schema (a define element) but it is unclear to me how that would fit in an ODD.
My impression at the time was that the error had been resolved, but if it isn’t, can someone tell me how I should change my ODD to avoid it?
Huygens Institute for the History of the Netherlands (Royal Netherlands Academy of Arts and Sciences)
Tel.: +31 20 2246825