[tei-council] macro.anyXML

[Martin Holmes]

On 13-04-01 04:24 PM, Sebastian Rahtz wrote:
> Namespace prefixes dont have to be humanly readable or the same all the time. Do they map to the right thing?

I think they map to the right thing in the context of any given build of 
the Guidelines, but I was looking at the reference page from the point 
of view of its being documentation for regular users. There's no way to 
tell what they map to from the HTML page. I wonder if it might be better 
to use Clark Notation for namespaces in the HTML output?

Cheers,
Martin

>
> 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