LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  November 1991

TEI-L November 1991

Subject:

%% Undelivered Mail %%

From:

[log in to unmask]

Reply-To:

[log in to unmask]

Date:

Mon, 25 Nov 1991 19:29:00 GMT

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (241 lines)

Your mail was not delivered as follows:
%MAIL-E-SENDERR, error sending to user ELS009
-MAIL-E-OPENOUT, error opening DISK$EL:[ELS009]MAIL.MAI; as output
-SYSTEM-F-IVDEVNAM, invalid device name
%MAIL-E-SENDERR, error sending to user ELS009
-MAIL-E-OPENOUT, error opening DISK$EL:[ELS009]MAIL.MAI; as output
-SYSTEM-F-IVDEVNAM, invalid device name
 
Your original mail header and message follow.
 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Via: UK.AC.EARN-RELAY; Mon, 25 Nov 91 19:29 GMT
Received: from UKACRL by UK.AC.RL.IB (Mailer R2.07) with BSMTP id 5058; Mon, 25
          Nov 91 18:16:42 GMT
Received: from UICVM by UKACRL.BITNET (Mailer R2.07) with BSMTP id 0462; Mon,
          25 Nov 91 18:16:37 GM
Received: by UICVM (Mailer R2.07) id 0706; Mon, 25 Nov 91 12:14:06 CST
Date: Mon, 25 Nov 1991 09:28:23 MST
Reply-To: Terry Langendoen <[log in to unmask]>
Sender: "TEI-L: Text Encoding Initiative public discussion list" <[log in to unmask]
          UICVM>
From: Terry Langendoen <[log in to unmask]>
Subject: Alignment mechanisms
X-cc: Wendy Plotkin <[log in to unmask]>
To: "Thomas N. Corns" <[log in to unmask]>
 
<tei.1 id=am1>
<tei.header>
<file.description>
<title.statement>
<title>Alignment mechanisms
<author>D. Terence Langendoen
<!--The following six lines are not TEI-conformant!-->
<address>
<address.line>Department of Linguistics
<address.line>University of Arizona
<address.line>Tucson, AZ 85721 USA
<address.line>[log in to unmask]
</address>
</file.description>
<revision.history>
<change.note>
<who>DTL
<date>24 November 1991</date>
<what>first draft
</change.note>
<change.note>
<who>DTL
<date>25 November 1991</date>
<what>update, incorporating reference to <citn>Norway meeting
report</citn>.
</change.note>
</revision.history>
</tei.header>
<text>
<front>
<front.part>
<head>Request for comments
<p>Comments are welcome, but if you have any, send them quickly, to
the sender, and, if you think they are important enough, to the file
server or the TEI editors.
<body>
<head>Alignment mechanisms
<div1 n=1>
<head>Background
<div2 n=1>
<head>Explicit alignment in <citn>TEI P1</citn>
<p id=eap1>The mechanism for explicit alignment of different parts of
text with one another is described in detail in <citn id=c1>TEI P1,
section 6.2.5, pp. 142-144</citn>. It consists of an
<tag>alignment</tag>, made up of pointers (in the form of
<tag>al.ptr</tag> and other elements), which point from the
<tag>alignment</tag> into the <tag>text</tag>. However, it is possible
also to have pointers from the <tag>text</tag> into the
<tag>alignment</tag>, if <tag>al.ptr</tag> and the other elements in the
<tag>alignment</tag> are permitted to have their own <term>id</term>s.
This mechanism can be used to align not only the different linguistic
analyses of text portions (the only application described in that<xref
target=c1> section), but also parallel texts.
<div2 n=2>
<head>Proposal in <citn>TEI AI2 W1</citn> for <tag>timeline</tag>
<p>The Spoken Text Workgroup chaired by <name>Stig Johansson</name>
proposed that encodings of spoken texts be accompanied by a
<tag>timeline</tag>, consisting of pointers from the <tag>text</tag>
into the <tag>timeline</tag>. One purpose for the <tag>timeline</tag>
is to align the elements of spoken text according to when they were
spoken, so that, for example, temporal overlapping of speakers can be
represented.
<div1 n=2>
<head>Discussion of alignment mechanisms at Myrdal meeting
<p>At the meeting of Working Group chairs and other TEI
representatives recently concluded at Myrdal, Norway, the similarity of
the <tag>alignment</tag> and <tag>timeline</tag> mechanisms was noted,
and I was charged with the task of reconciling the two mechanisms for
<citn>TEI P2</citn>.
<note place=foot>See <citn>Norway meeting report, posted on TEI-L,
24 November 1991, item 7.</note>
<trailer>
<p>In the next section<xref target=d3>, I outline my solution to
this problem. As this<xref target=am1> is being written, my research
assistant <name>Steven Zepp</name> is writing the formal specifications
and validating them. Once they are prepared and validated, they will be
circulated.
<div1 id=d3 n=3>
<head>Outline of proposal for <citn>TEI P2</citn>
<div2 n=1>
<head>Justification for distinct tagsets
<p>The two mechanisms are sufficiently different that they require
different tagsets. An <tag>alignment</tag> as described in <citn>TEI
P1</citn> consists of one or more <tag>al.map</tag>s, which in turn must
consist of at least two <tag>al.ptr</tag>s or other pointing elements
(<tag>al.list</tag> and <tag>al.range</tag>). The two or more pointers
that are grouped together within an <tag>al.map</tag> may be said to
<emph>correspond</emph> to one another. On the other hand, a
<tag>timeline</tag> contains a set of <tag>point</tag>s, which as
described in <citn>TEI AI2 W1</citn> are unstructured,
but which can be thought of as consisting of zero or more pointing
elements, which are aligned with those points (and perhaps understood as
synchronous with those points). The <tag>timeline</tag> moreover
requires attributes which the <tag>alignment</tag> does not; similarly
the <tag>point</tag>s require attributes which the <tag>al.map</tag>s do
not.
<div2 n=2>
<head>Restructuring of the tagset for analytic and textual
correspondence
<p>First, I suggest that certain tags in the tagset for textual and
analytic correspondence (what <citn>TEI P1</citn> called
<cited.word>explicit alignment</cited.word>) be renamed as follows.
<list type=ordered>
<enum>1. <item><tag>alignment</tag> becomes <tag>corresp.grp</tag>;
<enum>2. <item><tag>al.map</tag> becomes <tag>corresp</tag>;
<enum>3. <item><tag>al.ptr</tag> becomes <tag>xref</tag>;
<note place=foot>
<p>On the use of <tag>xref</tag> as a general purpose pointer, see
<citn>Norway meeting report, posted on TEI-L, 24 November 1991</citn>.
<p>I assume here that <tag>xref</tag> is characterized as in
<citn>TEI P1</citn>. However, its definition may be expected to change
in ways which are not material here.</note>
<enum>4. <item><tag>al.list</tag> becomes <tag>xref.grp</tag>, and
should consist of two or more <tag>xref</tag>s, not one or more
<tag>al.ptr</tag>s, as in <citn>TEI P1</citn>.
</list>
The names <cited.word>corresp.grp</cited.word> and
<cited.word>corresp</cited.word> more accurately reflect the intended
semantics of their respective elements than do
<cited.word>alignment</cited.word> and <cited.word>al.map</cited.word>.
<p> Second, I propose to eliminate <tag>al.range</tag>, as its function
can be subsumed under <tag>xref</tag>, in virtue of the
<term>target.end</term> attribute on <tag>xref</tag>.
<div2 n=3>
<head>Restructuring of the tagset for synchronizing text
<p>First, I suggest that certain tags in the tagset proposed in
<citn>TEI AI2 W1, Spoken Texts</citn> for synchronizing text be
renamed as follows.
<list type=ordered>
<enum>1. <item><tag>timeline</tag> becomes <tag>align</tag>;
<enum>2. <item><tag>point</tag> becomes <tag>loc</tag>.
</list>
The reason for giving <tag>timeline</tag> a more neutral name is that it
can be used not only for alignment with time but also with any
one-dimensional structure associated with a text, such as lineation and
word position. The reason for giving <tag>point</tag> a new name is to
dissociate it from the notion of a <term>pointer</term>; the name
<cited.word>loc</cited.word> indifferently represents
<gloss>locus</gloss> or <gloss>location</gloss>.
<p>Second, I suggest that <tag>align</tag> should have certain
attributes which specify whether it is a temporal or spatial (textual)
alignment; what the origin is, if any; whether the <tag>loc</tag>s are
understood to be a fixed distance apart; how the distance beween
<tag>loc</tag>s is measured; whether the distance to a particular
<tag>loc</tag> is being measured from the origin or from the immediately
preceding <tag>loc</tag>; etc. Similarly <tag>loc</tag>s should have
attributes which indicate their value in the dimension represented by
<tag>align</tag> (at minimum, the <tag>loc</tag> identified as the
origin should be so specified); their distance from the previous
<tag>loc</tag> or the origin; etc.
<p>Third, I suggest that the content model for an <tag>align</tag>
be one or more <tag>loc</tag>s, like that of a <tag>corresp.grp</tag>,
which consists of one or more <tag>corresp</tag>s. However, a
<tag>loc</tag> should consist of zero or more <tag>xref</tag>s, in
contrast to a <tag>corresp</tag>, which consists of two or more
<tag>xref</tag>s or <tag>xref.grp</tag>s. The content model for
<tag>loc</tag> need not include <tag>xref.grp</tag>s.
<p>Finally, note that both <tag>corresp.grp</tag> and <tag>align</tag>
permit pointing from the text to the map and from the map to the text.
This bidirectionality is illustrated in the following<xref
target=d3.3.1> illustration of the use of <tag>align</tag>.
<div3 id=d3.3.1 n=1>
<head>Example of the use of a temporal <tag>align</tag>
<p>The following<xref target=ex1> example is adapted from <citn>TEI AI2
W1, section 8.5, Speaker overlap</citn>.
<xmp id=ex1><![ CDATA [
<text>
<u who=A><xref id=x1 target=p1>this <xref id=x2 target=p2>is <xref
id=x3 target=p3>my <xref id=x4 target=p4>turn<xref id=x5 target=p5></u>
<u who=B><xref id=x6 target=p2>balderdash<xref id=x7 target=p4></u>
<u who=C><xref id=x8 target=p3>no <xref id=x9 target=p4>it's mine<xref
id=x10 target=p5></u>
<kinesic who=B id=k1 start=p4 end=p5 desc="waves arms">
</text>
<align origin=p1 interval=1 measured.from=previous>
<loc id=p1 value=0>
<xref target=x1>
</loc>
<loc id=p2>
<xref target=x2>
<xref target=x6>
</loc>
<loc id=p3>
<xref target=x3>
<xref target=x8>
</loc>
<loc id=p4>
<xref target=x4>
<xref target=x7>
<xref target=x9>
<xref target=k1>
</loc>
<loc id=p5>
<xref target=x5>
<xref target=x10>
<xref target=k1>
</loc>
</align>
]]</xmp>
<div1 n=4>
<head>Possible extensions of <tag>align</tag> to multidimensional
alignment
<p>Each <tag>align</tag> represents a one-dimensional structure (i.e.,
sequence) of <tag>loc</tag>s. It is easy to see how this concept can be
extended to two-, three- and even higher-dimensional structures, to
represent, for example the alignment of text on a page (two-dimensional
structure) or a book (three-dimensional structure in which the third
dimension is the page number).
</body>
</text>
</tei.1>
 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
End of returned mail

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
January 1996
December 1995
November 1995
October 1995
September 1995
August 1995
July 1995
June 1995
May 1995
April 1995
March 1995
February 1995
January 1995
December 1994
November 1994
October 1994
September 1994
August 1994
July 1994
June 1994
May 1994
April 1994
March 1994
February 1994
January 1994
December 1993
November 1993
October 1993
September 1993
August 1993
July 1993
June 1993
May 1993
April 1993
March 1993
February 1993
January 1993
December 1992
November 1992
October 1992
September 1992
August 1992
July 1992
June 1992
May 1992
April 1992
March 1992
February 1992
January 1992
December 1991
November 1991
October 1991
September 1991
August 1991
July 1991
June 1991
May 1991
April 1991
March 1991
February 1991
January 1991
December 1990
November 1990
October 1990
September 1990
August 1990
July 1990
June 1990
April 1990
March 1990
February 1990
January 1990

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager