Greetings, Council! We need one representative from Council to serve on a
little three-person committee to award the Rahtz Prize for TEI Ingenuity
<https://tei-c.org/activities/rahtz-prize-for-tei-ingenuity/> for 2023: one
from Council, one from Board, and one who won the award in a previous
cycle. Apparently we have a proud tradition of always running late in the
posted cycle--but we do need to get started quickly! I understand that the
little committee needs to form and issue a call for applications, likely by
early August and then start reviewing them to make a decision by the time
of the TEI / MEC conference.
This involves looking for applications, reviewing submissions and that
we'll typically announce the winner at the TEI Conference in the Annual
General Meeting. So long as you have not served on the committee 4 times
already, you're eligible to represent Council.
Are you interested in serving on the Rahtz committee to represent the
Council? If so reply to this and let me know--probably in course of the
next week--say before July 27, okay? I am willing to serve in this capacity
but I wanted to ask the group first--I am also going to be crazy busy in
August getting ready for my university classes (which start 21 August) and
the Council F2F. I'd be super grateful for anyone with a more peaceful
August schedule who is willing to serve on this committee!
Thanks,
Elisa
--
Elisa Beshero-Bondar, PhD
TEI Technical Council Chair
Program Chair of Digital Media, Arts, and Technology | Professor of Digital
Humanities | Director of the Digital Humanities Lab at Penn State Erie,
The Behrend College
Development site: https://newtfire.org
Magic removal time!
OMG, I am so excited. But I have to prep slides for tomorrow, no time to do this now. Thus I am writing some notes here.
See https://tei-c.org/Vault/P5/4.6.0/doc/tei-p5-doc/en/html/ref-TEI.html. Note that there is a proper namespace declaration in both examples. How the BLEEP did it get there? We cannot put a namespace declaration for the empty namespace on an element in an <eg:egXML> (unless it is on an element that has an explicit prefix), because its contents need to be in the eg: namespace.
The answer is that there is magic in the Stylesheets.[1]
Now take a look at https://www.wwp.neu.edu/outreach/seminars/miami_2023-07/presentations/manus…. The source for that slide uses <egMarkup>, an element that has the same kind of namespace specification restriction. So how did the namespace declaration get there?
Simple. So simple I am annoyed at myself for not thinking of this long ago. In the source it is not a namespace declaration, it is an xmlns attribute in a namespace. Thus it makes it to the Stylesheet as an attribute node and can be processed like any other attribute. The special case in the stylesheet that processes that slide is simple, straightforward, and easy to document: “An attribute in the duck: namespace has its prefix stripped off before it is rendered in the output”.
Note
[1] Particularly in Stylesheets/common/verbatim.xsl, starting at roughly line 463.
