New subject: [tei-council] correspDesc desc update

9 Feb 2015

      As most of you will have noticed, over the weekend Peter quite rightly
added a new section to the Header chapter describing correspDesc, along
with associated ODDs to implement the proposals. I feel very guilty for
not having found time to feedback suggestions for the new text (which I
promised to do months ago).,.. but here they are now! I haven't checked
the following in yet, but am happy to do so. As the section is quite
short, I am just pasting it into this message. We're all grown ups here
and can cope with a few TEI tags, right?

My revisions are mostly to enlarge and make a bit more explicit what the
examples are doing, plus a few other things changed for conformity with
house style. I have however reordered the original, putting
correspContext first, since it is simpler and shorter than the rest and
I didn't want to introduce new subsections.

I am not certain that I've properly understood the last and first
examples, so please read my rewording carefully!

--------

  <div type="div3" xml:id="HD44CD">
             <head>Correspondence Description</head>
             <p>The <gi>correspDesc</gi> element is used within the
<gi>profileDesc</gi> element to
                provide detailed correspondence-specific metadata,
concerning in particular the
                communicative aspects (sending, receiving, forwarding
etc.) associated with acts of
                of correspondence. </p>
             <p>This information is intended to complement the
description of the objects recording
                correspondence activities (such as letters), typically
provided by the
                   <gi>sourceDesc</gi> element. <specList>
                   <specDesc key="correspDesc"/>
                </specList>
             </p>
             <p>The <gi>correspDesc</gi> element contains the elements
<gi>correspAction</gi> and
                   <gi>correspContext</gi>, describing the actions
identified and the context in
                which the correspondence occurs respectively. <specList>
                   <specDesc key="correspAction" atts="type"/>
                   <specDesc key="correspContext"/>
                </specList>
             </p>
             <p>Acts of correspondence typically do not occur in
isolation from each other. The
                   <gi>correspContext</gi> element is used to group
references relevant to the item
                of correspondence being described, typically to other
items such as the item to which
                it is a reply, or the item which replies to it: <egXML
                   xmlns="http://www.tei-c.org/ns/Examples">
                   <correspContext>
                      <ref type="replyTo" target="#CLF0102">Previous
letter of Chamisso to de La
                         Foye: 16 January 1807</ref>
                      <ref type="replyFrom" target="#CLF0104">Next
letter of Chamisso to de La Foye:
                         07 May 1810</ref>
                   </correspContext>
                </egXML>
             </p>
             <p>Many types of correspondence action may be
distinguished. The <att>type</att>
                attribut should be used to indicate the type of action
being documented, using values
                such as those suggested above. </p>
             <p>The following basic example uses <gi>correspAction</gi>
to describe the sending of a
                letter by Adelbert von Chamisso from Vertus at 29
January 1807 to Louis de La Foye at
                Caen. The date of reception is unknown: <egXML
                   xmlns="http://www.tei-c.org/ns/Examples">
                   <correspAction type="sending">
                      <persName>Adelbert von Chamisso</persName>
                      <placeName>Vertus</placeName>
                      <date when="1807-01-29">29 January 1807</date>
                   </correspAction>
                   <correspAction type="receiving">
                      <persName>Louis de La Foye</persName>
                      <placeName>Caen</placeName>
                      <date>unknown</date>
                   </correspAction>
                </egXML>
             </p>
             <p>Several senders, recipients, etc. can be specified for a
single
                   <gi>correspAction</gi> if the action is considered to
apply to them all acting as
                a single group. In the following example three people
are considered to have received
                the communication. <egXML
xmlns="http://www.tei-c.org/ns/Examples">
                   <correspAction type="receiving">
                      <persName>Hermann Hesse</persName>
                      <persName>Ninon Hesse</persName>
                      <placeName>Montagnola</placeName>
                   </correspAction>
                </egXML>
             </p>
             <!-- this example looks a bit unreal: why not give one with
proper names? -->
             <p>The <att>subtype</att> attribute may be used to further
distinguish types of action.
                In the following example, an e-mail is sent to two
people directly and to a third by
                blind copy (<term>cc</term>). <egXML
xmlns="http://www.tei-c.org/ns/Examples">
                   <correspAction type="sending">
                      <persName>PN0001</persName>
                      <date when="1999-06-02">Wed, 02 Jun 1999</date>
                   </correspAction>
                   <correspAction type="receiving" subtype="to">
                      <persName>PN0002</persName>
                   </correspAction>
                   <correspAction type="receiving" subtype="to">
                      <persName>PN0003</persName>
                   </correspAction>
                   <correspAction type="receiving" subtype="cc">
                      <persName>PN0004</persName>
                   </correspAction>
                </egXML>
             </p>
             <p>The same person may often be associated with many
actions. For example, it will often
                be the case that the author and sender of a message are
identical, and that many
                individual letters will need to be associated with the
same person. The
                   <att>sameAs</att> attribute defined in section <ptr
target="#SAIE"/> may be used
                to indicate that the same name applies to many actions.
Its value will usually be the
                identifier of an element defining the person or name
concerned, which is supplied
                elsewhere in the document. <egXML
xmlns="http://www.tei-c.org/ns/Examples">
                   <correspAction type="sending">
                      <name sameAs="#author"/>
                   </correspAction>
                </egXML>
                <!-- example needs expansion to include definition for
#author -->
             </p>
             <p>It is assumed that each correspondence action applies to
a single act of
                communication. It may however be the case that the same
physical object is involved
             in several such acts, if for example person A sends a
letter to person B,
                who then annotates it and sends it on to person C, or if
persons A and B both use
                the same document to convey quite different messages. In
such situations, multiple
                   <gi>correspDesc</gi> elements should be supplied, one
for each communication. In
                the following example, the same document contains
distinct messages, sent by two
                different people. to the same destination:
<gi>correspDesc</gi> is used for each
                separately: <egXML xmlns="http://www.tei-c.org/ns/Examples">
                   <correspDesc xml:id="message1">
                      <correspAction type="sending">
                         <persName>John Gneisenau Neihardt</persName>
                         <placeName>Branson (Montgomery)</placeName>
                         <date>17 December 1932</date>
                      </correspAction>
                      <correspAction type="receiving">
                         <persName xml:id="JTH">Julius Temple
House</persName>
                         <placeName>New York</placeName>
                      </correspAction>
                   </correspDesc>
                   <correspDesc xml:id="message2">
                      <correspAction type="sending">
                         <persName>Enid Neihardt</persName>
                         <placeName>Branson (Montgomery)</placeName>
                         <date>17 December 1932</date>
                      </correspAction>
                      <correspAction type="receiving">
                         <persName sameAs="#JTH"/>
                         <placeName>New York</placeName>
                      </correspAction>
                   </correspDesc>
                </egXML>
                <!-- This example is very strange! Have I understood it
correctly?
                   And is "Julius Temple House" really a person's name
rather than that of an org? -->
             </p>

correspDesc desc update

Lou Burnard

Peter Stadler

Lou Burnard

Peter Stadler

tags

participants (2)