Sorry then, please close. I was recursively dereferencing all define elements with a period in their @name and this was the only such definition that was circular.
Last edit: Jens Østergaard Petersen 2014-11-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What I was thinking was, since you can reference any text node as <text/>, and anyXML is any element node (not in the tei or teix namespace), it would be nice if you could express macro.anyXML as something like <element/> and be released from the circularity?
Last edit: Jens Østergaard Petersen 2014-11-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
because its recursive, not circular. each of the <element> itself has a content model of element/text, and the element therein has the same content model. etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
thats entirely normal. similarly, <hi> can contain <hi> ad nauseam.</hi></hi>
there are many problems with macro.anyXML, but this isn't one of them
Sorry then, please close. I was recursively dereferencing all define elements with a period in their @name and this was the only such definition that was circular.
Last edit: Jens Østergaard Petersen 2014-11-05
What I was thinking was, since you can reference any text node as <text/>, and anyXML is any element node (not in the tei or teix namespace), it would be nice if you could express macro.anyXML as something like <element/> and be released from the circularity?
Last edit: Jens Østergaard Petersen 2014-11-05
because its recursive, not circular. each of the
<element>itself has a content model of element/text, and the element therein has the same content model. etc.