merge latest

TEI-CMC-SIG · Dec 5, 2023 · 1afbfb9 · 1afbfb9
2 parents 225245f + 49cd3b4
commit 1afbfb9
Showing 1 changed file with 42 additions and 26 deletions.
diff --git a/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml b/P5/Source/Guidelines/en/CMC-ComputerMediatedCommunication.xml
@@ -243,8 +243,8 @@ See the file COPYING.txt for details.
       <p>As shown in Example <ptr target="#CMCcmcpostatts"/> above, nested threads of posts can be
         encoded sequentially, while the attribute <att>indentLevel</att> of <gi>post</gi> is used to
         keep track of the original nesting depth. This is especially meant for CMC text obtained
-        from a wiki code or HTML source, where it not always entirely clear whether the indentation
-        information actually reflects a reply action from a user.</p>
+        from a wiki code or HTML source, where it is not always entirely clear whether the
+        indentation information actually reflects a reply action from a user.</p>
 
       <p>In genres where technical reply information is available for each post, reply links can be
         encoded using the <att>replyTo</att> attribute on <gi>post</gi> elements, as shown in second
@@ -700,13 +700,13 @@ See the file COPYING.txt for details.
         example, the second is a reply to the first, and the third is a reply to the second. <egXML
           xml:id="e9" xmlns="http://www.tei-c.org/ns/Examples" xml:lang="de" source="#BIB_scilog1">
           <post type="comment" modality="written" generatedBy="human" xml:id="cmc_post10" who="#u7"
-            replyTo="#cmc_ex_p1" when-iso="2015-07-29T21:44">
+            replyTo="#cmc_ex_p9" when-iso="2015-07-29T21:44">
             <p>Es hat den Anschein, als wäre bei BER durchaus große Kompetenz am Bau, allerdings
               nicht in Form von Handwerkern….</p>
             <p>http://www.zeit.de/2015/29/imtech-flughafen-berlin-ber-verzoegerung/komplettansicht</p>
           </post>
           <post type="comment" modality="written" generatedBy="human" xml:id="cmc_post11" who="#u8"
-            replyTo="#cmc_ex_p28" when-iso="2015-07-30T19:11">
+            replyTo="#cmc_ex_p10" when-iso="2015-07-30T19:11">
             <p>Nein Nein, an den Handwerkern kann es rein strukturel nicht gelegen haben. Niemand
               lässt seine Handwerker auf der Baustelle derart allein. Zudem gibt es höchstoffizielle
               “Abnahmen” von Bauabschnitten/phasen. Welcher Mangel auch bestanden hatte, er hätte
@@ -715,7 +715,7 @@ See the file COPYING.txt for details.
               offenbar ein universeler Bauträger, der alles baut.</p>
           </post>
           <post type="comment" modality="written" generatedBy="human" xml:id="cmc_post12" who="#u8"
-            replyTo="#cmc_ex_p29" when-iso="2015-07-30T19:26">
+            replyTo="#cmc_ex_p11" when-iso="2015-07-30T19:26">
             <p>Stahlkunstruktionen dacht ich mal, was die bauen — oder bauen lassen.</p>
             <p>Das ist schon ein übles Ding. Die Ausschreibungenund Angebote sind unauffällig, aber
               wenn Unregelmässigkeiten auftreten (im Bauverlauf) dann gibt es die saftigen
@@ -773,11 +773,11 @@ See the file COPYING.txt for details.
       <p><att>generatedBy</att> may indicate, for <gi>post</gi> or any of its descendants, how the
         content transcribed in an element was generated in a CMC environment. That is, whether the
         source text being transcribed was created by a human user, created by the CMC system at the
-        request of a human user (e.g., when the user activates a template that generates the conent,
-        such as in a signature), outright generated by the CMC system (e.g. a status message or a
-        timestamp), or generated by an automated process external to the CMC system itself. This
-        attribute is optional; when it is not specified on a <gi>post</gi> element its value is
-        presumed to be <val>unspecified</val>; when it is unspecified on any descendant of
+        request of a human user (e.g., when the user activates a template that generates the
+        content, such as in a signature), outright generated by the CMC system (e.g. a status
+        message or a timestamp), or generated by an automated process external to the CMC system
+        itself. This attribute is optional; when it is not specified on a <gi>post</gi> element its
+        value is presumed to be <val>unspecified</val>; when it is unspecified on any descendant of
           <gi>post</gi> its value is inherited from the immediately enclosing element. (And, in
         turn, if <att>generatedBy</att> is not specified on that element it inherits the value from
         its immediately enclosing elment, and so on up the document hierarchy until a <gi>post</gi>
@@ -793,8 +793,10 @@ See the file COPYING.txt for details.
           correct, but they should match (if this section is kept).
           — Syd, 2023-11-24
       -->
-      <!-- What is the tagdoc? It does not seem to be part of this chapter, so I suggest to keep this here. -Harald 2023-11-27 -->
-      <!-- What is the difference between suggested and legal? Can't seem to find documentation of this -Harald 2023-11-27 -->
+
+      <!-- What is the tagdoc? It does not seem to be part of the chapter, so I suggest to keep this section here. -Harald 2023-11-27 -->
+      <!-- What is the difference between suggested and legal? Can't seem to find documentation on this -Harald 2023-11-27 -->
+
       <p> A list of suggested values for <att>generatedBy</att> follows: <list type="gloss">
           <label>human</label>
           <item>when then content of the respective element was <q>naturally</q> typed or spoken by
@@ -978,9 +980,9 @@ See the file COPYING.txt for details.
           xmlns="http://www.tei-c.org/ns/Examples" source="#UND">
           <post modality="written" generatedBy="human" synch="#t005" who="#A06" xml:id="cmc_post23">
             <figure type="image" generatedBy="human">
-              <desc>Screenshot von der Google-Suche nach dem Friseur "Haarraum" mit der
-                Durchschnitts-Google-Bewertung (4,5 von 5 Sternen), der Adresse, der Telefonnummer
-                und den Öffnungszeiten</desc>
+              <desc>screenshot of the google search for hairdresser "Pasha's Haare'm" with the
+                average google rating (4,5 of 5 stars), the address, the phone number, and the
+                opening hours. </desc>
             </figure>
           </post>
         </egXML>
@@ -1171,6 +1173,7 @@ See the file COPYING.txt for details.
           </post>
         </egXML>
       </p>
+    </div>
 
       <div xml:id="CMCnames">
         <head>Named entities</head>
@@ -1222,12 +1225,19 @@ See the file COPYING.txt for details.
           </egXML>
         </p>
       </div>
-    </div>
 
     <div xml:id="CMCmultimodal">
 
       <head>Multimodal CMC</head>
 
+      <p>As explained in Section <ptr target="#CMCUnits"/> the elements <gi>post</gi>, <gi>u</gi>,
+          <gi>kinesic</gi>, and <gi>incident</gi> are available to to encode textual transcriptions
+        of written posts, spoken turns, bodily activity of avatars, and onscreen activity by users
+        that occur in CMC data, and in Section <ptr/> we gave recommendations on how to encode
+        graphics or other media data within posts with modality="written". When two or more of these
+        features occur in a CMC interaction, we can speak of <hi rend="italic">multimodal</hi>
+        CMC.</p>
+
       <p>Some basic multimodality is available in private chat such as WhatsApp, where spoken and
         written posts and media posts containing images or video clips, can alternate. The following
         shows the suggested encoding of a extended part of the <hi rend="italic">haircut</hi> chat
@@ -1258,16 +1268,15 @@ See the file COPYING.txt for details.
           zusammen </post>
       </egXML>
 
-
-      <p>On the GUI (graphical user interface) of a multimodal CMC environment such as Second life,
-        a gaming or a learning platform, interactions may consist of interleaved occurrences of
-        posts (<gi>p</gi>), utterances (<gi>u</gi>) and non-verbal acts such as bodily activities
-          (<gi>kinesic</gi>) or other on-screen activities (<gi>incident</gi>). The following
-        example shows how a spoken utterance, an avatar's bodily activity, and a written post occur
-        on the same level within the text <gi>body</gi>, representing parts of a multimodal chat in
-        Second Life adapted from the Archi21 corpus <ptr type="cit" target="#BIB_ChanierWigham2015"
-        />. <egXML xmlns="http://www.tei-c.org/ns/Examples" source="#BIB_ChanierWigham2015"
-          xml:lang="en">
+      <p>On the GUI (graphical user interface) of a more complex multimodal CMC environment such as
+        Second life, a gaming or a learning platform, interactions may consist of interleaved
+        occurrences of posts (<gi>p</gi>), utterances (<gi>u</gi>) and non-verbal acts such as
+        bodily activities (<gi>kinesic</gi>) or other on-screen activities (<gi>incident</gi>). The
+        following example shows how a spoken utterance, an avatar's bodily activity, and a written
+        post occur on the same level within the <gi>body</gi> element, representing parts of a
+        multimodal chat in Second Life adapted from the Archi21 corpus <ptr type="cit"
+          target="#BIB_ChanierWigham2015"/>. <egXML xmlns="http://www.tei-c.org/ns/Examples"
+          source="#BIB_ChanierWigham2015" xml:lang="en">
           <text>
             <body>
               <u xml:id="cmr-archi21-slrefl-es-j3-1-a191" who="#tingrabu"
@@ -1292,6 +1301,13 @@ See the file COPYING.txt for details.
           </text>
         </egXML>
       </p>
+
+      <p>Note that the spoken utterance <gi>u</gi> represents a speaker turn that was transmitted
+        via an audio channel of the application that is continuously open during a session, whereas
+        a spoken <gi>post</gi> represents a spoken message that has been recorded in private and
+        been posted to the CMC server as a whole afterwards, see Section <ptr target="#CMCUnits"
+        /></p>
+
     </div>
   </div>