[tei-council] macro.anyXML

[Sebastian Rahtz]

Namespace prefixes dont have to be humanly readable or the same all the time. Do they map to the right thing?

Carved in stone on my iPad

On 2 Apr 2013, at 00:14, "Martin Holmes" <mholmes at uvic.ca> wrote:

> When I look at the ref page for macro.anyXML, I see something that looks 
> a bit weird:
> 
> macro.anyXML =
>    element * - (d36e2:* | d226960e7a3528:egXML)
>    {
>       attribute * { text }*,
>       ( text | macro.anyXML )*
>    }
> 
> I think those strange namespace prefixes must be accidental artifacts of 
> the processing; the spec itself specifies any element except for <egXML> 
> in the Examples namespace. In the latest Jinks build, the prefixes 
> differ slightly from those in the release, so I think they're 
> auto-generated by XSLT somehow.
> 
> Should I raise a bug, or am I missing something?
> 
> Cheers,
> Martin
> -- 
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
> 
> PLEASE NOTE: postings to this list are publicly archived