<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.
Attributes
- @modalitywritten or spoken mode.
- Status
- Recommended
- Datatype
- teidata.enumerated
- Suggested values
written- for stretches of text and/or multimodal elements
spoken- (for audio (or audio-visual) posts)
- @replyToindicates to which previous post the current post replies or refers.
- Status
- Datatype
- 1–∞ occurrences of teidata.pointer separated by whitespace
Classes and content
- Member of
- May contain
core
gaiji
msdescription
namesdates
tagdocs
textstructure
transcr
Character data
- character data
- Contained by
figures
Note
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.
Example
Usenet reply that comments on material quoted in an earlier message.
<post when="1990-10-11" who="#dmerritt" xml:id="sgml-tei-3" replyTo="#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"/>
<elementRef key="closer"/>
<elementRef key="postscript"/>
<elementRef key="signed"/>
<elementRef key="trailer"/>
<classRef key="model.divWrapper"/>
</alternate>
</content>