#158 modify language in Guidelines, range() vs. targetEnd

Dot Porter

When I asked on the TEI listserv about possibly having @targetEnd added to <ref> (so I could note any arbitrary span of text) I was told that instead we should be using target="range()". It appears that @target+@targetEnd has been depreciated in favor of target="range()", but if so the Guidelines do not reflect this.

(thread begins here: http://listserv.brown.edu/archives/cgi-bin/wa?A2=ind0811&L=TEI-L&P=R6545\)

The request is to update the language in the Guidelines to specifically recommend ref@target='range()', and to change the description of <note> to say that @targetEnd is depreciated and @target='range()' is preferred to @targetEnd for new encoding.


  • Lou Burnard

    Lou Burnard - 2009-01-14
    • milestone: --> GREEN
  • Lou Burnard

    Lou Burnard - 2009-01-14

    Your suggestion makes good sense and I see no reason not to implement it. We should probably scan through for any other similar ambiguities.

  • Peter Boot

    Peter Boot - 2009-01-14

    range() as the recommended way of doing things is OK, but deprecating @targetEnd seems too early (while there is no software that exploits the xpointer schemes).

  • Lou Burnard

    Lou Burnard - 2009-01-23
    • status: open --> closed
  • Lou Burnard

    Lou Burnard - 2009-01-23

    Added the following remarks to the element spec:

    This attribute is retained for backwards compatibility; it
    may be removed at a subsequent release of the Guidelines. The
    recommended way of pointing to a span of elements is by means
    of the <ident>range</ident> function of XPointer, as further
    described in <ptr target="#SATSRN"/>.

    and removed the reference to this attribute in CO. The only other reference in the Guidelines is in a deeply murky section of SA (#SAPTIP) which I have tried to tidy up, but needs much more work and raises some difficult problems.

    But this particular request can be closed as of revision 5501


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks