kempersc/glam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
glam/docs/convention/schema/tei-p5-extracted/OPS/CMC.html
kempersc d661947830 update enriched entries
2025-12-03 17:38:46 +01:00

3 lines
No EOL
185 KiB
HTML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<html xmlns="http://www.w3.org/1999/xhtml"><head><!--THIS FILE IS GENERATED FROM AN XML MASTER. DO NOT EDIT (2)--><title>Computer-mediated Communication</title><meta name="Language" content="en"/><meta name="DC.Title" content="Computer-mediated Communication"/><meta name="DC.Language" content="SCHEME=iso639 en"/><meta charset="utf-8"/><link href="stylesheet.css" rel="stylesheet" type="text/css"/><link href="print.css" rel="stylesheet" type="text/css" media="print"/></head><body id="TOP"><div class="teidiv"><div class="titlePart"><span class="titlem">TEI P5: </span></div><div class="titlePart"><i>Guidelines for Electronic Text Encoding and Interchange</i></div><div lang="en" class="div1" id="CMC"><h2><span class="headingNumber">9. </span><span class="head">Computer-mediated Communication</span></h2><div style="margin-top: 0em;" class="miniTOC miniTOC_left"><p><span class="subtochead">Table of contents</span></p><div class="subtoc"><ul class="subtoc"><li class="subtoc"><a class="subtoc" href="CMC.html#CMCintro" title="General Considerations">9.1. General Considerations</a></li><li class="subtoc"><a class="subtoc" href="CMC.html#CMCUnits" title="Basic Units of CMC">9.2. Basic Units of CMC</a></li><li class="subtoc"><a class="subtoc" href="CMC.html#CMCcmc" title="Encoding Unique to CMC">9.3. Encoding Unique to CMC</a></li><li class="subtoc"><a class="subtoc" href="CMC.html#CMCmacrometa" title="CMC Macrostructure">9.4. CMC Macrostructure</a></li><li class="subtoc"><a class="subtoc" href="CMC.html#CMCmetadata" title="Documenting CMC (and providing general metadata)">9.5. Documenting CMC (and providing general metadata)</a></li><li class="subtoc"><a class="subtoc" href="CMC.html#CMCrecs" title="Recommendations for Encoding CMC Microstructure">9.6. Recommendations for Encoding CMC Microstructure</a></li><li class="subtoc"><a class="subtoc" href="CMC.html#CMCmodule" title="The TEI CMC Module">9.7. The TEI CMC Module</a></li></ul></div><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="TS.html"><span class="headingNumber">8. </span>Transcriptions of Speech</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="DI.html"><span class="headingNumber">10. </span>Dictionaries</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><p>This chapter describes the TEI encoding mechanisms available for textual data that represents discourse from genres of computer-mediated communication (CMC). It is intended to provide the basic framework needed to encode CMC corpora.</p><div class="div2" id="CMCintro"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"/><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCUnits"><span class="headingNumber">9.2. </span>Basic Units of CMC</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h2><span class="bookmarklink"><a class="bookmarklink" href="#CMCintro" title="link to this section "><span class="invisible">TEI: General Considerations</span>⚓︎</a></span><span class="headingNumber">9.1. </span><span class="head">General Considerations</span></h2><p>While the term <span class="term">computer-mediated communication</span> might be used broadly to describe all kinds of communications that are mediated by digital technologies (such as text on web pages, written exchanges in chats and forums, interactions with artificial intelligence systems, the spoken conversations in internet video meetings), for the purposes of these Guidelines we use the term to apply to forms of communication that share the following features: </p><ul class="bulleted"><li class="item">they are dialogic;</li><li class="item">they are organized as interactional sequences so that each communicative move may determine the context for subsequent moves (typically taken by another interlocutor) and may react to the context created by a prior move;</li><li class="item">they are created and displayed using computer technology or human-machine interfaces such as keyboard, mouse, speech-to-text conversion software, monitor or screen and transmitted over a computer network (typically the internet).</li></ul><p> Such communications may be expressed as posts (cf. <a class="link_ptr" href="CMC.html#CMCcmcpost" title="CMC Posts"><span class="headingNumber">9.3.1. </span>CMC Posts</a>), utterances, onscreen activities, or bodily activities exerted by a virtual avatar.</p><p>The following kinds of platforms support CMC: </p><ul class="simple"><li class="item">chats, messengers, or online forums;</li><li class="item">social media platforms and applications;</li><li class="item">the communication functions of collaborative platforms and projects (e.g. an online learning environment, or a ‘talk’ page);</li><li class="item">3D virtual world environments;</li><li class="item">other interactive services supported by the internet.</li></ul><p>CMC supports multimodal expression combining text, images, sound. Whereas early CMC systems (e.g. Internet Relay Chat, ‘IRC’ for short, the Usenet ‘newsgroups’, or even the Unix <span class="name">talk</span> system) were completely ASCII-based, most CMC applications now permit combining media formats (e.g. written or spoken language with graphic icons and images) and mixing communication technologies on one platform (e.g. combined use of an audio connection, a chat system, and a 3D interface in which users control a virtual avatar as in many multiplayer online computer games or in virtual worlds).</p></div><div class="div2" id="CMCUnits"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCintro"><span class="headingNumber">9.1. </span>General Considerations</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCcmc"><span class="headingNumber">9.3. </span>Encoding Unique to CMC</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h2><span class="bookmarklink"><a class="bookmarklink" href="#CMCUnits" title="link to this section "><span class="invisible">TEI: Basic Units of CMC</span>⚓︎</a></span><span class="headingNumber">9.2. </span><span class="head">Basic Units of CMC</span></h2><p>This section describes the encoding mechanisms for the basic units of CMC and for their combined use to encode CMC data.</p><p>We use the term <span class="term">basic CMC unit</span> to refer to a communication produced by an interlocutor to initiate or contribute to an ongoing CMC interaction or joint CMC activity. Contributions to an ongoing interaction are produced to perform a move to develop the interactional sequence, for instance to respond in chats or forum discussions. Contributions to joint CMC activities may not all be directly interactional; some may be part of a collaborative project of the involved individuals. Such collaboration could involve editing activities in a shared text editor or whiteboard in parallel with an ongoing CMC interaction (chat, audio conversation, or audio-video conference) in the same CMC environment in which these editing activities are discussed by the participants.</p><p>Basic units of CMC can be described according to three criteria: </p><ol class="numbered"><li class="item">the temporal properties of when these contributions are produced by their creators, transmitted via CMC systems, and made accessible for the recipients;</li><li class="item">the modality of the unit as a whole, whether verbal or nonverbal;</li><li class="item">for verbal units: whether the unit is expressed in the written or spoken mode.</li></ol><p> A taxonomy of basic CMC units resulting from these criteria is given in the following figure.</p><div class="figure" id="cmcunits-taxonomy"><img src="media/resource17.png" alt="Taxonomy of basic CMC units according to " class="graphic"/><div class="caption">Figure 11. Taxonomy of basic CMC units according to <a class="citlink" href="BIB.html#BIB_CMC_Core">Beißwenger and Lüngen (2020)</a></div></div><p>The most important distinction in the <a class="link_ref" href="CMC.html#cmcunits-taxonomy" title="Taxonomy of basic CMC units according to">CMC taxonomy</a> concerns the temporal nature of units exchanged via CMC technologies. The left part of the taxonomy describes units that are performed (by a producer) and perceived (by a recipient) as a continuous stream of behaviour. Units of this type can be performed as</p><dl><dt><span style="font-weight:bold">spoken utterances,</span></dt><dd>i.e. stretches of speech which are produced to perform a speaker turn in a conversation,</dd><dt><span style="font-weight:bold">bodily activity,</span></dt><dd>i.e. nonverbal behaviour (gesture, gaze) produced to perform a speaker turn, either performed by the real body of an interlocutor (e.g. in a video conference) or through the virtual avatar of an interlocutor in a 3D environment,</dd><dt><span style="font-weight:bold">onscreen activities,</span></dt><dd>i.e. non-bodily expressions that are transmitted to the group of interacting or coworking participants, for instance the editing of content in a shared text editor which can be perceived by the other parties simultaneously (as may be the case in learning or collaboration environments).</dd></dl><p>The right part of <a class="link_ref" href="CMC.html#cmcunits-taxonomy" title="Taxonomy of basic CMC units according to">the CMC taxonomy</a> describes units in which the production, transmission, and perception of contributions to CMC interactions are organized in a strictly consecutive order: The content—verbal, nonverbal, or multimodal—of the contribution has to be produced before it can be transmitted through a network and made available on the computer monitor or mobile screen of any other party as a preserved and persistent unit. We term this type of unit a <span class="term">post</span>. Posts occur in two different variants: </p><ul class="bulleted"><li class="item">as <em style="font-weight:bold">written or multimodal posts,</em> which are produced with an editor form that is designed for the composition of stretches of written text. Most contemporary post-based CMC technologies provide features for the inclusion of graphic and audio-visual content (emoji graphics, images, videos) into posts and even to produce posts without verbal content (which then may consist only of emojis, an image, or a video file). Written and multimodal posts are the standard formats for user contributions in primarily text-based CMC genres and applications such as chat, SMS, WhatsApp, Instagram, Facebook, X (Twitter), online forums, or Wikipedia talk pages.</li><li class="item">as <em style="font-weight:bold">audio posts</em>, which are produced using a recording function. In contrast to CMC units of the type <span class="term">utterance</span> which are produced and transmitted simultaneously, audio posts first have to be recorded as a whole and are then transmitted, as audio files, via the internet; the availability of the recording is indicated in the screen protocol by a template-generated, visual post; the recipients can play the recording (repeatedly) by activating the play button displayed in the post on the screen. Examples of CMC applications that implement audio posts are WhatsApp or RocketChat.</li></ul><p>Three of the four basic CMC units described above can be represented with models that are described elsewhere in the TEI Guidelines:</p><div class="table" id="CMCUnits-table-qm"><table><tr style="text-decoration:underline"><td>CMC unit</td><td>Type of corpus data</td><td>TEI P5 element</td></tr><tr><td>spoken utterance</td><td>transcription of speech</td><td><a class="gi" title="(utterance) contains a stretch of speech usually preceded and followed by silence or by a change of speaker." href="ref-u.html">u</a></td></tr><tr><td>bodily activity</td><td>textual description</td><td><a class="gi" title="(kinesic) marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc." href="ref-kinesic.html">kinesic</a></td></tr><tr><td>onscreen activity</td><td>textual description</td><td><a class="gi" title="(incident) marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication." href="ref-incident.html">incident</a></td></tr></table></div><p>The <a class="gi" title="(utterance) contains a stretch of speech usually preceded and followed by silence or by a change of speaker." href="ref-u.html">u</a>, <a class="gi" title="(kinesic) marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc." href="ref-kinesic.html">kinesic</a>, and <a class="gi" title="(incident) marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication." href="ref-incident.html">incident</a> elements are not limited to CMC, but apply to encode textual transcriptions of spoken turns and CMC data about bodily activity and onscreen activity. The CMC unit <span class="term">post</span>, which is specific to CMC, is introduced in <a class="link_ptr" href="CMC.html#CMCcmcpost" title="CMC Posts"><span class="headingNumber">9.3.1. </span>CMC Posts</a>.</p></div><div class="div2" id="CMCcmc"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCUnits"><span class="headingNumber">9.2. </span>Basic Units of CMC</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCmacrometa"><span class="headingNumber">9.4. </span>CMC Macrostructure</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h2><span class="bookmarklink"><a class="bookmarklink" href="#CMCcmc" title="link to this section "><span class="invisible">TEI: Encoding Unique to CMC</span>⚓︎</a></span><span class="headingNumber">9.3. </span><span class="head">Encoding Unique to CMC</span></h2><p>This section describes elements, attributes, and models which are unique to CMC and the TEI CMC module.</p><div class="teidiv2" id="CMCcmcpost"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"/><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCcmcpostatts"><span class="headingNumber">9.3.2. </span>Attributes Specific to CMC post</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCcmcpost" title="link to this section "><span class="invisible">TEI: CMC Posts</span>⚓︎</a></span><span class="headingNumber">9.3.1. </span><span class="head">CMC Posts</span></h3><p>While the concept of a <span class="term">post</span> is not unique to computer-mediated communication (ask anyone who has posted a <span class="q">‘lost cat’</span> sign in the local market), this chapter concerns itself only with postings within a framework of a CMC system. Thus the element <a class="gi" title="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." href="ref-post.html">post</a> is unique to the encoding of computer-mediated communication (CMC). </p><ul class="specList"><li><span class="specList-elementSpec"><a href="ref-post.html">post</a></span> 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.</li></ul><p> Posts occur in a broad range of written CMC genres, including (but not limited to) messages in chats and WhatsApp dialogues, tweets in X (Twitter) timelines, comments on Facebook pages, posts in forum threads, and comments or contributions to discussions on Wikipedia talk pages or in the comment sections of weblogs.</p><p>Posts can be either written or spoken: </p><ul><li class="item"><em style="font-weight:bold">written</em> or <em style="font-weight:bold">multimodal posts</em>: In the majority of CMC technologies posts are composed as stretches of text using a keyboard or speech-to-text conversion software in an entry form on the screen. In many cases the technology allows authors to include or embed graphics (emojis or images), video files, and hyperlinks into their posts.</li><li class="item"><em style="font-weight:bold">spoken (audio posts)</em>: A growing number of CMC technologies, e.g. messenger software such as WhatsApp or RocketChat, allow for an alternative, spoken production of posts by providing a recording function which allows users to record a stretch of spoken language and transmit the resulting audio file to the other parties.</li></ul><p>The element <a class="gi" title="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." href="ref-post.html">post</a> may co-occur with <a class="gi" title="(utterance) contains a stretch of speech usually preceded and followed by silence or by a change of speaker." href="ref-u.html">u</a>, <a class="gi" title="(kinesic) marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc." href="ref-kinesic.html">kinesic</a>, <a class="gi" title="(incident) marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication." href="ref-incident.html">incident</a>, or other existing TEI elements within a <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a>, or directly within the <a class="gi" title="(text body) contains the whole body of a single unitary text, excluding any front or back matter." href="ref-body.html">body</a>, and may contain headings, paragraphs, openers, closers, or salutations.</p><p>The <a class="gi" title="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." href="ref-post.html">post</a> element is a member of several TEI attribute classes, including <a class="link_odd" title="provides attributes for elements representing speech or action that can be ascribed to a specific individual." href="ref-att.ascribed.html">att.ascribed</a>, <a class="link_odd" title="provides attributes that can be used to associate a representation such as a name or title with canonical information about the object being named or referenced." href="ref-att.canonical.html">att.canonical</a>, <a class="link_odd" title="provides attributes for normalization of elements that contain dates, times, or datable events." href="ref-att.datable.html">att.datable</a>, <a class="link_odd" title="provides attributes common to all elements in the TEI encoding scheme." href="ref-att.global.html">att.global</a>, <a class="link_odd" title="provides attributes common to those elements which have a duration in time, expressed either absolutely or by reference to an alignment map." href="ref-att.timed.html">att.timed</a>, and <a class="link_odd" title="provides attributes that can be used to classify or subclassify elements in any way." href="ref-att.typed.html">att.typed</a>, and as such may take a variety of attributes. </p></div><div class="teidiv2" id="CMCcmcpostatts"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCcmcpost"><span class="headingNumber">9.3.1. </span>CMC Posts</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCcmcatts"><span class="headingNumber">9.3.3. </span>Attributes for General CMC Encoding</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCcmcpostatts" title="link to this section "><span class="invisible">TEI: Attributes Specific to CMC post</span>⚓︎</a></span><span class="headingNumber">9.3.2. </span><span class="head">Attributes Specific to CMC <span class="gi">&lt;post&gt;</span></span></h3><div class="p">Three attributes pertain specifically to <a class="gi" title="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." href="ref-post.html">post</a>: <ul class="specList"><li><span class="specList-elementSpec"><a href="ref-post.html">post</a></span> 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.<table class="specDesc"><tr><td class="Attribute"><span class="att">modality</span></td><td>written or spoken mode.
Suggested values include: 1] written; 2] spoken (for audio (or audio-visual) posts)</td></tr><tr><td class="Attribute"><span class="att">replyTo</span></td><td>indicates to which previous post the current post replies or refers.</td></tr></table></li><li><span class="specList-classSpec"><a href="ref-att.indentation.html">att.indentation</a></span> provides attributes for describing the indentation of a textual element on the source page or object.<table class="specDesc"><tr><td class="Attribute"><span class="att">indentLevel</span></td><td>specifies the level of indentation of an item using a numeric value.</td></tr></table></li></ul> The type of the content of a post (i.e., whether the content is text, an image, a video clip, etc.) is indicated by the child elements of the <a class="gi" title="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." href="ref-post.html">post</a>. (E.g., a <a class="gi" title="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." href="ref-post.html">post</a> might have a child <a class="gi" title="(paragraph) marks paragraphs in prose." href="ref-p.html">p</a>, or a child <a class="gi" title="(figure) groups elements representing or containing graphic information such as an illustration, formula, or figure." href="ref-figure.html">figure</a> with a <a class="gi" title="(graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it." href="ref-graphic.html">graphic</a>, or a child <a class="gi" title="(figure) groups elements representing or containing graphic information such as an illustration, formula, or figure." href="ref-figure.html">figure</a> with a <a class="gi" title="indicates the location of any form of external media such as an audio or video clip etc." href="ref-media.html">media</a>, or some combination thereof.) How that content was created—whether it was recorded speech or not—may be described with the <span class="att">modality</span> attribute. Because spoken language differs significantly from written language, the suggested values only separate the <span class="val">spoken</span> modality from the <span class="val">written</span> modality, which covers all cases other than spoken natural language. The use of <span class="att">modality</span> is recommended but not required. <div id="CMCcmcpostatts-egXML-yz" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t005</span>" <span class="attribute">who</span>="<span class="attributevalue">#A06</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post09</span>"&gt;</span><br/> <span class="element">&lt;figure <span class="attribute">type</span>="<span class="attributevalue">image</span>" <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"&gt;</span><br/>  <span class="element">&lt;desc <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"&gt;</span>screenshot of the google search for hairdresser "Pasha's Haare'm"<br/>     with the average google rating (4,5 of 5 stars), the address, the phone number, and<br/>     the opening hours.<span class="element">&lt;/desc&gt;</span><br/> <span class="element">&lt;/figure&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCcmcpostatts-egXML-yz">⚓︎</a></div></div></div><p>The <span class="att">replyTo</span> attribute is used to capture information drawn from the original metadata associated with a post that asserts to which previous post the current post is a response, or to which previous post it refers. This metadata is included by many, but not all, CMC environments, when the user executes a formal reply action (e.g., by clicking or tapping a reply button). This attribute should not be used to encode interpreted or inferred reply relations based on linguistic cues or discourse markers.</p><div class="p">The <span class="att">replyTo</span> attribute indicates the replied-to or referred-to posts by providing one or more pointers to them. In the following example, reply references in the source indicate that the first <a class="gi" title="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." href="ref-post.html">post</a> is a reply to an initial post that is not part of the example, the second is a reply to the first, and the third is a reply to the second. <div id="e9" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">type</span>="<span class="attributevalue">comment</span>" <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post10</span>" <span class="attribute">who</span>="<span class="attributevalue">#u7</span>"<br/> <span class="attribute">replyTo</span>="<span class="attributevalue">#cmc_post09</span>" <span class="attribute">when-iso</span>="<span class="attributevalue">2015-07-29T21:44</span>"&gt;</span><br/> <span class="element">&lt;p&gt;</span>Es hat den Anschein, als wäre bei BER durchaus große Kompetenz am Bau, allerdings<br/>   nicht in Form von Handwerkern….<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;p&gt;</span>http://www.zeit.de/2015/29/imtech-flughafen-berlin-ber-verzoegerung/komplettansicht<span class="element">&lt;/p&gt;</span><br/><span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">type</span>="<span class="attributevalue">comment</span>" <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post11</span>" <span class="attribute">who</span>="<span class="attributevalue">#u8</span>"<br/> <span class="attribute">replyTo</span>="<span class="attributevalue">#cmc_post10</span>" <span class="attribute">when-iso</span>="<span class="attributevalue">2015-07-30T19:11</span>"&gt;</span><br/> <span class="element">&lt;p&gt;</span>Nein Nein, an den Handwerkern kann es rein strukturel nicht gelegen haben. Niemand<br/>   lässt seine Handwerker auf der Baustelle derart allein. Zudem gibt es höchstoffizielle<br/>   “Abnahmen” von Bauabschnitten/phasen. Welcher Mangel auch bestanden hatte, er hätte<br/>   Zeitnah auffallen müssen.<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;p&gt;</span>Uuups, für Imtek hab ich mal in einer Nachunternehmerfirma gearbeitet. Imtek is<br/>   offenbar ein universeler Bauträger, der alles baut.<span class="element">&lt;/p&gt;</span><br/><span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">type</span>="<span class="attributevalue">comment</span>" <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post12</span>" <span class="attribute">who</span>="<span class="attributevalue">#u8</span>"<br/> <span class="attribute">replyTo</span>="<span class="attributevalue">#cmc_post11</span>" <span class="attribute">when-iso</span>="<span class="attributevalue">2015-07-30T19:26</span>"&gt;</span><br/> <span class="element">&lt;p&gt;</span>Stahlkunstruktionen dacht ich mal, was die bauen—oder bauen lassen.<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;p&gt;</span>Das ist schon ein übles Ding. Die Ausschreibungenund Angebote sind unauffällig, aber<br/>   wenn Unregelmässigkeiten auftreten (im Bauverlauf) dann gibt es die saftigen<br/>   Rechnungen. Da steht dann der Bauherr da und fragt sich, wie er denn so schnell einen<br/>   fähigen Ersatz herbekommt. Und diese Frage erübrigt sich meist, weil der Markt der<br/>   Baufirmen das nicht hergibt — weil tendenziel 100 % Auslastung. (und noch schlimmer:<br/>   Absprachen) Was auch Folge des Marktdrucks gewesen war.<span class="element">&lt;/p&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_scilog1">bibliography</a> <a class="bookmarklink" title="link to this example" href="#e9">⚓︎</a></div></div></div><p>In the CMC genre of wiki talk, users insert their contribution to a discussion by modifying the wiki page of the discussion—the talk page. Since there is no technical reply action available in wiki software, users apply textual indentation in the wiki code to indicate a reply to a previous message, and a threaded structure is formed by a series of such indentations. The attribute <span class="att">indentLevel</span> records the level of indentation, that is the nesting depth of the current post in such a thread-like structure (as defined by its author and in relation to the standard level of non-indentation which should be encoded with an <span class="att">indentLevel</span> of <span class="val">0</span>). It is used in wiki talk corpora but may also be used for other threaded genres, for example when HTML is used as a source.</p><div class="p">The following is a sample encoding of a portion of a discussion among four different users on a Wikipedia talk page. <div id="CMCcmcpostatts-egXML-zm" class="pre egXML_valid"><span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">thread</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">i.10031_19</span>"&gt;</span><br/> <span class="element">&lt;head&gt;</span>[[WP:AUTO]]<span class="element">&lt;/head&gt;</span><br/> <span class="element">&lt;post <span class="attribute">indentLevel</span>="<span class="attributevalue">0</span>" <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/>  <span class="attribute">when-iso</span>="<span class="attributevalue">2006-09-07T03:09+00</span>" <span class="attribute">who</span>="<span class="attributevalue">#WU00010808</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post13</span>"&gt;</span><br/>  <span class="element">&lt;p&gt;</span> I would kindly request from Mr. Meyer to allow others to edit the [...]<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;/post&gt;</span><br/> <span class="element">&lt;post <span class="attribute">indentLevel</span>="<span class="attributevalue">1</span>" <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/>  <span class="attribute">when-iso</span>="<span class="attributevalue">2006-09-08T03:49+00</span>" <span class="attribute">who</span>="<span class="attributevalue">#WU00010804</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post14</span>"&gt;</span><br/>  <span class="element">&lt;p&gt;</span>I dont agree, this article is not about Dr. Meyer, [...]<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;/post&gt;</span><br/> <span class="element">&lt;post <span class="attribute">indentLevel</span>="<span class="attributevalue">2</span>" <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/>  <span class="attribute">when-iso</span>="<span class="attributevalue">2006-09-08T04:16+00</span>" <span class="attribute">who</span>="<span class="attributevalue">#WU00005520</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post15</span>"&gt;</span><br/>  <span class="element">&lt;p&gt;</span>Why don't you read the policy. [...]<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;/post&gt;</span><br/> <span class="element">&lt;post <span class="attribute">indentLevel</span>="<span class="attributevalue">3</span>" <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/>  <span class="attribute">when-iso</span>="<span class="attributevalue">2006-11-01T22:58+00</span>" <span class="attribute">who</span>="<span class="attributevalue">#WU00010815</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post16</span>"&gt;</span><br/>  <span class="element">&lt;p&gt;</span>Because the policy makes no sense, [...]<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;/div&gt;</span><div style="float: right;"><a href="BIB.html#BIB_WPTalkEiffel">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCcmcpostatts-egXML-zm">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCcmcatts"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCcmcpostatts"><span class="headingNumber">9.3.2. </span>Attributes Specific to CMC post</a></li><li class="subtoc"/><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCcmcatts" title="link to this section "><span class="invisible">TEI: Attributes for General CMC Encoding</span>⚓︎</a></span><span class="headingNumber">9.3.3. </span><span class="head">Attributes for General CMC Encoding</span></h3><p>The attribute <span class="att">generatedBy</span> is also unique to CMC encoding. But unlike <span class="att">modality</span>, <span class="att">replyTo</span>, and <span class="att">indentLevel</span>, <span class="att">generatedBy</span> is available not only on the <a class="gi" title="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." href="ref-post.html">post</a> element, but on any of its descendants as well. </p><ul class="specList"><li><span class="specList-classSpec"><a href="ref-att.cmc.html">att.cmc</a></span> (computer-mediated communication) provides attributes categorizing how the element content was created in a CMC environment.<table class="specDesc"><tr><td class="Attribute"><span class="att">generatedBy</span></td><td>(generated by) categorizes how the content of an element was generated in a CMC environment.
Suggested values include: 1] human; 2] template; 3] system; 4] bot; 5] unspecified</td></tr></table></li></ul><p>The <span class="att">generatedBy</span> attribute may indicate, for <a class="gi" title="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." href="ref-post.html">post</a> 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 content, such as in a signature), 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 <a class="gi" title="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." href="ref-post.html">post</a> element its value is presumed to be <span class="val">unspecified</span>; when it is unspecified on any descendant of <a class="gi" title="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." href="ref-post.html">post</a> its value is inherited from the immediately enclosing element. In turn, if <span class="att">generatedBy</span> is not specified on that element it inherits the value from its immediately enclosing element, and so on up the document hierarchy until a <a class="gi" title="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." href="ref-post.html">post</a> is reached; the <a class="gi" title="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." href="ref-post.html">post</a> either has a <span class="att">generatedBy</span> attribute specified or its presumed value is <span class="val">unspecified</span>.</p><p>A list of suggested values for <span class="att">generatedBy</span> follows: </p><dl><dt><span>human</span></dt><dd>when the content of the respective element was <span class="q">‘naturally’</span> typed or spoken by a human user (cf. the chat posts in example <a class="link_ref" href="CMC.html#ex.haarschnitt" title="Da kostet ein Haarschnitt 50 € face screaming in fearU+1F631">haircut</a>)</dd><dt><span>template</span></dt><dd>when the content of the respective element was generated after a human user activated a template for its insertion (often applicable to <a class="gi" title="(signature) contains the closing salutation, etc., appended to a foreword, dedicatory epistle, or other division of a text." href="ref-signed.html">signed</a> and <a class="gi" title="(time) contains a phrase defining a time of day in any format." href="ref-time.html">time</a>; e.g. see the signature in wiki talk in <a class="link_ref" href="CMC.html#ex.naturally" title="Im not sure that this is a proper criterium or even what this means. What if we set an explosion that breaks a comet into two p...">this example below</a>)</dd><dt><span>system</span></dt><dd>when the content of the respective element was generated by the system, i.e. the CMC environment (see, e.g., the system message in an IRC chat in the <a class="link_ref" href="CMC.html#ex.listPerson" title="Interseb betritt den Raum.">this other example below</a>)</dd><dt><span>bot</span></dt><dd>when the content of the respective element was generated by a bot, i.e. a non-human agent, typically one that is not part of the CMC environment itself</dd><dt><span>unspecified</span></dt><dd>when it is unspecified or unknown how the content of the respective element was generated (see, e.g. the retweet that forms the second <a class="gi" title="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." href="ref-post.html">post</a> in <a class="link_ref" href="CMC.html#ex.grunzen" title="1231 Heute mit super Unterstützung wir grunzen wenn die Zeit vorbei ist. bcrn18wikidach PS Die beiden brauchen noch Namen. Hinw...">this example below</a>).</dd></dl><div class="p">The following is a sample encoding of a chat post that contains an emoji. Although the post was written by a human, the emoji itself was marked in the source as having been generated by a template: <div id="ex.haarschnitt" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t003</span>" <span class="attribute">who</span>="<span class="attributevalue">#A02</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post18</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"&gt;</span> Da kostet ein Haarschnitt 50 €<br/><span class="element">&lt;figure <span class="attribute">type</span>="<span class="attributevalue">emoji</span>"<br/>  <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"&gt;</span><br/>  <span class="element">&lt;desc <span class="attribute">type</span>="<span class="attributevalue">label</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"&gt;</span>face screaming in fear<span class="element">&lt;/desc&gt;</span><br/>  <span class="element">&lt;desc <span class="attribute">type</span>="<span class="attributevalue">unicode</span>"&gt;</span>U+1F631<span class="element">&lt;/desc&gt;</span><br/> <span class="element">&lt;/figure&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_MoCoDa2">bibliography</a> <a class="bookmarklink" title="link to this example" href="#ex.haarschnitt">⚓︎</a></div></div></div><div class="p">In the following example, the user signature of a wiki talk post was inserted by activating a template, and is thus marked accordingly: <div id="ex.naturally" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post19</span>" <span class="attribute">indentLevel</span>="<span class="attributevalue">0</span>" <span class="attribute">who</span>="<span class="attributevalue">#u005</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t005</span>"&gt;</span><br/> <span class="element">&lt;p&gt;</span>I'm not sure that this is a proper criterium, or even what this means. What if we set<br/>   an explosion that breaks a comet into two pieces? What if we build a moon? Cheers,<br/> <span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;signed <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"<br/>  <span class="attribute">rend</span>="<span class="attributevalue">inline</span>"&gt;</span><br/>  <span class="element">&lt;ref <span class="attribute">target</span>="<span class="attributevalue">/wiki/User:Greenodd</span>"&gt;</span>Greenodd<span class="element">&lt;/ref&gt;</span> (<span class="element">&lt;ref <span class="attribute">target</span>="<span class="attributevalue">/wiki/User_talk:Greenodd</span>"&gt;</span>talk<span class="element">&lt;/ref&gt;</span>) <span class="element">&lt;time&gt;</span>01:00, 21<br/>     July 2011 (UTC)<span class="element">&lt;/time&gt;</span><br/> <span class="element">&lt;/signed&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_WPTalkAstronomicalObject">bibliography</a> <a class="bookmarklink" title="link to this example" href="#ex.naturally">⚓︎</a></div></div></div><div class="p">In the following example, a tweet is specified as having been written by a human; however inside the tweet, the timestamp is marked as generated by the CMC system: <div id="ex.grunzen" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>" <span class="attribute">type</span>="<span class="attributevalue">tweet</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#tweetsbcrn18.t001</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_1043764753502486528</span>" <span class="attribute">who</span>="<span class="attributevalue">#u1</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"&gt;</span><br/> <span class="element">&lt;time <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>"&gt;</span> 12:31 <span class="element">&lt;/time&gt;</span> Heute mit super Unterstützung, wir grunzen,<br/> wenn die Zeit vorbei ist. <span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">hashtag</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/hashtag/bcrn18?src=hash</span>"&gt;</span>#bcrn18<span class="element">&lt;/ref&gt;</span><br/> <span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">hashtag</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/hashtag/wikidach?src=hash</span>"&gt;</span>#wikidach<span class="element">&lt;/ref&gt;</span> PS: Die beiden brauchen noch Namen. Hinweise dazu am Empfang abgeben!<br/><span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">twitter-account</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/AndreLo79</span>"&gt;</span>@AndreLo79<span class="element">&lt;/ref&gt;</span><br/> <span class="element">&lt;figure <span class="attribute">type</span>="<span class="attributevalue">image</span>"&gt;</span><br/>  <span class="element">&lt;graphic <span class="attribute">url</span>="<span class="attributevalue">https://pbs.twimg.com/media/DnwygdSW4AAoTUn.jpg:large</span>"/&gt;</span><br/> <span class="element">&lt;/figure&gt;</span><br/><span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">unspecified</span>" <span class="attribute">type</span>="<span class="attributevalue">tweet</span>" <span class="attribute">who</span>="<span class="attributevalue">#u1</span>"<br/> <span class="attribute">synch</span>="<span class="attributevalue">#tweetsbcrn18.t002</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_1043769240136880128</span>"&gt;</span><br/> <span class="element">&lt;ptr <span class="attribute">type</span>="<span class="attributevalue">retweet</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">#cmc_post_1043767827927388160</span>"/&gt;</span><br/><span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">type</span>="<span class="attributevalue">tweet</span>" <span class="attribute">who</span>="<span class="attributevalue">#u3</span>"<br/> <span class="attribute">synch</span>="<span class="attributevalue">#tweetsbcrn18.t002</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_1043767827927388160</span>"&gt;</span><br/> <span class="element">&lt;time <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>"&gt;</span> 12:43 <span class="element">&lt;/time&gt;</span><br/> <span class="element">&lt;figure <span class="attribute">type</span>="<span class="attributevalue">image</span>" <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"&gt;</span><br/>  <span class="element">&lt;graphic <span class="attribute">url</span>="<span class="attributevalue">https://pbs.twimg.com/media/Dnw1TRNXgAAKqlK.jpg:large</span>"/&gt;</span><br/> <span class="element">&lt;/figure&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#ex.grunzen">⚓︎</a></div></div></div><div class="p">Finally, in the following example of an IRC post, the status message that user <span class="q">‘Interseb has entered the room’</span> was generated by the system, i.e. the chat environment. <div id="ex.listPerson" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">type</span>="<span class="attributevalue">event</span>" <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>"<br/> <span class="attribute">who</span>="<span class="attributevalue">#SYSTEM</span>" <span class="attribute">rend</span>="<span class="attributevalue">color:navy</span>"&gt;</span><br/> <span class="element">&lt;p&gt;</span><br/>  <span class="element">&lt;name <span class="attribute">type</span>="<span class="attributevalue">nickname</span>" <span class="attribute">ref</span>="<span class="attributevalue">#A07</span>"&gt;</span>Interseb<span class="element">&lt;/name&gt;</span> betritt den Raum.<span class="element">&lt;/p&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_DCK">bibliography</a> <a class="bookmarklink" title="link to this example" href="#ex.listPerson">⚓︎</a></div></div></div></div></div><div class="teidiv1" id="CMCmacrometa"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCcmc"><span class="headingNumber">9.3. </span>Encoding Unique to CMC</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCmetadata"><span class="headingNumber">9.5. </span>Documenting CMC (and providing general metadata)</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h2><span class="bookmarklink"><a class="bookmarklink" href="#CMCmacrometa" title="link to this section "><span class="invisible">TEI: CMC Macrostructure</span>⚓︎</a></span><span class="headingNumber">9.4. </span><span class="head">CMC Macrostructure</span></h2><p>In many CMC genres, posts may occur in a variety of ways: e.g. in a sequence or in threads, or grouped in some other way. For example, in chat communication such as WhatsApp, posts are part of <span class="q">‘a chat’</span> of one user with another user or among a group of users. When an entire chat is saved, typically a ‘logfile’ of the chat is obtained from the CMC system and downloaded. Similarly, Wikipedia discussions occur on a <span class="term">talk page</span>, which ultimately is a web page containing the user posts, sub-structured in threads. Likewise, YouTube comments occur on a webpage containing the YouTube video along with comment posts and posts replying to those comments displayed below the video. The video serves as a <span class="term">prompt</span> for the whole discussion. In forum discussions, the prompt may be a news item, and in Wikipedia, an article may be viewed as the prompt for the discussion on the talk page associated with that article.</p><div class="teidiv2" id="CMCmacro"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"/><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCthreads"><span class="headingNumber">9.4.2. </span>Sequences, Sections, Threads</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCmacro" title="link to this section "><span class="invisible">TEI: Macrostructure of CMC Collections and Documents</span>⚓︎</a></span><span class="headingNumber">9.4.1. </span><span class="head">Macrostructure of CMC Collections and Documents</span></h3><div class="p">When CMC documents are compiled into a collection, dataset, or corpus, we distinguish the following levels in the macrostructure of CMC in TEI: <dl><dt><span style="font-weight:bold">The corpus level</span></dt><dd><p>The level of a corpus or collection of CMC texts of a particular genre, generally obtained from a particular CMC platform, sometimes even from several platforms. This level may be represented by either a <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple &lt;TEI&gt; elements may be combined within a &lt;TEI&gt; (or &lt;teiCorpus&gt;) element." href="ref-TEI.html">TEI</a> element or a <a class="gi" title="(TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more &lt;TEI&gt; elements, each containing a single text header and a text." href="ref-teiCorpus.html">teiCorpus</a> element. The <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> of the corpus (i.e., the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> that is a child of the outermost <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple &lt;TEI&gt; elements may be combined within a &lt;TEI&gt; (or &lt;teiCorpus&gt;) element." href="ref-TEI.html">TEI</a> or <a class="gi" title="(TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more &lt;TEI&gt; elements, each containing a single text header and a text." href="ref-teiCorpus.html">teiCorpus</a>) will contain metadata in its <a class="gi" title="(source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as “born digital” for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> about the CMC platform(s). Metadata about the project responsible for collecting the data and building the corpus, if applicable, should be recorded as well.</p></dd><dt><span style="font-weight:bold">The document level</span></dt><dd><p>A set of posts collected (or sampled) by a researcher for analysis. The posts of the document will often map directly to the set of posts grouped on an existing web page, thread, or document within a CMC environment. Within the CMC environment the document as such is often created by a particular user, thereby initiating the communication which other users may read, and to which some other users might contribute. This level will naturally be represented by the <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple &lt;TEI&gt; elements may be combined within a &lt;TEI&gt; (or &lt;teiCorpus&gt;) element." href="ref-TEI.html">TEI</a> element. The <a class="gi" title="(TEI corpus) contains the whole of a TEI encoded corpus, comprising a single corpus header and one or more &lt;TEI&gt; elements, each containing a single text header and a text." href="ref-teiCorpus.html">teiCorpus</a> (or <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple &lt;TEI&gt; elements may be combined within a &lt;TEI&gt; (or &lt;teiCorpus&gt;) element." href="ref-TEI.html">TEI</a>) element that represents the corpus will contain one or more <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple &lt;TEI&gt; elements may be combined within a &lt;TEI&gt; (or &lt;teiCorpus&gt;) element." href="ref-TEI.html">TEI</a> elements as usual.</p> <p>In the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> of a document level <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple &lt;TEI&gt; elements may be combined within a &lt;TEI&gt; (or &lt;teiCorpus&gt;) element." href="ref-TEI.html">TEI</a>, the <a class="gi" title="(source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as “born digital” for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> will contain metadata about the CMC document such as a title, its author or owner, its URL, the date of its creation, the date of the last change made to it, and other metadata that are available and to be recorded such as one or more categories associated with the document.</p> <p>The document sometimes contains, or is associated with, a prompt such as a video or a news item, either provided by the initiating user herself or located elsewhere and referenced at the beginning of the document. In such cases, the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> of the document should also contain metadata about this prompt.</p></dd><dt><span style="font-weight:bold">The post level</span></dt><dd><p>The level of the individual post is naturally represented by the <a class="gi" title="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." href="ref-post.html">post</a> element; its encoding is further described in section <a class="link_ptr" href="CMC.html#CMCcmcpost" title="CMC Posts"><span class="headingNumber">9.3.1. </span>CMC Posts</a>. A <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple &lt;TEI&gt; elements may be combined within a &lt;TEI&gt; (or &lt;teiCorpus&gt;) element." href="ref-TEI.html">TEI</a> element will contain a number of <a class="gi" title="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." href="ref-post.html">post</a> elements, which can be grouped or ordered in <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> elements representing sequences or threads (section <a class="link_ptr" href="CMC.html#CMCthreads" title="Sequences Sections Threads"><span class="headingNumber">9.4.2. </span>Sequences, Sections, Threads</a>) if appropriate.</p></dd></dl> <div id="macrostructure" class="pre egXML_feasible"><span class="element">&lt;teiCorpus xmlns="http://www.tei-c.org/ns/1.0"&gt;</span><br/><span class="comment">&lt;!-- a corpus, collection or dataset of CMC documents --&gt;</span><br/> <span class="element">&lt;teiHeader&gt;</span><br/><span class="comment">&lt;!-- metadata pertaining to the corpus or CMC dataset--&gt;</span><br/> <span class="element">&lt;/teiHeader&gt;</span><br/> <span class="element">&lt;TEI&gt;</span><br/><span class="comment">&lt;!-- a CMC document such as a chat log or a discussion page --&gt;</span><br/>  <span class="element">&lt;teiHeader&gt;</span><br/><span class="comment">&lt;!-- metadata pertaining to the CMC document --&gt;</span><br/>  <span class="element">&lt;/teiHeader&gt;</span><br/>  <span class="element">&lt;text&gt;</span><br/>   <span class="element">&lt;body&gt;</span><br/>    <span class="element">&lt;div&gt;</span><br/><span class="comment">&lt;!-- subdivisions of the CMC document e.g. in sections or threads if applicable--&gt;</span><br/>     <span class="element">&lt;post&gt;</span><br/><span class="comment">&lt;!-- one post --&gt;</span><br/>     <span class="element">&lt;/post&gt;</span><br/><span class="comment">&lt;!-- more posts --&gt;</span><br/>    <span class="element">&lt;/div&gt;</span><br/>   <span class="element">&lt;/body&gt;</span><br/>  <span class="element">&lt;/text&gt;</span><br/> <span class="element">&lt;/TEI&gt;</span><br/><span class="comment">&lt;!-- more documents --&gt;</span><br/><span class="element">&lt;/teiCorpus&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#macrostructure">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCthreads"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCmacro"><span class="headingNumber">9.4.1. </span>Macrostructure of CMC Collections and Documents</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCmultimodal"><span class="headingNumber">9.4.3. </span>Multimodal CMC</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCthreads" title="link to this section "><span class="invisible">TEI: Sequences, Sections, Threads</span>⚓︎</a></span><span class="headingNumber">9.4.2. </span><span class="head">Sequences, Sections, Threads</span></h3><p>As shown in Example <a class="link_ptr" href="CMC.html#CMCcmcpostatts" title="Attributes Specific to CMC post"><span class="headingNumber">9.3.2. </span>Attributes Specific to CMC post</a> above, nested threads of posts may be encoded sequentially, while the <span class="att">indentLevel</span> attribute of <a class="gi" title="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." href="ref-post.html">post</a> 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 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 <span class="att">replyTo</span> attribute on <a class="gi" title="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." href="ref-post.html">post</a> elements, as shown in the second example of <a class="link_ptr" href="CMC.html#CMCcmcpostatts" title="Attributes Specific to CMC post"><span class="headingNumber">9.3.2. </span>Attributes Specific to CMC post</a>. The network of all reply links will then also form a threaded structure, and visual indentations can be reconstructed from it and need not be explicitly encoded.</p><div class="p">Threads may also be explicitly encoded as nested <a class="gi" title="(text division) contains a subdivision of the front, body, or back of a text." href="ref-div.html">div</a> elements as in the following skeleton: <div id="CMCthreads-egXML-go" class="pre egXML_valid"><span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">thread</span>" <span class="attribute">n</span>="<span class="attributevalue">0</span>"&gt;</span><br/> <span class="element">&lt;post&gt;</span>...<span class="element">&lt;/post&gt;</span><br/> <span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">thread</span>" <span class="attribute">n</span>="<span class="attributevalue">1</span>"&gt;</span><br/>  <span class="element">&lt;post&gt;</span> ... <span class="element">&lt;/post&gt;</span><br/>  <span class="element">&lt;post&gt;</span> ... <span class="element">&lt;/post&gt;</span><br/>  <span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">thread</span>" <span class="attribute">n</span>="<span class="attributevalue">2</span>"&gt;</span><br/><span class="comment">&lt;!-- posts --&gt;</span><br/>  <span class="element">&lt;/div&gt;</span><br/> <span class="element">&lt;/div&gt;</span><br/><span class="element">&lt;/div&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCthreads-egXML-go">⚓︎</a></div></div></div><div class="p">Using this encoding strategy, <a class="link_ref" href="CMC.html#e9" title="Es hat den Anschein als wäre bei BER durchaus große Kompetenz am Bau allerdings nicht in Form von Handwerkern.httpwww.zeit.de20...">this example</a> from <a class="link_ptr" href="CMC.html#CMCcmcpostatts" title="Attributes Specific to CMC post"><span class="headingNumber">9.3.2. </span>Attributes Specific to CMC post</a> could be encoded as follows: <div id="CMCthreads-egXML-gd" class="pre egXML_valid"><span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">thread</span>" <span class="attribute">n</span>="<span class="attributevalue">0</span>"&gt;</span><br/> <span class="element">&lt;post <span class="attribute">type</span>="<span class="attributevalue">comment</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post01</span>"<br/>  <span class="attribute">who</span>="<span class="attributevalue">#u7</span>" <span class="attribute">when-iso</span>="<span class="attributevalue">2015-07-29T21:44</span>"&gt;</span><br/>  <span class="element">&lt;p&gt;</span>Es hat den Anschein, ...<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;/post&gt;</span><br/> <span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">thread</span>" <span class="attribute">n</span>="<span class="attributevalue">1</span>"&gt;</span><br/>  <span class="element">&lt;post <span class="attribute">type</span>="<span class="attributevalue">comment</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post02</span>"<br/>   <span class="attribute">who</span>="<span class="attributevalue">#u8</span>" <span class="attribute">when-iso</span>="<span class="attributevalue">2015-07-30T19:11</span>"&gt;</span><br/>   <span class="element">&lt;p&gt;</span>Nein Nein, an den Handwerkern kann es ...<span class="element">&lt;/p&gt;</span><br/>  <span class="element">&lt;/post&gt;</span><br/>  <span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">thread</span>" <span class="attribute">n</span>="<span class="attributevalue">2</span>"&gt;</span><br/>   <span class="element">&lt;post <span class="attribute">type</span>="<span class="attributevalue">comment</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post03</span>"<br/>    <span class="attribute">who</span>="<span class="attributevalue">#u8</span>" <span class="attribute">when-iso</span>="<span class="attributevalue">2015-07-30T19:26</span>"&gt;</span><br/>    <span class="element">&lt;p&gt;</span>Stahlkunstruktionen dacht ich mal, ....<span class="element">&lt;/p&gt;</span><br/>   <span class="element">&lt;/post&gt;</span><br/>  <span class="element">&lt;/div&gt;</span><br/> <span class="element">&lt;/div&gt;</span><br/><span class="element">&lt;/div&gt;</span><div style="float: right;"><a href="BIB.html#BIB_scilog1">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCthreads-egXML-gd">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCmultimodal"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCthreads"><span class="headingNumber">9.4.2. </span>Sequences, Sections, Threads</a></li><li class="subtoc"/><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCmultimodal" title="link to this section "><span class="invisible">TEI: Multimodal CMC</span>⚓︎</a></span><span class="headingNumber">9.4.3. </span><span class="head">Multimodal CMC</span></h3><p>As explained in section <a class="link_ptr" href="CMC.html#CMCUnits" title="Basic Units of CMC"><span class="headingNumber">9.2. </span>Basic Units of CMC</a>, the elements <a class="gi" title="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." href="ref-post.html">post</a>, <a class="gi" title="(utterance) contains a stretch of speech usually preceded and followed by silence or by a change of speaker." href="ref-u.html">u</a>, <a class="gi" title="(kinesic) marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc." href="ref-kinesic.html">kinesic</a>, and <a class="gi" title="(incident) marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication." href="ref-incident.html">incident</a> are available to encode textual transcriptions of written posts, spoken turns, bodily activities of avatars, and onscreen activity by users that occur in CMC data; and, as discussed in section <a class="link_ptr" href="CMC.html#CMCcmcpostatts" title="Attributes Specific to CMC post"><span class="headingNumber">9.3.2. </span>Attributes Specific to CMC post</a>, graphics or other media data within posts are encoded in a <a class="gi" title="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." href="ref-post.html">post</a> with <span class="att">modality</span> set to <span class="val">written</span>. When two or more of these features occur in a CMC interaction, we can speak of <span class="term">multimodal</span> CMC.</p><p>Some basic multimodality is available in many private chat systems such as WhatsApp, where spoken and written posts and media posts containing images or video clips can alternate in the sequence of posts. The following shows the suggested encoding of an extended part of the <span style="font-style:italic">haircut</span> chat example from above, including a spoken post, several written posts, and a post containing a graphic image (adapted from the MoCoDa2 corpus <a class="link_ptr" href="BIB.html#BIB_MoCoDa2" title="Mobile Communication Database 2 (MoCoDa2) Michael Beißwenger Evelyn Ziegler Marcel Fladrich Wolfgang Imo Katharina König httpsd...">Beißwenger et al. (eds.) (visited 30 March 2022)</a>)</p><div id="CMCmultimodal-egXML-vr" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">spoken</span>" <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"<br/> <span class="attribute">synch</span>="<span class="attributevalue">#cmc-haircut_t004</span>" <span class="attribute">who</span>="<span class="attributevalue">#cmc-haircut_A05</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc-haircut_m9</span>"&gt;</span> In Düsseldorf gibt's da so Abstufungen. Da gibt's einmal Oliver<br/> Schmidt, Oliver Schmidt's Hair Design, also dann, ist eher also, keine Ahnung, zum<br/> Beispiel ich war da bei dem etwas Günstigeren dann. Ich weiß nicht, ob's das in Essen auch<br/> gibt diese Abstufungen <span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#cmc-haircut_t004</span>"<br/> <span class="attribute">who</span>="<span class="attributevalue">#cmc-haircut_A02</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc-haircut_m10</span>"&gt;</span> Ich schau mal :) <span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#cmc-haircut_t005</span>"<br/> <span class="attribute">who</span>="<span class="attributevalue">#cmc-haircut_A06</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc-haircut_m11</span>"&gt;</span> Ich gehe immer nach Katernberg zu Pasha’s<br/> haarem Hahaha also die sind echt entspannt und gut und nicht teuer <span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#tcmc-haircut_005</span>"<br/> <span class="attribute">who</span>="<span class="attributevalue">#cmc-haircut_A06</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc-haircut_m12</span>"&gt;</span><br/> <span class="element">&lt;figure <span class="attribute">type</span>="<span class="attributevalue">image</span>" <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"&gt;</span><br/>  <span class="element">&lt;desc <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"&gt;</span>screenshot of the google search for hairdresser "Pasha's Haare'm"<br/>     with the average google rating (4,5 of 5 stars), the address, the phone number, and<br/>     the opening hours. <span class="element">&lt;/desc&gt;</span><br/> <span class="element">&lt;/figure&gt;</span><br/><span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#cmc-haircut_t006</span>"<br/> <span class="attribute">who</span>="<span class="attributevalue">#cmc-haircut_A03</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc-haircut_m13</span>"&gt;</span> Olivers hair und Oliver Schmidt gehören<br/> zusammen <span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_MoCoDa2">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCmultimodal-egXML-vr">⚓︎</a></div></div><div class="p">In the graphical user interface (GUI) of a more complex multimodal CMC environment such as Second Life, a gaming and learning platform, interactions may consist of interleaved occurrences of posts (<a class="gi" title="(paragraph) marks paragraphs in prose." href="ref-p.html">p</a>), utterances (<a class="gi" title="(utterance) contains a stretch of speech usually preceded and followed by silence or by a change of speaker." href="ref-u.html">u</a>) and nonverbal acts such as bodily activities (<a class="gi" title="(kinesic) marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc." href="ref-kinesic.html">kinesic</a>) or other on-screen activities (<a class="gi" title="(incident) marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication." href="ref-incident.html">incident</a>). In the following example a spoken utterance, an avatar's bodily activity, and a written post occur on the same level within the <a class="gi" title="(text body) contains the whole body of a single unitary text, excluding any front or back matter." href="ref-body.html">body</a> element, representing parts of a multimodal chat in Second Life (adapted from the <a class="link_ref" href="BIB.html#BIB_ChanierWigham2015" title="Ciara Wigham Thierry Chanier Interactions between text chat and audio modalities for L2 communication and feedback in the synth...">Archi21 corpus</a>). <div id="CMCmultimodal-egXML-hz" class="pre egXML_valid"><span class="element">&lt;text&gt;</span><br/> <span class="element">&lt;body&gt;</span><br/>  <span class="element">&lt;u <span class="attribute">xml:id</span>="<span class="attributevalue">cmr-archi21-slrefl-es-j3-1-a191</span>"<br/>   <span class="attribute">who</span>="<span class="attributevalue">#tingrabu</span>"<br/>   <span class="attribute">start</span>="<span class="attributevalue">#cmr-archi21-slrefl-es-j3-1-ts373</span>" <span class="attribute">end</span>="<span class="attributevalue">#cmr-archi21-slrefl-es-j3-1-ts430</span>"&gt;</span>ok<br/>     hm for me this presentation was hm <span class="element">&lt;pause <span class="attribute">dur</span>="<span class="attributevalue">PT1S</span>"/&gt;</span> become too fast because it's<br/>     always the same in our architecture school euh we have not time and hm <span class="element">&lt;pause <span class="attribute">dur</span>="<span class="attributevalue">PT1S</span>"/&gt;</span> too quickly sorry [...]<span class="element">&lt;/u&gt;</span><br/>  <span class="element">&lt;kinesic <span class="attribute">xml:id</span>="<span class="attributevalue">cmr-archi21-slrefl-es-j3-1-a192</span>"<br/>   <span class="attribute">who</span>="<span class="attributevalue">#romeorez</span>"<br/>   <span class="attribute">start</span>="<span class="attributevalue">#cmr-archi21-slrefl-es-j3-1-ts376</span>" <span class="attribute">end</span>="<span class="attributevalue">#cmr-archi21-slrefl-es-j3-1-ts377</span>"<br/>   <span class="attribute">type</span>="<span class="attributevalue">body</span>" <span class="attribute">subtype</span>="<span class="attributevalue">kinesics</span>"&gt;</span><br/>   <span class="element">&lt;desc&gt;</span><br/>    <span class="element">&lt;code&gt;</span>eat(popcorn)<span class="element">&lt;/code&gt;</span><br/>   <span class="element">&lt;/desc&gt;</span><br/>  <span class="element">&lt;/kinesic&gt;</span><br/><span class="comment">&lt;!-- more bodily activities of avatars --&gt;</span><br/>  <span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/>   <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmr-archi21-slrefl-es-j3-1-a195</span>"<br/>   <span class="attribute">who</span>="<span class="attributevalue">#tfrez2</span>"<br/>   <span class="attribute">start</span>="<span class="attributevalue">#cmr-archi21-slrefl-es-j3-1-ts380</span>" <span class="attribute">end</span>="<span class="attributevalue">#cmr-archi21-slrefl-es-j3-1-ts381</span>"<br/>   <span class="attribute">type</span>="<span class="attributevalue">chat-message</span>"&gt;</span><br/>   <span class="element">&lt;p&gt;</span>it went too quickly?<span class="element">&lt;/p&gt;</span><br/>  <span class="element">&lt;/post&gt;</span><br/> <span class="element">&lt;/body&gt;</span><br/><span class="element">&lt;/text&gt;</span><div style="float: right;"><a href="BIB.html#BIB_ChanierWigham2015">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCmultimodal-egXML-hz">⚓︎</a></div></div></div><p>Note that the spoken utterance <a class="gi" title="(utterance) contains a stretch of speech usually preceded and followed by silence or by a change of speaker." href="ref-u.html">u</a> represents a speaker turn that was transmitted via an audio channel of the application that is continuously open during a session, whereas a spoken <a class="gi" title="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." href="ref-post.html">post</a> represents a spoken message that has been recorded in private and been posted to the CMC server as a whole. See section <a class="link_ptr" href="CMC.html#CMCUnits" title="Basic Units of CMC"><span class="headingNumber">9.2. </span>Basic Units of CMC</a>.</p></div></div><div class="teidiv1" id="CMCmetadata"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCmacrometa"><span class="headingNumber">9.4. </span>CMC Macrostructure</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCrecs"><span class="headingNumber">9.6. </span>Recommendations for Encoding CMC Microstructure</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h2><span class="bookmarklink"><a class="bookmarklink" href="#CMCmetadata" title="link to this section "><span class="invisible">TEI: Documenting CMC (and providing general metadata)</span>⚓︎</a></span><span class="headingNumber">9.5. </span><span class="head">Documenting CMC (and providing general metadata)</span></h2><div class="teidiv2" id="CMCCorpusSource"><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCCorpusSource" title="link to this section "><span class="invisible">TEI: Documenting the Source of a Corpus of CMC data</span>⚓︎</a></span><span class="headingNumber">9.5.1. </span><span class="head">Documenting the Source of a Corpus of CMC data</span></h3><p>The <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> of the corpus should contain metadata about the CMC platform(s), e.g. its name, information about its owner (often a company) including their address or location, the URL of the server where the CMC data were collected from, or the filename of a database dump that was used as a source. Metadata about the project responsible for collecting the data and building the corpus, if applicable, should be recorded as well.</p><div class="p">The following example shows the <a class="gi" title="(source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as “born digital” for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> of a X (Twitter) corpus. <div id="CMCCorpusSource-egXML-zu" class="pre egXML_valid"><span class="element">&lt;sourceDesc&gt;</span><br/> <span class="element">&lt;biblFull&gt;</span><br/>  <span class="element">&lt;titleStmt&gt;</span><br/>   <span class="element">&lt;title&gt;</span>Twitter Sample<span class="element">&lt;/title&gt;</span><br/>  <span class="element">&lt;/titleStmt&gt;</span><br/>  <span class="element">&lt;publicationStmt&gt;</span><br/>   <span class="element">&lt;distributor&gt;</span>Twitter International Company<span class="element">&lt;/distributor&gt;</span><br/>   <span class="element">&lt;address&gt;</span><br/>    <span class="element">&lt;addrLine&gt;</span>1 Cumberland Place<span class="element">&lt;/addrLine&gt;</span><br/>    <span class="element">&lt;addrLine&gt;</span>Fenian Street<span class="element">&lt;/addrLine&gt;</span><br/>    <span class="element">&lt;addrLine&gt;</span>Dublin 2<span class="element">&lt;/addrLine&gt;</span><br/>    <span class="element">&lt;postCode&gt;</span>D02 AX07<span class="element">&lt;/postCode&gt;</span><br/>    <span class="element">&lt;country&gt;</span>Ireland<span class="element">&lt;/country&gt;</span><br/>   <span class="element">&lt;/address&gt;</span><br/>   <span class="element">&lt;ptr <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/</span>"/&gt;</span><br/>   <span class="element">&lt;date <span class="attribute">when</span>="<span class="attributevalue">2024-04-27</span>"/&gt;</span><br/>  <span class="element">&lt;/publicationStmt&gt;</span><br/> <span class="element">&lt;/biblFull&gt;</span><br/><span class="element">&lt;/sourceDesc&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCCorpusSource-egXML-zu">⚓︎</a></div></div></div><div class="p">The following example shows how a Wikipedia database dump may be encoded as the source. <div id="CMCCorpusSource-egXML-yn" class="pre egXML_valid"><span class="element">&lt;sourceDesc&gt;</span><br/> <span class="element">&lt;biblFull&gt;</span><br/>  <span class="element">&lt;titleStmt&gt;</span><br/>   <span class="element">&lt;title&gt;</span>German Wikipedia Data Dump of 2019-08-01<span class="element">&lt;/title&gt;</span><br/>  <span class="element">&lt;/titleStmt&gt;</span><br/>  <span class="element">&lt;editionStmt&gt;</span><br/>   <span class="element">&lt;edition&gt;</span>Dump file in XML (compressed)<span class="element">&lt;/edition&gt;</span><br/>  <span class="element">&lt;/editionStmt&gt;</span><br/>  <span class="element">&lt;extent&gt;</span><br/>   <span class="element">&lt;measure <span class="attribute">unit</span>="<span class="attributevalue">GiB</span>" <span class="attribute">quantity</span>="<span class="attributevalue">7.9</span>"/&gt;</span><br/>  <span class="element">&lt;/extent&gt;</span><br/>  <span class="element">&lt;publicationStmt&gt;</span><br/>   <span class="element">&lt;publisher&gt;</span>Wikimedia Foundation, Inc.<span class="element">&lt;/publisher&gt;</span><br/>   <span class="element">&lt;pubPlace&gt;</span><br/>    <span class="element">&lt;ptr <span class="attribute">target</span>="<span class="attributevalue">https://dumps.wikimedia.org/</span>"/&gt;</span><br/>   <span class="element">&lt;/pubPlace&gt;</span><br/>   <span class="element">&lt;date <span class="attribute">when</span>="<span class="attributevalue">2019-08-01</span>"&gt;</span>01 Aug 19<span class="element">&lt;/date&gt;</span><br/>   <span class="element">&lt;idno <span class="attribute">type</span>="<span class="attributevalue">dump-filename</span>"&gt;</span>dewiki-2019-08-01-pages-meta-current<span class="element">&lt;/idno&gt;</span><br/>  <span class="element">&lt;/publicationStmt&gt;</span><br/> <span class="element">&lt;/biblFull&gt;</span><br/><span class="element">&lt;/sourceDesc&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCCorpusSource-egXML-yn">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCDocumentSource"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCCorpusSource"><span class="headingNumber">9.5.1. </span>Documenting the Source of a Corpus of CMC data</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCSampling"><span class="headingNumber">9.5.3. </span>Documenting the Sampling of CMC data</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCDocumentSource" title="link to this section "><span class="invisible">TEI: Describing the Source of a CMC Document</span>⚓︎</a></span><span class="headingNumber">9.5.2. </span><span class="head">Describing the Source of a CMC Document</span></h3><p>A CMC document may be a chat logfile, a discussion page, or a thematical thread of posts as encoded within a <a class="gi" title="(TEI document) contains a single TEI-conformant document, combining a single TEI header with one or more members of the model.resource class. Multiple &lt;TEI&gt; elements may be combined within a &lt;TEI&gt; (or &lt;teiCorpus&gt;) element." href="ref-TEI.html">TEI</a> element. Among the metadata to be recorded in the <a class="gi" title="(source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as “born digital” for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> of its <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> are, if available, its title, author or owner, its URL, the date of its creation and/or the date of its last change (i.e. the time when the last post was added to it).</p><div class="p">The following example is the <a class="gi" title="(source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as “born digital” for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> of a TEI encoding of a YouTube page that contained a video and user comments on the video (which are encoded in the <a class="gi" title="(text body) contains the whole body of a single unitary text, excluding any front or back matter." href="ref-body.html">body</a> of the text as posts). The metadata contain a URL reference to the video and the YouTube channel that posted the video in <a class="gi" title="contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it." href="ref-relatedItem.html">relatedItem</a> elements. The date when the page was created is not known. The example is adapted from the NottDeuYTSch corpus (<a class="link_ptr" href="BIB.html#BIB_Cotgrove" title="Louis Alexander Cotgrove Nottinghamer Korpus Deutscher YouTubeSprache (The NottDeuYTSch Corpus) httphdl.handle.net11372LRT4806 ...">Cotgrove (ed.) (2018)</a>), where the video itself is not contained in the corpus. <div id="CMCDocumentSource-egXML-mg" class="pre egXML_valid"><span class="element">&lt;sourceDesc&gt;</span><br/> <span class="element">&lt;bibl&gt;</span><br/>  <span class="element">&lt;title <span class="attribute">type</span>="<span class="attributevalue">main</span>"&gt;</span>Iron Man 3 in 3D (Official Trailer German) Parodie<span class="element">&lt;/title&gt;</span><br/>  <span class="element">&lt;respStmt&gt;</span><br/>   <span class="element">&lt;name <span class="attribute">type</span>="<span class="attributevalue">user</span>"&gt;</span>DieAussenseiter<span class="element">&lt;/name&gt;</span><br/>   <span class="element">&lt;resp&gt;</span>posted video, created page<span class="element">&lt;/resp&gt;</span><br/>  <span class="element">&lt;/respStmt&gt;</span><br/>  <span class="element">&lt;distributor&gt;</span>YouTube<span class="element">&lt;/distributor&gt;</span><br/>  <span class="element">&lt;ptr <span class="attribute">type</span>="<span class="attributevalue">url</span>"<br/>   <span class="attribute">target</span>="<span class="attributevalue">https://www.youtube.com/watch?v=T-WU_3-0UpU</span>"/&gt;</span><br/>  <span class="element">&lt;series&gt;</span><br/>   <span class="element">&lt;title&gt;</span>DieAussenseiter’s Channel<span class="element">&lt;/title&gt;</span><br/>   <span class="element">&lt;ptr <span class="attribute">target</span>="<span class="attributevalue">https://www.youtube.com/watch?v=UCKn1vL4Ou4DKu0BlcK3NlDQ</span>"/&gt;</span><br/>  <span class="element">&lt;/series&gt;</span><br/> <span class="element">&lt;/bibl&gt;</span><br/><span class="element">&lt;/sourceDesc&gt;</span><div style="float: right;"><a href="BIB.html#BIB_Cotgrove">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCDocumentSource-egXML-mg">⚓︎</a></div></div></div><div class="p">The following example is the <a class="gi" title="(source description) describes the source(s) from which an electronic text was derived or generated, typically a bibliographic description in the case of a digitized text, or a phrase such as “born digital” for a text which has no previous existence." href="ref-sourceDesc.html">sourceDesc</a> of a Wikipedia talk page. Note that a <a class="gi" title="contains or references some other bibliographic item which is related to the present one in some specified manner, for example as a constituent or alternative version of it." href="ref-relatedItem.html">relatedItem</a> element is used to record a reference to the Wikipedia article that the transcribed discussion is about. <div id="CMCDocumentSource-egXML-pi" class="pre egXML_valid"><span class="element">&lt;sourceDesc&gt;</span><br/> <span class="element">&lt;bibl&gt;</span><br/>  <span class="element">&lt;title <span class="attribute">type</span>="<span class="attributevalue">main</span>"&gt;</span>Diskussion:FKM-Richtlinie<span class="element">&lt;/title&gt;</span><br/>  <span class="element">&lt;author&gt;</span><br/>   <span class="element">&lt;name <span class="attribute">type</span>="<span class="attributevalue">user</span>"&gt;</span>OnkelSchuppig<span class="element">&lt;/name&gt;</span>, et al.<span class="element">&lt;/author&gt;</span><br/>  <span class="element">&lt;publisher&gt;</span>Wikimedia Foundation, Inc.<span class="element">&lt;/publisher&gt;</span><br/>  <span class="element">&lt;ptr <span class="attribute">target</span>="<span class="attributevalue">https://de.wikipedia.org/wiki/Diskussion:FKM-Richtlinie</span>"<br/>   <span class="attribute">type</span>="<span class="attributevalue">page_url</span>" <span class="attribute">targetLang</span>="<span class="attributevalue">de</span>"/&gt;</span><br/>  <span class="element">&lt;date <span class="attribute">type</span>="<span class="attributevalue">last-change</span>"<br/>   <span class="attribute">when</span>="<span class="attributevalue">2013-09-14T17:04:48Z</span>"/&gt;</span><br/>  <span class="element">&lt;idno <span class="attribute">type</span>="<span class="attributevalue">wikipedia-id</span>"&gt;</span>7632113<span class="element">&lt;/idno&gt;</span><br/>  <span class="element">&lt;relatedItem <span class="attribute">type</span>="<span class="attributevalue">articleLink</span>"&gt;</span><br/>   <span class="element">&lt;ref <span class="attribute">n</span>="<span class="attributevalue">5138958</span>"<br/>    <span class="attribute">target</span>="<span class="attributevalue">https://de.wikipedia.org/wiki/FKM-Richtlinie</span>" <span class="attribute">targetLang</span>="<span class="attributevalue">de</span>"&gt;</span>FKM-Richtlinie<span class="element">&lt;/ref&gt;</span><br/>  <span class="element">&lt;/relatedItem&gt;</span><br/> <span class="element">&lt;/bibl&gt;</span><br/><span class="element">&lt;/sourceDesc&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCDocumentSource-egXML-pi">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCSampling"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCDocumentSource"><span class="headingNumber">9.5.2. </span>Describing the Source of a CMC Document</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCParticipants"><span class="headingNumber">9.5.4. </span>Participants</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCSampling" title="link to this section "><span class="invisible">TEI: Documenting the Sampling of CMC data</span>⚓︎</a></span><span class="headingNumber">9.5.3. </span><span class="head">Documenting the Sampling of CMC data</span></h3><p>The documentation of how the data were collected, e.g. how it was scraped or sampled from the web, or downloaded from a server, should be recorded in the <a class="gi" title="(sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource." href="ref-samplingDecl.html">samplingDecl</a>. Like other metadata, information about sampling should be recorded at the highest level applicable. That is, if the information applies to an entire corpus, the <a class="gi" title="(sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource." href="ref-samplingDecl.html">samplingDecl</a> should appear in the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> of the corpus level; if the information is different for each document, it should appear in the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> of the document level texts.</p><div class="p">The sampling information typically considered of interest consists of at least the following four components: <ul><li class="item">interface: The API that was used for the download, possibly encoded as a <span class="tag">&lt;name type="API"&gt;</span>;</li><li class="item">client: The client or other tool that was used for the download, possibly encoded as a <span class="tag">&lt;name type="client"&gt;</span>;</li><li class="item">query: The query or command used for the download, possibly encoded with a <span class="tag">&lt;ptr type="query"&gt;</span> when it is a URI, or a <a class="gi" title="contains literal code from some formal language such as a programming language." href="ref-code.html">code</a> when it is a command;</li><li class="item">date: The date of the download.</li></ul> For example, in the case of an X (Twitter) corpus a sampling declaration might look like the following: <div id="CMCSampling-egXML-on" class="pre egXML_valid"><span class="element">&lt;samplingDecl&gt;</span><br/> <span class="element">&lt;p&gt;</span>Sampled using the <span class="element">&lt;name <span class="attribute">type</span>="<span class="attributevalue">API</span>"&gt;</span>Twitter Filtered stream v2-API<span class="element">&lt;/name&gt;</span> (see <span class="element">&lt;ptr <span class="attribute">type</span>="<span class="attributevalue">APIdoc</span>"<br/>   <span class="attribute">target</span>="<span class="attributevalue">https://developer.twitter.com/en/docs/twitter-api/tweets/filtered-stream/api-reference/get-tweets-search-stream</span>"/&gt;</span>) Filtered for the German language and the following countries: Germany, Austria,<br/>   Belgium, Switzerland, Denmark, and Luxembourg. Downloaded on <span class="element">&lt;date <span class="attribute">when</span>="<span class="attributevalue">2022-12-12</span>"&gt;</span>Mon 12 Dec 22<span class="element">&lt;/date&gt;</span> using the command<br/> <span class="element">&lt;code&gt;</span>requests.get("https://api.twitter.com/2/tweets/search/stream",<br/>     headers=headers, params=params, stream=True,)<span class="element">&lt;/code&gt;</span> in the python script <span class="element">&lt;name <span class="attribute">type</span>="<span class="attributevalue">script</span>"&gt;</span>collectFilteredTwitterStream.py<span class="element">&lt;/name&gt;</span>. <span class="element">&lt;/p&gt;</span><br/><span class="element">&lt;/samplingDecl&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCSampling-egXML-on">⚓︎</a></div></div></div><div class="p">The <a class="gi" title="(sampling declaration) contains a prose description of the rationale and methods used in selecting texts, or parts of a text, for inclusion in the resource." href="ref-samplingDecl.html">samplingDecl</a> of a Usenet Newsgroup corpus: <div id="CMCSampling-egXML-sx" class="pre egXML_valid"><span class="element">&lt;samplingDecl&gt;</span><br/> <span class="element">&lt;p&gt;</span>Downloaded from the news.individual.de server on 2016-01-15 using nntp client in<br/>   Python<span class="element">&lt;/p&gt;</span><br/><span class="element">&lt;/samplingDecl&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCSampling-egXML-sx">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCParticipants"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCSampling"><span class="headingNumber">9.5.3. </span>Documenting the Sampling of CMC data</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCTimeline"><span class="headingNumber">9.5.5. </span>Timeline</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCParticipants" title="link to this section "><span class="invisible">TEI: Participants</span>⚓︎</a></span><span class="headingNumber">9.5.4. </span><span class="head">Participants</span></h3><p>A <a class="gi" title="(list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source." href="ref-listPerson.html">listPerson</a> may be used to maintain an inventory of users and bots taking part in a CMC interaction, along with information about them. As with other such contextual information, it may be kept in the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a> (where it would occur in a <a class="gi" title="(participation description) describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata." href="ref-particDesc.html">particDesc</a> within a <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a>) or in a separate document completely. In either case, an encoded <a class="gi" title="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." href="ref-post.html">post</a> may then be linked to its author by use of the <span class="att">who</span> attribute.</p><div class="p">In the following example, a list of participants is maintained in a <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a>. <div id="CMCParticipants-egXML-mu" class="pre egXML_valid"><br/><span class="comment">&lt;!-- In the &lt;teiHeader&gt;: --&gt;</span><span class="element">&lt;profileDesc&gt;</span><br/> <span class="element">&lt;particDesc&gt;</span><br/>  <span class="element">&lt;listPerson&gt;</span><br/>   <span class="element">&lt;person <span class="attribute">role</span>="<span class="attributevalue">user</span>" <span class="attribute">sex</span>="<span class="attributevalue">male</span>"<br/>    <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_user_01</span>"&gt;</span><br/>    <span class="element">&lt;persName <span class="attribute">type</span>="<span class="attributevalue">userName</span>"&gt;</span>M<span class="element">&lt;/persName&gt;</span><br/>    <span class="element">&lt;note <span class="attribute">type</span>="<span class="attributevalue">link</span>"&gt;</span>/wiki/User:M<span class="element">&lt;/note&gt;</span><br/>    <span class="element">&lt;affiliation&gt;</span><br/>     <span class="element">&lt;email&gt;</span>mike@mydomain.com<span class="element">&lt;/email&gt;</span><br/>     <span class="element">&lt;country&gt;</span>CH<span class="element">&lt;/country&gt;</span><br/>    <span class="element">&lt;/affiliation&gt;</span><br/>   <span class="element">&lt;/person&gt;</span><br/><span class="comment">&lt;!-- … more persons … --&gt;</span><br/>   <span class="element">&lt;person <span class="attribute">role</span>="<span class="attributevalue">user</span>" <span class="attribute">sex</span>="<span class="attributevalue">female</span>"<br/>    <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_user_06</span>"&gt;</span><br/>    <span class="element">&lt;persName <span class="attribute">type</span>="<span class="attributevalue">userName</span>"&gt;</span>P<span class="element">&lt;/persName&gt;</span><br/>    <span class="element">&lt;note <span class="attribute">type</span>="<span class="attributevalue">link</span>"&gt;</span>/wiki/User:P<span class="element">&lt;/note&gt;</span><br/>    <span class="element">&lt;affiliation&gt;</span><br/>     <span class="element">&lt;email&gt;</span>pat@super.net<span class="element">&lt;/email&gt;</span><br/>     <span class="element">&lt;country&gt;</span>ES<span class="element">&lt;/country&gt;</span><br/>    <span class="element">&lt;/affiliation&gt;</span><br/>   <span class="element">&lt;/person&gt;</span><br/>   <span class="element">&lt;person <span class="attribute">role</span>="<span class="attributevalue">user</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_user_07</span>"&gt;</span><br/>    <span class="element">&lt;persName <span class="attribute">type</span>="<span class="attributevalue">userName</span>"&gt;</span>PKP<span class="element">&lt;/persName&gt;</span><br/>    <span class="element">&lt;note <span class="attribute">type</span>="<span class="attributevalue">link</span>"&gt;</span>/wiki/User:Pi<span class="element">&lt;/note&gt;</span><br/>   <span class="element">&lt;/person&gt;</span><br/>  <span class="element">&lt;/listPerson&gt;</span><br/> <span class="element">&lt;/particDesc&gt;</span><br/><span class="element">&lt;/profileDesc&gt;</span><br/><span class="comment">&lt;!-- In the &lt;body&gt;: --&gt;</span><br/><span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">wiki_discussion_page</span>" <span class="attribute">n</span>="<span class="attributevalue">073</span>"&gt;</span><br/><span class="comment">&lt;!-- 4 other &lt;post&gt;s --&gt;</span><br/> <span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/>  <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post04</span>" <span class="attribute">indentLevel</span>="<span class="attributevalue">1</span>"<br/>  <span class="attribute">replyTo</span>="<span class="attributevalue">#cmc_post_073.004</span>" <span class="attribute">who</span>="<span class="attributevalue">#cmc_user_06</span>"&gt;</span><br/>  <span class="element">&lt;p&gt;</span>Those haven't happened. If they do, we can revisit the concern.<span class="element">&lt;/p&gt;</span><br/>  <span class="element">&lt;signed <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"<br/>   <span class="attribute">rend</span>="<span class="attributevalue">noLineBreak</span>"&gt;</span><br/>   <span class="element">&lt;ref <span class="attribute">target</span>="<span class="attributevalue">/wiki/User:P</span>"&gt;</span>P<span class="element">&lt;/ref&gt;</span><br/>   <span class="element">&lt;date&gt;</span>01:35, 8 April 2014 (UTC)<span class="element">&lt;/date&gt;</span><br/>  <span class="element">&lt;/signed&gt;</span><br/> <span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;/div&gt;</span><div style="float: right;"><a href="BIB.html#BIB_WPTalkAstronomicalObject">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCParticipants-egXML-mu">⚓︎</a></div></div></div><div class="p">In the following version of the <a class="gi" title="(text body) contains the whole body of a single unitary text, excluding any front or back matter." href="ref-body.html">body</a> portion of the same example, the list of interactants is stored in a separate file (in this case the file <span class="name">userList.xml</span> in the same directory). <div id="CMCParticipants-egXML-br" class="pre egXML_valid"><br/><span class="comment">&lt;!-- In the &lt;body&gt;: --&gt;</span><span class="element">&lt;div <span class="attribute">type</span>="<span class="attributevalue">wiki_discussion_page</span>" <span class="attribute">n</span>="<span class="attributevalue">073</span>"&gt;</span><br/><span class="comment">&lt;!-- 4 other &lt;post&gt;s --&gt;</span><br/> <span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/>  <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post05</span>" <span class="attribute">indentLevel</span>="<span class="attributevalue">1</span>"<br/>  <span class="attribute">replyTo</span>="<span class="attributevalue">#cmc_post_073.004</span>" <span class="attribute">who</span>="<span class="attributevalue">./userList.xml#cmc_user_06</span>"&gt;</span><br/>  <span class="element">&lt;p&gt;</span>Those haven't happened. If they do, we can revisit the concern.<span class="element">&lt;/p&gt;</span><br/>  <span class="element">&lt;signed <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"<br/>   <span class="attribute">rend</span>="<span class="attributevalue">noLineBreak</span>"&gt;</span><br/>   <span class="element">&lt;ref <span class="attribute">target</span>="<span class="attributevalue">/wiki/User:P</span>"&gt;</span>P<span class="element">&lt;/ref&gt;</span><br/>   <span class="element">&lt;date&gt;</span>01:35, 8 April 2014 (UTC)<span class="element">&lt;/date&gt;</span><br/>  <span class="element">&lt;/signed&gt;</span><br/> <span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;/div&gt;</span><div style="float: right;"><a href="BIB.html#BIB_WPTalkAstronomicalObject">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCParticipants-egXML-br">⚓︎</a></div></div> Alternatively, a <a class="gi" title="(prefix definition) defines a prefixing scheme used in teidata.pointer values, showing how abbreviated URIs using the scheme may be expanded into full URIs." href="ref-prefixDef.html">prefixDef</a> may be used to declare a prefix which can be used in the value of <span class="att">who</span> to generate a complete URI, thus making the values of <span class="att">who</span> shorter, less error-prone, and easier to maintain. For example, the prefix <code>uL:</code> could be used to map the value <span class="val">uL:06</span> to <code>file:/userList.xml#cmc_user_06</code>. See <a class="link_ptr" href="SA.html#SAPU" title="Using Abbreviated Pointers"><span class="headingNumber">17.2.3. </span>Using Abbreviated Pointers</a> for more information on establishing prefix definitions.</div><p>This indirection—using a <a class="gi" title="(list of persons) contains a list of descriptions, each of which provides information about an identifiable person or a group of people, for example the participants in a language interaction, or the people referred to in a historical source." href="ref-listPerson.html">listPerson</a>, particularly one in a separate file, to store information about the users involved in a CMC interaction—is particularly useful when there is both a need to keep such information locally, and to remove it (e.g., to ‘anonymize’ the data) when the data are published or shared with other researchers.</p></div><div class="teidiv2" id="CMCTimeline"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCParticipants"><span class="headingNumber">9.5.4. </span>Participants</a></li><li class="subtoc"/><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCTimeline" title="link to this section "><span class="invisible">TEI: Timeline</span>⚓︎</a></span><span class="headingNumber">9.5.5. </span><span class="head">Timeline</span></h3><div class="p">From most CMC environments, user posts come provided with a timestamp marking the time (often down to the second) when the post arrived and was registered at the CMC server. In the display of chat interactions, for instance, the time is automatically added by the system and usually precedes or follows the actual content of the post. In Wikipedia talk, a timestamp is automatically added when the user inserts his or her signature. A timestamp in the text body may be transcribed using a <a class="gi" title="(date) contains a date in any format." href="ref-date.html">date</a> or <a class="gi" title="(time) contains a phrase defining a time of day in any format." href="ref-time.html">time</a> element, in which case the <span class="att">when</span> attribute may be used to record a normalized version of the date, time, or date and time if this information is available or reconstructible. <div id="CMCTimeline-egXML-ly" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>" <span class="attribute">rend</span>="<span class="attributevalue">color:black</span>"<br/> <span class="attribute">who</span>="<span class="attributevalue">#f2213001.A06</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post06</span>"&gt;</span><br/> <span class="element">&lt;time <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>"&gt;</span>21:52<span class="element">&lt;/time&gt;</span><br/> das ist auf jedenfall krankheit<br/><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_DCK">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCTimeline-egXML-ly">⚓︎</a></div></div> <div id="CMCTimeline-egXML-fu" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post07</span>" <span class="attribute">indentLevel</span>="<span class="attributevalue">1</span>" <span class="attribute">who</span>="<span class="attributevalue">#u006</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t006</span>"&gt;</span><br/> <span class="element">&lt;p&gt;</span>Those haven't happened. If they do, we can revisit the concern.<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;signed <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"&gt;</span><br/>  <span class="element">&lt;ref <span class="attribute">target</span>="<span class="attributevalue">/wiki/User:P</span>"&gt;</span>P<span class="element">&lt;/ref&gt;</span><br/>  <span class="element">&lt;date <span class="attribute">when</span>="<span class="attributevalue">2014-04-08T01:35:00Z</span>"&gt;</span>01:35, 8 April 2014 (UTC)<span class="element">&lt;/date&gt;</span><br/> <span class="element">&lt;/signed&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_WPTalkAstronomicalObject">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCTimeline-egXML-fu">⚓︎</a></div></div> Alternatively the timestamp may be recorded using the <span class="att">when</span> attribute of <a class="gi" title="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." href="ref-post.html">post</a>. In this case, if the details of how the timestamp appeared in the original are considered unimportant, the actual transcription may be omitted. <div id="CMCTimeline-egXML-zx" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">when</span>="<span class="attributevalue">2014-04-08T01:35:00Z</span>" <span class="attribute">who</span>="<span class="attributevalue">#u006</span>"&gt;</span><br/> <span class="element">&lt;p&gt;</span>Those haven't happened. If they do, we can revisit the concern.<span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;signed <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"&gt;</span><br/>  <span class="element">&lt;ref <span class="attribute">target</span>="<span class="attributevalue">/wiki/User:P</span>"&gt;</span>P<span class="element">&lt;/ref&gt;</span><br/> <span class="element">&lt;/signed&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_WPTalkAstronomicalObject">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCTimeline-egXML-zx">⚓︎</a></div></div></div><div class="p">Instead of transcribing timestamps or recording the timestamp directly on an attribute of <a class="gi" title="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." href="ref-post.html">post</a>, all timestamps of a set of posts can be collected in <a class="gi" title="indicates a point in time either relative to other elements in the same timeline tag, or absolutely." href="ref-when.html">when</a> elements in a <a class="gi" title="(timeline) provides a set of ordered points in time which can be linked to elements of a spoken text to create a temporal alignment of that text." href="ref-timeline.html">timeline</a> element in the <a class="gi" title="(TEI header) supplies descriptive and declarative metadata associated with a digital resource or set of resources." href="ref-teiHeader.html">teiHeader</a>, most suitably in the <a class="gi" title="(interaction) describes the extent, cardinality and nature of any interaction among those producing and experiencing the text, for example in the form of response or interjection, commentary, etc." href="ref-interaction.html">interaction</a> element (itself in the <a class="gi" title="(text description) provides a description of a text in terms of its situational parameters." href="ref-textDesc.html">textDesc</a> in the <a class="gi" title="(text-profile description) provides a detailed description of non-bibliographic aspects of a text, specifically the languages and sublanguages used, the situation in which it was produced, the participants and their setting." href="ref-profileDesc.html">profileDesc</a>). In which case, similar to the encoding of transcripts of spoken utterances (for which see <a class="link_ptr" href="TS.html" title="11"><span class="headingNumber">8. </span>Transcriptions of Speech</a>), each individual post can be linked to its timestamp via the <span class="att">synch</span> attribute as in the following alternative encoding of the Wikipedia talk example above. <div id="CMCTimeline-egXML-jz" class="pre egXML_valid"><span class="element">&lt;profileDesc&gt;</span><br/> <span class="element">&lt;particDesc&gt;</span><br/>  <span class="element">&lt;listPerson&gt;</span><br/>   <span class="element">&lt;person <span class="attribute">role</span>="<span class="attributevalue">user</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">u001</span>"&gt;</span><br/>    <span class="element">&lt;persName <span class="attribute">type</span>="<span class="attributevalue">userName</span>"&gt;</span>M<span class="element">&lt;/persName&gt;</span><br/>    <span class="element">&lt;note <span class="attribute">type</span>="<span class="attributevalue">link</span>"&gt;</span>/wiki/User:M<span class="element">&lt;/note&gt;</span><br/>   <span class="element">&lt;/person&gt;</span><br/><span class="comment">&lt;!-- more persons --&gt;</span><br/>   <span class="element">&lt;person <span class="attribute">role</span>="<span class="attributevalue">user</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">u006</span>"&gt;</span><br/>    <span class="element">&lt;persName <span class="attribute">type</span>="<span class="attributevalue">userName</span>"&gt;</span>P<span class="element">&lt;/persName&gt;</span><br/>    <span class="element">&lt;note <span class="attribute">type</span>="<span class="attributevalue">link</span>"&gt;</span>/wiki/User:P<span class="element">&lt;/note&gt;</span><br/>   <span class="element">&lt;/person&gt;</span><br/>   <span class="element">&lt;person <span class="attribute">role</span>="<span class="attributevalue">user</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">u007</span>"&gt;</span><br/>    <span class="element">&lt;persName <span class="attribute">type</span>="<span class="attributevalue">userName</span>"&gt;</span>PKP<span class="element">&lt;/persName&gt;</span><br/>    <span class="element">&lt;note <span class="attribute">type</span>="<span class="attributevalue">link</span>"&gt;</span>/wiki/User:Pi<span class="element">&lt;/note&gt;</span><br/>   <span class="element">&lt;/person&gt;</span><br/>  <span class="element">&lt;/listPerson&gt;</span><br/> <span class="element">&lt;/particDesc&gt;</span><br/> <span class="element">&lt;textDesc&gt;</span><br/>  <span class="element">&lt;channel/&gt;</span><br/>  <span class="element">&lt;constitution/&gt;</span><br/>  <span class="element">&lt;derivation/&gt;</span><br/>  <span class="element">&lt;domain/&gt;</span><br/>  <span class="element">&lt;factuality/&gt;</span><br/>  <span class="element">&lt;interaction&gt;</span><br/>   <span class="element">&lt;timeline&gt;</span><br/>    <span class="element">&lt;when <span class="attribute">xml:id</span>="<span class="attributevalue">t001</span>"<br/>     <span class="attribute">absolute</span>="<span class="attributevalue">2011-03-23T19:56:00</span>"/&gt;</span><br/>    <span class="element">&lt;when <span class="attribute">xml:id</span>="<span class="attributevalue">t002</span>"<br/>     <span class="attribute">absolute</span>="<span class="attributevalue">2011-06-14T21:22:00</span>"/&gt;</span><br/>    <span class="element">&lt;when <span class="attribute">xml:id</span>="<span class="attributevalue">t003</span>"<br/>     <span class="attribute">absolute</span>="<span class="attributevalue">2011-06-14T23:28:00</span>"/&gt;</span><br/>    <span class="element">&lt;when <span class="attribute">xml:id</span>="<span class="attributevalue">t004</span>"<br/>     <span class="attribute">absolute</span>="<span class="attributevalue">2011-07-02T07:20:00</span>"/&gt;</span><br/>    <span class="element">&lt;when <span class="attribute">xml:id</span>="<span class="attributevalue">t005</span>"<br/>     <span class="attribute">absolute</span>="<span class="attributevalue">2011-07-21T01:00:00</span>"/&gt;</span><br/>    <span class="element">&lt;when <span class="attribute">xml:id</span>="<span class="attributevalue">t006</span>"<br/>     <span class="attribute">absolute</span>="<span class="attributevalue">2014-04-08T01:35:00</span>"/&gt;</span><br/>   <span class="element">&lt;/timeline&gt;</span><br/>  <span class="element">&lt;/interaction&gt;</span><br/>  <span class="element">&lt;preparedness/&gt;</span><br/>  <span class="element">&lt;purpose/&gt;</span><br/> <span class="element">&lt;/textDesc&gt;</span><br/><span class="element">&lt;/profileDesc&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCTimeline-egXML-jz">⚓︎</a></div></div> Note that the <span class="att">synch</span> attribute is provided by the module described in chapter <a class="link_ptr" href="SA.html" title="14"><span class="headingNumber">17. </span>Linking, Segmentation, and Alignment</a>.</div><div class="p">Removing timestamps from the text body can help meet requirements of text anonymization. For instance, if the <a class="gi" title="(participation description) describes the identifiable speakers, voices, or other participants in any kind of text or other persons named or otherwise referred to in a text, edition, or metadata." href="ref-particDesc.html">particDesc</a> and the <a class="gi" title="(timeline) provides a set of ordered points in time which can be linked to elements of a spoken text to create a temporal alignment of that text." href="ref-timeline.html">timeline</a> are stored in a separate file, the rest of the corpus can be distributed without this separate file. Thus the recipient of the corpus may know in what order posts were made (if the values of the <span class="att">synch</span> are sequential), and will be able to group posts made by the same user, but will not have exact timestamps or actual user names, thus providing a significant degree of anonymization. <div id="e10" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post08</span>" <span class="attribute">indentLevel</span>="<span class="attributevalue">1</span>" <span class="attribute">who</span>="<span class="attributevalue">#u006</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t006</span>"&gt;</span><br/> <span class="element">&lt;p&gt;</span>Those haven't happened. If they do, we can revisit the concern. <span class="element">&lt;/p&gt;</span><br/> <span class="element">&lt;signed <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"&gt;</span> [_DELETED-SIGNATURE_]<br/> <span class="element">&lt;date <span class="attribute">synch</span>="<span class="attributevalue">#t007</span>"&gt;</span>[_DELETED-TIMESTAMP_]<span class="element">&lt;/date&gt;</span><br/> <span class="element">&lt;/signed&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_WPTalkAstronomicalObject">bibliography</a> <a class="bookmarklink" title="link to this example" href="#e10">⚓︎</a></div></div> As demonstrated above, the <span class="att">synch</span> attribute can be used on <a class="gi" title="(date) contains a date in any format." href="ref-date.html">date</a> or <a class="gi" title="(time) contains a phrase defining a time of day in any format." href="ref-time.html">time</a> (or indeed any other element) rather than on the <a class="gi" title="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." href="ref-post.html">post</a> itself.</div></div></div><div class="teidiv1" id="CMCrecs"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCmetadata"><span class="headingNumber">9.5. </span>Documenting CMC (and providing general metadata)</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCmodule"><span class="headingNumber">9.7. </span>The TEI CMC Module</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h2><span class="bookmarklink"><a class="bookmarklink" href="#CMCrecs" title="link to this section "><span class="invisible">TEI: Recommendations for Encoding CMC Microstructure</span>⚓︎</a></span><span class="headingNumber">9.6. </span><span class="head">Recommendations for Encoding CMC Microstructure</span></h2><div class="teidiv2" id="CMCemos"><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCemos" title="link to this section "><span class="invisible">TEI: Emojis and Emoticons</span>⚓︎</a></span><span class="headingNumber">9.6.1. </span><span class="head">Emojis and Emoticons</span></h3><p>Emojis are iconic or symbolic, invariant graphic units which the users of social media applications such as WhatsApp, Instagram, and X (Twitter) can select from a menu or ‘emoji keyboard’ and embed into their written posts. Examples are 😁, 😷, 🌈, 😱, and 🙈. An emoji is encoded by one or more Unicode characters which are intended to be mapped directly to a pictorial symbol.</p><p>Emoticons predate emojis and are created as combinations of ASCII punctuation and other characters using the keyboard. Examples are <code>:-)</code>, <code>;-)</code>, <code>:-(</code>, <code>:-x</code>, <code>\O/</code>, and <code>Oo</code>. They first occurred on a computer bulletin board system at Carnegie Mellon University (<a class="link_ref" href="BIB.html#BIB_smiley" title="Scott E. Fahlman Joke Conversation Thread in which the ) Was Invented">Fahlman, 2021</a>) and then became frequent in chat communications during the mid-1980s. An emoticon typically consists of several Unicode characters (from the ASCII subset) in a row, each of which has an intended use other than as part of an emoticon.</p><p>Both emoticons and emojis may be simply transcribed as a sequence of characters. As with any other characters, they may be entered as numeric character entities if this is more convenient. (E.g., <span class="mentioned">❤</span> might be transcribed as <code>&amp;#x2764;</code> in any XML document, including a TEI document; see <a class="link_ptr" href="CH.html#D4-44" title="Entry of Characters">Entry of Characters</a>.)</p><p>When the text of a post is being tokenized, e.g. for linguistic analysis, it may be useful to encode the emoticon or emoji as a separate token. In such cases elements such as <a class="gi" title="(word) represents a grammatical (not necessarily orthographic) word." href="ref-w.html">w</a> or <a class="gi" title="(character) represents a character." href="ref-c.html">c</a> may be used for tokenization, and the <span class="att">pos</span> attribute may be used to indicate that the encoded string is an emoji or an emoticon. (See <a class="link_ptr" href="AI.html#AILC" title="Linguistic Segment Categories"><span class="headingNumber">18.1. </span>Linguistic Segment Categories</a>.)</p><div class="p">For example, the source post <span class="q">‘da bin ich nicht so empfindlich ;)’</span> (English:. <span class="q">‘I am not so touchy with that ;)’</span>) ends with an emoticon, and might be encoded as follows: <div id="CMCemos-egXML-cs" class="pre egXML_valid"><span class="element">&lt;post&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">ADV</span>"&gt;</span>da<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">VAFIN</span>"&gt;</span>bin<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">PPER</span>"&gt;</span>ich<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">PTKNEG</span>"&gt;</span>nicht<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">ADV</span>"&gt;</span>so<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">ADJD</span>"&gt;</span>empfindlich<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">EMOASC</span>"&gt;</span>;)<span class="element">&lt;/w&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCemos-egXML-cs">⚓︎</a></div></div></div><div class="p">Similarly, the source post <span class="q">‘Klar 😁’</span> (<span class="q">‘Sure 😁’</span> in English) might be encoded as follows: <div id="CMCemos-egXML-xk" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#lscLB.t004</span>" <span class="attribute">who</span>="<span class="attributevalue">#lscLB.A03</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post21</span>"&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">ADV</span>"&gt;</span>Klar<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">EMOIMG</span>"&gt;</span>😁<span class="element">&lt;/w&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCemos-egXML-xk">⚓︎</a></div></div></div><p>The values of <span class="att">pos</span> in the above examples are from the STTS_IBK Tagset for German (see <a class="citlink" href="BIB.html#STTS_IBK">Beißwenger et al. (2015-09-13)</a>), which includes tags for CMC-specific elements such as <span class="val">EMOASC</span> for an ASCII-based emoticon and <span class="val">EMOIMG</span> for an icon-based emoji.</p><div class="p">Alternatively, e.g. when <a class="gi" title="(word) represents a grammatical (not necessarily orthographic) word." href="ref-w.html">w</a> is not regularly used to encode tokens in the TEI document, <a class="gi" title="(character) represents a character." href="ref-c.html">c</a> may be used to mark an emoji. For example, the source post <span class="q">‘Da kostet ein Haarschnitt 50 € 😱’</span> (from the corpus <a class="link_ptr" href="BIB.html#BIB_MoCoDa2" title="Mobile Communication Database 2 (MoCoDa2) Michael Beißwenger Evelyn Ziegler Marcel Fladrich Wolfgang Imo Katharina König httpsd...">Beißwenger et al. (eds.) (visited 30 March 2022)</a>, in English <span class="q">‘A haircut there costs 50 € 😱’</span>) might be encoded as follows: <div id="CMCemos-egXML-rt" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"&gt;</span>Da kostet ein Haarschnitt 50 € <span class="element">&lt;c <span class="attribute">type</span>="<span class="attributevalue">emoji</span>" <span class="attribute">ana</span>="<span class="attributevalue">#fsif</span>"<br/>  <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"&gt;</span>😱<span class="element">&lt;/c&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCemos-egXML-rt">⚓︎</a></div></div></div><p>Sometimes, e.g. when the source of the TEI document was a web page in HTML, the emojis may occur only as an icon graphic in the source. In such a case, they may be encoded using <a class="gi" title="(figure) groups elements representing or containing graphic information such as an illustration, formula, or figure." href="ref-figure.html">figure</a>. The corresponding Unicode character can then be recorded in the <a class="gi" title="(description) contains a short description of the purpose, function, or use of its parent element, or when the parent is a documentation element, describes or defines the object being documented." href="ref-desc.html">desc</a> element by the encoder if desired.</p><div class="p">For example, the source text: <span class="q">‘... ich überlege noch 🙈’</span> (English: <span class="q">‘... I'm still thinking 🙈’</span>) might be encoded as follows: <div id="CMCemos-egXML-uu" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#lscLB.t004</span>" <span class="attribute">who</span>="<span class="attributevalue">#lscLB.A03</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post22</span>"&gt;</span> ... ich überlege noch <span class="element">&lt;figure <span class="attribute">type</span>="<span class="attributevalue">emoji</span>"<br/>  <span class="attribute">generatedBy</span>="<span class="attributevalue">template</span>"&gt;</span><br/>  <span class="element">&lt;graphic <span class="attribute">url</span>="<span class="attributevalue">fig1.png</span>"/&gt;</span><br/>  <span class="element">&lt;desc <span class="attribute">type</span>="<span class="attributevalue">gloss</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">en</span>"&gt;</span>see no evil monkey<span class="element">&lt;/desc&gt;</span><br/>  <span class="element">&lt;desc <span class="attribute">type</span>="<span class="attributevalue">unicode</span>"&gt;</span>U+1F648<span class="element">&lt;/desc&gt;</span><br/> <span class="element">&lt;/figure&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCemos-egXML-uu">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCgraphic"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCemos"><span class="headingNumber">9.6.1. </span>Emojis and Emoticons</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCcirculation"><span class="headingNumber">9.6.3. </span>Circulation</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCgraphic" title="link to this section "><span class="invisible">TEI: Posts with Graphics</span>⚓︎</a></span><span class="headingNumber">9.6.2. </span><span class="head">Posts with Graphics</span></h3><p>A post in a CMC interaction may contain a graphic in addition to some text or even contain only a graphic (without any text). As explained in <a class="link_ptr" href="CMC.html#CMCcmcpostatts" title="Attributes Specific to CMC post"><span class="headingNumber">9.3.2. </span>Attributes Specific to CMC post</a>, the modality of such a post should be considered as <span class="val">written</span>. To encode the graphic information, the <a class="gi" title="(figure) groups elements representing or containing graphic information such as an illustration, formula, or figure." href="ref-figure.html">figure</a> element may be used at the appropriate place.</p><div class="p">In the following example a private chat post that contained only a screenshot of a google search result for a hairdresser is encoded as a <a class="gi" title="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." href="ref-post.html">post</a> with a child <a class="gi" title="(figure) groups elements representing or containing graphic information such as an illustration, formula, or figure." href="ref-figure.html">figure</a>. A link to the graphic file itself is not included presumably because this is a text-only corpus that does not include images. <div id="CMCgraphic-egXML-oe" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t005</span>" <span class="attribute">who</span>="<span class="attributevalue">#A06</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post23</span>"&gt;</span><br/> <span class="element">&lt;figure <span class="attribute">type</span>="<span class="attributevalue">image</span>" <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"&gt;</span><br/>  <span class="element">&lt;desc&gt;</span>screenshot of the google search for hairdresser "Pasha's Haare'm" with the<br/>     average google rating (4,5 of 5 stars), the address, the phone number, and the<br/>     opening hours. <span class="element">&lt;/desc&gt;</span><br/> <span class="element">&lt;/figure&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#UND">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCgraphic-egXML-oe">⚓︎</a></div></div></div><div class="p">The following is an example of the encoding of a tweet which contains both text (including hashtags and mentions) and a graphic. The <a class="gi" title="(graphic) indicates the location of a graphic or illustration, either forming part of a text, or providing an image of it." href="ref-graphic.html">graphic</a> element retains the URL of the graphic on the web just as in the source. <div id="CMCgraphic-egXML-hd" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">type</span>="<span class="attributevalue">tweet</span>" <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">synch</span>="<span class="attributevalue">#tweetsbcrn18.t006</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_1043823300479258624</span>" <span class="attribute">who</span>="<span class="attributevalue">#u1</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"&gt;</span><br/> <span class="element">&lt;time <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>"&gt;</span> 16:24 <span class="element">&lt;/time&gt;</span> Bro Tri-Engel...so hab ich mir das<br/> vorgestellt!!! @AndreLo79 #bcrn18 #wikidach @Heiko komm' mal Twitter! #Engel <span class="element">&lt;figure <span class="attribute">type</span>="<span class="attributevalue">image</span>" <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"&gt;</span><br/>  <span class="element">&lt;graphic <span class="attribute">url</span>="<span class="attributevalue">https://pbs.twimg.com/media/DnxnwN9XsAEHXw2.jpg:large</span>"/&gt;</span><br/> <span class="element">&lt;/figure&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCgraphic-egXML-hd">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCcirculation"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCgraphic"><span class="headingNumber">9.6.2. </span>Posts with Graphics</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCanalysis"><span class="headingNumber">9.6.4. </span>Linguistic Annotation</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCcirculation" title="link to this section "><span class="invisible">TEI: Circulation</span>⚓︎</a></span><span class="headingNumber">9.6.3. </span><span class="head">Circulation</span></h3><p>The following recommendations on how to encode features of the circulation of posts, such as IDs, re-posts (retweets), hashtags, and mentions use X (Twitter) posts (tweets) as an example; this phenomenon is not in any way unique to X (Twitter), however.</p><p>In the following example, the type of post (in this case, a tweet) is recorded using the <span class="att">type</span> attribute of <a class="gi" title="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." href="ref-post.html">post</a>. If it were useful to record a particular sub-categorization of tweet, the <span class="att">subtype</span> attribute could also be used. Furthermore, the original unique identifer of the tweet as supplied by X (Twitter) is recorded as part of the value of the <span class="att">xml:id</span> attribute of the <a class="gi" title="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." href="ref-post.html">post</a>.</p><p>Also in the following example a retweet and its corresponding retweeted tweet are encoded as two separate posts each with its own set of attributes. The post representing the retweet itself does not contain or duplicate the content of the retweeted tweet. Instead it refers to the ID of the retweeted tweet via a <a class="gi" title="(pointer) defines a pointer to another location." href="ref-ptr.html">ptr</a> in the post content. All original content of the retweet goes in the content of the <a class="gi" title="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." href="ref-post.html">post</a> element as well. In addition, the hashtags found in the body of the source tweets have been encoded using <a class="gi" title="(reference) defines a reference to another location, possibly modified by additional text or comment." href="ref-ref.html">ref</a> elements (with a <span class="att">type</span> of <span class="val">hashtag</span>), as they are links like any other hyperlink.</p><div id="ex.tweets" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">type</span>="<span class="attributevalue">tweet</span>" <span class="attribute">who</span>="<span class="attributevalue">#u1</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_1043796550101716993</span>" <span class="attribute">synch</span>="<span class="attributevalue">#tweetsbcrn18.t004</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"&gt;</span><br/> <span class="element">&lt;ptr <span class="attribute">type</span>="<span class="attributevalue">retweet</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">#cmc_post_1043796093786566656</span>"/&gt;</span> Ich mich auch? <span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">hashtag</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/hashtag/dynamicduo?src=hash</span>"&gt;</span>#dynamicduo<span class="element">&lt;/ref&gt;</span><br/> <span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">hashtag</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/hashtag/wirk%C3%BCmmernunsauchumIhrenEmpfang?src=hash</span>"&gt;</span>#wirkümmernunsauchumIhrenEmpfang<span class="element">&lt;/ref&gt;</span><br/> <span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">hashtag</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/hashtag/bcrn18?src=hash</span>"&gt;</span>#bcrn18<span class="element">&lt;/ref&gt;</span><br/> <span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">hashtag</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/hashtag/wikidach?src=hash</span>"&gt;</span>#wikidach<span class="element">&lt;/ref&gt;</span><br/><span class="element">&lt;/post&gt;</span><br/><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>" <span class="attribute">type</span>="<span class="attributevalue">tweet</span>" <span class="attribute">who</span>="<span class="attributevalue">#u2</span>"<br/> <span class="attribute">synch</span>="<span class="attributevalue">#tweetsbcrn18.t003</span>" <span class="attribute">xml:lang</span>="<span class="attributevalue">de</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_1043796093786566656</span>"&gt;</span><br/> <span class="element">&lt;time <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>"&gt;</span> 14:35 <span class="element">&lt;/time&gt;</span> Immer wieder gerne. Kann ich mich schon für<br/> nächstes Jahr als Empfangs- <span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">hashtag</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/hashtag/Engel?src=hash</span>"&gt;</span>#Engel<span class="element">&lt;/ref&gt;</span> für das nächste<br/> BarCamp bewerben <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">EMO</span>"&gt;</span>🤪<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;ref <span class="attribute">type</span>="<span class="attributevalue">hashtag</span>"<br/>  <span class="attribute">target</span>="<span class="attributevalue">https://twitter.com/hashtag/bcrn18?src=hash</span>"&gt;</span>#bcrn18<span class="element">&lt;/ref&gt;</span><br/> <span class="element">&lt;trailer&gt;</span><br/>  <span class="element">&lt;fs&gt;</span><br/>   <span class="element">&lt;f <span class="attribute">name</span>="<span class="attributevalue">favoritecount</span>"&gt;</span><br/>    <span class="element">&lt;numeric <span class="attribute">value</span>="<span class="attributevalue">4</span>"/&gt;</span><br/>   <span class="element">&lt;/f&gt;</span><br/>  <span class="element">&lt;/fs&gt;</span><br/> <span class="element">&lt;/trailer&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#ex.tweets">⚓︎</a></div></div><p>Note that in the above example ‘CoMeRe’ style (cf. <a class="link_ptr" href="BIB.html#BIB_CoMeRe" title="Chanier Thierry Poudat Céline Sagot Benoit Antoniadis Georges Wigham Ciara R. Hriba Linda Longhi Julien Seddah Djamé The CoMeRe...">Thierry et al. (2014)</a>) encoding is used to represent the number of favorites. It would also be reasonable to use a TEI <a class="gi" title="(measure) contains a word or phrase referring to some quantity of an object or commodity, usually comprising a number, a unit, and a commodity name." href="ref-measure.html">measure</a> element instead of the <a class="gi" title="(feature structure) represents a feature structure, that is, a collection of feature-value pairs organized as a structural unit." href="ref-fs.html">fs</a>.</p></div><div class="teidiv2" id="CMCanalysis"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCcirculation"><span class="headingNumber">9.6.3. </span>Circulation</a></li><li class="subtoc"><span class="nextLink"> Next </span><a class="navigation" href="CMC.html#CMCnames"><span class="headingNumber">9.6.5. </span>Named Entities and Anonymization</a></li><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCanalysis" title="link to this section "><span class="invisible">TEI: Linguistic Annotation</span>⚓︎</a></span><span class="headingNumber">9.6.4. </span><span class="head">Linguistic Annotation</span></h3><p>For encoding linguistic analyses of CMC text, we may use the dedicated elements and attributes from the analysis module, which is described in <a class="link_ptr" href="SA.html" title="14"><span class="headingNumber">17. </span>Linking, Segmentation, and Alignment</a>. For example, the tokenization (segmentation into word-like units) of a CMC text should be encoded using the <a class="gi" title="(word) represents a grammatical (not necessarily orthographic) word." href="ref-w.html">w</a> element.</p><div class="p">Let us take, for example a posting that contains the content <span lang="de" class="q">‘00:22 Bin soooooo im stress gewesen ich Armer lol’</span> (in English: <span class="q">‘I was soooooo stressed out poor me lol’</span>). This may be encoded as follows. <div id="CMCanalysis-egXML-kw" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"<br/> <span class="attribute">rend</span>="<span class="attributevalue">color:black</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t010.a</span>" <span class="attribute">who</span>="<span class="attributevalue">#A03.a</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_m16.a</span>"&gt;</span><br/> <span class="element">&lt;time&gt;</span>00:22<span class="element">&lt;/time&gt;</span><br/> <span class="element">&lt;w&gt;</span>Bin<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>soooooo<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>im<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>stress<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>gewesen<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>ich<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>Armer<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>lol<span class="element">&lt;/w&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCanalysis-egXML-kw">⚓︎</a></div></div></div><p>In many CMC genres, especially in private chat, informal writing abounds including irregular spellings imitating spoken language, omitted word boundaries, and spurious boundaries leading to tokens separated in parts. For encoding these writing phenomena typical of CMC, the TEI attributes <span class="att">norm</span> and <span class="att">join</span> may be used.</p><div class="p">For example, the normalized spelling of an irregularly spelled word may be recorded using the <span class="att">norm</span> attribute (from <a class="link_odd" title="provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically &lt;w&gt; and &lt;pc&gt; in the analysis module." href="ref-att.linguistic.html">att.linguistic</a>): <div id="CMCanalysis-egXML-km" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"<br/> <span class="attribute">rend</span>="<span class="attributevalue">color:black</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t010.b</span>" <span class="attribute">who</span>="<span class="attributevalue">#A03.b</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_m16.b</span>"&gt;</span><br/> <span class="element">&lt;time&gt;</span> 00:22 <span class="element">&lt;/time&gt;</span><br/> <span class="element">&lt;w&gt;</span>Bin<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">norm</span>="<span class="attributevalue">so</span>"&gt;</span>soooooo<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>im<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">norm</span>="<span class="attributevalue">Stress</span>"&gt;</span>stress<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>gewesen<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>ich<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>Armer<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w&gt;</span>lol<span class="element">&lt;/w&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCanalysis-egXML-km">⚓︎</a></div></div></div><div class="p">When the boundaries between <a class="gi" title="(word) represents a grammatical (not necessarily orthographic) word." href="ref-w.html">w</a> elements are generally thought of as denoting word boundaries, we can keep track of boundaries not present in the source by using the <span class="att">join</span> attribute, also from <a class="link_odd" title="provides a set of attributes concerning linguistic features of tokens, for usage within token-level elements, specifically &lt;w&gt; and &lt;pc&gt; in the analysis module." href="ref-att.linguistic.html">att.linguistic</a>. For example, for an original post that has nothing more than the token <span class="q">‘Inmyoffice’</span>, the following encoding demonstrates an interpretation that the single token represents the three words <span class="q">‘In my office’</span>: <div id="CMCanalysis-egXML-pi" class="pre egXML_valid"><span class="element">&lt;post&gt;</span><br/> <span class="element">&lt;w&gt;</span>In<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">join</span>="<span class="attributevalue">left</span>"&gt;</span>my<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">join</span>="<span class="attributevalue">left</span>"&gt;</span>office<span class="element">&lt;/w&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCanalysis-egXML-pi">⚓︎</a></div></div></div><div class="p">Alternatively, and especially when the normalization information pertains to more than one token, we can apply the notation using the elements <a class="gi" title="(regularization) contains a reading which has been regularized or normalized in some sense." href="ref-reg.html">reg</a> and <a class="gi" title="(original form) contains a reading which is marked as following the original, rather than being normalized or corrected." href="ref-orig.html">orig</a>, related by a <a class="gi" title="(choice) groups a number of alternative encodings for the same point in a text." href="ref-choice.html">choice</a> element as described in <a class="link_ptr" href="CO.html#COEDREG" title="Regularization and Normalization"><span class="headingNumber">3.5.2. </span>Regularization and Normalization</a>. <div id="CMCanalysis-egXML-dy" class="pre egXML_valid"><span class="element">&lt;post&gt;</span><br/> <span class="element">&lt;choice&gt;</span><br/>  <span class="element">&lt;orig&gt;</span><br/>   <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">VAPPER</span>" <span class="attribute">lemma</span>="<span class="attributevalue"/>"&gt;</span>hastes<span class="element">&lt;/w&gt;</span><br/>  <span class="element">&lt;/orig&gt;</span><br/>  <span class="element">&lt;reg&gt;</span><br/>   <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">VAFIN</span>" <span class="attribute">lemma</span>="<span class="attributevalue">haben</span>"&gt;</span>hast<span class="element">&lt;/w&gt;</span><br/>   <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">PPER</span>" <span class="attribute">lemma</span>="<span class="attributevalue">du</span>"&gt;</span>du<span class="element">&lt;/w&gt;</span><br/>   <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">PPER</span>" <span class="attribute">lemma</span>="<span class="attributevalue">es</span>"&gt;</span>es<span class="element">&lt;/w&gt;</span><br/>  <span class="element">&lt;/reg&gt;</span><br/> <span class="element">&lt;/choice&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCanalysis-egXML-dy">⚓︎</a></div></div></div><div class="p">Other analysis attributes like <span class="att">lemma</span> and <span class="att">pos</span> (for part of speech) may be used as with traditional text. It is a matter of the tagset used to cater for POS categories that are appropriate for CMC. In the example below, for instance, the tag <span class="val">AKW</span> stands for <span lang="de" style="font-style:italic">Aktionswort</span> (<span lang="en" class="gloss">action word</span>, see <a class="citlink" href="BIB.html#STTS_IBK">Beißwenger et al. (2015-09-13)</a>). <div id="CMCanalysis-egXML-pz" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">generatedBy</span>="<span class="attributevalue">human</span>"<br/> <span class="attribute">rend</span>="<span class="attributevalue">color:black</span>" <span class="attribute">synch</span>="<span class="attributevalue">#t010.c</span>" <span class="attribute">who</span>="<span class="attributevalue">#A03.c</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">cmc_post_m16.c</span>"&gt;</span><br/> <span class="element">&lt;time&gt;</span> 00:22 <span class="element">&lt;/time&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">sein</span>" <span class="attribute">pos</span>="<span class="attributevalue">VAFIN</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">m16.t9</span>"&gt;</span>Bin<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">so</span>" <span class="attribute">norm</span>="<span class="attributevalue">so</span>" <span class="attribute">pos</span>="<span class="attributevalue">PTKIFG</span>"<br/>  <span class="attribute">xml:id</span>="<span class="attributevalue">m16.t10</span>"&gt;</span>soooooo<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">in</span>" <span class="attribute">pos</span>="<span class="attributevalue">APPRART</span>"<br/>  <span class="attribute">xml:id</span>="<span class="attributevalue">m16.t11</span>"&gt;</span>im<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">Stress</span>" <span class="attribute">norm</span>="<span class="attributevalue">Stress</span>" <span class="attribute">pos</span>="<span class="attributevalue">NN</span>"<br/>  <span class="attribute">xml:id</span>="<span class="attributevalue">m16.t12</span>"&gt;</span>stress<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">sein</span>" <span class="attribute">pos</span>="<span class="attributevalue">VAPP</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">m16.t13</span>"&gt;</span>gewesen<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">ich</span>" <span class="attribute">pos</span>="<span class="attributevalue">PPER</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">m16.t14</span>"&gt;</span>ich<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">Armer</span>" <span class="attribute">pos</span>="<span class="attributevalue">NN</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">m16.t15</span>"&gt;</span>Armer<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">lol</span>" <span class="attribute">pos</span>="<span class="attributevalue">AKW</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">m16.t16</span>"&gt;</span>lol<span class="element">&lt;/w&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a class="bookmarklink" title="link to this example" href="#CMCanalysis-egXML-pz">⚓︎</a></div></div></div></div><div class="teidiv2" id="CMCnames"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCanalysis"><span class="headingNumber">9.6.4. </span>Linguistic Annotation</a></li><li class="subtoc"/><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h3><span class="bookmarklink"><a class="bookmarklink" href="#CMCnames" title="link to this section "><span class="invisible">TEI: Named Entities and Anonymization</span>⚓︎</a></span><span class="headingNumber">9.6.5. </span><span class="head">Named Entities and Anonymization</span></h3><div class="p">Named entities (NEs) may be marked up using <a class="gi" title="(name, proper noun) contains a proper noun or noun phrase." href="ref-name.html">name</a> or the elements encoding different subcategories of names as described in <a class="link_ptr" href="ND.html" title="20"><span class="headingNumber">14. </span>Names, Dates, People, and Places</a> such as <a class="gi" title="(surname) contains a family (inherited) name, as opposed to a given, baptismal, or nick name." href="ref-surname.html">surname</a> or <a class="gi" title="(geographical name) identifies a name associated with some geographical feature such as Windrush Valley or Mount Sinai." href="ref-geogName.html">geogName</a>, or <a class="gi" title="(referencing string) contains a general purpose name or referring string." href="ref-rs.html">rs</a> for a general referencing string. In the following chat example (adapted from <a class="link_ptr" href="BIB.html#BIB_DCK" title="Dortmund Chat Corpus Angelika Storrer Michael Beißwenger httphdl.handle.net109320003B014FAA8D00F01F 2017LeibnizInstitut für Deu...">Storrer and Beißwenger (eds.) (2017)</a>), nicknames are linked to a <a class="gi" title="(person) provides information about an identifiable individual, for example a participant in a language interaction, or a person referred to in a historical source." href="ref-person.html">person</a> entry as shown in section <a class="link_ptr" href="CMC.html#CMCParticipants" title="Participants"><span class="headingNumber">9.5.4. </span>Participants</a> via the <span class="att">ref</span> attribute. <div id="CMCnames-egXML-wf" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>" <span class="attribute">rend</span>="<span class="attributevalue">color:black</span>" <span class="attribute">synch</span>="<span class="attributevalue">#f2213001.t007</span>"<br/> <span class="attribute">type</span>="<span class="attributevalue">standard</span>" <span class="attribute">who</span>="<span class="attributevalue">#f2213001.A04</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">f2213001.m27.eg35</span>"&gt;</span><br/> <span class="element">&lt;name <span class="attribute">ref</span>="<span class="attributevalue">#f2213001.A04</span>" <span class="attribute">type</span>="<span class="attributevalue">NICK</span>"&gt;</span><br/>  <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">Konstanze</span>" <span class="attribute">pos</span>="<span class="attributevalue">NE</span>"<br/>   <span class="attribute">xml:id</span>="<span class="attributevalue">f2213001.m27.t1</span>"&gt;</span>Konstanze<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;/name&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">versuchen</span>" <span class="attribute">pos</span>="<span class="attributevalue">VVPP</span>"&gt;</span>versucht<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;name <span class="attribute">ref</span>="<span class="attributevalue">#f2213001.A03</span>" <span class="attribute">type</span>="<span class="attributevalue">NICK</span>"&gt;</span><br/>  <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">Nasenloch</span>" <span class="attribute">pos</span>="<span class="attributevalue">NN</span>"&gt;</span>nasenloch<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;/name&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">die</span>" <span class="attribute">pos</span>="<span class="attributevalue">ART</span>"&gt;</span>den<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">Wunsch</span>" <span class="attribute">pos</span>="<span class="attributevalue">NN</span>"&gt;</span>wunsch<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">zu</span>" <span class="attribute">pos</span>="<span class="attributevalue">PTKZU</span>"&gt;</span>zu<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">erfüllen</span>" <span class="attribute">pos</span>="<span class="attributevalue">VVINF</span>"&gt;</span>erfüllen<span class="element">&lt;/w&gt;</span><br/><span class="comment">&lt;!-- ... --&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_DCK">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCnames-egXML-wf">⚓︎</a></div></div></div><div class="p">In the following version of the same chat snippet, the text strings with the nicknames have been replaced by category label strings for the purpose of anonymization. <div id="CMCnames-egXML-vr" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>" <span class="attribute">rend</span>="<span class="attributevalue">color:black</span>"<br/> <span class="attribute">synch</span>="<span class="attributevalue">#f2213001a.t007</span>" <span class="attribute">type</span>="<span class="attributevalue">standard</span>" <span class="attribute">who</span>="<span class="attributevalue">#f2213001a.A04</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">f2213001a.m27.eg35</span>"&gt;</span><br/> <span class="element">&lt;name <span class="attribute">ref</span>="<span class="attributevalue">#f2213001a.A04</span>" <span class="attribute">type</span>="<span class="attributevalue">NICK</span>"&gt;</span><br/>  <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">NE</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">f2213001a.m27.t1</span>"&gt;</span><br/>   <span class="element">&lt;gap <span class="attribute">reason</span>="<span class="attributevalue">anonymization</span>" <span class="attribute">unit</span>="<span class="attributevalue">token</span>"<br/>    <span class="attribute">quantity</span>="<span class="attributevalue">1</span>"/&gt;</span><br/>   <span class="element">&lt;supplied <span class="attribute">reason</span>="<span class="attributevalue">anonymization</span>"&gt;</span>[_FEMALE-PARTICIPANT-A04_]<span class="element">&lt;/supplied&gt;</span><br/>  <span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;/name&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">versuchen</span>" <span class="attribute">pos</span>="<span class="attributevalue">VVPP</span>"&gt;</span>versucht<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;name <span class="attribute">ref</span>="<span class="attributevalue">#f2213001a.A03</span>" <span class="attribute">type</span>="<span class="attributevalue">NICK</span>"&gt;</span><br/>  <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">NN</span>"&gt;</span><br/>   <span class="element">&lt;gap <span class="attribute">reason</span>="<span class="attributevalue">anonymization</span>" <span class="attribute">unit</span>="<span class="attributevalue">token</span>"<br/>    <span class="attribute">quantity</span>="<span class="attributevalue">1</span>"/&gt;</span><br/>   <span class="element">&lt;supplied <span class="attribute">reason</span>="<span class="attributevalue">anonymization</span>"&gt;</span>[_PARTICIPANT-A04_]<span class="element">&lt;/supplied&gt;</span><br/>  <span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;/name&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">die</span>" <span class="attribute">pos</span>="<span class="attributevalue">ART</span>"&gt;</span>den<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">Wunsch</span>" <span class="attribute">pos</span>="<span class="attributevalue">NN</span>"&gt;</span>wunsch<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">zu</span>" <span class="attribute">pos</span>="<span class="attributevalue">PTKZU</span>"&gt;</span>zu<span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">erfüllen</span>" <span class="attribute">pos</span>="<span class="attributevalue">VVINF</span>"&gt;</span>erfüllen<span class="element">&lt;/w&gt;</span><br/><span class="comment">&lt;!-- ... --&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_DCK">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCnames-egXML-vr">⚓︎</a></div></div></div><p>In the preceding example, pairs of a <a class="gi" title="(gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible." href="ref-gap.html">gap</a> and a <a class="gi" title="(supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe." href="ref-supplied.html">supplied</a> element encode the fact that some substring has been removed and replaced with another string for anonymization purposes. Note that in this example, the <a class="gi" title="(name, proper noun) contains a proper noun or noun phrase." href="ref-name.html">name</a> and the <a class="gi" title="(word) represents a grammatical (not necessarily orthographic) word." href="ref-w.html">w</a> elements and their attributes also provide some categorical information about what has been removed. Using <a class="gi" title="(gap) indicates a point where material has been omitted in a transcription, whether for editorial reasons described in the TEI header, as part of sampling practice, or because the material is illegible, invisible, or inaudible." href="ref-gap.html">gap</a> and <a class="gi" title="(supplied) signifies text supplied by the transcriber or editor for any reason; for example because the original cannot be read due to physical damage, or because of an obvious omission by the author or scribe." href="ref-supplied.html">supplied</a> to record the anonymization is especially recommendable when the original name or referencing string has been ‘pseudonymized’, i.e. replaced by a different referencing string of the same ontological category (such as replacing the female name <span class="mentioned">Konstanze</span> by the female name <span class="mentioned">Kornelia.</span>). In that case, the markup would be the only place where it can be seen that a pseudonymization has been carried out, as in the following version of the example.</p><div class="p"><div id="CMCnames-egXML-vu" class="pre egXML_valid"><span class="element">&lt;post <span class="attribute">modality</span>="<span class="attributevalue">written</span>"<br/> <span class="attribute">generatedBy</span>="<span class="attributevalue">system</span>" <span class="attribute">rend</span>="<span class="attributevalue">color:black</span>"<br/> <span class="attribute">synch</span>="<span class="attributevalue">#f2213001p.t007</span>" <span class="attribute">type</span>="<span class="attributevalue">standard</span>" <span class="attribute">who</span>="<span class="attributevalue">#f2213001p.A04</span>"<br/> <span class="attribute">xml:id</span>="<span class="attributevalue">f2213001p.m27.eg35</span>"&gt;</span><br/> <span class="element">&lt;name <span class="attribute">ref</span>="<span class="attributevalue">#f2213001p.A04</span>" <span class="attribute">type</span>="<span class="attributevalue">NICK</span>"&gt;</span><br/>  <span class="element">&lt;w <span class="attribute">pos</span>="<span class="attributevalue">NE</span>" <span class="attribute">xml:id</span>="<span class="attributevalue">f2213001p.m27.t1</span>"&gt;</span><br/>   <span class="element">&lt;gap <span class="attribute">reason</span>="<span class="attributevalue">pseudonymization</span>"<br/>    <span class="attribute">unit</span>="<span class="attributevalue">token</span>" <span class="attribute">quantity</span>="<span class="attributevalue">1</span>"/&gt;</span><br/>   <span class="element">&lt;supplied <span class="attribute">reason</span>="<span class="attributevalue">pseudonymization</span>"&gt;</span>Kornelia<span class="element">&lt;/supplied&gt;</span><br/>  <span class="element">&lt;/w&gt;</span><br/> <span class="element">&lt;/name&gt;</span><br/> <span class="element">&lt;w <span class="attribute">lemma</span>="<span class="attributevalue">versuchen</span>" <span class="attribute">pos</span>="<span class="attributevalue">VVPP</span>"&gt;</span>versucht<span class="element">&lt;/w&gt;</span><br/><span class="comment">&lt;!-- the rest of the post --&gt;</span><br/><span class="element">&lt;/post&gt;</span><div style="float: right;"><a href="BIB.html#BIB_DCK">bibliography</a> <a class="bookmarklink" title="link to this example" href="#CMCnames-egXML-vu">⚓︎</a></div></div></div></div></div><div class="teidiv1" id="CMCmodule"><div style="margin-top: 0em;" class="miniTOC miniTOC_right"><ul class="subtoc"><li class="subtoc"><span class="previousLink"> Previous </span><a class="navigation" href="CMC.html#CMCrecs"><span class="headingNumber">9.6. </span>Recommendations for Encoding CMC Microstructure</a></li><li class="subtoc"/><li class="subtoc"><a class="navigation" href="index.html">Home</a></li><li class="subtoc"/></ul></div><h2><span class="bookmarklink"><a class="bookmarklink" href="#CMCmodule" title="link to this section "><span class="invisible">TEI: The TEI CMC Module</span>⚓︎</a></span><span class="headingNumber">9.7. </span><span class="head">The TEI CMC Module</span></h2><p>The module described in this chapter makes available the following components: </p><dl class="moduleSpec"><dt class="moduleSpecHead"><span xml:lang="en">Module</span> cmc: Computer-mediated communication</dt><dd><ul><li><span xml:lang="en">Elements defined</span>: <a class="link_odd" title="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." href="ref-post.html">post</a></li><li><span xml:lang="en">Macros defined</span>: <a class="link_odd" title="" href="ref-macro.specialPara.cmc.html">macro.specialPara.cmc</a></li></ul></dd></dl><p> The selection and combination of modules to form a TEI schema is described in <a class="link_ptr" href="ST.html#STIN" title="Defining a TEI Schema"><span class="headingNumber">1.2. </span>Defining a TEI Schema</a>.</p></div></div><div class="stdfooter autogenerated"><address><br/>TEI Guidelines P5 <a class="link_ref" href="AB.html#ABTEI4" title="Future Developments and Version Numbers">Version</a> 4.10.2. Last updated on <span class="date">4th September 2025</span>, revision <a class="link_ref" href="https://github.com/TEIC/TEI/commit/bcfa98f42">bcfa98f42</a>. This page generated on 2025-09-04T16:07:18Z.</address></div></div></body></html>
Reference in a new issue View git blame Copy permalink