<post>

<post> a written (or spoken) contribution to a CMC interaction which has been composed (or recorded) by its author in its entirety before being transmitted over a network (e.g., the internet) and made available on the monitor or screen of the other parties en bloc. [9.3.1 CMC Posts]
Modul cmc — Computer-mediated Communication
Attribute
modality⚓︎ written or spoken mode
Zustand Empfohlen
Datentyp teidata.enumerated
Empfohlene Werte sind:
written
for stretches of text and/or multimodal elements
spoken
(for audio (or audio-visual) posts)
replyTo⚓︎ indicates to which previous post the current post replies or refers to. This attribute should be used to encode ‘technical’ reply information that is due to a formal reply action (such as activating a ‘reply’ button in the client software) and that is formally represented in the source, e.g. in the ‘references’ field of a Usenet message header or in the subject line of a forum post. It should not be used for inferred, or interpreted reply relations based only on ambiguous signs such as linguistic discourse markers or the indentation relations in Wiki talk pages.
Zustand Optional
Datentyp 1–∞ Vorkommen von teidata.pointer durch Leerzeichen getrennt
Mitglied des
Enthalten in
Kann enthalten
dictionaries: lang oRef pRef
gaiji: g
header: biblFull idno
iso-fs: fLib fs fvLib
verse: caesura rhyme
Zeichendaten
Anmerkung

Even though in some CMC genres (e.g., WhatsApp), the other parties are informed by an automated alert about the fact that another party is currently composing a new post, they cannot track the process of verbalization, i.e. how the written utterance emerges in the entry form on the user interface of its author. It is not until the author performs a ‘posting’ action (e.g., by hitting the ‘enter’ key or by activating a ‘send’ button with the mouse) that the result of the composition process — the post — is made available for the other parties. From the perspective of its addressees/readers, a post is a stretch of text that has been composed in advance. Different from spoken utterances but similar to edited text, (1) the reader of a post does not have access to the verbalization process and (2) the mental processing of a post is not possible until the process of verbalization (the composition) has been finished and the posting action has been performed by the author. Posts occur in a broad range of written CMC genres: as user ‘messages’ in chats and WhatsApp dialogues, as SMS messages, as tweets in Twitter timelines, as individual comments following a status update on Facebook pages, as posts in forum threads, as contributions on Wikipedia talk pages or in the comments section of a weblog. [Element adopted from the DeRiK schema. Aspects of the model adopted from the CoMeRe Schema]. The post element is a member of the model class model.common (via model.CMC). This allows for using (and combining) occurrences of post, u, incident, and kinesicin one and the same div in order to be able to represent the combined use of written and spoken utterances and nonverbal acts on the GUI of multimodal CMC environments.

The use of the modality attribute is recommended, but not required. Its value is either written or spoken. Because spoken language differs fundamentally from written language, when the value is spoken projects may wish to limit the content of the post to character data and only those elements available in the u element, thus avoiding elements like p or head that are used for the encoding of written text.

Beispiel

standard user postings in chat

<post type="standardgeneratedBy="human"
 who="#A05rend="color:red">

 <p>oh ja, in die Wärme...</p>
</post>
<post type="standardgeneratedBy="human"
 who="#A03rend="color:red">

 <p>nein, hast du nicht !!</p>
</post>
Beispiel

chat message-type "system": user enters a chatroom, "system" defined in listPerson

<listPerson>
 <person xml:id="system">
  <persName>system</persName>
 </person>
<!-- ... -->
</listPerson>
<!-- ... -->
<post type="eventgeneratedBy="system"
 who="#systemrend="color:navy">

 <p>
  <name type="nicknamecorresp="#A07">Interseb</name> betritt den Raum.</p>
</post>
Beispiel

action message in chat

<post type="eventgeneratedBy="human"
 who="#A02rend="color:blue">

 <p>
  <name type="nicknamecorresp="#A02">McMike</name> hechtet zum Steuer </p>
</post>
Beispiel

chat messages incl. interaction words (types: inflective and acronym) and an interaction phrase

<post type="standardgeneratedBy="human"
 who="#A03rend="color:green">

 <p>
  <w type="AKWIND">*</w>
  <w type="AKWsubtype="inflective">schwank</w>
  <w type="AKWIND">*</w>
<!-- ... -->
  <w type="AKWIND">*</w>
  <w type="AKW">seekrank</w>
  <w type="AKWIND">*</w>
 </p>
</post>
<!-- ... -->
<post type="standardgeneratedBy="human"
 who="#A02rend="color:blue">

 <p>
  <w type="AKWIND">*</w>
  <w type="AKWsubtype="acronym">lol</w>
  <w type="AKWIND">*</w> ... </p>
</post>
<!-- ... -->
<post type="standardgeneratedBy="human"
 who="#A01rend="color:black">

 <p>
  <phr type="AKW">
   <w type="AKWIND">*</w>
   <name type="nicknamecorresp="#A02">McMike</name> einen fallschirm <w type="AKWsubtype="inflective">umbind</w>
   <w type="AKWIND">*</w>
  </phr>
 </p>
</post>
Beispiel

user posting incl. an emoticon

<post type="standardgeneratedBy="human"
 who="#A01rend="color:black">

 <p> naja, der war gestrandet <w type="emoticonsubtype="ascii">:(</w>
 </p>
</post>
Beispiel

Twitter: Tweet containing an addressing term and a hashtag expression

<post type="standardgeneratedBy="human"
 who="#A01when="2015-11-18">

 <p>
  <ref corresp="#A02"
   target="https://twitter.com/textarchiv">

   <w type="ADRIND">@</w>
   <w type="ADR">textarchiv</w>
  </ref> Erfurter
   Europäische Welt- und Staats-Geschichte: 20 Ausgaben von 1744 aus dem MKHZ
   bereits in DTAQ <ref target="http://www.deutschestextarchiv.de/dtaq/about"> http://www.deutschestextarchiv.de/dtaq/about</ref>
  <ref target="https://twitter.com/hashtag/dtaclarin14?src=hash">
   <w type="hashtag">#dtaclarin14</w>
  </ref>
 </p>
</post>
Beispiel

example from Wikipedia discussion

<post type="standardgeneratedBy="human"
 indentLevel="3synch="#t02622878who="#WU00018921">

 <p> Wie du siehst hab ich die Lemma geändert, danke für den Hinweis, ich war nämlich
   selbst auch etwas unsicher bei der ganzen Sache und bin jetzt damit auch viel
   glücklicher!--</p>
 <signed rend="inline"
  generatedBy="template">

  <gap reason="signatureContent"/>
  <time generatedBy="template">12:01, 12. Jun. 2009 (CEST)</time>
 </signed>
</post>
Beispiel

Blog comment: Die Anthropodizee-Frage. Wer den Himmel leerräumt, schafft die Menschheit ab. by Volker Birk. https://scilogs.spektrum.de/natur-des-glaubens/die-anthropodizee-frage-wer-himmel/#comment-31899

<post xml:id="p5type="commentwho="#u4"
 synch="#t005replyTo="#p4">

 <p>“Wenn Sie diesen Gruppen also “mangelnde Bildung“ attestieren wollen, so
   verwenden Sie bereits einen bestimmten, kulturgebundenen Bildungsbegriff.”</p>
 <p>Ich hoffe doch, wir können beim Bildungsbegriff der Aufklärung bleiben. Wer das
   nicht möchte, hat die Wissenschaft verlassen.</p>
</post>
Beispiel

Usenet reply that comments on material quoted in an earlier message.

<post when="1990-10-11who="#dmerritt"
 xml:id="sgml-tei-3replyTo="#sgml-tei-1">

 <time generatedBy="system">04:37:51 UTC</time>
 <p>
  <seg generatedBy="system">In article <ref target="#sgml-tei-1"><2****.**********0@m*******.***.*****.**c.uk></ref> S.*.*.*****z@e**.*****.**c.uk (Sebastian Rahtz) writes:</seg>
  <cit>
   <bibl>[for] Lou Burnard:</bibl>
   <quote>the Text Encoding Initiative document is a many-splendoured thing,
       redolent of the mysterious east, caribbean evenings and the scent of
       fresh pine in the himalayas [...]</quote>
  </cit>
 </p>
 <p>Very poetic.</p>
 <p>But really, what is it?</p>
 <signed generatedBy="human">Doug</signed>
 <signed generatedBy="template">Doug Merritt ****@e***.********y.edu (ucbvax!eris!doug)
   or uunet.uu.net!crossck!dougm</signed>
</post>
Content model
<content>
 <alternate minOccurs="0"
  maxOccurs="unbounded">

  <textNode/>
  <classRef key="model.headLike"/>
  <elementRef key="opener"/>
  <classRef key="model.pLike"/>
  <classRef key="model.gLike"/>
  <classRef key="model.phrase"/>
  <classRef key="model.inter"/>
  <classRef key="model.global"/>
  <elementRef key="lg"/>
  <classRef key="model.lLike"/>
  <classRef key="model.divBottom"/>
 </alternate>
</content>
Schema Deklaration
<rng:element name="post">
 <rng:ref name="att.global.attributes"/>
 <rng:ref name="att.global.rendition.attributes"/>
 <rng:ref name="att.global.linking.attributes"/>
 <rng:ref name="att.global.analytic.attributes"/>
 <rng:ref name="att.global.facs.attributes"/>
 <rng:ref name="att.global.change.attributes"/>
 <rng:ref name="att.global.responsibility.attributes"/>
 <rng:ref name="att.global.source.attributes"/>
 <rng:ref name="att.cmc.attributes"/>
 <rng:ref name="att.indentation.attributes"/>
 <rng:ref name="att.ascribed.attributes"/>
 <rng:ref name="att.datable.attributes"/>
 <rng:ref name="att.datable.w3c.attributes"/>
 <rng:ref name="att.datable.iso.attributes"/>
 <rng:ref name="att.datable.custom.attributes"/>
 <rng:ref name="att.fragmentable.attributes"/>
 <rng:ref name="att.docStatus.attributes"/>
 <rng:ref name="att.timed.attributes"/>
 <rng:ref name="att.duration.w3c.attributes"/>
 <rng:ref name="att.duration.iso.attributes"/>
 <rng:ref name="att.typed.attributes"/>
 <rng:ref name="att.canonical.attributes"/>
 <rng:optional>
  <rng:attribute name="modality">
   <rng:choice>
    <rng:value>written</rng:value>
    <rng:value>spoken</rng:value>
    <rng:ref name="teidata.enumerated"/>
   </rng:choice>
  </rng:attribute>
 </rng:optional>
 <rng:optional>
  <rng:attribute name="replyTo">
   <rng:list>
    <rng:oneOrMore>
     <rng:ref name="teidata.pointer"/>
    </rng:oneOrMore>
   </rng:list>
  </rng:attribute>
 </rng:optional>
 <rng:zeroOrMore>
  <rng:choice>
   <rng:text/>
   <rng:ref name="model.headLike"/>
   <rng:ref name="opener"/>
   <rng:ref name="model.pLike"/>
   <rng:ref name="model.gLike"/>
   <rng:ref name="model.phrase"/>
   <rng:ref name="model.inter"/>
   <rng:ref name="model.global"/>
   <rng:ref name="lg"/>
   <rng:ref name="model.lLike"/>
   <rng:ref name="model.divBottom"/>
  </rng:choice>
 </rng:zeroOrMore>
</rng:element>
element post
{
   att.global.attributes,
   att.global.rendition.attributes,
   att.global.linking.attributes,
   att.global.analytic.attributes,
   att.global.facs.attributes,
   att.global.change.attributes,
   att.global.responsibility.attributes,
   att.global.source.attributes,
   att.cmc.attributes,
   att.indentation.attributes,
   att.ascribed.attributes,
   att.datable.attributes,
   att.datable.w3c.attributes,
   att.datable.iso.attributes,
   att.datable.custom.attributes,
   att.fragmentable.attributes,
   att.docStatus.attributes,
   att.timed.attributes,
   att.duration.w3c.attributes,
   att.duration.iso.attributes,
   att.typed.attributes,
   att.canonical.attributes,
   attribute modality { "written" | "spoken" | teidata.enumerated }?,
   attribute replyTo { list { teidata.pointer+ } }?,
   (
      text
    | model.headLikeopenermodel.pLikemodel.gLikemodel.phrasemodel.intermodel.globallgmodel.lLikemodel.divBottom
   )*
}