<?tei:SOF p2sapt.odd ?>
<!-- $Id: p2sapt.odd,v 1.10 1998/02/05 17:14:35 tei Exp $ -->
<!--*
    * $Log: p2sapt.odd,v $
    * Revision 1.10  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.9  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.8  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.7  1994/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.6  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * 
    * Revision 1.5  1994/02/12  10:22:43  lou
    * reviions for P3
    * 
    * Revision 1.3  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * -->
<!-- Revisions:                                               -->
<!-- 94-04-08 : MSM : linkGrp has no TYPE att, but inherits it from POINTER -->
<!-- 94-04-08 : MSM : change tagdesc and add adlist to show this\ -->
<!-- 94-04-08 : MSM : .                                       -->
<!-- 94-03-26 : MSM : typos from HG, DB, SJ                   -->
<!-- 94-03-26 : MSM : disambiguate TERM, Q (code, ident ...)  -->
<!-- 4 feb 94 : LB tidied up structure; reverted some changes -->
<!-- 20 dec 93: LB: changed grouper to ptrgroup -->
<!-- 93-09-15 : MSM : minor SGML cleanup                      -->
<!-- 93-07-21 : DTL : add discussion of < ptr> within < linkGrp> -->
<!--                   in SAptip (per Eynsham suggestion)     -->
<!--                  change argTypes= to targFunc=           -->
<!-- 93-07-16 : DTL : use the term "connected" rather than    -->
<!--                   "linked" to describe the result of     -->
<!--                   pointing, to avoid confusion between   -->
<!--                   two senses of "link" noted by LB       -->
<!--                  make other small corrections and changes -->
<!-- 93-07-12 : DTL : create grouper class, query editors on  -->
<!--                   a vexing question                      -->
<!-- 93-07-08 : DTL : describe < linkGrp> attributes, correct -->
<!--                   typo in first < linkGrp> example       -->
<!--                  add targOrder= to first < link> example -->
<!-- 93-07-07 : DTL : elaborate < linkGrp> definition         -->
<!--                  clarify distinction between "pointing"  -->
<!--                   and "pointer"; similarly between       -->
<!--                   "linking" and "link".                  -->
<!--                  make numerous other revisions           -->
<!--                  "Multi-headed" renamed "Intermediate",  -->
<!--                  rename section and make into a div3     -->
<!--                  modify tagging of Pope examples         -->
<!-- 93-01-26 : MSM : last chance revisions                   -->
<!-- 93-01-22 : MSM : once more lightly                       -->
<!-- 93-01-18 : MSM : rev more thoroughly                     -->
<!-- 93-01-12 : MSM : revise for publication                  -->
<!-- 92-12-23 : MSM : strip header                            -->
<!-- Date: Wed, 23 Dec 1992 14:25:19 +0000                    -->
<!-- From: Lou Burnard <lou@vax.ox.ac.uk>                     -->
<!-- To: U35395@UICVM.UIC.EDU                                 -->
<!-- Subject: sapt.odd (4 of 9)                               -->
 
<!-- 21 Dec 92: some changes in wording following comments from SR & MSM -->
 
<div2 id=SAPT><head>Pointers</head>
 
<p>We say that one element <term rend=noindex>points</term> to others if
the first has an attribute whose value is a reference to the others:
such an element is called a <term>pointer element</term>, or simply a
<term>pointer</term>.  Among the pointers that have been introduced up
to this point in these Guidelines are <gi>note</gi>, <gi>ref</gi> and
<gi>ptr</gi>.  These elements all indicate an association between one
place in the document (the location of the pointer itself) and one or
more others (the elements whose identifiers are specified by the
pointer's <att>target</att> attribute).  This element set defines a
variation on this basic kind of pointer, known as a <term>link</term>
which specifies both <soCalled>ends</soCalled> of an association.  In
addition, we define a syntax for representing locations in a document by
a variety of means not dependent on the use of SGML identifiers.
 
<div3 id=SAPTL><head>Pointers and Links</head>
 
<p>In section <xref target=COXR> we introduced the simplest pointer
elements, <gi>ptr</gi> and <gi>ref</gi>.  Here we introduce additionally
the <gi>link</gi> element, which represents an association between two
(or more) locations by specifying each location explicitly.  Its own
location is irrelevant to the intended linkage.
 
<tagList>
<tagDesc tagDoc=PTR atts='target'>
<tagDesc tagDoc=REF atts='target'>
<tagDesc tagDoc=LINK atts='targets'>
</tagList>
 
The <gi>ptr</gi> element may be called a <soCalled>pure
pointer</soCalled>, because its primary function is simply to point.  A
pointer sets up a <term rend=noindex>connection</term> between an
element (which, in the case of a pure pointer, can be thought of simply
as a location in a document), and one or more others, known collectively
as its <term>target</term>.
 
<!--Following para deleted by DTL but restored -->
 
The <gi>ptr</gi> and <gi>ref</gi> elements bear a <att>target</att>
attribute (in the singular), because they point, conceptually, at a
single target, even if that target may be discontinuous in the document.
The <gi>link</gi> element bears a <att>targets</att> attribute, with a
plural name, because it specifies at least two targets, each of which is
a unitary object.  It may be thought of as a representing a <term>double
link</term> between the objects specified.
 
<p>As members of the class <ident type=class>pointer</ident>, these
elements share a common set of attributes:
 
<adList classDoc=POINTER
        atts="type resp crdate targType targOrder evaluate">
 
<!--      Currently the pointer class is:                     -->
<!--      ptr       (SApt)                                    -->
<!--      ref       (SApt)                                    -->
<!--      link      (SApt)                                    -->
<!--      xptr      (SAxr)                                    -->
<!--      xref      (SAxr)                                    -->
<!--      join      (SAag)                                    -->
<!--      alt       (SAat)                                    -->
 
<!-- added following clarification (LB) -->
 
<p>The <att>targType</att> and <att>targOrder</att> attributes may be
used to constrain the scope of a link to certain element types.  For
example:
 
<eg>
<![ CDATA [
<link type='echo' targets='P1 P2'>
]]>
</eg>
 
This is a complete unconstrained link, of type <code
type=value>echo</code>.  It assumes only that there is an element with
identifier <code type=value>P1</code> and another with identifier <code
type=value>P2</code> somewhere in the current document.
 
<eg>
<![ CDATA [
<link type='echo' targType='p seg note' targets='P1 P2'>
]]>
</eg>
 
This is a slightly more constrained link of the same type.  P1 and P2
must now both identify a <gi>p</gi>, a <gi>seg</gi>, or a <gi>note</gi>,
but there is no requirement as to which is which.  (This may be useful
if, as is often the case, different elements may participate in the same
kind of link.)
 
<eg>
<![ CDATA [
<link type='echo' targType='p note' targOrder=Y targets='P1 P2'>
]]>
</eg>
 
In this variation, not only must the link targets be either <gi>p</gi>
or <gi>note</gi> elements, but the one with identifier <code
type=value>P1</code> must be a <gi>p</gi>, and that with identifier
<code type=value>P2</code> must be a <gi>note</gi>.  Note that the
present Guidelines provide no direct way of saying that <code
type=value>P1</code> may identify either a <gi>seg</gi> or a <gi>p</gi>
and <code type=value>P2</code> must identify a <gi>note</gi>.
 
<p>These attributes are most useful if applied to a group of links, when
additional constraints may also be specified, as further discussed in
section <xref target=SAPTLG> below.
 
<!-- note from Terry deleted here -->
 
<p>Double connection among elements could also be expressed by a
combination of pointer elements, for example, two <gi>ptr</gi> elements,
or one <gi>ptr</gi> element and one <gi>note</gi> element.  All that is
required is that the value of the <att>target</att> (or other pointing)
attribute of the one be the value of the <att>id</att> attribute of the
other.  What the <gi>link</gi> element accomplishes is the handling of
double connection by means of a single element.  Thus, in the following
encoding:
 
<eg>
<![ CDATA [
  <ptr id=P1 target=P2> .....  <ptr id=P2 target=P1>
]]>
</eg>
 
P1 points to P2, and P2 points to P1.  This is logically equivalent to
the more compact encoding:
 
<eg>
<![ CDATA [
  <link targets='P1 P2'>
]]>
</eg>
 
<p>As noted above, all elements pointed to or linked by these elements
must be identifiable using the global <att>id</att> attribute.  This
implies that they must be present in the same document, and that they
must bear unique <att>id</att> values.  Pointing or linking to external
documents and pointing or linking where SGML identifiers are not
available is implemented by the external pointing mechanisms discussed
in section <xref target=SAXR>, where the <gi>xptr</gi> and <gi>xref</gi>
elements are discussed.  External links and links involving elements
without identifiers do not require a special element; they may be
represented using the standard <gi>link</gi> element, but an
intermediate <gi>xptr</gi> element must be provided within the current
document, to bear the <att>id</att> attribute used in the target of the
link.
 
<div3 id=SAPTEG><head>Using Pointers and Links</head>
 
<p>As an example of the use of these mechanisms which establish
connections among elements, consider the practice (common in 18th
century English verse and elsewhere) of providing footnotes citing
parallel passages from classical authors.
<figure id='POPE' rend='float fullpage'>
<figDesc>The figure shows the original page of Pope's
<title>Dunciad</title> which is discussed in the text.</figDesc>
</figure>
Such footnotes can of course simply be encoded using the <gi>note</gi>
element (see section <xref target=CONO>) without a <att>target</att>
attribute, placed adjacent to the passage to which the note refers:<note
place=foot>The <att>type</att> attribute on the note is used to classify
the notes using the typology established in the Advertisement to the
work:  <q>The <term rend=noindex>Imitations</term> of the Ancients are
added, to gratify those who either never read, or may have forgotten
them; together with some of the Parodies, and Allusions to the most
excellent of the Moderns.</q> In the source text, the text of the poem
shares the page with two sets of notes, one headed <q>Remarks</q> and
the other <q>Imitations</q>.</note>
 
<eg>
<![ CDATA [
<l>(Diff'rent our parties, but with equal grace</l>
<l>The Goddess smiles on Whig and Tory race,</l>
<note type='imitation' place=foot anchored=no>
    <bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.</l></quote>
</note>
<l>'Tis the same rope at sev'ral ends they twist,</l>
<l>To Dulness, Ridpath is as dear as Mist)</l>
]]>
</eg><!-- Pope, Dunciad (1729) III.284 -->
 
<p>This use of the <gi>note</gi> element can be called <term>implicit
pointing</term> (or <term>implicit linking</term>).  It relies on the
juxtaposition of the note to the text being commented on for the
connection to be understood.  If it is felt that the mere juxtaposition
of the note to the text does not make it sufficiently clear exactly what
text segment is being commented on (for example, is it the immediately
preceding line, or the immediately preceding two lines, or what?), or if
it is decided to place the note at some distance from the text, then the
pointing or the linking must be made explicit.  We now consider various
methods for doing that.
 
<p>First, a <gi>ptr</gi> element might be placed at an appropriate point
within the text to link it with the annotation:
 
<eg>
<![ CDATA [
<l>(Diff'rent our parties, but with equal grace</l>
<l>The Goddess smiles on Whig and Tory race,
<ptr rend='unmarked' target=N3.284></l>
<l>'Tis the same rope at sev'ral ends they twist,</l>
<l>To Dulness, Ridpath is as dear as Mist)</l>
<!-- elsewhere in the document ... -->
<note id=N3.284 type='imitation' place=foot anchored=no>
    <bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.</l></quote>
</note>
]]>
</eg><!-- Pope, Dunciad (1729) III.284 -->
 
The <gi>note</gi> element has been given an arbitrary identifier (<code
type=value>N3.284</code>) to enable it to be specified as the target of
the pointer element.  Because there is nothing in the text to signal the
existence of the annotation, the <att>rend</att> attribute has been
given the value <code type=value>unmarked</code>.
 
<!-- I don't understand the need for rend= here.  If there    -->
<!-- were a marker in the text, such as a footnote number     -->
<!-- or special sign, surely you wouldn't say, for example    -->
<!-- <ptr rend=dagger target=N3.284>. (DTL)                   -->
<!-- why ever not? LB -->
 
<p>Second, the <att>target</att> attribute of the <gi>note</gi> element
can be used to point at its associated text, provided that an
<att>id</att> attribute has been supplied for the associated text.
Since, in this case, the note itself contains a pointer to the place in
the text which it is annotating, this has also been encoded, using a
<gi>ref</gi> element, which bears a <att>target</att> attribute of its
own and contains a (slightly misquoted) extract from the text marked as
a <gi>quote</gi> element:
 
<eg>
<![ CDATA [
<!--  ... -->
<note target=L3.284
    type='imitation' place=foot anchored=no>
    <ref target='L3.284' rend='sc'>
    Verse 283-84.
    <quote><l>&mdash;&mdash;. With equal grace
        </l><l>Our Goddess smiles on Whig and Tory race.
     </l></quote></ref>
    <bibl>Virg. &AElig;n. 10.</bibl>
    <quote>
    <l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.
    </l></quote>
</note>
]]>
</eg><!-- Pope, Dunciad (1729) III.284 -->
 
<!-- SJ asks what rend='sc' means.  no action taken (msm)     -->
<!-- material deleted -->
<!-- An SGML identifier has been given to each line, for      -->
<!-- convenience in transcribing other commentaries, even     -->
<!-- though in this example the note points only at line      -->
<!-- L3.284.                                                  -->
<!-- End material deleted -->
 
<p>Combining these two solutions gives us the following associations:
 
<list>
<item>a pointer within one line indicates the note
<item>the note indicates the line
<item>a pointer within the note indicates the line
</list>
 
Note that we do not have any way of pointing from the line itself to the
note:  the association is implied by containment of the pointer.  We do
not as yet have a true double link between text and note.
 
<!-- deleted DTL's third example -->
 
<p>Thirdly, therefore, we supply identifiers for both verse line and
annotation, and use a <gi>link</gi> element to associate the two.  Note
that the <gi>ptr</gi> element and the <att>target</att> attribute on the
<gi>note</gi> may now be dispensed with:
 
<eg>
<![ CDATA [
<l id=L3.283>(Diff'rent our parties, but with equal grace</l>
<l id=L3.284>The Goddess smiles on Whig and Tory race,</l>
<l id=L3.285>'Tis the same rope at sev'ral ends they twist,</l>
<l id=L3.286>To Dulness, Ridpath is as dear as Mist)</l>
<!-- elsewhere in the document ... -->
<note id=N3.284
    type='imitation' place=foot anchored=no>
    <ref target='L3.284' rend='sc'>
    Verse 283-84.
    <quote><l>&mdash;&mdash;. With equal grace
           </l><l>Our Goddess smiles on Whig and Tory race.
    </l></quote>]</ref>
    <bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.
    </l></quote>
</note>
<!-- ... and yet elsewhere in the document ... -->
<link targType='note l' targOrder=Y targets='N3.284 L3.284'>
]]>
</eg><!-- Pope, Dunciad (1729) III.284 -->
 
<p>The <att>targets</att> attribute of the <gi>link</gi> element here
bears the identifiers of the note followed by that of the verse line.
The <att>targType</att> and <att>targOrder</att> attributes may be used
to enable application programs to check that the identifiers in fact
pick out a <gi>note</gi> element and an <gi>l</gi> element and in that
order.  If <att>targOrder</att> has the value <code type=value>N</code>,
then the elements indicated by the <att>targets</att> attribute have to
be either <gi>note</gi> or <gi>l</gi> elements, but are otherwise
unconstrained.  If neither attribute is present, then the only
constraint is that the identifiers given must apply to some element
within the current document.
 
<p>For completeness, we could also allocate an identifier to the
reference within the note and encode the association between it and the
verse line in the same way:
 
<eg>
<![ CDATA [
<!-- ... -->
<note id=N3.284 type='imitation' place=foot anchored=no>
    <ref id=R3.284 rend='sc'>
    <!-- ... -->
    </ref>
</note>
<!-- ... -->
<link targType='ref  l' targOrder=Y targets='R3.284 L3.284'>
]]>
</eg><!-- Pope, Dunciad (1729) III.284 -->
 
Indeed, the two <gi>link</gi>s could be combined into one, as follows:
 
<eg><![ CDATA [
<link targType='note ref l' targOrder=Y
      targets='N3.284 R3.284 L3.284'>
]]>
</eg>
 
<div3 id=SAPTLG><head>Groups of Links</head>
 
<!-- Material on <linkGrp> moved up from following section (DTL) -->
<!-- moved back! (LB) -->
 
<p>Clearly, there are many reasons for which an encoder might wish to
represent a link or association between different elements.  For some of
them, specific elements are provided in these Guidelines; some of these
are discussed elsewhere in the present chapter.  The <gi>link</gi>
element is a general purpose element which may be used for any kind of
association.  The element <gi>linkGrp</gi> may be used to group links of
a particular type together in a single part of the document; such a
collection may be used to represent what is sometimes referred to in the
literature of Hypertext as a <term>web</term>, a term introduced by the
Brown University FRESS project in 1969.
 
<tagList>
<tagDesc tagDoc=LINKGRP>
</tagList>
 
As a member of the class <ident type=class>pointerGroup</ident>, this
element shares the following attributes with other members of that
class:
 
<adList classDoc=PTRGROUP
        atts="domains targFunc ">
 
<!-- extendTarg"> killed by LB -->
<!--      linkGrp   (SApt)                                    -->
<!--      joinGrp   (SAag)                                    -->
<!--      altGrp    (SAat)                                    -->
 
It is also a member of the <ident type=class>pointer</ident> class, and
therefore also carries the attributes specified in section
<xref target=SAPTL> above, in particular the <att>type</att> attribute:
 
<adList classDoc=POINTER atts='type'>
 
<p>The <gi>linkGrp</gi> element provides a convenient way of
establishing a default for the <att>type</att> attribute on a group of
links of the same type:  by default, the <att>type</att> attribute on a
<gi>link</gi> element has the same value as that given for
<att>type</att> on the enclosing <gi>linkGrp</gi>.
 
<p>Typical software might hide a web entirely from the user, but use it
as a source of information about links, which are displayed
independently at their referenced locations.  Alternatively, software
might provide a direct view of the link collection, along with added
functions for manipulating the collection, as by filtering, sorting, and
so on.
 
<!-- <p>If many <tag>link</tag> tags are used, they may be    -->
<!-- grouped together within a <tag>linkGrp</tag>, and the    -->
<!-- attributes of that tag used to make precise how all the  -->
<!-- links are to be understood.                              -->
 
To continue our previous example, this text contains many other notes,
of a kind similar to the one shown above.  To avoid having to repeat the
<att>type=imitation</att> on each <gi>note</gi>, we may specify it once
for all on a <gi>linkGrp</gi> element containing all links of this type.
The <att>targType</att> and <att>targOrder</att> attributes can also be
specified for a <gi>linkGrp</gi> element:
 
<eg>
<![ CDATA [
<l id=L2.79>A place there is, betwixt earth, air and seas</l>
<l id=L2.80>Where from Ambrosia, Jove retires for ease.</l>
<l> ...
<l id=L2.88>Sign'd with that Ichor which from Gods distills.</l>
<l> ...
<l id=L3.283>(Diff'rent our parties, but with equal grace</l>
<l id=L3.284>The Goddess smiles on Whig and Tory race,</l>
<l id=L3.285>'Tis the same rope at sev'ral ends they twist,</l>
<l id=L3.286>To Dulness, Ridpath is as dear as Mist)</l>
<!-- ... -->
<!-- elsewhere in the document ... -->
<note id=N2.79 place=foot anchored=no><bibl>Ovid Met. 12.</bibl>
    <quote lang=la>
        <l>Orbe locus media est, inter terrasq; fretumq;
        </l><l>C&oelig;lestesq; plagas &mdash;
    </l></quote>
</note>
<note id=N2.88 place=foot anchored=no>
    Alludes to <bibl>Homer, Iliad 5</bibl>
<!-- .... -->
</note>
<!-- ... -->
<note id=N3.284 place=foot anchored=no><bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.
    </l></quote>
</note>
<!-- ... -->
<!-- yet elsewhere in the document ... -->
<linkGrp type='imitation' targType='note l' targOrder=Y>
  <link targets='N2.79 L2.79'>
  <link targets='N2.88 L2.88'>
  <!-- ... -->
  <link targets='N3.284 L3.284'>
  <!-- ... -->
</linkGrp>
]]>
</eg>
 
<p>Additional information for applications that use <gi>linkGrp</gi>
elements can be provided by means of special attributes.  First, the
<att>domains</att> attribute can be used to identify the text elements
within which the individual targets of the links are to be found.
Suppose that the text under discussion is organized into a <gi>body</gi>
element, containing the text of the poem, and a <gi>back</gi> element
containing the notes.  Then the <att>domains</att> attribute can have as
its value the identifiers of the <gi>body</gi> and the <gi>back</gi>, to
enable an application to verify that the link targets are in fact
contained by appropriate elements, or to limit its search space:
 
<eg>
<![ CDATA [
<body id=DUNCIAD>
<!-- .... -->
<l id=L2.79>A place there is, betwixt earth, air and seas</l>
<l id=L2.80>Where from Ambrosia, Jove retires for ease.</l>
<l> ...
<l id=L2.88>Sign'd with that Ichor which from Gods distills.</l>
<l> ...
<l id=L3.283>(Diff'rent our parties, but with equal grace</l>
<l id=L3.284>The Goddess smiles on Whig and Tory race,</l>
<l id=L3.285>'Tis the same rope at sev'ral ends they twist,</l>
<l id=L3.286>To Dulness, Ridpath is as dear as Mist)</l>
<!-- ... -->
</body>
<back>
<div type="Notes" id=DUNNOTES><head>Notes to the Dunciad</head>
<!-- ... -->
<note id=N2.79 place=foot anchored=no><bibl>Ovid Met. 12.</bibl>
    <quote lang=la><l>
        Orbe locus media est, inter terrasq; fretumq;
        </l><l>C&oelig;lestesq; plagas &mdash;
    </l></quote>
</note>
<note id=N2.88 place=foot anchored=no>
    Alludes to <bibl>Homer, Iliad 5</bibl>
<!-- .... -->
</note>
<!-- ... -->
<note id=N3.284 place=foot anchored=no><bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.
    </l></quote>
</note>
<!-- ... -->
</back>
<!-- elsewhere in the document ... -->
<linkGrp type='imitation'
         domains='dunciad dunnotes'
         targType='note l'
         targOrder=Y>
  <link targets='N2.79 L2.79'>
  <link targets='N2.88 L2.88'>
  <!-- ... -->
  <link targets='N3.284 L3.284'>
  <!-- ... -->
</linkGrp>
]]>
</eg>
 
<p>Note that there must be a single parent element for each
<soCalled>domain</soCalled>; if some notes are contained by a section
with identifier <code type=value>dunnotes</code>, and others by a
section with identifier <code type=value>dunimits</code>, an
intermediate pointer must be provided (as described in section <xref
target=SAPTIP>) within the <gi>linkGrp</gi> and its identifier used
instead.
 
<!-- and where does the linkGrp go itself? -->
 
<p>Next, the <att>targFunc</att> attribute can be used to provide
further information about the role or function of the various targets
specified for each link in the group.
 
<!-- type of link being used in that particular -->
<!-- gi>linkGrp</gi> tag beyond that which is provided by the -->
<!-- <att>type</att> and <att>targType</att> attributes.   -->
 
The value of the <att>targFunc</att> attribute is a list of names
(formally, SGML name tokens), one for each of the targets in the link;
these names can be chosen freely by the encoder, but their significance
should be documented in the encoding declaration in the header.<note>No
special element is provided for this purpose at present:  the
information should be supplied as a series of paragraphs at the end of
the <gi>encodingDesc</gi> element described in section <xref
target=HD5>.</note>  In the current example, we might think of the note
as containing the <term rend=noindex>source</term> of the imitation and
the verse line as containing the <term rend=noindex>goal</term> of the
imitation.  Accordingly, we can specify the <gi>linkGrp</gi> in the
preceding example thus:
 
<eg><![ CDATA [
<linkGrp type='imitation'
         domains='dunciad dunnotes'
         targType='note l'
         targFunc='source goal'
         targOrder=Y>
  <link targets='N2.79 L2.79'>
  <link targets='N2.88 L2.88'>
  <!-- ... -->
  <link targets='N3.284 L3.284'>
  <!-- ... -->
</linkGrp>
]]>
</eg>
 
<!-- extendTarg attribute axed by LB pending further clarification -->
 
 
<!-- <p>Finally, the <att>extendTarg</att> attribute can be used -->
<!-- to combine links which share one or more target -->
<!-- identifiers.  Suppose that more than one different verse -->
<!-- line may imitate the same classical source as recorded in a -->
<!-- single note; in particular suppose that not only line L2.79, -->
<!-- but also lines 2.302 and L3.154 imitate the Ovid passage -->
<!-- quoted in note N2.79. -->
 
<!-- <note place=foot>For purposes of this illustration, -->
<!-- assume that the notes are not explicitly tied to the -->
<!-- verse lines in any way (in particular, that the notes do not -->
<!-- contain cross-references to the verse lines), as if the -->
<!-- author of the verse and the notes were challenging the -->
<!-- reader to discover the links between them.  The encoder in -->
<!-- this case may be considered to be recording the scholarship -->
<!-- of the critic NPR in figuring out the links between the text -->
<!-- and the notes.</note> -->
 
<!-- <p>These can be recorded as separate links, thus: -->
 
<!-- <eg><![ CDATA [ -->
<!-- <link resp=NPR targets='N2.79 L2.79'> -->
<!-- <link resp=NPR targets='N2.79 L2.302'> -->
<!-- <link resp=NPR targets='N2.79 L3.154'> -->
<!-- ]]> -->
<!-- </eg> -->
 
<!-- <p>Alternatively, if the <att>extendTarg</att> attribute is -->
<!-- given the value <term>2</term>, meaning that the second -->
<!-- target (consisting of pointers to verse lines) can be -->
<!-- <term>extended</term> with additional values, then the three -->
<!-- <gi>link</gi> tags can be combined into one: -->
 
<!-- <eg><![ CDATA [ -->
<!-- <linkGrp resp=NPR -->
<!--          type='imitation' -->
<!--          domains='dunciad dunnotes' -->
<!--          targType='note l' -->
<!--          targFunc='source goal' -->
<!--          targOrder=Y -->
<!--          extendTarg=2> -->
<!--   <link targets='N2.79 L2.79 L2.302 L3.154'> -->
<!--   <link targets='N2.88 L2.88'> -->
<!--    ... -->
<!--   <link targets='N3.284 L3.284'> -->
<!--    ... -->
<!-- </linkGrp> -->
<!-- ]]> -->
<!-- </eg> -->
 
<!-- <p>The default value of the <att>extendTarg</att> -->
<!-- attribute is 0, which means that the number of targets -->
<!-- in each <gi>link</gi> element should exactly match the number -->
<!-- of arguments in the <att>domains</att>, <att>targType</att> -->
<!-- and <att>targFunc</att> attributes (which should also all -->
<!-- match each other no matter what the value of the -->
<!-- <att>extendTarg</att> attribute is). -->
 
<p>The <gi>link</gi> and <gi>linkGrp</gi> elements are formally defined
as follows:
 
<dtdFrag id=DSAPT n='Links'>
<tagDecl tagDoc=LINK>
<tagDecl tagDoc=LINKGRP>
</dtdFrag>
 
<div3 id=SAPTIP><head>Intermediate Pointers</head>
 
<p>In the preceding examples, we have shown various ways of linking an
annotation and a single verse line.  However, the example cited in fact
requires us to encode an association between the note and a
<emph>pair</emph> of verse lines (lines 284 and 285).
 
<p>There are a number of possible ways of correcting this error:  one
could use the <att>target</att> and <att>targetEnd</att> attributes of
the <gi>note</gi> element to delimit the span to which the note applies
(see further section <xref target=CONO>).  Alternatively one could
create an element to encode the couplet itself and assign it an
<att>id</att> attribute, which can then be linked to the <gi>note</gi>
and <gi>ref</gi> elements.  This could be done either explicitly by
means of a <gi>lg</gi> element, as defined in section <xref
target=COVE>, or a <gi>seg</gi> element, as defined in section <xref
target=SASE>, or implicitly, by means of the <gi>join</gi> element
discussed in section <xref target=SAAG>.
 
<p>A third possibility however, is to use an <soCalled>intermediate
pointer</soCalled> as follows:
 
<eg>
<![ CDATA [
<l id=L3.283>(Diff'rent our parties, but with equal grace</l>
<l id=L3.284>The Goddess smiles on Whig and Tory race,</l>
<!-- ... -->
<ptr id=L3.283284 target='L3.283 L3.284' targOrder=Y >
]]>
</eg>
 
<!-- sentence deleted by Terry but restored by LB -->
 
When the <att>target</att> attribute of a <gi>ptr</gi> or <gi>ref</gi>
element specifies more than one element, the indicated elements are
always understood to be combined or aggregated in some way to produce
the object of the pointer.
 
<p>In this example, the <att>targOrder</att> attribute should be
specified to indicate that the order in which identifier values are
supplied in the <att>target</att> attribute is significant.  The
<att>id</att> attribute provides an identifier which can then be linked
to the <gi>note</gi> and <gi>ref</gi> elements:
 
<eg>
<![ CDATA [
<link targets='N3.284 R3.284 L3.283284'
      targType='note ref ptr' evaluate=all>
]]>
</eg><!-- Pope, Dunciad (1729) III.284 -->
 
<p>The <att>evaluate=all</att> attribute value is used on the
<gi>link</gi> element to specify that any pointer encountered as a
target of that element is itself evaluated.  If <att>evaluate</att> had
the value <code type=value>none</code>, the link target would be the
pointer itself, rather than the objects it points to.
 
<p>Where a <gi>linkGrp</gi> element is used to group a collection of
<gi>link</gi> elements, any intermediate pointer elements used by those
<gi>link</gi> elements should be included within the <gi>linkGrp</gi>.
 
<p>Intermediate pointers of this kind are particularly important when
extended pointers (discussed in the next section) are in use.
 
<!-- material deleted by Terry and not yet restored -->
<!-- <p>This use of<soCalled>multi-headed< /soCalled>      -->
<!-- pointing should be carefully distinguished from that     -->
<!-- used by the<att>targets< /att> attribute of the<     -->
<!-- gi>link< /gi> element.  As the attribute name            -->
<!-- suggests, in the latter case, the indicated elements     -->
<!-- are not simply combined together as if they were a       -->
<!-- single target, but associated in some respect,           -->
<!-- specifically, that indicated by the<att>type< /att>    -->
<!-- attribute.  Crucially, the intended relationship         -->
<!-- between every item in a list of identifiers must be      -->
<!-- identical.  To represent the link discussed above as     -->
<!-- follows would be erroneous:                              -->
 
<!-- <eg >                                                   -->
<!-- <![ CDATA [                                             -->
<!-- <link type=imitation targets='N3.284 L3.283 L3.284' >   -->
<!-- ]] >                                                     -->
<!-- </eg >                                                  -->
 
<!-- This is not correct, because the association between     -->
<!-- N3.284 and L3.284 (the note and one line of text) is     -->
<!-- not of the same kind as that between L3.283 and L3.284   -->
<!-- (the two lines of text).  A processor cannot be          -->
<!-- expected to process this kind of target list             -->
<!-- correctly.  To represent the link correctly, an          -->
<!-- intermediate pointer or a virtual element must be        -->
<!-- introduced as discussed above.                           -->
<!-- End material deleted -->
 
<?tei:EOF p2sapt.odd ?>
