I'd second what Lou suggest and use <ptr/> and you can even
document how the private URI is to be expanded in the header.
Another possibility is an XML processing instruction... but that
seems worse to me than using a <ptr/> since it always feels
outside the markup to me.
On 03/04/13 15:31, Lou Burnard wrote:
> Interesting question! We do something a bit like this in ODD,
> whereby a <specList> is processed to find the language-specific
> <desc> for the element cited. But that requires us to maintain
> all the language variations within each element spec, which (we
> are now realising) is a maintenance nightmare.
> I think the best we can do for you in unmodified TEI is <ptr>
> Something like <ptr type="helpText" ref="uri::my:magicCode"/>
> ought to use "magicCode" to go and find the value required at
> this point (the value of @ref is a URI which can use any of the
> many wild and wonderful syntaxes listed at eg
> The behaviour of the TEI stylesheets (transforming them into a
> link to the parent::div/head ) is entirely customisable : that's
> one reason there's a @type attribute on <ptr> so you shouldn't
> let that stop you.
> Otherwise, you might consider using xInclude.
> I don't know whether the ITS tagset ( http://www.w3.org/TR/its/)
> provides an easier solution
> On 03/04/13 15:09, Benjamin Wolff Bohl wrote:
>> Hi TEI-L:isteners,
>> currently I am working on a "born digital" document that is
>> designatedto become the help/documentation file of our
>> software. Doing this in TEI I would like to ease later
>> overhauling by inserting placeholders that will get values
>> assigned from another file (e.g. the software's lang file with
>> all button and mouseover texts etc.) on transformation to an
>> output format.
>> As I would like to do this as TEI conformant as possible I am
>> looking for a tag that could make up for the placeholder and
>> could appear anywhere common text can appear.
>> My first thoughts wen't in the direction of tei:ptr or similar,
>> as the TEI stylesheets provide templates for transforming them
>> into links with a target tei:div's tei:head string value. Then
>> again, I don't want all the occurences of a certain
>> <placeholder> to becom links; sometimes I just want to have the
>> possibility to alter the string value just in one place. So my
>> second thought was tei:rs but that somehow seems wrong as I
>> don't want to mark an arbitrary word as referencing somewhere,
>> but an empty element standing for a certain
>> Can you give me a hint?
>> Does anyone deal with such things?
>> Best wishes,
Dr James Cummings, [log in to unmask]
Academic IT Services, University of Oxford