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:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  January 2009

TEI-L January 2009

Subject:

Complex text versioning

From:

Efraim Feinstein <[log in to unmask]>

Reply-To:

Efraim Feinstein <[log in to unmask]>

Date:

Wed, 28 Jan 2009 11:55:47 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (146 lines)

Hello list,

The project I'm working on <http://jewishliturgy.googlecode.com> intends 
to encode Jewish prayer books ("siddur," sing., "siddurim," pl) in TEI, 
and make the texts freely available with a free software framework to 
represent the texts in printable formats.  The resulting texts are 
intended to be used by individuals and congregations, and the majority 
of the end-user audience will likely be non-academic.  I'm currently 
working on the project's schema and encoding guidelines.

One of the problems we're encountering is that "the siddur" is not one 
book.  It's more like a lot of separate books with large amounts of 
overlapping content.  In its current forms, there are multiple major 
rites, and, even within the major rites, there are minor textual 
variations.  There are also a large number of repeated texts with minor 
differences where which variant should be used depends on the function 
of the text at its particular place in the service or the time of the 
year the text is being used. 

Ideally, I would like to represent the text with as little repetition of 
core text as reasonably possible.

An example is the "Kaddish" <http://en.wikipedia.org/wiki/Kaddish>, 
which has 5 (or 6) major functional variants:
1. "Half kaddish" - used as a separator within services (shortest 
version, contains the first 2 paragraphs)
2. "Mourner's kaddish" - said by mourners during or at the end of the 
service (half kaddish+2 lines)
3. "Rabbi's kaddish" - said after a section of study included in the 
service has been read (mourners kaddish+1 paragraph)
4. "Full kaddish" -  said to complete a prayer service  (mourners 
kaddish+1 line)
5. "Burial/completion kaddish" - said either at funerals or at the 
completion of study of Talmud (full kaddish+multiple additions)
[A possible #6. "Reform mourner's kaddish" - traditional mourner's 
kaddish + 1 paragraph]

Within those variants, there are additional variants that are time 
dependent, such as the repetition of 1 word in the second paragraph or 
the modification of 1 word in the final line; and some variants that are 
dependent on rite (for example, one line in the first paragraph).  In 
addition, there are numerous other rite variants in the text.

As far as I can tell, none of the stock TEI mechanisms for text 
versioning can represent this level of detail(?).

I wrote a proof of concept version as a TEI extension with 5 new 
elements (in a separate namespace, prefixed here "j"):
j:txtVar / j:txt (essentially a rename of tei:app / tei:rdg ) - 
variation in text
j:tempVar / j:temp - [temporal] variation in when a text is used
j:funcVar / j:func - functional variation
j:custVar / j:cust - variation in custom (usually for instructions)
j:varVar / j:var - variation that doesn't fit into any of the above 
categories

I'd been thinking a bit about how to link each variant to its source.  
The options (as far as I can tell) are: @wit attached to tei:witness 
(like tei:rdg), a new attribute, or @decls attached to tei:sourceDesc or 
tei:sourceDesc/tei:biblStruct.  @decls seems like the most "portable" 
way to do it because then the same processing could be done on the 
variants as is done on tei:text or tei:div to link to sources.

The next problem is how to link each variant to a user's (or a text's) 
selections - and here's where I really might be getting into borderline 
TEI-abusive territory.  I defined three new attributes: @j:set, 
@j:include and @j:omit.  @j:set is a global attribute that allows a 
variant to be selected as active in the (similar to @select from linking 
module).  @j:include and @j:omit can appear on tags such as the variant 
tags mentioned above, and define the conditions under which the tag 
should be included in a text.  When conditions are evaluated by 
@j:include or @j:omit, the values from the list of URIs are combined by 
logical or.  The result of testing the settings by @j:omit overrides the 
result of @j:include if @j:include returns true.  All of the conditional 
attributes take a list of URIs as their content that point to TEI 
feature structures.

Most of the switches are 3-way switches.  The possible feature values 
are: YES, NO and MAYBE.  When YES is selected, conditional text should 
always be included.  When NO is selected, conditional text should always 
be excluded.  When MAYBE is selected, conditional text should be 
included, and any instructional text associated with the conditional 
text should also be included.  For example, in the Kaddish, there's a 
word variant that is only included between the two high holidays of Rosh 
Hashanna and Yom Kippur.   A (simplified) example of the system would be 
this (excluding the documentation elements):

<!-- in the file header, define (and document) the conditional: -->
<tei:fsDecl type="time">
  <tei:f name="BetweenRHandYK">
    <tei:vRange>
      <tei:vAlt>
        <tei:symbol xml:id="YES" value="YES"/>
        <tei:symbol xml:id="NO" value="NO"/>
        <tei:symbol xml:id="MAYBE" value="MAYBE"/>
      </tei:vAlt>
    </tei:vRange>
  </tei:f>
</tei:fsDecl>
...
<!-- somewhere in the file: -->
<tei:fs xml:id="BetweenRHandYK_Y" type="time">
   <tei:f name="BetweenRHandYK" fVal="#YES" />
</tei:fs>
<tei:fs xml:id="BetweenRHandYK_N" type="time">
   <tei:f name="BetweenRHandYK" fVal="#NO" />
</tei:fs>
<tei:fs xml:id="BetweenRHandYK_M" type="time">
   <tei:f name="BetweenRHandYK" fVal="#MAYBE" />
</tei:fs>
...
<!-- the division specifying the possible times: -->
<tei:div j:set="#BetweenRHandYK_M">
...
  <!-- the text under variation: -->
  <j:tempVar>
    <!-- this is a bit overspecified to show everything being used: -->
    <j:temp j:include="#BetweenRHandYK_Y #BetweenRHandYK_M" 
j:omit="#BetweenRHandYK_N">
      <tei:note type="instruct" j:include="#BetweenRHandYK_M">Between 
Rosh Hashanna and Yom Kippur, add:</tei:note>
      <!-- text to be included conditionally here -->
    </j:temp>
  </j:tempVar>
...
</tei:div>

There are quite a few more complicated switches, involving combinations 
of switches and the application of "and" and "or" logic to figure out 
whether a particular text should be included.

Another option would be not using feature structures and defining a 
separate 3-way switch system specifically for the purpose.

Has anyone ever faced a problem like this?  How does this solution 
compare to something that might be developed by someone with more TEI 
experience?  Does it fit within the "TEI abstract model" or is it abusive?

Thanks,

-- 
----
Efraim Feinstein
[log in to unmask]
http://jewishliturgy.googlecode.com

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

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