I really think you've chosen a bad example here Stuart. Implementing
cRefpattern, if it means anything, means translating a standard regular
expression into a standard XPath. What you do with the XPath and how you
do the translation is up to the implementor, who is under no obligation
to tell the rest of the world about their choices (though obviously we'd
like it if they did) You might as well complain that there's no known
"implementation" of (insert name of any arbitrary feature not currently
treated by Sebastian's stylesheets -- how about @citRef) because a
implementor has to decide all on their own what HTML tag to map it to.
There there, never mind. At least its (note spelling) semantics are
entirely clear and fully specified in the Guidelines! (which is, as Syd
reminds us, what the Guidelines are intended to do)
On 25/01/13 23:22, stuart yeates wrote:
> On 26/01/13 11:58, Sebastian Rahtz wrote:
>> On 25 Jan 2013, at 22:50, "stuart yeates" <[log in to unmask]> wrote:
>>> I would like to propose a new note on the definition of
>>> There are no known implementations of cRefPattern, so it's
>>> usefulness is primarily theoretical. Reports of implementations are
>>> welcome on the TEI mailing list.
>> Oh dear. If we start down that line, what's the definition of an
>> implementation? And to how many other tags would it apply?
>> Nice idea though.... Bring on the howling protests from the "there is
>> no beast as a tei implementation" faction.
> You're welcome to recast the note without term you find offensive, but
> neglecting to warn newbie users of serious issues just because the
> grey-beards have a terminological quandary is asking for TEI to become
> a cul de sac.