TEIWiki - User contributions [en]

SIG:CMC/CoMeRe metadata schema draft for CMC (2014)

2015-10-28T21:24:36Z

Thierry CHANIER: /* Status of this draft */

'''This page is part of the wiki space of the [[SIG:Computer-Mediated Communication|TEI-SIG “Computer-mediated communication"]].'''
__FORCETOC__

==Status of this draft==
This page describes a draft for a '''metadata schema for genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] and applied to all corpora of the CoMeRe project: all these corpora can be fully downloaded from the repository http://hdl.handle.net/11403/comere . Documentation on the CoMeRe project is on its website: http://comere.org

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''. This page should be read in parallel to [[SIG:CMC/Draft: A basic schema for representing CMC in TEI]].

'''Authors of this draft:''' Thierry Chanier.

==Rationales for Modelling CMC discourse==
Note : we use the terme CMC (which stands for Computer-Mediated Communication) in a broad meaning, when refering to all kinds of Networks Mediated Communication (cf. SMS).

Annotation is basically an interpretation and the TEI markup naturally encompasses hypotheses concerning what a text is and what it should be. Although the TEI was historically dedicated to the markup of literature texts, various extensions have been developed for the annotation of other genres and discourses, including poetry, dictionaries, language corpora or speech transcriptions.
If one wants to still apply the word “text” to a coherent and circumscribed set of CMC interactions, it is not so much in the sense originally developed by the TEI. Indeed, it would be closer to the meaning adopted by Bauldry & Thibault (2006). These authors consider (ibid: 4) “texts to be meaning-making events whose functions are defined in particular social contexts” following Halliday (1989:10) who declared that “any instance of living language that is playing a role some part in a context of situation, we shall call it a text. It may be either spoken or written, or indeed in any other medium of expression that we like to think of.”

Bearing the above in mind, we found it more relevant to start from a general framework, that we will term “Interaction Space”, encompassing, from the outset, the richest and the more complex CMC genres and situations. Therefore, we did not work genre by genre, nor with scales that would, for instance, oppose simple and complex situations (e.g. unimodal versus multimodal environments) - as said, our goal is to release guidelines for all CMC documents and not for each CMC genre. This also explains why we did not limit ourselves solely to written communication. For these reasons, we take multimodality into account and our approach is akin to the one under discussion in European networks delaing with TEI and oral corpora: they tend to reject the collection and study of oral corpora as self contained elements and prefer to study oral and multimodal corpora within a common framework.

==Interaction Space==
'''Figure 1:''' Interaction Space
[[File:IS space.jpg|thumb|left]]

===Interaction space: time, location, participants===
An Interaction Space (henceforth referred to as IS) is an abstract concept, located in time (with a beginning and ending date with absolute time, hence a time frame) where interactions between a set of participants occur within an online location. The online location is defined by the properties of the set of environments used by the set of participants. Online means that interactions have been transmitted through networks, Internet, Intranet, telephone, etc.
The set of participants is composed of individual members or groups. It can be a predefined learner group or a circumscribed interest group. A mandatory property of a group is the listing of its participants.

The range of types of interactions (and their related locations) is widespread. On one end of the scale, we find simple types with one environment based on one modality / tool (e.g., one email system, or text chat system, etc). On the other end of the scale, complex environments such as LMSs, where several type of communication modalities are integrated (see hereafter example with the LMS WebCT which uses only textual modalities synchronous — text chat — and asynchronous — email and forum —).
 
===Environment, mode and modality===
An environment may be synchronous or asynchronous, mono or multimodal. Multimodality refers to environments that offer several interaction tools, integrated within the same interface. Every tool uses one mode of communication (e.g., oral, text, icon, nonverbal) and one modality (e.g., a text chat has a specific textual modality, different from the modality of a collective word processor, although both are based on the same textual mode). Every modality has its own grammar which constraints interactions. The icon modality within an audio-graphic environment is composed of a finite set of icons (raise hand, clap hand, is_talking, momentarily absent, etc.). Consequently, an interaction may be multimodal because several modes are used and/or several modalities.

An environment offers the participants one or more locations / places in which to interact. For example, a conference system may have several rooms where a set of participants may work separately in sub-groups or gather in one place. In a 3D environment such as the synthetic world Second Life, a location may be an island or a plot. A plot may even be divided into small sub-plots where verbal communication (text chat, audio) is impossible from one to another. Hence we say that participants are in the same location / place if they can interact at a given time. Notions of location and interaction are closely related and are defined by the affordances of the environment. Lastly, an IS is an abstract space where interaction occurs. When the same participants interact over several weeks, different interaction sessions will occur.

More information on interactions in [[SIG:CMC/Draft: A basic schema for representing CMC in TEI]]

==Describing the interaction space of monomodal environment within the TEI header==
In this section we present the way Interaction Space(s) have been described for monomodal environemnts. next section will consider example fo multimodal environments.

===Environments and affordances===
The first step when describing an environment is to define the general features attached to the overall environment type to which it belongs (e.g., IRC text chat systems). However, this needs to be refined in order to elicit specific features of the system. For example, (1a) describes, in TEI, the general text chat modality where inside one public channel every connected participant may interact with the other participants. Example (1b), however, details the affordances related to the specific IRC system used in cmr-getalp_org. This simplified extract displays the three main types of chat actions (message, command, and event), and part of the subtype of events.
<table>
<tr><td>
<pre>(1a)
<textDesc xml:lang="en-GB">
<channel mode="w" xml:lang="en-GB">
<term ref="#texchat-epiknet">text chat</term></channel>
<constitution>Messages typed by participants inside EpikNet
IRC Channels and then collected by Botstats.com </constitution>
<derivation type="original"/>
<domain type="public"/>
<factuality type="fact"/>
<interaction type="complete" active="plural" passive="many"/>
<preparedness type="spontaneous"/>
<purpose degree="high"><note>Informal discussion</note></purpose>
</textDesc>
</pre></td>
<td><pre>(1b)
<classDecl>
<taxonomy>
<category xml:id="texchat-epiknet" />
<catDesc>Definition of the modality textchat. Type
of messages used in cmr-getalp_org.
Textchat features are those coming from
EPIKNET <ref target="http://www.epiknet.org/"/>
</catDesc>
<category xml:id="chat-message"/>
<category xml:id="chat-command"/>
<category xml:id="chat-event">
<category xml:id="connexion" />
<category xml:id="deconnexion"/>
<category xml:id="changementpseudo" />
[...]
</pre>
</td></tr></table>

====Structure of a textchat message, the <nowiki><post></nowiki> element====
Part of the description a textchat turn, maybe applied to any kind of textchat environment. But particularities imposed by a specific environment (here, again, IRC EpikNet) have to be detailed in order to guide further research analyses (see explanation on attributes @who @alias, on the time), in order to help future research analysis.

<pre>(2)<editorialDecl>
<normalization>
for details about encoding before TEI, see the attached document
<idno>cmr-getalp_org-tei-v1-manuel.pdf</idno>
[…] </normalization>
<stdVals>
The time of a post in second is not known in the textchat logfile.
Hence the values of <att>when-iso</att> on the <gi>time</gi> element always
end in the format <val>HH:MM</val>; i.e., seconds, fractions thereof,
and time zone designators are not present.
</stdVals>
<segmentation>
<gi>post</gi> correspond to textchat turns
</segmentation>
</editorialDecl>
<tagsDecl>
<tagUsage gi="post">one post corresponds to one texchat turn, i.e. one participant's utterrance.<list>
<item><att>xml:id</att>ID of the posting.</item>
<item>
<att>alias</att> is the participant's alias. It does not identify a
participant since a participant may change her/his alias
(cf. <att>type</att>chat-command). Moreover two participant may use the
same alias (we have never checked this).</item>
<item>
<att>who</att>is the login ID given by the system to a participant present in the channel
at one given moment. In other words, if the participant leaves the channel and then comes back,
s/he will receive another system ID. This system ID does not identify a participant
in the whole channel. It only identifies a participant during a short period of interaction.
2 different participants cannot have the same system ID. Tracking aliases' use and relating it
to system IDs may be one way of approaching this identification. This identification (knowing the
exhaustive list of posts sent by the same person) may be a topic of investigation for future analyses.</item>
<item>
<att>type</att>type of message cf. taxononomy. </item>
<item><att>sub-type</att>subtype of message in the taxonomy </item>
<item>
<att>synch</att>absolute time when the IRC channel displayed the post</item>
</list></tagUsage>
</namespace>
</tagsDecl></pre>

===Interactions spaces within the environment===

====Location and time frames====
In (3) is described the general location of the server, then a particular channel with its time frame. 80 other channels (in distinct TEI files) have been described in a similar way in ''cmr-getalp_org_tei_v1'..
<pre>(3) <profileDesc>
<creation>
<date from="2004-02-03" to="2004-04-09"/>
<location type="online_environment">
<placeName>whereas epiknet.org was the place where IR Channels occurred, botstats.com collected
the logfiles of the interactions</placeName>
<geogName>
<rs type="city">Blanquefort, France</rs>
<rs type="TGN">7008161</rs>
<rs type="URL">http://www.botstats.com</rs>
<rs type="URL">http://www.epiknet.org</rs> </geogName>
</creation>
[…]
<settingDesc>
<setting>
<name>rhone-alpes</name>
<locale>one IRC EpikNet channel</locale>
<time from-iso="2004-03-09T00:00" to-iso="2004-04-09T12:08">begining time
of first sessions and end time of last texchat session</time>
<activity>participants type on keyboard. They can only see threads of messages of the IRC
Channel</activity>
</setting>
</settingDesc></pre>

In (4), for SMS, collected from volontarily participating people, we distinguish dates and locations of a company in charge of collecting the data (creation) from the participant location and times (settingDesc)(''cmr-smslareunion-tei-v1'' corpus).

<pre>(4) <profileDesc>
<creation>
<date from="2008-04-10" to="2008-06-30"/>
<location type="telephone network">
<placeName>A private company collected the messages and sent them to
"Laboratoire de recherche sur les espaces Créolophones et Francophones",
Université de la Réunion. All participants were located in La Réunion</placeName>
<geogName>
<rs type="city">La Réunion, France</rs>
<rs type="TGN">1000184</rs>
</geogName></location>
</creation>
[…]
<settingDesc>
<setting>
<name>La Réunion</name>
<locale> private phones (or phones given by their company) of authors of sms </locale>
<time from-iso="2008-04-10T10:57 " to-iso="2008-06-30T21:35"> beginning time of the first
message received by the project server and time of the last message received by the server.
</time>
<activity>participants, leaving in La Réunion freely accepted to send a copy of their SMS to
the server of the project. The copy was sent by authors via a specific process, i.e. a process
different from the SMS sent to their correspondent. </activity>
</setting>
</settingDesc></pre>

==Multimodal environments==

'''Figure 2:''' complex CMC environment with several modalities
[[File:Lms.jpg|thumb|left]] This image shows the description of modalities embedded into an Learning Managment System (LMS) environment: email, textchat, forum (''cmr-simuligne-tei-v1'' corpus). Example(5) details the way the data have bben collected and nature of interactions among the participants. Note that the TEI file contains seperate interactions spaces, one per group of learners, whihc all followed the same learning scenario. Every group IS has a recursive structure where to every learning activity correspond an IS. Locations and time frames are accordingly organized as shown in (6), where there is an allusion to rationales for participants' interaction. Of course, resercherhs who would like to cross participants interactions with the nature of the task they had to accomplish would have to access the ful description of the learning scenario, which is not giveninto the TEI file, but within a specific LETEC corpus.

 

<pre>(5)<textDesc xml:lang="en-GB">
<channel mode="w" xml:lang="en-GB"><term ref="#webCT">Learning Management System (LMS), WebCT</term></channel>
<constitution>This corpus is made of interactions between participants (learners, natives, tutors, researchers)
during the online language learning Simuligne experiment (2001). All these interactions happened within the
LMS and are made of textacht turns, emails and forum messages. Participants were organized in groups
(learning groups): 4 following "scenario 1", a fifth one gathering all participants during the Interculture
activity ("scenario 2",(see <gi>projectDesc</gi>) a sixth restrained to tutors). All details about groups
are in <gi>particDesc</gi>. Data have been collected by the <ref target="CR">corpus compiler of the first
LETEC Simuligne corpus (2009). Since WebCT had no export facilities, data have been extracted out of WebCT
internal database, then structured and anonymized.</ref>
</constitution>
<derivation type="original"/>
<domain>education</domain>
<factuality type="fact"/>
<interaction type="complete" active="many"><note>Interactions happened accordingly to the guidelines
of the learning activities (see <gi>projectDesc</gi> for access to guidelines) </note></interaction>
<preparedness type="spontaneous"/>
<purpose degree="high">learn and practice French, develop intercultural competences</purpose>
</textDesc></pre>

<pre>(6)<creation>
<date from="2001-04-09" to="2001-07-06"/>
<location type="online_environment">
<placeName>Interactions collected on the LMS server in Besançon.
Participants members of two universities one in UK, the other one in France,
but could be online anywhere in the world.</placeName>
<geogName><rs type="city">Milton Keynes, United Kingdom</rs>
<rs type="city">Besançon, France</rs>
<rs type="TGN">7026232</rs>
<rs type="TGN">7008356</rs></geogName>
</location>
</creation>
[….]
<settingDesc>
<setting>
<name>Simuligne online language learning course</name>
<locale>Locations of interactions were different from one learning group to another,
but follow the same learning scenario. They all happened through the communication tools
(email, forum, textchat) of the LMS environment adn their respective spaces: mailboxes, forums, chat rooms.</locale>
<time from-iso="2001-04-09T00:00" to-iso="2001-07-06T12:10">beginning time of first post and end time
of last post</time>
<activity>Participants interacted while following the learning activities and their
guidelines (see <gi>textDesc</gi>, <gi>classDesc</gi>, and <gi>tagDesc</gi> for more information.</activity>
</setting>
</settingDesc></pre>

===Participant's description===

Participants descriptions may considerably vary from one corpus to another. When CMC interacitons happen in an free/open environment, it is almots imossible to collect any information on participant, except those whihc can only be automatically processed.
See (7) for an extract comin from the open IRC textchat already mentionned above (''cmr-getalp_org-tei-v1'' corpus). Participant with ID cmr-get-c024-p45906 has been processed as being different from participant with ID cmr-get-c024-p45905. They both share some common aliases. Impossible to tell whether it is the same person. Here they are considered as 2 people. Within such environment participants tend to constantly change their aliaises in order to tell other participants what their current mood or occupation are.
<pre>(7)
<person xml:id="cmr-get-c024-p45906">
<persName>
<addName type="alias">[tilulu]pYcOoZ</addName>
<addName type="alias">pYcOoZ</addName>
<addName type="alias">pYcOoZ|away</addName>
</persName> </person>
<person xml:id="cmr-get-c024-p45905">
<persName>
<addName type="alias">[tilulu]pYcOoZ</addName>
<addName type="alias">pYcOoZ</addName>
</persName> </person></pre>

On the opposite side when CMC happend in learning situations, reserachers can collect rich informaiotn on users, which need to be incorporated in order to support further research. (8) give an extract of participants (individuals and groups) coming the aforementioned ''cmr-smuligne-tei-v1'' corpus. It is only an extract, many more informaiton on language biography, education, etc. for example can be present.

<pre> (8)<particDesc>
<listPerson>
<person role="learner" xml:id="Gl1">
[here gender, TEI element cannot be written in the wiki!]
<age value="51"/>
<residence>United Kindom</residence>
<affiliation>
<orgName>Open University</orgName>
</affiliation>
<persName>
<addName type="alias">Alba</addName>
</persName>
</person>
[other participants]
<personGrp role="learnerGroup" xml:id="Simu-g-Ga">
<persName>
<addName type="alias">Gallia</addName>
</persName>
</personGrp>
[other groups]
<listRelation corresp="#Simu-g-Ga">
<relation type="social" name="tutor" active="#Gt"/>
<relation type="social" name="native" active="#Gn1 #Gn2"/>
<relation type="social" name="learner"
active="#Gl1 #Gl2 #Gl3 #Gl4 #Gl5 #Gl6 #Gl8 #Gl9 #Gl10"/>
<relation type="social" name="researcher" active="#Tm"/>
</listRelation></pre>

==<nowiki><teiHeader></nowiki> elements used and some limitations to the current TEI version==
When presenting metadata information attached to CMC corpora we have mainly used these elements of the <nowiki><teiHeader></nowiki>. Note that the @mode attribute of <channel> in <nowiki><textDesc></nowiki> have not enough values for describing multimodal texts.

<pre>
encodingDesc
<projectDesc>
<editorialDecl>
<tagsDecl>
<taxonomy>
<classDecl>
<profileDesc>
<creation>
<textDesc>
<particDesc>
</pre>

===Multimodal corpus and TEI file===
When you consider a multimodal corpus, it is made of a set of files (audio files, video files, documents, etc.) among which the TEI file only represents the data structuration related to interactions (see for example a LEarning and TEaching Corpora - LETEC - [http://repository.mulce.org] which gathers into one unique corpus all these files, among which one corresponds to structured interactions , here in the XML manifest).
These interactions are transcriptions of audio and video files or come from logfiles. Hence these files play an important role and should be clearly referred to in the TEI file. As far as we know, there is no easy nor standard way of referencing them within the TEI file. This diffculty has also be stressed by consortia working on oral corpora. There is a clear distinction between a multimodal corpus and a TEI corpus made out of manuscript or a paper-based book. Audio and video files are part of the corpus and go hand in hand with the TEI file.

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2015-10-28T21:24:00Z

Thierry CHANIER: /* Status of this draft */

'''This page is part of the wiki space of the [[SIG:Computer-Mediated Communication|TEI-SIG “Computer-mediated communication"]].'''
__FORCETOC__

== ODD file ==

* '''[[File:Tei-cmc-odd.zip]]''' (version 16th January 2015, Kun Jin and Thierry Chanier)

This ZIP file contains the ODD file defining new elements and new attributes corresponding to the extension proposal of TEI-CMC + an HTML fle documenting the ODD file.

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>). This ODD has been applied to all corpora of the CoMeRe project, which corpora can be fully downloaded from the repository http://hdl.handle.net/11403/comere . Documentation on the CoMeRe project is on its website: http://comere.org

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example for Tweets]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><addressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

== References ==

<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2015-10-28T21:20:50Z

Thierry CHANIER: /* Status of this draft */

'''This page is part of the wiki space of the [[SIG:Computer-Mediated Communication|TEI-SIG “Computer-mediated communication"]].'''
__FORCETOC__

== ODD file ==

* '''[[File:Tei-cmc-odd.zip]]''' (version 16th January 2015, Kun Jin and Thierry Chanier)

This ZIP file contains the ODD file defining new elements and new attributes corresponding to the extension proposal of TEI-CMC + an HTML fle documenting the ODD file.

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>). This ODD has been applied to all corpora of the CoMeRe project, which corpora can be fully downloaded from the repository [http://hdl.handle.net/11403/comere | http://hdl.handle.net/11403/comere]. Documentation on the CoMeRe project is on its website: [http://comere.org | http://comere.org]

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example for Tweets]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><addressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

== References ==

<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe metadata schema draft for CMC (2014)

2015-10-28T21:01:38Z

Thierry CHANIER: /* Status of this draft */

'''This page is part of the wiki space of the [[SIG:Computer-Mediated Communication|TEI-SIG “Computer-mediated communication"]].'''
__FORCETOC__

==Status of this draft==
This page describes a draft for a '''metadata schema for genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] and applied to all corpora of the CoMeRe project: all these corpora can be fully downloaded from the repository [http://hdl.handle.net/11403/comere | http://hdl.handle.net/11403/comere]. Documentation on the CoMeRe project is on its website: [http://comere.org | http://comere.org]

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''. This page should be read in parallel to [[SIG:CMC/Draft: A basic schema for representing CMC in TEI]].

'''Authors of this draft:''' Thierry Chanier.

==Rationales for Modelling CMC discourse==
Note : we use the terme CMC (which stands for Computer-Mediated Communication) in a broad meaning, when refering to all kinds of Networks Mediated Communication (cf. SMS).

Annotation is basically an interpretation and the TEI markup naturally encompasses hypotheses concerning what a text is and what it should be. Although the TEI was historically dedicated to the markup of literature texts, various extensions have been developed for the annotation of other genres and discourses, including poetry, dictionaries, language corpora or speech transcriptions.
If one wants to still apply the word “text” to a coherent and circumscribed set of CMC interactions, it is not so much in the sense originally developed by the TEI. Indeed, it would be closer to the meaning adopted by Bauldry & Thibault (2006). These authors consider (ibid: 4) “texts to be meaning-making events whose functions are defined in particular social contexts” following Halliday (1989:10) who declared that “any instance of living language that is playing a role some part in a context of situation, we shall call it a text. It may be either spoken or written, or indeed in any other medium of expression that we like to think of.”

Bearing the above in mind, we found it more relevant to start from a general framework, that we will term “Interaction Space”, encompassing, from the outset, the richest and the more complex CMC genres and situations. Therefore, we did not work genre by genre, nor with scales that would, for instance, oppose simple and complex situations (e.g. unimodal versus multimodal environments) - as said, our goal is to release guidelines for all CMC documents and not for each CMC genre. This also explains why we did not limit ourselves solely to written communication. For these reasons, we take multimodality into account and our approach is akin to the one under discussion in European networks delaing with TEI and oral corpora: they tend to reject the collection and study of oral corpora as self contained elements and prefer to study oral and multimodal corpora within a common framework.

==Interaction Space==
'''Figure 1:''' Interaction Space
[[File:IS space.jpg|thumb|left]]

===Interaction space: time, location, participants===
An Interaction Space (henceforth referred to as IS) is an abstract concept, located in time (with a beginning and ending date with absolute time, hence a time frame) where interactions between a set of participants occur within an online location. The online location is defined by the properties of the set of environments used by the set of participants. Online means that interactions have been transmitted through networks, Internet, Intranet, telephone, etc.
The set of participants is composed of individual members or groups. It can be a predefined learner group or a circumscribed interest group. A mandatory property of a group is the listing of its participants.

The range of types of interactions (and their related locations) is widespread. On one end of the scale, we find simple types with one environment based on one modality / tool (e.g., one email system, or text chat system, etc). On the other end of the scale, complex environments such as LMSs, where several type of communication modalities are integrated (see hereafter example with the LMS WebCT which uses only textual modalities synchronous — text chat — and asynchronous — email and forum —).
 
===Environment, mode and modality===
An environment may be synchronous or asynchronous, mono or multimodal. Multimodality refers to environments that offer several interaction tools, integrated within the same interface. Every tool uses one mode of communication (e.g., oral, text, icon, nonverbal) and one modality (e.g., a text chat has a specific textual modality, different from the modality of a collective word processor, although both are based on the same textual mode). Every modality has its own grammar which constraints interactions. The icon modality within an audio-graphic environment is composed of a finite set of icons (raise hand, clap hand, is_talking, momentarily absent, etc.). Consequently, an interaction may be multimodal because several modes are used and/or several modalities.

An environment offers the participants one or more locations / places in which to interact. For example, a conference system may have several rooms where a set of participants may work separately in sub-groups or gather in one place. In a 3D environment such as the synthetic world Second Life, a location may be an island or a plot. A plot may even be divided into small sub-plots where verbal communication (text chat, audio) is impossible from one to another. Hence we say that participants are in the same location / place if they can interact at a given time. Notions of location and interaction are closely related and are defined by the affordances of the environment. Lastly, an IS is an abstract space where interaction occurs. When the same participants interact over several weeks, different interaction sessions will occur.

More information on interactions in [[SIG:CMC/Draft: A basic schema for representing CMC in TEI]]

==Describing the interaction space of monomodal environment within the TEI header==
In this section we present the way Interaction Space(s) have been described for monomodal environemnts. next section will consider example fo multimodal environments.

===Environments and affordances===
The first step when describing an environment is to define the general features attached to the overall environment type to which it belongs (e.g., IRC text chat systems). However, this needs to be refined in order to elicit specific features of the system. For example, (1a) describes, in TEI, the general text chat modality where inside one public channel every connected participant may interact with the other participants. Example (1b), however, details the affordances related to the specific IRC system used in cmr-getalp_org. This simplified extract displays the three main types of chat actions (message, command, and event), and part of the subtype of events.
<table>
<tr><td>
<pre>(1a)
<textDesc xml:lang="en-GB">
<channel mode="w" xml:lang="en-GB">
<term ref="#texchat-epiknet">text chat</term></channel>
<constitution>Messages typed by participants inside EpikNet
IRC Channels and then collected by Botstats.com </constitution>
<derivation type="original"/>
<domain type="public"/>
<factuality type="fact"/>
<interaction type="complete" active="plural" passive="many"/>
<preparedness type="spontaneous"/>
<purpose degree="high"><note>Informal discussion</note></purpose>
</textDesc>
</pre></td>
<td><pre>(1b)
<classDecl>
<taxonomy>
<category xml:id="texchat-epiknet" />
<catDesc>Definition of the modality textchat. Type
of messages used in cmr-getalp_org.
Textchat features are those coming from
EPIKNET <ref target="http://www.epiknet.org/"/>
</catDesc>
<category xml:id="chat-message"/>
<category xml:id="chat-command"/>
<category xml:id="chat-event">
<category xml:id="connexion" />
<category xml:id="deconnexion"/>
<category xml:id="changementpseudo" />
[...]
</pre>
</td></tr></table>

====Structure of a textchat message, the <nowiki><post></nowiki> element====
Part of the description a textchat turn, maybe applied to any kind of textchat environment. But particularities imposed by a specific environment (here, again, IRC EpikNet) have to be detailed in order to guide further research analyses (see explanation on attributes @who @alias, on the time), in order to help future research analysis.

<pre>(2)<editorialDecl>
<normalization>
for details about encoding before TEI, see the attached document
<idno>cmr-getalp_org-tei-v1-manuel.pdf</idno>
[…] </normalization>
<stdVals>
The time of a post in second is not known in the textchat logfile.
Hence the values of <att>when-iso</att> on the <gi>time</gi> element always
end in the format <val>HH:MM</val>; i.e., seconds, fractions thereof,
and time zone designators are not present.
</stdVals>
<segmentation>
<gi>post</gi> correspond to textchat turns
</segmentation>
</editorialDecl>
<tagsDecl>
<tagUsage gi="post">one post corresponds to one texchat turn, i.e. one participant's utterrance.<list>
<item><att>xml:id</att>ID of the posting.</item>
<item>
<att>alias</att> is the participant's alias. It does not identify a
participant since a participant may change her/his alias
(cf. <att>type</att>chat-command). Moreover two participant may use the
same alias (we have never checked this).</item>
<item>
<att>who</att>is the login ID given by the system to a participant present in the channel
at one given moment. In other words, if the participant leaves the channel and then comes back,
s/he will receive another system ID. This system ID does not identify a participant
in the whole channel. It only identifies a participant during a short period of interaction.
2 different participants cannot have the same system ID. Tracking aliases' use and relating it
to system IDs may be one way of approaching this identification. This identification (knowing the
exhaustive list of posts sent by the same person) may be a topic of investigation for future analyses.</item>
<item>
<att>type</att>type of message cf. taxononomy. </item>
<item><att>sub-type</att>subtype of message in the taxonomy </item>
<item>
<att>synch</att>absolute time when the IRC channel displayed the post</item>
</list></tagUsage>
</namespace>
</tagsDecl></pre>

===Interactions spaces within the environment===

====Location and time frames====
In (3) is described the general location of the server, then a particular channel with its time frame. 80 other channels (in distinct TEI files) have been described in a similar way in ''cmr-getalp_org_tei_v1'..
<pre>(3) <profileDesc>
<creation>
<date from="2004-02-03" to="2004-04-09"/>
<location type="online_environment">
<placeName>whereas epiknet.org was the place where IR Channels occurred, botstats.com collected
the logfiles of the interactions</placeName>
<geogName>
<rs type="city">Blanquefort, France</rs>
<rs type="TGN">7008161</rs>
<rs type="URL">http://www.botstats.com</rs>
<rs type="URL">http://www.epiknet.org</rs> </geogName>
</creation>
[…]
<settingDesc>
<setting>
<name>rhone-alpes</name>
<locale>one IRC EpikNet channel</locale>
<time from-iso="2004-03-09T00:00" to-iso="2004-04-09T12:08">begining time
of first sessions and end time of last texchat session</time>
<activity>participants type on keyboard. They can only see threads of messages of the IRC
Channel</activity>
</setting>
</settingDesc></pre>

In (4), for SMS, collected from volontarily participating people, we distinguish dates and locations of a company in charge of collecting the data (creation) from the participant location and times (settingDesc)(''cmr-smslareunion-tei-v1'' corpus).

<pre>(4) <profileDesc>
<creation>
<date from="2008-04-10" to="2008-06-30"/>
<location type="telephone network">
<placeName>A private company collected the messages and sent them to
"Laboratoire de recherche sur les espaces Créolophones et Francophones",
Université de la Réunion. All participants were located in La Réunion</placeName>
<geogName>
<rs type="city">La Réunion, France</rs>
<rs type="TGN">1000184</rs>
</geogName></location>
</creation>
[…]
<settingDesc>
<setting>
<name>La Réunion</name>
<locale> private phones (or phones given by their company) of authors of sms </locale>
<time from-iso="2008-04-10T10:57 " to-iso="2008-06-30T21:35"> beginning time of the first
message received by the project server and time of the last message received by the server.
</time>
<activity>participants, leaving in La Réunion freely accepted to send a copy of their SMS to
the server of the project. The copy was sent by authors via a specific process, i.e. a process
different from the SMS sent to their correspondent. </activity>
</setting>
</settingDesc></pre>

==Multimodal environments==

'''Figure 2:''' complex CMC environment with several modalities
[[File:Lms.jpg|thumb|left]] This image shows the description of modalities embedded into an Learning Managment System (LMS) environment: email, textchat, forum (''cmr-simuligne-tei-v1'' corpus). Example(5) details the way the data have bben collected and nature of interactions among the participants. Note that the TEI file contains seperate interactions spaces, one per group of learners, whihc all followed the same learning scenario. Every group IS has a recursive structure where to every learning activity correspond an IS. Locations and time frames are accordingly organized as shown in (6), where there is an allusion to rationales for participants' interaction. Of course, resercherhs who would like to cross participants interactions with the nature of the task they had to accomplish would have to access the ful description of the learning scenario, which is not giveninto the TEI file, but within a specific LETEC corpus.

 

<pre>(5)<textDesc xml:lang="en-GB">
<channel mode="w" xml:lang="en-GB"><term ref="#webCT">Learning Management System (LMS), WebCT</term></channel>
<constitution>This corpus is made of interactions between participants (learners, natives, tutors, researchers)
during the online language learning Simuligne experiment (2001). All these interactions happened within the
LMS and are made of textacht turns, emails and forum messages. Participants were organized in groups
(learning groups): 4 following "scenario 1", a fifth one gathering all participants during the Interculture
activity ("scenario 2",(see <gi>projectDesc</gi>) a sixth restrained to tutors). All details about groups
are in <gi>particDesc</gi>. Data have been collected by the <ref target="CR">corpus compiler of the first
LETEC Simuligne corpus (2009). Since WebCT had no export facilities, data have been extracted out of WebCT
internal database, then structured and anonymized.</ref>
</constitution>
<derivation type="original"/>
<domain>education</domain>
<factuality type="fact"/>
<interaction type="complete" active="many"><note>Interactions happened accordingly to the guidelines
of the learning activities (see <gi>projectDesc</gi> for access to guidelines) </note></interaction>
<preparedness type="spontaneous"/>
<purpose degree="high">learn and practice French, develop intercultural competences</purpose>
</textDesc></pre>

<pre>(6)<creation>
<date from="2001-04-09" to="2001-07-06"/>
<location type="online_environment">
<placeName>Interactions collected on the LMS server in Besançon.
Participants members of two universities one in UK, the other one in France,
but could be online anywhere in the world.</placeName>
<geogName><rs type="city">Milton Keynes, United Kingdom</rs>
<rs type="city">Besançon, France</rs>
<rs type="TGN">7026232</rs>
<rs type="TGN">7008356</rs></geogName>
</location>
</creation>
[….]
<settingDesc>
<setting>
<name>Simuligne online language learning course</name>
<locale>Locations of interactions were different from one learning group to another,
but follow the same learning scenario. They all happened through the communication tools
(email, forum, textchat) of the LMS environment adn their respective spaces: mailboxes, forums, chat rooms.</locale>
<time from-iso="2001-04-09T00:00" to-iso="2001-07-06T12:10">beginning time of first post and end time
of last post</time>
<activity>Participants interacted while following the learning activities and their
guidelines (see <gi>textDesc</gi>, <gi>classDesc</gi>, and <gi>tagDesc</gi> for more information.</activity>
</setting>
</settingDesc></pre>

===Participant's description===

Participants descriptions may considerably vary from one corpus to another. When CMC interacitons happen in an free/open environment, it is almots imossible to collect any information on participant, except those whihc can only be automatically processed.
See (7) for an extract comin from the open IRC textchat already mentionned above (''cmr-getalp_org-tei-v1'' corpus). Participant with ID cmr-get-c024-p45906 has been processed as being different from participant with ID cmr-get-c024-p45905. They both share some common aliases. Impossible to tell whether it is the same person. Here they are considered as 2 people. Within such environment participants tend to constantly change their aliaises in order to tell other participants what their current mood or occupation are.
<pre>(7)
<person xml:id="cmr-get-c024-p45906">
<persName>
<addName type="alias">[tilulu]pYcOoZ</addName>
<addName type="alias">pYcOoZ</addName>
<addName type="alias">pYcOoZ|away</addName>
</persName> </person>
<person xml:id="cmr-get-c024-p45905">
<persName>
<addName type="alias">[tilulu]pYcOoZ</addName>
<addName type="alias">pYcOoZ</addName>
</persName> </person></pre>

On the opposite side when CMC happend in learning situations, reserachers can collect rich informaiotn on users, which need to be incorporated in order to support further research. (8) give an extract of participants (individuals and groups) coming the aforementioned ''cmr-smuligne-tei-v1'' corpus. It is only an extract, many more informaiton on language biography, education, etc. for example can be present.

<pre> (8)<particDesc>
<listPerson>
<person role="learner" xml:id="Gl1">
[here gender, TEI element cannot be written in the wiki!]
<age value="51"/>
<residence>United Kindom</residence>
<affiliation>
<orgName>Open University</orgName>
</affiliation>
<persName>
<addName type="alias">Alba</addName>
</persName>
</person>
[other participants]
<personGrp role="learnerGroup" xml:id="Simu-g-Ga">
<persName>
<addName type="alias">Gallia</addName>
</persName>
</personGrp>
[other groups]
<listRelation corresp="#Simu-g-Ga">
<relation type="social" name="tutor" active="#Gt"/>
<relation type="social" name="native" active="#Gn1 #Gn2"/>
<relation type="social" name="learner"
active="#Gl1 #Gl2 #Gl3 #Gl4 #Gl5 #Gl6 #Gl8 #Gl9 #Gl10"/>
<relation type="social" name="researcher" active="#Tm"/>
</listRelation></pre>

==<nowiki><teiHeader></nowiki> elements used and some limitations to the current TEI version==
When presenting metadata information attached to CMC corpora we have mainly used these elements of the <nowiki><teiHeader></nowiki>. Note that the @mode attribute of <channel> in <nowiki><textDesc></nowiki> have not enough values for describing multimodal texts.

<pre>
encodingDesc
<projectDesc>
<editorialDecl>
<tagsDecl>
<taxonomy>
<classDecl>
<profileDesc>
<creation>
<textDesc>
<particDesc>
</pre>

===Multimodal corpus and TEI file===
When you consider a multimodal corpus, it is made of a set of files (audio files, video files, documents, etc.) among which the TEI file only represents the data structuration related to interactions (see for example a LEarning and TEaching Corpora - LETEC - [http://repository.mulce.org] which gathers into one unique corpus all these files, among which one corresponds to structured interactions , here in the XML manifest).
These interactions are transcriptions of audio and video files or come from logfiles. Hence these files play an important role and should be clearly referred to in the TEI file. As far as we know, there is no easy nor standard way of referencing them within the TEI file. This diffculty has also be stressed by consortia working on oral corpora. There is a clear distinction between a multimodal corpus and a TEI corpus made out of manuscript or a paper-based book. Audio and video files are part of the corpus and go hand in hand with the TEI file.

SIG:CMC/CoMeRe metadata schema draft for CMC (2014)

2015-10-28T20:56:52Z

Thierry CHANIER: /* Status of this draft */

'''This page is part of the wiki space of the [[SIG:Computer-Mediated Communication|TEI-SIG “Computer-mediated communication"]].'''
__FORCETOC__

==Status of this draft==
This page describes a draft for a '''metadata schema for genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]].

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''. This page should be read in parallel to [[SIG:CMC/Draft: A basic schema for representing CMC in TEI]].

'''Authors of this draft:''' Thierry Chanier.

==Rationales for Modelling CMC discourse==
Note : we use the terme CMC (which stands for Computer-Mediated Communication) in a broad meaning, when refering to all kinds of Networks Mediated Communication (cf. SMS).

Annotation is basically an interpretation and the TEI markup naturally encompasses hypotheses concerning what a text is and what it should be. Although the TEI was historically dedicated to the markup of literature texts, various extensions have been developed for the annotation of other genres and discourses, including poetry, dictionaries, language corpora or speech transcriptions.
If one wants to still apply the word “text” to a coherent and circumscribed set of CMC interactions, it is not so much in the sense originally developed by the TEI. Indeed, it would be closer to the meaning adopted by Bauldry & Thibault (2006). These authors consider (ibid: 4) “texts to be meaning-making events whose functions are defined in particular social contexts” following Halliday (1989:10) who declared that “any instance of living language that is playing a role some part in a context of situation, we shall call it a text. It may be either spoken or written, or indeed in any other medium of expression that we like to think of.”

Bearing the above in mind, we found it more relevant to start from a general framework, that we will term “Interaction Space”, encompassing, from the outset, the richest and the more complex CMC genres and situations. Therefore, we did not work genre by genre, nor with scales that would, for instance, oppose simple and complex situations (e.g. unimodal versus multimodal environments) - as said, our goal is to release guidelines for all CMC documents and not for each CMC genre. This also explains why we did not limit ourselves solely to written communication. For these reasons, we take multimodality into account and our approach is akin to the one under discussion in European networks delaing with TEI and oral corpora: they tend to reject the collection and study of oral corpora as self contained elements and prefer to study oral and multimodal corpora within a common framework.

==Interaction Space==
'''Figure 1:''' Interaction Space
[[File:IS space.jpg|thumb|left]]

===Interaction space: time, location, participants===
An Interaction Space (henceforth referred to as IS) is an abstract concept, located in time (with a beginning and ending date with absolute time, hence a time frame) where interactions between a set of participants occur within an online location. The online location is defined by the properties of the set of environments used by the set of participants. Online means that interactions have been transmitted through networks, Internet, Intranet, telephone, etc.
The set of participants is composed of individual members or groups. It can be a predefined learner group or a circumscribed interest group. A mandatory property of a group is the listing of its participants.

The range of types of interactions (and their related locations) is widespread. On one end of the scale, we find simple types with one environment based on one modality / tool (e.g., one email system, or text chat system, etc). On the other end of the scale, complex environments such as LMSs, where several type of communication modalities are integrated (see hereafter example with the LMS WebCT which uses only textual modalities synchronous — text chat — and asynchronous — email and forum —).
 
===Environment, mode and modality===
An environment may be synchronous or asynchronous, mono or multimodal. Multimodality refers to environments that offer several interaction tools, integrated within the same interface. Every tool uses one mode of communication (e.g., oral, text, icon, nonverbal) and one modality (e.g., a text chat has a specific textual modality, different from the modality of a collective word processor, although both are based on the same textual mode). Every modality has its own grammar which constraints interactions. The icon modality within an audio-graphic environment is composed of a finite set of icons (raise hand, clap hand, is_talking, momentarily absent, etc.). Consequently, an interaction may be multimodal because several modes are used and/or several modalities.

An environment offers the participants one or more locations / places in which to interact. For example, a conference system may have several rooms where a set of participants may work separately in sub-groups or gather in one place. In a 3D environment such as the synthetic world Second Life, a location may be an island or a plot. A plot may even be divided into small sub-plots where verbal communication (text chat, audio) is impossible from one to another. Hence we say that participants are in the same location / place if they can interact at a given time. Notions of location and interaction are closely related and are defined by the affordances of the environment. Lastly, an IS is an abstract space where interaction occurs. When the same participants interact over several weeks, different interaction sessions will occur.

More information on interactions in [[SIG:CMC/Draft: A basic schema for representing CMC in TEI]]

==Describing the interaction space of monomodal environment within the TEI header==
In this section we present the way Interaction Space(s) have been described for monomodal environemnts. next section will consider example fo multimodal environments.

===Environments and affordances===
The first step when describing an environment is to define the general features attached to the overall environment type to which it belongs (e.g., IRC text chat systems). However, this needs to be refined in order to elicit specific features of the system. For example, (1a) describes, in TEI, the general text chat modality where inside one public channel every connected participant may interact with the other participants. Example (1b), however, details the affordances related to the specific IRC system used in cmr-getalp_org. This simplified extract displays the three main types of chat actions (message, command, and event), and part of the subtype of events.
<table>
<tr><td>
<pre>(1a)
<textDesc xml:lang="en-GB">
<channel mode="w" xml:lang="en-GB">
<term ref="#texchat-epiknet">text chat</term></channel>
<constitution>Messages typed by participants inside EpikNet
IRC Channels and then collected by Botstats.com </constitution>
<derivation type="original"/>
<domain type="public"/>
<factuality type="fact"/>
<interaction type="complete" active="plural" passive="many"/>
<preparedness type="spontaneous"/>
<purpose degree="high"><note>Informal discussion</note></purpose>
</textDesc>
</pre></td>
<td><pre>(1b)
<classDecl>
<taxonomy>
<category xml:id="texchat-epiknet" />
<catDesc>Definition of the modality textchat. Type
of messages used in cmr-getalp_org.
Textchat features are those coming from
EPIKNET <ref target="http://www.epiknet.org/"/>
</catDesc>
<category xml:id="chat-message"/>
<category xml:id="chat-command"/>
<category xml:id="chat-event">
<category xml:id="connexion" />
<category xml:id="deconnexion"/>
<category xml:id="changementpseudo" />
[...]
</pre>
</td></tr></table>

====Structure of a textchat message, the <nowiki><post></nowiki> element====
Part of the description a textchat turn, maybe applied to any kind of textchat environment. But particularities imposed by a specific environment (here, again, IRC EpikNet) have to be detailed in order to guide further research analyses (see explanation on attributes @who @alias, on the time), in order to help future research analysis.

<pre>(2)<editorialDecl>
<normalization>
for details about encoding before TEI, see the attached document
<idno>cmr-getalp_org-tei-v1-manuel.pdf</idno>
[…] </normalization>
<stdVals>
The time of a post in second is not known in the textchat logfile.
Hence the values of <att>when-iso</att> on the <gi>time</gi> element always
end in the format <val>HH:MM</val>; i.e., seconds, fractions thereof,
and time zone designators are not present.
</stdVals>
<segmentation>
<gi>post</gi> correspond to textchat turns
</segmentation>
</editorialDecl>
<tagsDecl>
<tagUsage gi="post">one post corresponds to one texchat turn, i.e. one participant's utterrance.<list>
<item><att>xml:id</att>ID of the posting.</item>
<item>
<att>alias</att> is the participant's alias. It does not identify a
participant since a participant may change her/his alias
(cf. <att>type</att>chat-command). Moreover two participant may use the
same alias (we have never checked this).</item>
<item>
<att>who</att>is the login ID given by the system to a participant present in the channel
at one given moment. In other words, if the participant leaves the channel and then comes back,
s/he will receive another system ID. This system ID does not identify a participant
in the whole channel. It only identifies a participant during a short period of interaction.
2 different participants cannot have the same system ID. Tracking aliases' use and relating it
to system IDs may be one way of approaching this identification. This identification (knowing the
exhaustive list of posts sent by the same person) may be a topic of investigation for future analyses.</item>
<item>
<att>type</att>type of message cf. taxononomy. </item>
<item><att>sub-type</att>subtype of message in the taxonomy </item>
<item>
<att>synch</att>absolute time when the IRC channel displayed the post</item>
</list></tagUsage>
</namespace>
</tagsDecl></pre>

===Interactions spaces within the environment===

====Location and time frames====
In (3) is described the general location of the server, then a particular channel with its time frame. 80 other channels (in distinct TEI files) have been described in a similar way in ''cmr-getalp_org_tei_v1'..
<pre>(3) <profileDesc>
<creation>
<date from="2004-02-03" to="2004-04-09"/>
<location type="online_environment">
<placeName>whereas epiknet.org was the place where IR Channels occurred, botstats.com collected
the logfiles of the interactions</placeName>
<geogName>
<rs type="city">Blanquefort, France</rs>
<rs type="TGN">7008161</rs>
<rs type="URL">http://www.botstats.com</rs>
<rs type="URL">http://www.epiknet.org</rs> </geogName>
</creation>
[…]
<settingDesc>
<setting>
<name>rhone-alpes</name>
<locale>one IRC EpikNet channel</locale>
<time from-iso="2004-03-09T00:00" to-iso="2004-04-09T12:08">begining time
of first sessions and end time of last texchat session</time>
<activity>participants type on keyboard. They can only see threads of messages of the IRC
Channel</activity>
</setting>
</settingDesc></pre>

In (4), for SMS, collected from volontarily participating people, we distinguish dates and locations of a company in charge of collecting the data (creation) from the participant location and times (settingDesc)(''cmr-smslareunion-tei-v1'' corpus).

<pre>(4) <profileDesc>
<creation>
<date from="2008-04-10" to="2008-06-30"/>
<location type="telephone network">
<placeName>A private company collected the messages and sent them to
"Laboratoire de recherche sur les espaces Créolophones et Francophones",
Université de la Réunion. All participants were located in La Réunion</placeName>
<geogName>
<rs type="city">La Réunion, France</rs>
<rs type="TGN">1000184</rs>
</geogName></location>
</creation>
[…]
<settingDesc>
<setting>
<name>La Réunion</name>
<locale> private phones (or phones given by their company) of authors of sms </locale>
<time from-iso="2008-04-10T10:57 " to-iso="2008-06-30T21:35"> beginning time of the first
message received by the project server and time of the last message received by the server.
</time>
<activity>participants, leaving in La Réunion freely accepted to send a copy of their SMS to
the server of the project. The copy was sent by authors via a specific process, i.e. a process
different from the SMS sent to their correspondent. </activity>
</setting>
</settingDesc></pre>

==Multimodal environments==

'''Figure 2:''' complex CMC environment with several modalities
[[File:Lms.jpg|thumb|left]] This image shows the description of modalities embedded into an Learning Managment System (LMS) environment: email, textchat, forum (''cmr-simuligne-tei-v1'' corpus). Example(5) details the way the data have bben collected and nature of interactions among the participants. Note that the TEI file contains seperate interactions spaces, one per group of learners, whihc all followed the same learning scenario. Every group IS has a recursive structure where to every learning activity correspond an IS. Locations and time frames are accordingly organized as shown in (6), where there is an allusion to rationales for participants' interaction. Of course, resercherhs who would like to cross participants interactions with the nature of the task they had to accomplish would have to access the ful description of the learning scenario, which is not giveninto the TEI file, but within a specific LETEC corpus.

 

<pre>(5)<textDesc xml:lang="en-GB">
<channel mode="w" xml:lang="en-GB"><term ref="#webCT">Learning Management System (LMS), WebCT</term></channel>
<constitution>This corpus is made of interactions between participants (learners, natives, tutors, researchers)
during the online language learning Simuligne experiment (2001). All these interactions happened within the
LMS and are made of textacht turns, emails and forum messages. Participants were organized in groups
(learning groups): 4 following "scenario 1", a fifth one gathering all participants during the Interculture
activity ("scenario 2",(see <gi>projectDesc</gi>) a sixth restrained to tutors). All details about groups
are in <gi>particDesc</gi>. Data have been collected by the <ref target="CR">corpus compiler of the first
LETEC Simuligne corpus (2009). Since WebCT had no export facilities, data have been extracted out of WebCT
internal database, then structured and anonymized.</ref>
</constitution>
<derivation type="original"/>
<domain>education</domain>
<factuality type="fact"/>
<interaction type="complete" active="many"><note>Interactions happened accordingly to the guidelines
of the learning activities (see <gi>projectDesc</gi> for access to guidelines) </note></interaction>
<preparedness type="spontaneous"/>
<purpose degree="high">learn and practice French, develop intercultural competences</purpose>
</textDesc></pre>

<pre>(6)<creation>
<date from="2001-04-09" to="2001-07-06"/>
<location type="online_environment">
<placeName>Interactions collected on the LMS server in Besançon.
Participants members of two universities one in UK, the other one in France,
but could be online anywhere in the world.</placeName>
<geogName><rs type="city">Milton Keynes, United Kingdom</rs>
<rs type="city">Besançon, France</rs>
<rs type="TGN">7026232</rs>
<rs type="TGN">7008356</rs></geogName>
</location>
</creation>
[….]
<settingDesc>
<setting>
<name>Simuligne online language learning course</name>
<locale>Locations of interactions were different from one learning group to another,
but follow the same learning scenario. They all happened through the communication tools
(email, forum, textchat) of the LMS environment adn their respective spaces: mailboxes, forums, chat rooms.</locale>
<time from-iso="2001-04-09T00:00" to-iso="2001-07-06T12:10">beginning time of first post and end time
of last post</time>
<activity>Participants interacted while following the learning activities and their
guidelines (see <gi>textDesc</gi>, <gi>classDesc</gi>, and <gi>tagDesc</gi> for more information.</activity>
</setting>
</settingDesc></pre>

===Participant's description===

Participants descriptions may considerably vary from one corpus to another. When CMC interacitons happen in an free/open environment, it is almots imossible to collect any information on participant, except those whihc can only be automatically processed.
See (7) for an extract comin from the open IRC textchat already mentionned above (''cmr-getalp_org-tei-v1'' corpus). Participant with ID cmr-get-c024-p45906 has been processed as being different from participant with ID cmr-get-c024-p45905. They both share some common aliases. Impossible to tell whether it is the same person. Here they are considered as 2 people. Within such environment participants tend to constantly change their aliaises in order to tell other participants what their current mood or occupation are.
<pre>(7)
<person xml:id="cmr-get-c024-p45906">
<persName>
<addName type="alias">[tilulu]pYcOoZ</addName>
<addName type="alias">pYcOoZ</addName>
<addName type="alias">pYcOoZ|away</addName>
</persName> </person>
<person xml:id="cmr-get-c024-p45905">
<persName>
<addName type="alias">[tilulu]pYcOoZ</addName>
<addName type="alias">pYcOoZ</addName>
</persName> </person></pre>

On the opposite side when CMC happend in learning situations, reserachers can collect rich informaiotn on users, which need to be incorporated in order to support further research. (8) give an extract of participants (individuals and groups) coming the aforementioned ''cmr-smuligne-tei-v1'' corpus. It is only an extract, many more informaiton on language biography, education, etc. for example can be present.

<pre> (8)<particDesc>
<listPerson>
<person role="learner" xml:id="Gl1">
[here gender, TEI element cannot be written in the wiki!]
<age value="51"/>
<residence>United Kindom</residence>
<affiliation>
<orgName>Open University</orgName>
</affiliation>
<persName>
<addName type="alias">Alba</addName>
</persName>
</person>
[other participants]
<personGrp role="learnerGroup" xml:id="Simu-g-Ga">
<persName>
<addName type="alias">Gallia</addName>
</persName>
</personGrp>
[other groups]
<listRelation corresp="#Simu-g-Ga">
<relation type="social" name="tutor" active="#Gt"/>
<relation type="social" name="native" active="#Gn1 #Gn2"/>
<relation type="social" name="learner"
active="#Gl1 #Gl2 #Gl3 #Gl4 #Gl5 #Gl6 #Gl8 #Gl9 #Gl10"/>
<relation type="social" name="researcher" active="#Tm"/>
</listRelation></pre>

==<nowiki><teiHeader></nowiki> elements used and some limitations to the current TEI version==
When presenting metadata information attached to CMC corpora we have mainly used these elements of the <nowiki><teiHeader></nowiki>. Note that the @mode attribute of <channel> in <nowiki><textDesc></nowiki> have not enough values for describing multimodal texts.

<pre>
encodingDesc
<projectDesc>
<editorialDecl>
<tagsDecl>
<taxonomy>
<classDecl>
<profileDesc>
<creation>
<textDesc>
<particDesc>
</pre>

===Multimodal corpus and TEI file===
When you consider a multimodal corpus, it is made of a set of files (audio files, video files, documents, etc.) among which the TEI file only represents the data structuration related to interactions (see for example a LEarning and TEaching Corpora - LETEC - [http://repository.mulce.org] which gathers into one unique corpus all these files, among which one corresponds to structured interactions , here in the XML manifest).
These interactions are transcriptions of audio and video files or come from logfiles. Hence these files play an important role and should be clearly referred to in the TEI file. As far as we know, there is no easy nor standard way of referencing them within the TEI file. This diffculty has also be stressed by consortia working on oral corpora. There is a clear distinction between a multimodal corpus and a TEI corpus made out of manuscript or a paper-based book. Audio and video files are part of the corpus and go hand in hand with the TEI file.

File:Tei-cmc-odd.zip

2015-03-02T11:34:05Z

Thierry CHANIER: uploaded a new version of "File:Tei-cmc-odd.zip": - tei_cmr-cmc-kernel.odd: ODD which contains all the changes made to TEI-P5. The TEI header has been fully documented in order to explain how we proceeded in CoMeRe PLEASE READ THE

Zip which contains the ODD file + the documentation (HTML file) corresponding to the extension proposal TEI-CMC

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2015-01-16T15:26:54Z

Thierry CHANIER: /* Documentation and ODD on TEI-CMC */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example for Tweets]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><addressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

==Documentation and References==

=== Documentation and ODD on TEI-CMC ===
This is the first version of the ODD corresponding to TEI-CMC and its documentation.

* ODD : [[File:Tei-cmc-odd.zip]] (version 16th January 2015, Kun Jin and Thierry Chanier ; ''please do not circulate, just the very first draft not fully documented'').

This ZIP file contains the ODD file defining new elements and new attributes corresponding to the extension proposal of TEI-CMC + an HTML fle documenting the ODD file. It will be regularly updates while the discussion goes on.

=== References ===

<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe metadata schema draft for CMC (2014)

2015-01-16T15:21:16Z

Thierry CHANIER: /* Documentation and ODD on TEI-CMC */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''metadata schema for genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]].

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''. This page should be read in parallel to [[SIG:CMC/Draft: A basic schema for representing CMC in TEI]].

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Rationales for Modelling CMC discourse==
Note : we use the terme CMC (which stands for Computer-Mediated Communication) in a broad meaning, when refering to all kinds of Networks Mediated Communication (cf. SMS).

Annotation is basically an interpretation and the TEI markup naturally encompasses hypotheses concerning what a text is and what it should be. Although the TEI was historically dedicated to the markup of literature texts, various extensions have been developed for the annotation of other genres and discourses, including poetry, dictionaries, language corpora or speech transcriptions.
If one wants to still apply the word “text” to a coherent and circumscribed set of CMC interactions, it is not so much in the sense originally developed by the TEI. Indeed, it would be closer to the meaning adopted by Bauldry & Thibault (2006). These authors consider (ibid: 4) “texts to be meaning-making events whose functions are defined in particular social contexts” following Halliday (1989:10) who declared that “any instance of living language that is playing a role some part in a context of situation, we shall call it a text. It may be either spoken or written, or indeed in any other medium of expression that we like to think of.”

Bearing the above in mind, we found it more relevant to start from a general framework, that we will term “Interaction Space”, encompassing, from the outset, the richest and the more complex CMC genres and situations. Therefore, we did not work genre by genre, nor with scales that would, for instance, oppose simple and complex situations (e.g. unimodal versus multimodal environments) - as said, our goal is to release guidelines for all CMC documents and not for each CMC genre. This also explains why we did not limit ourselves solely to written communication. For these reasons, we take multimodality into account and our approach is akin to the one under discussion in European networks delaing with TEI and oral corpora: they tend to reject the collection and study of oral corpora as self contained elements and prefer to study oral and multimodal corpora within a common framework.

==Interaction Space==
'''Figure 1:''' Interaction Space
[[File:IS space.jpg|thumb|left]]

===Interaction space: time, location, participants===
An Interaction Space (henceforth referred to as IS) is an abstract concept, located in time (with a beginning and ending date with absolute time, hence a time frame) where interactions between a set of participants occur within an online location. The online location is defined by the properties of the set of environments used by the set of participants. Online means that interactions have been transmitted through networks, Internet, Intranet, telephone, etc.
The set of participants is composed of individual members or groups. It can be a predefined learner group or a circumscribed interest group. A mandatory property of a group is the listing of its participants.

The range of types of interactions (and their related locations) is widespread. On one end of the scale, we find simple types with one environment based on one modality / tool (e.g., one email system, or text chat system, etc). On the other end of the scale, complex environments such as LMSs, where several type of communication modalities are integrated (see hereafter example with the LMS WebCT which uses only textual modalities synchronous — text chat — and asynchronous — email and forum —).
 
===Environment, mode and modality===
An environment may be synchronous or asynchronous, mono or multimodal. Multimodality refers to environments that offer several interaction tools, integrated within the same interface. Every tool uses one mode of communication (e.g., oral, text, icon, nonverbal) and one modality (e.g., a text chat has a specific textual modality, different from the modality of a collective word processor, although both are based on the same textual mode). Every modality has its own grammar which constraints interactions. The icon modality within an audio-graphic environment is composed of a finite set of icons (raise hand, clap hand, is_talking, momentarily absent, etc.). Consequently, an interaction may be multimodal because several modes are used and/or several modalities.

An environment offers the participants one or more locations / places in which to interact. For example, a conference system may have several rooms where a set of participants may work separately in sub-groups or gather in one place. In a 3D environment such as the synthetic world Second Life, a location may be an island or a plot. A plot may even be divided into small sub-plots where verbal communication (text chat, audio) is impossible from one to another. Hence we say that participants are in the same location / place if they can interact at a given time. Notions of location and interaction are closely related and are defined by the affordances of the environment. Lastly, an IS is an abstract space where interaction occurs. When the same participants interact over several weeks, different interaction sessions will occur.

More information on interactions in [[SIG:CMC/Draft: A basic schema for representing CMC in TEI]]

==Describing the interaction space of monomodal environment within the TEI header==
In this section we present the way Interaction Space(s) have been described for monomodal environemnts. next section will consider example fo multimodal environments.

===Environments and affordances===
The first step when describing an environment is to define the general features attached to the overall environment type to which it belongs (e.g., IRC text chat systems). However, this needs to be refined in order to elicit specific features of the system. For example, (1a) describes, in TEI, the general text chat modality where inside one public channel every connected participant may interact with the other participants. Example (1b), however, details the affordances related to the specific IRC system used in cmr-getalp_org. This simplified extract displays the three main types of chat actions (message, command, and event), and part of the subtype of events.
<table>
<tr><td>
<pre>(1a)
<textDesc xml:lang="en-GB">
<channel mode="w" xml:lang="en-GB">
<term ref="#texchat-epiknet">text chat</term></channel>
<constitution>Messages typed by participants inside EpikNet
IRC Channels and then collected by Botstats.com </constitution>
<derivation type="original"/>
<domain type="public"/>
<factuality type="fact"/>
<interaction type="complete" active="plural" passive="many"/>
<preparedness type="spontaneous"/>
<purpose degree="high"><note>Informal discussion</note></purpose>
</textDesc>
</pre></td>
<td><pre>(1b)
<classDecl>
<taxonomy>
<category xml:id="texchat-epiknet" />
<catDesc>Definition of the modality textchat. Type
of messages used in cmr-getalp_org.
Textchat features are those coming from
EPIKNET <ref target="http://www.epiknet.org/"/>
</catDesc>
<category xml:id="chat-message"/>
<category xml:id="chat-command"/>
<category xml:id="chat-event">
<category xml:id="connexion" />
<category xml:id="deconnexion"/>
<category xml:id="changementpseudo" />
[...]
</pre>
</td></tr></table>

====Structure of a textchat message, the <nowiki><post></nowiki> element====
Part of the description a textchat turn, maybe applied to any kind of textchat environment. But particularities imposed by a specific environment (here, again, IRC EpikNet) have to be detailed in order to guide further research analyses (see explanation on attributes @who @alias, on the time), in order to help future research analysis.

<pre>(2)<editorialDecl>
<normalization>
for details about encoding before TEI, see the attached document
<idno>cmr-getalp_org-tei-v1-manuel.pdf</idno>
[…] </normalization>
<stdVals>
The time of a post in second is not known in the textchat logfile.
Hence the values of <att>when-iso</att> on the <gi>time</gi> element always
end in the format <val>HH:MM</val>; i.e., seconds, fractions thereof,
and time zone designators are not present.
</stdVals>
<segmentation>
<gi>post</gi> correspond to textchat turns
</segmentation>
</editorialDecl>
<tagsDecl>
<tagUsage gi="post">one post corresponds to one texchat turn, i.e. one participant's utterrance.<list>
<item><att>xml:id</att>ID of the posting.</item>
<item>
<att>alias</att> is the participant's alias. It does not identify a
participant since a participant may change her/his alias
(cf. <att>type</att>chat-command). Moreover two participant may use the
same alias (we have never checked this).</item>
<item>
<att>who</att>is the login ID given by the system to a participant present in the channel
at one given moment. In other words, if the participant leaves the channel and then comes back,
s/he will receive another system ID. This system ID does not identify a participant
in the whole channel. It only identifies a participant during a short period of interaction.
2 different participants cannot have the same system ID. Tracking aliases' use and relating it
to system IDs may be one way of approaching this identification. This identification (knowing the
exhaustive list of posts sent by the same person) may be a topic of investigation for future analyses.</item>
<item>
<att>type</att>type of message cf. taxononomy. </item>
<item><att>sub-type</att>subtype of message in the taxonomy </item>
<item>
<att>synch</att>absolute time when the IRC channel displayed the post</item>
</list></tagUsage>
</namespace>
</tagsDecl></pre>

===Interactions spaces within the environment===

====Location and time frames====
In (3) is described the general location of the server, then a particular channel with its time frame. 80 other channels (in distinct TEI files) have been described in a similar way in ''cmr-getalp_org_tei_v1'..
<pre>(3) <profileDesc>
<creation>
<date from="2004-02-03" to="2004-04-09"/>
<location type="online_environment">
<placeName>whereas epiknet.org was the place where IR Channels occurred, botstats.com collected
the logfiles of the interactions</placeName>
<geogName>
<rs type="city">Blanquefort, France</rs>
<rs type="TGN">7008161</rs>
<rs type="URL">http://www.botstats.com</rs>
<rs type="URL">http://www.epiknet.org</rs> </geogName>
</creation>
[…]
<settingDesc>
<setting>
<name>rhone-alpes</name>
<locale>one IRC EpikNet channel</locale>
<time from-iso="2004-03-09T00:00" to-iso="2004-04-09T12:08">begining time
of first sessions and end time of last texchat session</time>
<activity>participants type on keyboard. They can only see threads of messages of the IRC
Channel</activity>
</setting>
</settingDesc></pre>

In (4), for SMS, collected from volontarily participating people, we distinguish dates and locations of a company in charge of collecting the data (creation) from the participant location and times (settingDesc)(''cmr-smslareunion-tei-v1'' corpus).

<pre>(4) <profileDesc>
<creation>
<date from="2008-04-10" to="2008-06-30"/>
<location type="telephone network">
<placeName>A private company collected the messages and sent them to
"Laboratoire de recherche sur les espaces Créolophones et Francophones",
Université de la Réunion. All participants were located in La Réunion</placeName>
<geogName>
<rs type="city">La Réunion, France</rs>
<rs type="TGN">1000184</rs>
</geogName></location>
</creation>
[…]
<settingDesc>
<setting>
<name>La Réunion</name>
<locale> private phones (or phones given by their company) of authors of sms </locale>
<time from-iso="2008-04-10T10:57 " to-iso="2008-06-30T21:35"> beginning time of the first
message received by the project server and time of the last message received by the server.
</time>
<activity>participants, leaving in La Réunion freely accepted to send a copy of their SMS to
the server of the project. The copy was sent by authors via a specific process, i.e. a process
different from the SMS sent to their correspondent. </activity>
</setting>
</settingDesc></pre>

==Multimodal environments==

'''Figure 2:''' complex CMC environment with several modalities
[[File:Lms.jpg|thumb|left]] This image shows the description of modalities embedded into an Learning Managment System (LMS) environment: email, textchat, forum (''cmr-simuligne-tei-v1'' corpus). Example(5) details the way the data have bben collected and nature of interactions among the participants. Note that the TEI file contains seperate interactions spaces, one per group of learners, whihc all followed the same learning scenario. Every group IS has a recursive structure where to every learning activity correspond an IS. Locations and time frames are accordingly organized as shown in (6), where there is an allusion to rationales for participants' interaction. Of course, resercherhs who would like to cross participants interactions with the nature of the task they had to accomplish would have to access the ful description of the learning scenario, which is not giveninto the TEI file, but within a specific LETEC corpus.

 

<pre>(5)<textDesc xml:lang="en-GB">
<channel mode="w" xml:lang="en-GB"><term ref="#webCT">Learning Management System (LMS), WebCT</term></channel>
<constitution>This corpus is made of interactions between participants (learners, natives, tutors, researchers)
during the online language learning Simuligne experiment (2001). All these interactions happened within the
LMS and are made of textacht turns, emails and forum messages. Participants were organized in groups
(learning groups): 4 following "scenario 1", a fifth one gathering all participants during the Interculture
activity ("scenario 2",(see <gi>projectDesc</gi>) a sixth restrained to tutors). All details about groups
are in <gi>particDesc</gi>. Data have been collected by the <ref target="CR">corpus compiler of the first
LETEC Simuligne corpus (2009). Since WebCT had no export facilities, data have been extracted out of WebCT
internal database, then structured and anonymized.</ref>
</constitution>
<derivation type="original"/>
<domain>education</domain>
<factuality type="fact"/>
<interaction type="complete" active="many"><note>Interactions happened accordingly to the guidelines
of the learning activities (see <gi>projectDesc</gi> for access to guidelines) </note></interaction>
<preparedness type="spontaneous"/>
<purpose degree="high">learn and practice French, develop intercultural competences</purpose>
</textDesc></pre>

<pre>(6)<creation>
<date from="2001-04-09" to="2001-07-06"/>
<location type="online_environment">
<placeName>Interactions collected on the LMS server in Besançon.
Participants members of two universities one in UK, the other one in France,
but could be online anywhere in the world.</placeName>
<geogName><rs type="city">Milton Keynes, United Kingdom</rs>
<rs type="city">Besançon, France</rs>
<rs type="TGN">7026232</rs>
<rs type="TGN">7008356</rs></geogName>
</location>
</creation>
[….]
<settingDesc>
<setting>
<name>Simuligne online language learning course</name>
<locale>Locations of interactions were different from one learning group to another,
but follow the same learning scenario. They all happened through the communication tools
(email, forum, textchat) of the LMS environment adn their respective spaces: mailboxes, forums, chat rooms.</locale>
<time from-iso="2001-04-09T00:00" to-iso="2001-07-06T12:10">beginning time of first post and end time
of last post</time>
<activity>Participants interacted while following the learning activities and their
guidelines (see <gi>textDesc</gi>, <gi>classDesc</gi>, and <gi>tagDesc</gi> for more information.</activity>
</setting>
</settingDesc></pre>

===Participant's description===

Participants descriptions may considerably vary from one corpus to another. When CMC interacitons happen in an free/open environment, it is almots imossible to collect any information on participant, except those whihc can only be automatically processed.
See (7) for an extract comin from the open IRC textchat already mentionned above (''cmr-getalp_org-tei-v1'' corpus). Participant with ID cmr-get-c024-p45906 has been processed as being different from participant with ID cmr-get-c024-p45905. They both share some common aliases. Impossible to tell whether it is the same person. Here they are considered as 2 people. Within such environment participants tend to constantly change their aliaises in order to tell other participants what their current mood or occupation are.
<pre>(7)
<person xml:id="cmr-get-c024-p45906">
<persName>
<addName type="alias">[tilulu]pYcOoZ</addName>
<addName type="alias">pYcOoZ</addName>
<addName type="alias">pYcOoZ|away</addName>
</persName> </person>
<person xml:id="cmr-get-c024-p45905">
<persName>
<addName type="alias">[tilulu]pYcOoZ</addName>
<addName type="alias">pYcOoZ</addName>
</persName> </person></pre>

On the opposite side when CMC happend in learning situations, reserachers can collect rich informaiotn on users, which need to be incorporated in order to support further research. (8) give an extract of participants (individuals and groups) coming the aforementioned ''cmr-smuligne-tei-v1'' corpus. It is only an extract, many more informaiton on language biography, education, etc. for example can be present.

<pre> (8)<particDesc>
<listPerson>
<person role="learner" xml:id="Gl1">
[here gender, TEI element cannot be written in the wiki!]
<age value="51"/>
<residence>United Kindom</residence>
<affiliation>
<orgName>Open University</orgName>
</affiliation>
<persName>
<addName type="alias">Alba</addName>
</persName>
</person>
[other participants]
<personGrp role="learnerGroup" xml:id="Simu-g-Ga">
<persName>
<addName type="alias">Gallia</addName>
</persName>
</personGrp>
[other groups]
<listRelation corresp="#Simu-g-Ga">
<relation type="social" name="tutor" active="#Gt"/>
<relation type="social" name="native" active="#Gn1 #Gn2"/>
<relation type="social" name="learner"
active="#Gl1 #Gl2 #Gl3 #Gl4 #Gl5 #Gl6 #Gl8 #Gl9 #Gl10"/>
<relation type="social" name="researcher" active="#Tm"/>
</listRelation></pre>

==<nowiki><teiHeader></nowiki> elements used and some limitations to the current TEI version==
When presenting metadata information attached to CMC corpora we have mainly used these elements of the <nowiki><teiHeader></nowiki>. Note that the @mode attribute of <channel> in <nowiki><textDesc></nowiki> have not enough values for describing multimodal texts.

<pre>
encodingDesc
<projectDesc>
<editorialDecl>
<tagsDecl>
<taxonomy>
<classDecl>
<profileDesc>
<creation>
<textDesc>
<particDesc>
</pre>

===Multimodal corpus and TEI file===
When you consider a multimodal corpus, it is made of a set of files (audio files, video files, documents, etc.) among which the TEI file only represents the data structuration related to interactions (see for example a LEarning and TEaching Corpora - LETEC - [http://repository.mulce.org] which gathers into one unique corpus all these files, among which one corresponds to structured interactions , here in the XML manifest).
These interactions are transcriptions of audio and video files or come from logfiles. Hence these files play an important role and should be clearly referred to in the TEI file. As far as we know, there is no easy nor standard way of referencing them within the TEI file. This diffculty has also be stressed by consortia working on oral corpora. There is a clear distinction between a multimodal corpus and a TEI corpus made out of manuscript or a paper-based book. Audio and video files are part of the corpus and go hand in hand with the TEI file.

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2015-01-16T15:20:46Z

Thierry CHANIER: /* References and notes */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example for Tweets]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><addressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

==Documentation and References==

=== Documentation and ODD on TEI-CMC ===
This is the first version of the ODD corresponding to TEI-CMC and its documentation.

* ODD : [[File:Tei-cmc-odd.zip]] (version 16th January 2015, Kun Jin and Thierry Chanier ; please do not circulate, just the very first draft not fully documented).

This ZIP file contains the ODD file defining new elements and new attributes corresponding to the extension proposal of TEI-CMC + an HTML fle documenting the ODD file. It will be regularly updates while the discussion goes on.

=== References ===

<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2015-01-16T15:20:07Z

Thierry CHANIER: /* Documentation and ODD on TEI-CMC */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example for Tweets]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><addressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

==References and notes==

=== Documentation and ODD on TEI-CMC ===
This is the first version of the ODD corresponding to TEI-CMC and its documentation.

* ODD : [[File:Tei-cmc-odd.zip]] (version 16th January 2015, Kun Jin and Thierry Chanier ; please do not circulate, just the very first draft not fully documented).

This ZIP file contains the ODD file defining new elements and new attributes corresponding to the extension proposal of TEI-CMC + an HTML fle documenting the ODD file. It will be regularly updates while the discussion goes on.

=== Other documentation ===

<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2015-01-16T15:19:43Z

Thierry CHANIER: /* References and notes */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example for Tweets]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><addressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

=== Documentation and ODD on TEI-CMC ===
This is the first version of the ODD corresponding to TEI-CMC and its documentation.

* ODD : [[File:Tei-cmc-odd.zip]] (version 16th January 2015, Kun Jin and Thierry Chanier ; please do not circulate, just the very first draft not fully documented).

This ZIP file contains the ODD file defining new elements and new attributes corresponding to the extension proposal of TEI-CMC + an HTML fle documenting the ODD file. It will be regularly updates while the discussion goes on.

==References and notes==

=== Documentation and ODD on TEI-CMC ===
This is the first version of the ODD corresponding to TEI-CMC and its documentation.

* ODD : [[File:Tei-cmc-odd.zip]] (version 16th January 2015, Kun Jin and Thierry Chanier ; please do not circulate, just the very first draft not fully documented).

This ZIP file contains the ODD file defining new elements and new attributes corresponding to the extension proposal of TEI-CMC + an HTML fle documenting the ODD file. It will be regularly updates while the discussion goes on.

=== Other documentation ===

<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2015-01-16T15:16:59Z

Thierry CHANIER: /* Anonymization */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example for Tweets]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><addressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

=== Documentation and ODD on TEI-CMC ===
This is the first version of the ODD corresponding to TEI-CMC and its documentation.

* ODD : [[File:Tei-cmc-odd.zip]] (version 16th January 2015, Kun Jin and Thierry Chanier ; please do not circulate, just the very first draft not fully documented).

This ZIP file contains the ODD file defining new elements and new attributes corresponding to the extension proposal of TEI-CMC + an HTML fle documenting the ODD file. It will be regularly updates while the discussion goes on.

==References and notes==
<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe metadata schema draft for CMC (2014)

2015-01-16T15:11:13Z

Thierry CHANIER: /* Documentation and ODD on TEI-CMC */

SIG:CMC/CoMeRe metadata schema draft for CMC (2014)

2015-01-16T15:04:49Z

Thierry CHANIER: /* Documentation and ODD on TEI-CMC */

File:Tei-cmc-odd.zip

2015-01-16T15:03:25Z

Thierry CHANIER: Zip which contains the ODD file + the documentation (HTML file) corresponding to the extension proposal TEI-CMC

Zip which contains the ODD file + the documentation (HTML file) corresponding to the extension proposal TEI-CMC

SIG:CMC/CoMeRe metadata schema draft for CMC (2014)

2015-01-16T14:54:58Z

Thierry CHANIER: /* Documentation and ODD on TEI-CMC */

SIG:CMC/CoMeRe metadata schema draft for CMC (2014)

2015-01-16T14:51:32Z

Thierry CHANIER: /* Multimodal corpus and TEI file */

SIG:CMC/Technical Meeting on CMC at DARIAH VCC 2014

2014-07-16T14:19:18Z

Thierry CHANIER: /* Pt. I: Presentations (Thu 15:00-17:00) */

<table width="90%" border="0" align="center">
<tr>
<td>
<big>
This pages describes a workshop and tentative program for a community session/technical meeting on issues related with the modeling of CMC corpora organized by members of the CMC-SIG at the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th DARIAH-EU VCC meeting 2014] in Rome.

'''Date:''' Thursday, September 18, 15:00-18:00

'''Location:''' Rome, [http://www.iliesi.cnr.it/EN/sede.shtml Villa Mirafiori]

Main page of the CMC-SIG in this wiki: [[SIG:Computer-Mediated Communication]]

== DESCRIPTION ==

<big>'''TEI CMC: Models and tools for structuring & annotating corpora of social media / computer-mediated communication'''</big> See [http://dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting/programme/community-sessions.html PDF version] on the DARIAH website

Corpora of ''computer-mediated communication'' (CMC) are a desideratum for many scholars in the humanities who are interested in doing empirical research of language use and of emerging communicative genres on the Internet and in social media applications. Important steps for building such corpora and for representing them in an interoperable way are:
*To create models for the representation of CMC (including text-only as well as multimodal genres) which comply with a standard or de-facto standard in the field of humanities;
*To adapt tools for boilerplate removal and natural language processing to the structural and linguistic peculiarities of these genres (e.g., tools for converting raw CMC data into a standard format; tools for linguistic processing, such as tokenizers, POS taggers, parsers etc.).

Researchers at a European level are already aware that many of the challenges in building CMC corpora in the humanities are the same for every language; therefore CMC corpus projects for different languages can benefit from sharing knowledge and experience with each other and from facing the challenges as a joint task. Since 2013, a group of corpus projects from France, Germany, bItaly and the Netherlands has started to exchange expertise and experience in building CMC corpora (= the network "Building and annotating CMC corpora", https://wiki.itmc.tu-dortmund.de/cmc/) and to jointly work on a proposal for an extension to the TEI standard which is adapted to the particularities of a broad range of CMC genres (= the TEI special interest group on CMC, http://www.tei-c.org/Activities/SIG/). The DARIAH technical meeting will gather a restricted number of researchers, coming from different European countries, involved in projects aiming at building, structuring, annotating and analyzing CMC corpora - including:

*''CoMeRe'': Project for a corpus of French CMC: http://comere.org
*''Dortmund Chat Corpus'': http://www.chatkorpus.tu-dortmund.de
*''DeRiK'': project for a reference corpus of German CMC: http://www.tinyurl.com/derik-llc
*''Web2CorpusIT'': Pilot Corpus of Italian Computer-Mediated communication: http://www.glottoweb.org/web2corpus/
*''Wikipedia corpora in DeReKo'' / IDS Mannheim: http://www.ids-mannheim.de/dereko
*''KobRA'': Corpus-based linguistic analysis with the help of data mining: http://www.kobra.tu-dortmund.de
The expected outcomes of the meeting are, amongst others:
*an advanced proposal for representing CMC genres in TEI (which subsequently shall be presented as a proposal to the TEI community in 2015);
*a first exchange about experience in automatically structuring and processing CMC data as well as a concept for a common platform (to be set up in 2015) for the documentation and exchange of NLP tools and annotation experiments with other projects and research groups interested in building CMC corpora in different languages;
* plans for international scientific events (extended workshops, conferences) based on these topics in 2015/16.

==PROGRAM (preliminary)==

*Wed, September 17, 2014: '''Short intro/presentation''' (3-5 mins) on the work of our community
*Thu, September 18, 2014: '''Community meeting''' (3 hours).

===Pt. I: Presentations (Thu 15:00-17:00)===

* Harald Lüngen & Eliza Margareta (IDS Mannheim): '''Applying the TEI CMC SIG proposal to Wikipedia corpora'''
* Thierry Chanier (UBP Clermont): '''End of phase 1 of the CoMeRe project: application of the Interaction Space (TEI-CMC) model to various CMC corpora in French'''
* Michael Beißwenger & Christian Pölitz (TU Dortmund): '''Analyzing CMC corpora using Machine Learning methods: report from the KobRA project'''
* Benoit Sagot (Alpage/CNRS & INRIA): '''Application of a general POS tagger for corpora in French to the CoMeRe-CMC corpora'''
* Michael Beißwenger (TU Dortmund): '''Shared task on linguistic annotation of German CMC: intermediate report from the preparation of ''EmpiriST2015'''''

===Pt. II: Round table: further work on standards and joint scientific activities (Thu 17:00-18:00)===

* Discussion of the current draft schema from the perspective of different projects and initiatives; ideas for annotations on the microlevel (= inner structure of postings) and about the interface between POS annotations and the microstructure in the TEI schema
* schedule for extending the standards (e.g., the next step in the TEI-CMC SIG)
* plans for scientific events in 2015-16 focused on annotations, NLP4CMC, work on wikipedia & other genres
* platform for the documentation and exchange of NLP tools and annotation experiments?
</big>
</td>
</tr>
</table>

SIG:CMC/Technical Meeting on CMC at DARIAH VCC 2014

2014-06-13T06:56:33Z

Thierry CHANIER: /* Technical meeting pt. I: Current state of building & modeling corpora (1,5 hrs) */

<table width="90%" border="0" align="center">
<tr>
<td>
<big>
This pages describes a proposal and tentative program for a technical meeting on issues related with the modeling of CMC corpora submitted by members of the CMC-SIG for the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th DARIAH-EU VCC meeting 2014] in Rome. '''The content of this page is preliminary and tentative.'''

Main page of the CMC-SIG in this wiki: [[SIG:Computer-Mediated Communication]]

= PROPOSAL =

Proposal for a technical meeting on the topic

'''Models and tools for structuring & annotating corpora of social media / computer-mediated communication'''

to be held during the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th General Virtual Competency Centre (VCC) meeting of DARIAH-EU], Rome, 17-19 September 2014
----
Corpora of ''computer-mediated communication'' (''CMC'') are a desideratum for many scholars in the Humanities who are interested in doing empirical research of language use and of emerging communicative genres on the Internet and in social media applications. Important steps for building such corpora and for representing them in an interoperable way are

*to create models for the representation of CMC (including text-only as well as multimodal genres) which comply with a standard or de-facto standard in the field of Humanities;
*to adapt tools for boilerplate removal and natural language processing to the structural and linguistic peculiarities of these genres (e.g., tools for converting raw CMC data into a standard format; tools for linguistic processing such as tokenizers, POS taggers, parsers etc.).

Researchers at a European level are already aware that many of the challenges in building CMC corpora in the Humanities are the same for every language; therefore CMC corpus projects for different languages can benefit from sharing knowledge and experiences with each other and from facing the challenges as a joint task. Since 2013, a group of corpus projects from France, Germany, Italy and the Netherlands has started to exchange expertise and experiences in building CMC corpora (= the network "Buildng and annotating CMC corpora", https://wiki.itmc.tu-dortmund.de/cmc/) and to jointly work on a proposal for an extension to the TEI standard which is adapted to the particularities of a broad range of CMC genres (= the TEI special interest group on CMC, http://www.tei-c.org/Activities/SIG/). The DARIAH technical meeting will gather a restricted number a researchers, coming from different European countries, involved in projects aiming at building, structuring, annotating and analyzing CMC corpora – including:

*CoMeRe: Project for a corpus of French CMC: http://comere.org
*Dortmund Chat Corpus: http://www.chatkorpus.tu-dortmund.de
*DeRiK: project for a reference corpus of German CMC: http://www.tinyurl.com/derik-llc
*SoNaR ?
*Web2CorpusIT, Pilot Corpus of Italian Computer-Mediated Communication: http://www.glottoweb.org/web2corpus/
*Wikipedia corpora in DeReKo / IDS Mannheim: http://www.ids-mannheim.de/dereko
*KobRA: Corpus-based linguistic analysis with the help of data mining: http://www.kobra.tu-dortmund.de

The expected outcomes of the meeting are, amongst other:

*an advanced proposal for representing CMC genres in TEI (which subsequently shall be presented as a proposal to the TEI community in 2015);
*a first exchange about experiences in automatically structuring and processing CMC data and a concept for a common platform (to be set up in 2015) for the documentation and exchange of NLP tools and annotation experiments with other projects and research groups interested in building CMC corpora in different languages;
*plans for international scientific events (extended workshops, conferences) around these topics in 2015/16.
 
=TENTATIVE SCHEDULE / PROGRAM=

*September 17, 2014: '''short intro/presentation''' (3-5 mins) on the work of our community
*September 18, 2014: '''technical meeting''' (1,5 + 1,5 + 2 hours).

'''Precise times for the meeting and presentations will be fixed after DARIAH has decided about the proposal. All titles given below are working titles.'''

'''Please everbody add preliminary titles for your contributions'''
(contributions marked as ''[confirmed]'' have been confirmed by the authors)

==Technical meeting pt. I: Current state of building & modeling corpora (1,5 hrs)==

* [confirmed] Harald Lüngen & Eliza Margareta (IDS Mannheim): Applying the TEI CMC SIG proposal to Wikipedia corpora
* [confirmed] Thierry Chanier (UBP Clermont): End of phase 1 of the CoMeRe project : application of the Interaction Space (TEI-CMC) model to various CMC corpora in French.
* ? A presentation by Isabella and/or Isabella and Axel ?
* ? discussion of the current draft schema from the perspective of different projects (DeRiK, SoNaR, Web2CorpusIT, ...)? Ideas about annotations on the microlevel (= inner structure of postings) and about the interface between POS annotations and the microstructure in the TEI schema?

==Technical meeting pt. II: NLP for CMC / social media corpora (1,5 hrs)==

* [confirmed] Michael Beißwenger & Christian Pölitz (TU Dortmund): Adapting machine learning methods for the analysis and annotation of CMC corpora: report from the KobRA project
* [to be confirmed] Application of a general POS tagger for corpora in French to the CoMeRe-CMC corpora.
* ? N.N. (members of the [http://www.empirikom.net Empirikom network]): Preparing a shared task on linguistic annotation of German CMC and web corpora (EmpiriST 2015)
* ? N.N.

==Technical meeting pt. III: schedule for further work on standards and joint scientific activities (2 hrs)==

* schedule for extending the standards (e.g., the next step in the TEI-CMC SIG)
* plans for scientific events in 2015-16 focused on annotations, NLP4CMC, work on wikipedia & other genres
* platform for the documentation and exchange of NLP tools and annotation experiments?
</big>
</td>
</tr>
</table>

SIG:CMC/Technical Meeting on CMC at DARIAH VCC 2014

2014-06-13T06:55:38Z

Thierry CHANIER: /* Technical meeting pt. II: NLP for CMC / social media corpora (1,5 hrs) */

<table width="90%" border="0" align="center">
<tr>
<td>
<big>
This pages describes a proposal and tentative program for a technical meeting on issues related with the modeling of CMC corpora submitted by members of the CMC-SIG for the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th DARIAH-EU VCC meeting 2014] in Rome. '''The content of this page is preliminary and tentative.'''

Main page of the CMC-SIG in this wiki: [[SIG:Computer-Mediated Communication]]

= PROPOSAL =

Proposal for a technical meeting on the topic

'''Models and tools for structuring & annotating corpora of social media / computer-mediated communication'''

to be held during the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th General Virtual Competency Centre (VCC) meeting of DARIAH-EU], Rome, 17-19 September 2014
----
Corpora of ''computer-mediated communication'' (''CMC'') are a desideratum for many scholars in the Humanities who are interested in doing empirical research of language use and of emerging communicative genres on the Internet and in social media applications. Important steps for building such corpora and for representing them in an interoperable way are

*to create models for the representation of CMC (including text-only as well as multimodal genres) which comply with a standard or de-facto standard in the field of Humanities;
*to adapt tools for boilerplate removal and natural language processing to the structural and linguistic peculiarities of these genres (e.g., tools for converting raw CMC data into a standard format; tools for linguistic processing such as tokenizers, POS taggers, parsers etc.).

Researchers at a European level are already aware that many of the challenges in building CMC corpora in the Humanities are the same for every language; therefore CMC corpus projects for different languages can benefit from sharing knowledge and experiences with each other and from facing the challenges as a joint task. Since 2013, a group of corpus projects from France, Germany, Italy and the Netherlands has started to exchange expertise and experiences in building CMC corpora (= the network "Buildng and annotating CMC corpora", https://wiki.itmc.tu-dortmund.de/cmc/) and to jointly work on a proposal for an extension to the TEI standard which is adapted to the particularities of a broad range of CMC genres (= the TEI special interest group on CMC, http://www.tei-c.org/Activities/SIG/). The DARIAH technical meeting will gather a restricted number a researchers, coming from different European countries, involved in projects aiming at building, structuring, annotating and analyzing CMC corpora – including:

*CoMeRe: Project for a corpus of French CMC: http://comere.org
*Dortmund Chat Corpus: http://www.chatkorpus.tu-dortmund.de
*DeRiK: project for a reference corpus of German CMC: http://www.tinyurl.com/derik-llc
*SoNaR ?
*Web2CorpusIT, Pilot Corpus of Italian Computer-Mediated Communication: http://www.glottoweb.org/web2corpus/
*Wikipedia corpora in DeReKo / IDS Mannheim: http://www.ids-mannheim.de/dereko
*KobRA: Corpus-based linguistic analysis with the help of data mining: http://www.kobra.tu-dortmund.de

The expected outcomes of the meeting are, amongst other:

*an advanced proposal for representing CMC genres in TEI (which subsequently shall be presented as a proposal to the TEI community in 2015);
*a first exchange about experiences in automatically structuring and processing CMC data and a concept for a common platform (to be set up in 2015) for the documentation and exchange of NLP tools and annotation experiments with other projects and research groups interested in building CMC corpora in different languages;
*plans for international scientific events (extended workshops, conferences) around these topics in 2015/16.
 
=TENTATIVE SCHEDULE / PROGRAM=

*September 17, 2014: '''short intro/presentation''' (3-5 mins) on the work of our community
*September 18, 2014: '''technical meeting''' (1,5 + 1,5 + 2 hours).

'''Precise times for the meeting and presentations will be fixed after DARIAH has decided about the proposal. All titles given below are working titles.'''

'''Please everbody add preliminary titles for your contributions'''
(contributions marked as ''[confirmed]'' have been confirmed by the authors)

==Technical meeting pt. I: Current state of building & modeling corpora (1,5 hrs)==

* [confirmed] Harald Lüngen & Eliza Margareta (IDS Mannheim): Applying the TEI CMC SIG proposal to Wikipedia corpora
* Thierry Chanier (UBP Clermont): End of phase 1 of the CoMeRe project : application of the Interaction Space (TEI-CMC) model to various CMC corpora in French.
* ? A presentation by Isabella and/or Isabella and Axel ?
* ? discussion of the current draft schema from the perspective of different projects (DeRiK, SoNaR, Web2CorpusIT, ...)? Ideas about annotations on the microlevel (= inner structure of postings) and about the interface between POS annotations and the microstructure in the TEI schema?

==Technical meeting pt. II: NLP for CMC / social media corpora (1,5 hrs)==

* [confirmed] Michael Beißwenger & Christian Pölitz (TU Dortmund): Adapting machine learning methods for the analysis and annotation of CMC corpora: report from the KobRA project
* [to be confirmed] Application of a general POS tagger for corpora in French to the CoMeRe-CMC corpora.
* ? N.N. (members of the [http://www.empirikom.net Empirikom network]): Preparing a shared task on linguistic annotation of German CMC and web corpora (EmpiriST 2015)
* ? N.N.

==Technical meeting pt. III: schedule for further work on standards and joint scientific activities (2 hrs)==

* schedule for extending the standards (e.g., the next step in the TEI-CMC SIG)
* plans for scientific events in 2015-16 focused on annotations, NLP4CMC, work on wikipedia & other genres
* platform for the documentation and exchange of NLP tools and annotation experiments?
</big>
</td>
</tr>
</table>

SIG:CMC/Technical Meeting on CMC at DARIAH VCC 2014

2014-06-13T06:53:10Z

Thierry CHANIER: /* Technical meeting pt. I: Current state of building & modeling corpora (1,5 hrs) */

<table width="90%" border="0" align="center">
<tr>
<td>
<big>
This pages describes a proposal and tentative program for a technical meeting on issues related with the modeling of CMC corpora submitted by members of the CMC-SIG for the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th DARIAH-EU VCC meeting 2014] in Rome. '''The content of this page is preliminary and tentative.'''

Main page of the CMC-SIG in this wiki: [[SIG:Computer-Mediated Communication]]

= PROPOSAL =

Proposal for a technical meeting on the topic

'''Models and tools for structuring & annotating corpora of social media / computer-mediated communication'''

to be held during the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th General Virtual Competency Centre (VCC) meeting of DARIAH-EU], Rome, 17-19 September 2014
----
Corpora of ''computer-mediated communication'' (''CMC'') are a desideratum for many scholars in the Humanities who are interested in doing empirical research of language use and of emerging communicative genres on the Internet and in social media applications. Important steps for building such corpora and for representing them in an interoperable way are

*to create models for the representation of CMC (including text-only as well as multimodal genres) which comply with a standard or de-facto standard in the field of Humanities;
*to adapt tools for boilerplate removal and natural language processing to the structural and linguistic peculiarities of these genres (e.g., tools for converting raw CMC data into a standard format; tools for linguistic processing such as tokenizers, POS taggers, parsers etc.).

Researchers at a European level are already aware that many of the challenges in building CMC corpora in the Humanities are the same for every language; therefore CMC corpus projects for different languages can benefit from sharing knowledge and experiences with each other and from facing the challenges as a joint task. Since 2013, a group of corpus projects from France, Germany, Italy and the Netherlands has started to exchange expertise and experiences in building CMC corpora (= the network "Buildng and annotating CMC corpora", https://wiki.itmc.tu-dortmund.de/cmc/) and to jointly work on a proposal for an extension to the TEI standard which is adapted to the particularities of a broad range of CMC genres (= the TEI special interest group on CMC, http://www.tei-c.org/Activities/SIG/). The DARIAH technical meeting will gather a restricted number a researchers, coming from different European countries, involved in projects aiming at building, structuring, annotating and analyzing CMC corpora – including:

*CoMeRe: Project for a corpus of French CMC: http://comere.org
*Dortmund Chat Corpus: http://www.chatkorpus.tu-dortmund.de
*DeRiK: project for a reference corpus of German CMC: http://www.tinyurl.com/derik-llc
*SoNaR ?
*Web2CorpusIT, Pilot Corpus of Italian Computer-Mediated Communication: http://www.glottoweb.org/web2corpus/
*Wikipedia corpora in DeReKo / IDS Mannheim: http://www.ids-mannheim.de/dereko
*KobRA: Corpus-based linguistic analysis with the help of data mining: http://www.kobra.tu-dortmund.de

The expected outcomes of the meeting are, amongst other:

*an advanced proposal for representing CMC genres in TEI (which subsequently shall be presented as a proposal to the TEI community in 2015);
*a first exchange about experiences in automatically structuring and processing CMC data and a concept for a common platform (to be set up in 2015) for the documentation and exchange of NLP tools and annotation experiments with other projects and research groups interested in building CMC corpora in different languages;
*plans for international scientific events (extended workshops, conferences) around these topics in 2015/16.
 
=TENTATIVE SCHEDULE / PROGRAM=

*September 17, 2014: '''short intro/presentation''' (3-5 mins) on the work of our community
*September 18, 2014: '''technical meeting''' (1,5 + 1,5 + 2 hours).

'''Precise times for the meeting and presentations will be fixed after DARIAH has decided about the proposal. All titles given below are working titles.'''

'''Please everbody add preliminary titles for your contributions'''
(contributions marked as ''[confirmed]'' have been confirmed by the authors)

==Technical meeting pt. I: Current state of building & modeling corpora (1,5 hrs)==

* [confirmed] Harald Lüngen & Eliza Margareta (IDS Mannheim): Applying the TEI CMC SIG proposal to Wikipedia corpora
* Thierry Chanier (UBP Clermont): End of phase 1 of the CoMeRe project : application of the Interaction Space (TEI-CMC) model to various CMC corpora in French.
* ? A presentation by Isabella and/or Isabella and Axel ?
* ? discussion of the current draft schema from the perspective of different projects (DeRiK, SoNaR, Web2CorpusIT, ...)? Ideas about annotations on the microlevel (= inner structure of postings) and about the interface between POS annotations and the microstructure in the TEI schema?

==Technical meeting pt. II: NLP for CMC / social media corpora (1,5 hrs)==

* [confirmed] Michael Beißwenger & Christian Pölitz (TU Dortmund): Adapting machine learning methods for the analysis and annotation of CMC corpora: report from the KobRA project
* ? a presentation by someone who's dealing with "NLP4CMC" issues in the French community?
* ? N.N. (members of the [http://www.empirikom.net Empirikom network]): Preparing a shared task on linguistic annotation of German CMC and web corpora (EmpiriST 2015)
* ? N.N.

==Technical meeting pt. III: schedule for further work on standards and joint scientific activities (2 hrs)==

* schedule for extending the standards (e.g., the next step in the TEI-CMC SIG)
* plans for scientific events in 2015-16 focused on annotations, NLP4CMC, work on wikipedia & other genres
* platform for the documentation and exchange of NLP tools and annotation experiments?
</big>
</td>
</tr>
</table>

SIG:CMC/Technical Meeting on CMC at DARIAH VCC 2014

2014-06-13T06:52:48Z

Thierry CHANIER: /* Technical meeting pt. I: Current state of building & modeling corpora (1,5 hrs) */

<table width="90%" border="0" align="center">
<tr>
<td>
<big>
This pages describes a proposal and tentative program for a technical meeting on issues related with the modeling of CMC corpora submitted by members of the CMC-SIG for the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th DARIAH-EU VCC meeting 2014] in Rome. '''The content of this page is preliminary and tentative.'''

Main page of the CMC-SIG in this wiki: [[SIG:Computer-Mediated Communication]]

= PROPOSAL =

Proposal for a technical meeting on the topic

'''Models and tools for structuring & annotating corpora of social media / computer-mediated communication'''

to be held during the [http://www.dariah.eu/activities/general-vcc-meetings/4th-general-vcc-meeting.html 4th General Virtual Competency Centre (VCC) meeting of DARIAH-EU], Rome, 17-19 September 2014
----
Corpora of ''computer-mediated communication'' (''CMC'') are a desideratum for many scholars in the Humanities who are interested in doing empirical research of language use and of emerging communicative genres on the Internet and in social media applications. Important steps for building such corpora and for representing them in an interoperable way are

*to create models for the representation of CMC (including text-only as well as multimodal genres) which comply with a standard or de-facto standard in the field of Humanities;
*to adapt tools for boilerplate removal and natural language processing to the structural and linguistic peculiarities of these genres (e.g., tools for converting raw CMC data into a standard format; tools for linguistic processing such as tokenizers, POS taggers, parsers etc.).

Researchers at a European level are already aware that many of the challenges in building CMC corpora in the Humanities are the same for every language; therefore CMC corpus projects for different languages can benefit from sharing knowledge and experiences with each other and from facing the challenges as a joint task. Since 2013, a group of corpus projects from France, Germany, Italy and the Netherlands has started to exchange expertise and experiences in building CMC corpora (= the network "Buildng and annotating CMC corpora", https://wiki.itmc.tu-dortmund.de/cmc/) and to jointly work on a proposal for an extension to the TEI standard which is adapted to the particularities of a broad range of CMC genres (= the TEI special interest group on CMC, http://www.tei-c.org/Activities/SIG/). The DARIAH technical meeting will gather a restricted number a researchers, coming from different European countries, involved in projects aiming at building, structuring, annotating and analyzing CMC corpora – including:

*CoMeRe: Project for a corpus of French CMC: http://comere.org
*Dortmund Chat Corpus: http://www.chatkorpus.tu-dortmund.de
*DeRiK: project for a reference corpus of German CMC: http://www.tinyurl.com/derik-llc
*SoNaR ?
*Web2CorpusIT, Pilot Corpus of Italian Computer-Mediated Communication: http://www.glottoweb.org/web2corpus/
*Wikipedia corpora in DeReKo / IDS Mannheim: http://www.ids-mannheim.de/dereko
*KobRA: Corpus-based linguistic analysis with the help of data mining: http://www.kobra.tu-dortmund.de

The expected outcomes of the meeting are, amongst other:

*an advanced proposal for representing CMC genres in TEI (which subsequently shall be presented as a proposal to the TEI community in 2015);
*a first exchange about experiences in automatically structuring and processing CMC data and a concept for a common platform (to be set up in 2015) for the documentation and exchange of NLP tools and annotation experiments with other projects and research groups interested in building CMC corpora in different languages;
*plans for international scientific events (extended workshops, conferences) around these topics in 2015/16.
 
=TENTATIVE SCHEDULE / PROGRAM=

*September 17, 2014: '''short intro/presentation''' (3-5 mins) on the work of our community
*September 18, 2014: '''technical meeting''' (1,5 + 1,5 + 2 hours).

'''Precise times for the meeting and presentations will be fixed after DARIAH has decided about the proposal. All titles given below are working titles.'''

'''Please everbody add preliminary titles for your contributions'''
(contributions marked as ''[confirmed]'' have been confirmed by the authors)

==Technical meeting pt. I: Current state of building & modeling corpora (1,5 hrs)==

* [confirmed] Harald Lüngen & Eliza Margareta (IDS Mannheim): Applying the TEI CMC SIG proposal to Wikipedia corpora
* Thierry Chanier (UBP Clermon)t: End of phase 1 of the CoMeRe project : application of the Interaction Space (TEI-CMC) model to various CMC corpora in French.
* ? A presentation by Isabella and/or Isabella and Axel ?
* ? discussion of the current draft schema from the perspective of different projects (DeRiK, SoNaR, Web2CorpusIT, ...)? Ideas about annotations on the microlevel (= inner structure of postings) and about the interface between POS annotations and the microstructure in the TEI schema?

==Technical meeting pt. II: NLP for CMC / social media corpora (1,5 hrs)==

* [confirmed] Michael Beißwenger & Christian Pölitz (TU Dortmund): Adapting machine learning methods for the analysis and annotation of CMC corpora: report from the KobRA project
* ? a presentation by someone who's dealing with "NLP4CMC" issues in the French community?
* ? N.N. (members of the [http://www.empirikom.net Empirikom network]): Preparing a shared task on linguistic annotation of German CMC and web corpora (EmpiriST 2015)
* ? N.N.

==Technical meeting pt. III: schedule for further work on standards and joint scientific activities (2 hrs)==

* schedule for extending the standards (e.g., the next step in the TEI-CMC SIG)
* plans for scientific events in 2015-16 focused on annotations, NLP4CMC, work on wikipedia & other genres
* platform for the documentation and exchange of NLP tools and annotation experiments?
</big>
</td>
</tr>
</table>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2014-04-15T10:05:56Z

Thierry CHANIER: /* Tweets */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example for Tweets]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><adressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

==References and notes==
<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2014-04-15T10:05:09Z

Thierry CHANIER: /* Email */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>
===Tweets===
See [[#Example]]

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><adressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

==References and notes==
<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2014-04-15T10:00:25Z

Thierry CHANIER: /* POS tagging and interactionTerm */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><adressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

==References and notes==
<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2014-04-15T09:59:59Z

Thierry CHANIER: /* Example for Tweets */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><adressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure <nowiki><fs></nowiki>.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

===POS tagging and interactionTerm===
In this section we would like to comment / discuss our previous proposals (table 3, figure 5) related to elements and attributes corresponding to interactionTerms, when facing the task of automatically annotating CMC interactions (POS - Part Of Speech- tags). This comments come from the CoMeRe project which currently undertakes this task.

Attributes listed in table 3 with their values may be extensively used when doing hand annotations. But during an automatic process the transformation into TEI may be simplified in order to reduce the management of graphic variations, for example on interactionWord. Example (10) display in (a) an SMS and in (b) part of the output after processing (once the lexicon has been extended, interactionTerms may also received a @lemma information).

<pre>
(10)
(a)
c vré c les kangourous ki saute banane de Wizou va mdrrrrrrrr bébé :)

(b)
[…] <interactionWord><w ana="#INTERJEC">mdrrrrrrrr</w></interactionWord>
<w ana="#N" lemma="bébé">bébé</w><emoticon><w ana="#INTERJEC">:)</w></emoticon>

(c)
mé Wizou kestu fous ici toi ofait ?

</pre>

Finding addressees may also be difficult because in many CMC environments there is no actual constraint on using addressing markers (more particularly the "@", as shown in another SMS exchange (10.c) where 'Wizou' is the addressee).
But, when considering tweets, it is mandatory to use addressing markers and the Tweet syntax may have to be tagged more explicitly (hashtag, retweet, reference to Twitter account, quotes from a Twitter account, etc.). In (11) a, b and c are examples taken from ''cmr-polititweets-tei-v1''. (11) d, e, f respectively give some foreseen outputs coming from the automatic processing. We here used the existing <nowiki><rs></nowiki> TEI element. Note that in the <nowiki><addresse></nowiki> element, we have not used @who, which must refer to the ID of a participant listed in the <nowiki><teiHeader></nowiki>. Instead of, we used the @ref attribute which value contains the ID given by Twitter.
<pre>(11)
(a) Déjeuner de travail avec @claudebartolone a l'Assemblee Nationale a l'ordre du jour le rôle de la Caisse des dépôt a la SNCM

(b) RT @AvecMennucci: L'équipe #Mennucci en marche! http://t.co/pBtgU1CrJN

(c) RT @marcelvayre: Oh peuchere...L'illusion Gaudin via @Marianne2fr #Marseille #Marseille2014 #Mennucci http://t.co/jYtSTW1gPn

(d)<rs type="twitter-account">
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker>
<addressee ref="IDtwitter"><w ana="#NP>claudebartolone</w></addressee></adressingTerm></rs>

(e)<rs type="twitter-retweet"><w ana="#??>RT</w>
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker>
<addressee ref="IDtwitter"><w ana="#NP>AvecMennucci</w></addressee></adressingTerm><w ana="PONCT">:</w></rs>
<w ana="#DET lemma="la">l</w> <w ana"#N" lemma="équipe">équipe</w> […]

(f)[…] <w ana="#PN">Gaudin</w> <rs type="twitter-ref-account"><w ana="#PREP>via</w>
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker><addressee ref="IDtwitter"><w ana="#NP>Marianne2fr</w></addressee>
</adressingTerm></rs>
<rs type="twitter-hashtag"><w ana="#??">#Marseille</w></rs></pre>

==References and notes==
<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2014-04-15T09:59:30Z

Thierry CHANIER: /* Example for Tweets */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><adressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker. When the twitter-account is described into the list of persons in the <nowiki><teiheader></nowiki> then its ID in the value of @ref, otherwise it is its URL page.

Note other features specific to tweets which are encoded into the <nowiki><trailer></nowiki> as a feature structure.

<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

===POS tagging and interactionTerm===
In this section we would like to comment / discuss our previous proposals (table 3, figure 5) related to elements and attributes corresponding to interactionTerms, when facing the task of automatically annotating CMC interactions (POS - Part Of Speech- tags). This comments come from the CoMeRe project which currently undertakes this task.

Attributes listed in table 3 with their values may be extensively used when doing hand annotations. But during an automatic process the transformation into TEI may be simplified in order to reduce the management of graphic variations, for example on interactionWord. Example (10) display in (a) an SMS and in (b) part of the output after processing (once the lexicon has been extended, interactionTerms may also received a @lemma information).

<pre>
(10)
(a)
c vré c les kangourous ki saute banane de Wizou va mdrrrrrrrr bébé :)

(b)
[…] <interactionWord><w ana="#INTERJEC">mdrrrrrrrr</w></interactionWord>
<w ana="#N" lemma="bébé">bébé</w><emoticon><w ana="#INTERJEC">:)</w></emoticon>

(c)
mé Wizou kestu fous ici toi ofait ?

</pre>

Finding addressees may also be difficult because in many CMC environments there is no actual constraint on using addressing markers (more particularly the "@", as shown in another SMS exchange (10.c) where 'Wizou' is the addressee).
But, when considering tweets, it is mandatory to use addressing markers and the Tweet syntax may have to be tagged more explicitly (hashtag, retweet, reference to Twitter account, quotes from a Twitter account, etc.). In (11) a, b and c are examples taken from ''cmr-polititweets-tei-v1''. (11) d, e, f respectively give some foreseen outputs coming from the automatic processing. We here used the existing <nowiki><rs></nowiki> TEI element. Note that in the <nowiki><addresse></nowiki> element, we have not used @who, which must refer to the ID of a participant listed in the <nowiki><teiHeader></nowiki>. Instead of, we used the @ref attribute which value contains the ID given by Twitter.
<pre>(11)
(a) Déjeuner de travail avec @claudebartolone a l'Assemblee Nationale a l'ordre du jour le rôle de la Caisse des dépôt a la SNCM

(b) RT @AvecMennucci: L'équipe #Mennucci en marche! http://t.co/pBtgU1CrJN

(c) RT @marcelvayre: Oh peuchere...L'illusion Gaudin via @Marianne2fr #Marseille #Marseille2014 #Mennucci http://t.co/jYtSTW1gPn

(d)<rs type="twitter-account">
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker>
<addressee ref="IDtwitter"><w ana="#NP>claudebartolone</w></addressee></adressingTerm></rs>

(e)<rs type="twitter-retweet"><w ana="#??>RT</w>
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker>
<addressee ref="IDtwitter"><w ana="#NP>AvecMennucci</w></addressee></adressingTerm><w ana="PONCT">:</w></rs>
<w ana="#DET lemma="la">l</w> <w ana"#N" lemma="équipe">équipe</w> […]

(f)[…] <w ana="#PN">Gaudin</w> <rs type="twitter-ref-account"><w ana="#PREP>via</w>
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker><addressee ref="IDtwitter"><w ana="#NP>Marianne2fr</w></addressee>
</adressingTerm></rs>
<rs type="twitter-hashtag"><w ana="#??">#Marseille</w></rs></pre>

==References and notes==
<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2014-04-15T09:55:32Z

Thierry CHANIER: /* Example for Tweets */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><adressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker.

Note other features specific to tweets:
<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</addressingTerm> : </distinct> A 07h50,
<addressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</addressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<addressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</addressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

===POS tagging and interactionTerm===
In this section we would like to comment / discuss our previous proposals (table 3, figure 5) related to elements and attributes corresponding to interactionTerms, when facing the task of automatically annotating CMC interactions (POS - Part Of Speech- tags). This comments come from the CoMeRe project which currently undertakes this task.

Attributes listed in table 3 with their values may be extensively used when doing hand annotations. But during an automatic process the transformation into TEI may be simplified in order to reduce the management of graphic variations, for example on interactionWord. Example (10) display in (a) an SMS and in (b) part of the output after processing (once the lexicon has been extended, interactionTerms may also received a @lemma information).

<pre>
(10)
(a)
c vré c les kangourous ki saute banane de Wizou va mdrrrrrrrr bébé :)

(b)
[…] <interactionWord><w ana="#INTERJEC">mdrrrrrrrr</w></interactionWord>
<w ana="#N" lemma="bébé">bébé</w><emoticon><w ana="#INTERJEC">:)</w></emoticon>

(c)
mé Wizou kestu fous ici toi ofait ?

</pre>

Finding addressees may also be difficult because in many CMC environments there is no actual constraint on using addressing markers (more particularly the "@", as shown in another SMS exchange (10.c) where 'Wizou' is the addressee).
But, when considering tweets, it is mandatory to use addressing markers and the Tweet syntax may have to be tagged more explicitly (hashtag, retweet, reference to Twitter account, quotes from a Twitter account, etc.). In (11) a, b and c are examples taken from ''cmr-polititweets-tei-v1''. (11) d, e, f respectively give some foreseen outputs coming from the automatic processing. We here used the existing <nowiki><rs></nowiki> TEI element. Note that in the <nowiki><addresse></nowiki> element, we have not used @who, which must refer to the ID of a participant listed in the <nowiki><teiHeader></nowiki>. Instead of, we used the @ref attribute which value contains the ID given by Twitter.
<pre>(11)
(a) Déjeuner de travail avec @claudebartolone a l'Assemblee Nationale a l'ordre du jour le rôle de la Caisse des dépôt a la SNCM

(b) RT @AvecMennucci: L'équipe #Mennucci en marche! http://t.co/pBtgU1CrJN

(c) RT @marcelvayre: Oh peuchere...L'illusion Gaudin via @Marianne2fr #Marseille #Marseille2014 #Mennucci http://t.co/jYtSTW1gPn

(d)<rs type="twitter-account">
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker>
<addressee ref="IDtwitter"><w ana="#NP>claudebartolone</w></addressee></adressingTerm></rs>

(e)<rs type="twitter-retweet"><w ana="#??>RT</w>
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker>
<addressee ref="IDtwitter"><w ana="#NP>AvecMennucci</w></addressee></adressingTerm><w ana="PONCT">:</w></rs>
<w ana="#DET lemma="la">l</w> <w ana"#N" lemma="équipe">équipe</w> […]

(f)[…] <w ana="#PN">Gaudin</w> <rs type="twitter-ref-account"><w ana="#PREP>via</w>
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker><addressee ref="IDtwitter"><w ana="#NP>Marianne2fr</w></addressee>
</adressingTerm></rs>
<rs type="twitter-hashtag"><w ana="#??">#Marseille</w></rs></pre>

==References and notes==
<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>

SIG:CMC/CoMeRe schema draft for representing CMC in TEI (2014)

2014-04-15T09:54:04Z

Thierry CHANIER: /* Example for Tweets */

__FORCETOC__

==Status of this draft==
This page describes a draft for a '''basic schema for representing genres on computer-mediated communication (CMC) in TEI'''. The draft has been created by members of the [[SIG:Computer-Mediated Communication|TEI-SIG "Computer-Mediated Communication"]] where members are developping databank of CMC corpora encoded into TEI in various European langues (e.g. <ref name="Derik"/> <ref name="comere"/>).

The SIG encourages everybody to discuss this draft and give their feedback/comments using the "discussion" function on top of this page. The comments/discussions will be carefully taken into consideration in the further development of the schema.

The history of the draft is documented on the '''[[SIG:Computer-Mediated Communication|main wiki page of the SIG]]'''.
This page should be read in parallel to [[SIG:CMC/Draft: A metadata schema for CMC]]

'''Authors of this draft:''' Thierry Chanier, N.N., N.N.

==Interaction types ==
'''Figure 1:''' Interaction Space and multimodal interactions
[[File:interaction_type.jpg|400px|thumb|left]]
===Interaction===
Participants are in the same [[SIG:CMC/Draft: A metadata schema for CMC|interaction space]] (IS) when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices,(microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices, mainly producing visual or oral signals. (These however, will not be described in this article). Hence when participants cannot hear nor see the other participants’ actions, they are not in the same IS. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early.

In an IS, actions occur between participants. Let us call the trace of an action within an environment and one particular modality an “act”. Acts are generated by participants, and sometimes by the system. Some of them may be considered as directly communicative (verbal ones in synchronous text or oral modalities). Others may not be directly communicative but may represent the cause of communicative reaction / interaction (e.g. when participants write collaboratively in an online word processor and comment on their work). Participants see and hear what others are doing. These actions may represent the rationale for participants to be there and to interact (produce something collectively). Hence the distinction between acts, directly communicative or not, is irrelevant.

An important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In the next section, we start presenting some examples of mono modality environments where actions occur en bloc (Beisswenger et al., 2012)<ref name="Beißwenger"/>. A more complicated case appears when an IS uses several modalities. We will also find an example in this article.

Within other multimodal environments verbal (speech, text chat) and nonverbal acts occur simultaneously. The main purpose of transcriptions is then to describe inter-relations amongst acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on other specific acts occurring at the same time (see Wigham & Chanier, 2013)<ref name="WighamRecall"/><ref name="WighamCall"/><ref name="ChanierAlsic"/><ref name="Ciekanski"/>. Indeed, written communication can be simultaneously combined with other modalities. For example, there are situations where a participant does not plan an utterance as a one-shot process before it is sent as an en bloc message to a server, which in turn displays it to the other participants as an non modifiable piece of language (e.g. as a text chat turn). Undeniably, an utterance can also be planned, then modified in the throes of the interaction while taking into account what is happening in other modalities of communication (e.g. in an audio chat turn.
 
'''Table 1''': CMC environments and modalities
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
CMC environment
</td>
<td width=149 valign=middle style='width:89.5pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Mode & modality
</td>
<td width=111 valign=middle style='width:66.85pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
TEI element
</td>
<td width=206 valign=middle style='width:123.4pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Main macrostructure issues with TEI
</td>
<td width=163 valign=middle style='width:97.8pt;border:solid windowtext 1.0pt;
border-left:none;padding:0cm 5.4pt 0cm 5.4pt'>
Corpora presently under processing into TEI
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
No notion of addresse (in <head> ?)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
@alias, @type, @subtype
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Addresses, readers, copy, attached file, etc. (in
<head> or <trailer>)
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Tweet
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
microstructure
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion Forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Threads (opening, answering) : @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Wikipedia discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Reply difficult to identify (indent): @ref
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + image 
asynchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Message & comment : @ref 
set of images attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio conferencing system (e.g. Skype)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
Audio 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post> 

</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=774 colspan=5 valign=middle style='width:464.4pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Complex CMC environment
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
LMS (Learning Management System) : WebCT, Moodle 
email + textchat + discussion forum
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text 
asynchronous & synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
One TEIcorpus file 
one <text> per main interaction space IS (group) 
ne main <div> per IS subspaces and /or type of modality
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Audio-graphic conference system (e.g. Lyceum,
Centra)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Every element at the same level, i.e. mixing of
these elements within a <div> 
set of audio files attached to the TEI file ?
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=145 valign=middle style='width:86.85pt;border:solid windowtext 1.0pt;
border-top:none;padding:0cm 5.4pt 0cm 5.4pt'>
Video-graphic or 3D environment (e.g. : Second Life)
</td>
<td width=149 valign=middle style='width:89.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Text + audio + nonverbal 
synchronous
</td>
<td width=111 valign=middle style='width:66.85pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
<post>

<prod>
</td>
<td width=206 valign=middle style='width:123.4pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Idem + set of video files attached to the TEI file
</td>
<td width=163 valign=middle style='width:97.8pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Examples of macrostructures==

Accordingly to (Beiswenger et al., 2012)<ref name="Beißwenger"/>, we refer to macro-structure when considering the general information attached to an interaction (adresses, copy-to, title, label, readers, attached files, etc.) as well as issues dealing with way of arranging sets of interactions per modality or interaction space. The micro-structure of the text (next section) refers to the type of elements found in the actual contents of the interaction (<nowiki><post>, or <prod></nowiki>) for example interaction words, emoticons, hash code, etc.

Before assembling general proposals concerning <nowiki><post> and <prod></nowiki> and their attributes, let us consider some examples of CMC interactions.

=== Multimodal example===
From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment, 3 learners (English L2) working into a word processor: one writing, others helping.
* (1.2): collaborative word processor
* (1.3): audio, clarification
* (1.4): textchat, correction (with error)
* (1.5): textchat, request clarification

<pre>(1)
(1.2)<prod xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14481" xml:lang="unk"
start="#cmr-copeas-tl_t-w1979" end="#cmr-copeas-tl_t-w1987" who="#AT3"
type="text_doc"> (modify),paragraph (ad,For example:to have comparaison between
web sites, to know more criterias for a good site)</prod>
(1.3)euh + to
euh + to use the good euh + good euh vocabulary + I think euh + we euh + we wrote
euh for me I have euh +++ I've euh much progress in euh in use the good vocabulary
to euh + to evaluate euh a website
(1.4)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14483" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1990" who="#AT6" type="chat-message">
according to the differents criteria
</post>
(1.5)<post xml:id="cmr-copeas-T8_s101_ecriture_multimodale-a_14484" xml:lang="unk"
synch="#cmr-copeas-tl_t-w1991" who="#AT6" type="chat-message">
?</pre>

===Textchat===
From ''cmr-getalp_org-rhone-alpes-tei-v1''<ref name="comere"/>. Textchat turns correspond here, respectively, to :
* the first 3: messages
* 4: change alias
* 5: change rights

<pre>(2)
<post xml:id="cmr-get-c065-a21693" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Apres je vé faire ma physique c aussi les equation bilan</post>
<post xml:id="cmr-get-c065-a21694" when-iso="2004-03-18T14:09" who="#cmr-get-c065-p39174" alias="cortex_taff" type="chat-message">
Aujourd'hui c la journée equation</post>
<post xml:id="cmr-get-c065-a21697" when-iso="2004-03-18T14:11" who="#cmr-get-c065-p36208" alias="roulie" type="chat-message">
lol</post>
<post xml:id="cmr-get-c065-a21699" when-iso="2004-03-18T14:13" who="#cmr-get-c065-p120845" alias="Tsu" type="chat-event" subtype="changementpseudo">
Changement de pseudo: Tsu -&gt; Tsu[H<add><code>alias_change(Tsu,Tsu[H)</code></add></post>
<post xml:id="cmr-get-c065-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode">
#Rhone-alpes:changement de mode(s) '+o Mega-Link' par Hera!services@olympe.epiknet.org</post>
</pre>

===SMS===
From ''cmr-smslareunion-tei-v1''<ref name="comere"/>. Two SMS messages sent by the same person to the same addressee. Note that here the adresse is not explicitly encoded (phone numbers of adresses have not been collected, hence are not known, and there is no attribute in TEI to encode adresses (same problem with speech / oral chapter in TEI)

<pre>(3)
<post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmr-slr-c001-p010" type="sms">
é@??$?Le + triste c ke tu na aucune phraz agréabl et ke tu va encor me dir ke c moi ki Merde par mon attitu2!
Moi je deman2 pa mieu ke klke mot agréabl échangé
[…]
<post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms">
...2 te comporter comme ca avec moi. Je ve bien admettr mes erreur kan j'agi vraimen mal comm hier mé fo pa exagérer.
Si t pa d'accor c ton droi. Si tentain.le rest c à dirreposer dé question sur 1 sujet déjà expliké c pa 1 raison valabl pr
ke tu te monte contr moi.pr moi ossi ca suffi.
</pre>

===Discussion forum===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. The author of the message is a native speaker of French who is replying to a post made by a learner of French. Each person mentioned has been identified in the message structure (author, list of readers -here shortened-) and in its contents (addressee, signature of the author, attached file). This information may lead to other types of research on discourse and group interactions. For example, who takes the position of a leader, or an animator in a group? Can subgroups of communication be traced within a group, thanks to an analysis of clusters, cliques?

<pre>(4)
<post xml:id="cmr-Simu-Aquitania-Principal_27.04-13.05.01-59"
when="2001-05-02T07:58:00" who="#cmr-Simu-Al5" type="forum-message">
<head>
<title>les sons du Suffolk</title>
<listPerson>
<person corresp="#cmr-Simu-An3">
<event type="Read" when="2001-05-02T07:58:00">
<label>Read</label>
</event>
</person>
[other readers]

</listPerson>
</head>
Puisqu'on parlait de ce qui est par la fenêtre, j'ai mis mon micro
tout près de la fenêtre ce soir... Le coucou s'était déjà couché,
malheureusement, mais les autres chantent très fort! Les 'Bullocks'
ont tous le même père: un grand taureau Charolais, qui est le père
de tous les boeufs de la région! bonne nuit à tous<name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name>

<trailer>
<ref type="attached_file" target="#Simu_Aqui_forum_attach_988833475"
>suffolk.qcp</ref>
</trailer>
</post>

</pre>

===Wikipedia discussion===
to be added

===Blog===
From ''cmr-infral-tei-v1''<ref name="comere"/>. In (5) one message and its comment .
<pre>(5)
<post xml:id="cmr-blog-a2" synch="#T2" who="#P2" type="blog-message">
<head>
<title>Présentation de ma personne</title>
<label>étapeE1 ; </label>
</head>
Bon soir à tous!<lb/> Maintenant, je vais commencer avec les présentations.......
<lb/> Je pense que vous avez vu que je m'appelle <name ref="#P2">Kerstin</name> .
J'ai 22 ans. Mon nom est un nom suédois qui est très fréquent en Allemagne. Comme
vous savez peut-être, on a commencé nos études en master cette semaine. <lb/> Ma
famille - mes parents et mes deux soeurs -habite à Osnabrueck. C'est une ville qui
est pas loin de Brême. Après avoir passé mon bac à Osnabrueck, j'ai commencé mes
études de francais et de sport à Brême. La raison pour laquelle j'ai choisi ces deux
matières est que j'aime faire du sport (jouer au tennis, nager) et que j'adore la
culture francaise. J'adore la langue francaise et le pays me plaît beaucoup (le
paysage francais....). <lb/> Les deux étés passés, j'ai fait un stage de plus que
deux mois en Suisse francophone et en France (près de Lyon) pour améliorer mes
connaissances de la langue francaise et la pratique du francais à l'oral. <lb/> En ce
qui concerne mes études de francais, ce qui me plaît surtout, c'est, d'explorer la
culture francaise d'une manière différente (les textes littéraires, les séquences
vidéos......). <lb/> J'attends vos présentations et je vous souhaite encore un bon
soir........ <lb/> A bientôt, <name ref="#P2">Kerstin</name>
</post>
<post xml:id="cmr-blog-a3" synch="#T3" who="#P3" type="blog-comment" ref="#cmr-blog-a2">
<head>
<title>Hallo Kirstin! J'ai lu que tu as fait des stages e...</title>
</head>
Hallo<name ref="#P2">Kirstin</name> ! J'ai lu que tu as fait des stages en Suisse
francophone ! Où exactement car j'habite près de la frontière suisse (à 1h de
Lausanne !)! Je pense qu'on aura l'occasion d'en reparler ! Bis Bald 
</post></pre>

===Email===
From ''cmr-simuligne-tei-v1''<ref name="comere"/>. On email sent to one person and read by this person.

<pre>(6)
<post xml:id="cmr-Simu-Aq-At-Outbox-0080" when="2001-05-12T01:15:00"
who="#cmr-Simu-At" type="email-message">
<head>
<title>ta photo</title>
<listPerson>
<person corresp="#cmr-Simu-Al6">
<event type="SendTo">
<label>SendTo</label></event></person>
<person corresp="#cmr-Simu-Al6">
<event type="Read" when="2001-05-12T01:15:00">
<label>Read</label></event></person>
</listPerson>
</head>
Coucou<name ref="#cmr-Simu-Al6" type="person"><forename>Mia</forename></name>, Tu peux aller te voir dans
Publications : maintenant, tu y existe en totalité ! A bientôt,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name>

</post></pre>

==Macrostructure: the <nowiki><post></nowiki> element==
===The element===
In our schema, the element <post> is the basic structural element of a CMC
document corresponding to textual "enbloc" interactions. We consider it a macrostructural element, but it is the pivot between the higher
level macrostructural components thread and logfile and the microstructure
of the content which it encloses . The structure of <post> is based on that of the existing <nowiki><div></nowiki> element.

The <nowiki><div></nowiki> and <post> elements have the following similarities:
* <nowiki><div></nowiki> and <post> are high-level elements, belonging to the same class(model.divLike);
* <nowiki><div></nowiki> and <post> contain the major divisions of text;
* <nowiki><div></nowiki> and <post> have similar internal content.

It is important to note that <post>, like <nowiki><div>, does not belong to the class of pLike
elements. One <post> may consist of one or more paragraphs, similar to a <nowiki><div></nowiki>. While
a division may represent, for example, a chapter of a book, <posting> represents one user
contribution to some computer-mediated communication event (forum, blog, web-discussion,
or chat). Such a contribution can contain multiple paragraphs, just like <nowiki><div></nowiki>. In the chat, all postings consist of exactly one paragraph and the portion of text exhibits no special markup, but on the Wikipedia talk page given in figure 2, some of
the postings contain divisions and markup that the authors inserted into the content of their
postings in order to structure their content. Therefore, <post> cannot be a model.pLike
element.

The <nowiki><div></nowiki> and <post> elements have the following differences:
* <nowiki><div></nowiki> is a self-nesting element, while <post> is not;
*<post>s can only appear inside of a division which encloses one complete CMC
document (such as an entire forum thread, an entire blog with user comments, or a chat
logfile).

In other words, <post> is a child element of <div> and shares its content model except that
it does not contain divisions and does not embed itself. Normally, <posting> consists of one
or more paragraphs. In some cases a posting contains a head, typically with a title.

===Attributes for <nowiki><post></nowiki>===
Here is a summary of the attributes and other information which may be attached to different types of CMC environments. Note that information relative to StatusRead and Receiver have been encoded in TEI in the <nowiki><head></nowiki> of the <nowiki><post></nowiki> (close to the <nowiki><title></nowiki> - for email, forum, blog- and <nowiki><label></nowiki> (for blog). In order to minimize the number of attributes, we also have used the <nowiki><trailer></nowiki> element in order to encode description of attached file (email, forum, etc.) or numerous information concerning tweets (see the corresponding section). Attributes relative to Wikipedia forums have not yet been used (see the corresponding section).

'''Table2''' : attributes of the <nowiki><post></nowiki>element
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=71 valign=top style='width:53.55pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
SMS
</td>
<td width=95 valign=top style='width:70.9pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Textchat
</td>
<td width=113 valign=top style='width:3.0cm;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Blog
</td>
<td width=123 valign=top style='width:92.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Email
</td>
<td width=142 valign=top style='width:106.35pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Discussion
forum
</td>
<td width=104 valign=top style='width:77.95pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Wiki forum
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:lang
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@xml:id
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@when /
when-iso / synch
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@type 
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@subtype
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@ref
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(comment)
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
(respond)
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y(respond)
</td>
</tr>
<tr>
<td width=782 colspan=7 valign=top style='width:586.6pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
Not in
TEI
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@alias
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
Receiver
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
SendTo,
Cc, Bcc
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
StatusRead
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Option
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedWhen
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@revisedBy
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
<tr>
<td width=134 valign=top style='width:100.7pt;border:solid windowtext 1.0pt;
border-top:none;background:#EDEDED;padding:0cm 5.4pt 0cm 5.4pt'>
@identLevel
</td>
<td width=71 valign=top style='width:53.55pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=95 valign=top style='width:70.9pt;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=113 valign=top style='width:3.0cm;border-top:none;border-left:none;
border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=123 valign=top style='width:92.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=142 valign=top style='width:106.35pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=104 valign=top style='width:77.95pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
</tr>
</table>

==Macrostructure & multimodality: u and prod elements==
'''Figure2:''' non verbal acts in a 3D CMC environment
[[File:non_verbal.jpg|350px|thumb|left]]

===Types of divisions for the interaction space===

As already seen an interaction space may be described at 2 very different levels:

* 1) the meta level (see [[SIG:CMC/Draft: A metadata schema for CMC]]) ;
* 2) the interactions per themselves (i.e. the set of acts. These acts, in all examples given here, are included within a division which correspond to a session or a division within a division.

We may distinguish several types of divisions :

* div type=”thread” , e.g. forum, blog with different tools and then
** child element : <nowiki><post></nowiki>with different types
* div type =”logfile” , e.g. textchat, SMS, with different tools
** child element : <nowiki><post></nowiki> with different types for example within a textchat
* div type =”oral-discourse" for audiochat
** child element : <nowiki></nowiki> see chapter TEI on speech
* div type=”multi-modalities”
** child element : <nowiki><post></nowiki>
** child element : <nowiki></nowiki>
** child element : <nowiki><prod></nowiki> (for iconic acts - vote, raise_hand, brief_absence_act, etc. - , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication ) . As an example of non-verbal classification of acts, see the figure besides which represents non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013)<ref name="WighamRecall"/>.

=== <nowiki><prod></nowiki> element===

As explained the <nowiki><prod></nowiki> element refers to acts which are non-verbal, are part of the interction process, at the same level than the <nowiki><post></nowiki> and <nowiki></nowiki> elements. After example (1) given herebefore, here is another example (7) of interactions between one tutor and learners (From : ''cmr-copeas-tei-v1''<ref name="comere"/>. Context: Context: Lyceum audio-graphic conference environment).
* (7.1) audio act : yes/no question by the tutor
* (7.2) positive answer givent through a non-verbal modality by a learner (inconic system, modality here named "vote" with content "agree")
* (7.3) audio act : yes/no question by the tutor
* (7.4) textchat act : complementary info given by a learner
* (7.5) to (7.9) : yes / no answers of 5 participants through the iconic system

<pre>
(7)
(7.1)
euh no + euh I don't know the + the style ++ in french it's a band + named +
{les enfoirés} ++ you know euh + {enfoirés} |+++
(7.2)<prod xml:id="cmr-copeas-R2_lobby-a_1298" synch="#cmr-copeas-tl_r-w108" who="#AR7"
type="vote">agree</prod>
(7.3)anybody else know |
(7.4)<post xml:id="cmr-copeas-R2_lobby-a_1301" xml:lang="unk" synch="#cmr-copeas-tl_r-w110" who="#AR6" type="chat-message">
french's singers
</post>
(7.5)<prod xml:id="cmr-copeas-R2_lobby-a_1302" synch="#cmr-copeas-tl_r-w111" who="#AR3"
type="vote">agree</prod>
(7.6)<prod xml:id="cmr-copeas-R2_lobby-a_1303" synch="#cmr-copeas-tl_r-w111" who="#AR2"
type="vote">agree</prod>
(7.7)<prod xml:id="cmr-copeas-R2_lobby-a_1304" synch="#cmr-copeas-tl_r-w112" who="#AR6"
type="vote">agree</prod>
(7.8)<prod xml:id="cmr-copeas-R2_lobby-a_1305" synch="#cmr-copeas-tl_r-w113" who="#TutR"
type="vote">disagree</prod>
(7.9)<prod xml:id="cmr-copeas-R2_lobby-a_1306" synch="#cmr-copeas-tl_r-w114" who="#AR1"
type="vote">disagree</prod>
</pre>

The contents of the <nowiki><prod></nowiki> element is fairly simple in (7), whereas it is much more complicated in the <nowiki><prod></nowiki> element of example (1). In (1) it corresponds to an act of typing within a collaborative word processor. It is up to the researchers who transcribe (out of videoscreen captures) actions within online collaborative tools to decide which kind ofcoding scheme they want. We should not impose anything for this contents. The only mandatory information should be restrained to attributes.

This element does not exist in the current TEI version. Of course, the element name may be debatable (here the name "prod" corresponds to the fact that the corresponding non verbal act is a production made by a participant), but not its function.

We have considered some TEI elements relared to non verbal features before introducing <nowiki><prod></nowiki>.

====Elements than cannot be used as an act of type prod====
* <nowiki><activity></nowiki>: “contains a brief informal description of what a participant in a language interaction is doing other than speaking, if anything.”, it is a brief description, no attribute @who, too low-level
* <nowiki><kinesic></nowiki>: “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside <nowiki></nowiki> , but may be used at the same level. However the name is wrong. Kinesic is a specific non-verbal notion related to gaze, posture, gesture, not a general one.
* <nowiki><incident></nowiki>: “marks any phenomenon or occurrence, not necessarily vocalized or communicative, for example incidental noises or other events affecting communication.” Name unacceptable, runs against the interaction and communicative framework.

This is the whole philosophy / theoretical standpoint of the TEI chapter on speech that cannot be applied to non verbal description placed as the same level as text and sppech. These TEI elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one. Their naming is also unacceptable and cannot refer to concepts we have mentioned here.

====Attributes of <nowiki></nowiki> and <nowiki><prod></nowiki>====
'''Figure 3:''' interplay between modalities
[[File:Modality_interplay.jpg|350px|thumb|left]]

<nowiki></nowiki> and <nowiki><prod></nowiki> elements share the main top attributes as those listed in the upper part of Table2 for the <nowiki><post></nowiki>.
However there is a striking difference with respect to time. Time attributes attached to <nowiki><post></nowiki> correspond to ''en bloc'' acts. The time encoded corresponds to the time of post received/sent by the server. This is also the time that other participants saw the result of the act appearing on their screen. They can only react to this act after this time. All participants perceived this act (let us say a textchat) as instantaneous, despiste the fact that is not <ref name="instant"/>.
On the contrary, all <nowiki></nowiki> and most <nowiki><prod></nowiki> acts have a duration, i.e. other participants perceived oral or visual cues of the act and may react before it ends. Their reaction may lead the first participant to change on the thores what s/he intended to say or do. For example, the figure on the left here display in the left column the trasncript of an audio act and on the three right columns contents of textchat acts. Whilst the first participant utters his message, the other three react. Consequenlty the first one changes two times what he had initially planed to utter (extract from Second Life environment <ref name="WighamCall"/>).

=====Attribute representing Addressee / Receiver for <nowiki></nowiki> <nowiki><post></nowiki> and more elements=====

In Table1 we mentioned the "Receiver" information, which described to whom a message (Email) was sent. Since there exist no such attribute in TEI, we encoded it into the <nowiki><head></nowiki> of the <nowiki><post></nowiki>, in a quite verbose way. If we had known the addresses of SMS messages (we could not for ethics reasons when collecting SMS), we would also have needed such feature within a <nowiki><post></nowiki>.

It appears that in oral corpora it is often an necessity to clearly mention the addresse of a speech utterance. See for example, the Alipe project ([http://lrl-diffusion.univ-bpclermont.fr/alipe/]) with child-parents interactions where addressees are clearly indentified and have been described through verbose feature structures.

A great improvement to these circumlocutions may be to design an @addressee attribute which may be added to <nowiki></nowiki> and <nowiki><post></nowiki> at least. We may also use it for the <nowiki><adressingTerm></nowiki> element (see next section).

==Microstructure==
'''Figure4:''' Hierarchy of interaction signs
[[File:interaction_sign.png|350px|thumb|left]]

The micro-structure refers to the elements and their attributes found in the actual contents of the interaction (here mainly within <nowiki><post></nowiki>). A large part of this section comes from (Beiswenger et al., 2012)<ref name="Beißwenger"/>

There is no common terminology to classify the elements of Internet jargon, nor consensus about the status of these elements in
a natural language grammar framework. To fill this gap, we have developed an annotation
schema for these phenomena on the microstructure level of CMC documents. The basic
linguistic description category of our approach is termed an interaction sign; in the schema,
instances of interaction signs such as emoticons, acronyms, etc. are represented using the
element <nowiki><interactionTerm></nowiki>.

In our schema, we introduce an element <nowiki><interactionTerm></nowiki> as a phrase-level element (in the
model.phrase class) which encloses one or more instances of subclasses of interaction signs.

 
===New elements child of <nowiki>InteractionTerm</nowiki>===
The <nowiki><interactionTerm></nowiki> element can have members of att.global as attributes. In addition,
we introduce elements for the following subclasses of interaction signs:

* <nowiki><emoticon></nowiki> : Emoticons are iconic units created using the keyboard. They are often used to portray facial expressions, and they typically serve as emotion, illocution, or irony markers. Due to their iconic character, the use of emoticons is not restricted to CMC in one particular language; instead, the same emoticons can be found in CMC data in different languages. The <emoticon> element, which is assigned to the gLike element class. Conventionally, elements of this class contain non-Unicode characters and glyphs. Although most emoticons are produced as a sequence of keyboard characters (dot, comma, colon, and the like), the resulting figure is comparable in its semiotic status to graphic characters. While some smiley faces have been included in Unicode, the variety of emoticons is still larger than can be captured by Unicode characters alone. That is why we place the <emoticon> element in the class of gLike elements.

* <nowiki><interactionWord></nowiki> : Interaction words are symbolic linguistic units. Their morphologic construction is based on a word or a phrase of a given language which describes expressions, gestures, bodily actions, or virtual events?for example, the units sing, g (< grins, “grin”), fg (< fat grin), s (< smile), wildsei (“being wild”) are used as emotion or illocution markers , irony markers or to playfully mimic simulated bodily activity .The element <nowiki><interactionWord></nowiki> in our schema is a member of model.global.spoken. It shares properties of the <nowiki><kinesic></nowiki>, <nowiki><incident></nowiki>, and <nowiki><vocal></nowiki> elements in TEI.

* <nowiki><interactionTemplate></nowiki>: Interaction templates are units that the user does not generate with the keyboard but by activating a template which automatically inserts a previously prepared text or graphical element into a space of the user’s choice. The category of interaction templates includes graphic smileys, chosen by the user of a CMC environment from a finite list of elements. These often portray facial expressions but can depict almost anything; in the case of animated GIFs, they can even portray entire scenes as moving pictures. This clearly goes beyond what can be expressed using only keyboardgenerated emoticons. On the other hand, users can invent new emoticons by combining keyboard characters, while template-generated units are always bound to predefined templates. The element <nowiki><interactionTemplate></nowiki> in our schema belongs to the model.global class of elements.

* <nowiki><addressingTerm></nowiki> : Addressing terms address an utterance to a particular interlocutor . The most widely used form here is the one made out of the “@” character together with a specification of the addressee’s name. The element <nowiki><addressingTerm></nowiki> in our schema belongs to the model.nameLike class of elements. While this element usually uses no attributes, our customization includes the att.global attributes. The content of <addressingTerm> is restricted to two elements:
** The <nowiki><addressMarker></nowiki> element belongs to the class model.labelLike (used to gloss or explain parts of a document) and is provided with the att.global class of attributes. The purpose of <nowiki><addressMarker></nowiki> is to identify or to highlight the addressee in a posting. This is typically achieved by using the “at” sign (“@”) or one of a set of fixed phrases (English: “to”; German: “an” or “für”).
** The element <nowiki><addressee></nowiki> is placed in the model.nameLike.agent class.

===Attributes of these elements===
'''Table 3:''' attributes of elemens corresponding to interaction terms
<table border=1 cellspacing=0 cellpadding=0
style='border-collapse:collapse;border:none'>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
 
</td>
<td width=123 valign=top style='width:92.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<emoticon>
</td>
<td width=106 valign=top style='width:79.3pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionWord>
</td>
<td width=124 valign=top style='width:93.1pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<interactionTemplate>
</td>
<td width=129 valign=top style='width:96.5pt;border:solid windowtext 1.0pt;
border-left:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
<addressee>
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@style
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Western, Japanese, Korean, Other.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@systemicFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
emotionMarker:positive,
emotionMarker:negative, emotionMarker:neutral,
emotionMarker:unspec,
responsive, ironyMarker, illocutionMarker, virtualEvent.
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@contextFunction
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
Y
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@topology
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@semioticSource
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
y
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
mimic, gesture ,
bodilyReaction , sound, action , sentiment , process , and emotion
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@formType
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
simple, complex, abbreviated
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
persNameFull, persNameAbbreviation,
persNameNickname
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@type
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
iconic, verbal, iconic-verbal
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@motion
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
static, animated
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@who
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
ID
</td>
</tr>
<tr>
<td width=123 valign=top style='width:91.9pt;border:solid windowtext 1.0pt;
border-top:none;background:#BDD6EE;padding:0cm 5.4pt 0cm 5.4pt'>
@scope
</td>
<td width=123 valign=top style='width:92.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=106 valign=top style='width:79.3pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=124 valign=top style='width:93.1pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
N
</td>
<td width=129 valign=top style='width:96.5pt;border-top:none;border-left:
none;border-bottom:solid windowtext 1.0pt;border-right:solid windowtext 1.0pt;
padding:0cm 5.4pt 0cm 5.4pt'>
all, group ,individual, unspec
</td>
</tr>
</table>

===Example taken out of a textchat===
'''Figure 5:''' example of encoding into TEI of interaction terms used in a textchat
[[File:InteractionTerm.jpg|350px|thumb|left]]

 
 

===Example for Tweets===
From ''cmr-politwwet-tei-v1''<ref name="comere"/>. (10.1) gives an example of tweet where a variety of Twitter syntax phenomena appears (for the sake of presentation, we have created this example out of several real ones).
* reference to twitter-account: @JLMelenchon
* Retweet: RT @LePG:
* Tweet transmetted via another one: via @LeHuffPostBlog
* hashtag: #France2

In order to mark the specific Twitter syntax, we use the <nowiki><distinct></nowiki> element with a specific type. <nowiki><adressingTerm></nowiki> and its subcomponent are included within <nowiki><distinct></nowiki> as shown in (10.2). Specific characters / terms such as '#', 'RT' or 'via' are included within an <nowiki><ident></nowiki> element. One may wonders whether it should not be the same for the addressmarker.

Note other features specific to tweets:
<pre>(10.1)
RT @LePG: A 07h50, @JLMelenchon est l'invité des #4vérités sur #France2. Nous
live-tweeterons. #Chômage #Municipales2014 http://t.co/5Qi1eB1nTm via
@LeHuffPostBlog
</pre>
<pre>(10.2)
<post xml:id="cmr-politweets-a449071343175471104" when="2014-03-27T07:32:06Z"
who="#cmr-politweets-p80820758" type="tweet" xml:lang="fra">

<distinct type="twitter-retweet">
<ident>RT</ident>
<adressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account" ref="https://twitter.com/LePG 12214546"
>LePG</addressee>
</adressingTerm> : </distinct> A 07h50,
<adressingTerm>
<addressMarker>@</addressMarker>

<addressee type="twitter-account"
ref="#cmr-politweets-p80820758">JLMelenchon</addressee>
</adressingTerm> est l'invité des <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%234vérités&src=hash"
>4vérités</rs>
</distinct> sur <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23France2&src=hash">France2></rs>
</distinct> . Nous live-tweeterons. <distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Chômage&src=hash">Chômage</rs>
</distinct>
<distinct type="twitter-hashtag">
<ident>#</ident>
<rs ref="https://twitter.com/search?q=%23Municipales2014&src=hash"
>Municipales2014</rs>
</distinct>
<ref target="http://t.co/5Qi1eB1nTm http://huff.to/1fMDTo7"
>http://t.co/5Qi1eB1nTm</ref>
<distinct type="twitter-via">
<ident>via</ident>
<adressingTerm>
<addressMarker>@</addressMarker>
<addressee type="twitter-account"
ref="https://twitter.com/LeHuffPostBlog">LeHuffPostBlog</addressee>
</adressingTerm>
</distinct>

<trailer>
<location>

<placeName>België</placeName>

<geo>41.687142 -74.870109</geo>
</location>
<fs>

<f name="medium"><string>web</string></f>
<f name="favoritecount"><numeric value="30"/></f>
<f name="retweetcount"><numeric value="73"/></f>
<f name="isRetweet"><binary value="true"/></f>
<f name="isTruncated"><binary value="true"/></f>
<f name="isFavorited"><binary value="true"/></f>
<f name="retweetedstatus_id"><numeric value="444087690850750464"/></f>
<f name="inReplyToUserId"><numeric value="23339387"/></f>
<f name="inReplyToScreenName"><string>josebove</string></f>
</fs>
</trailer>
</post></pre>

===Anonymization===
In order to be able to distribute the collected CMC data as widely as possible, we need to
anonymize the data. Our anonymization strategy shall support the following goals:
* Every user of the data shall be able to associate a certain set of interaction acts in a CMC document to a user. This user, however, shall not be identifiable as an individual of the “real world”.
* In some corpora, researchers have collected numerous information about users (sociolinguistic ones, language biography, etc.) it is important to release with the corpora for future research analysis.

To achieve these particular goals, we perform the following steps:
* All of the recoverable personal data of a CMC participant (or group) are collected into a person profile in a <person> element. This profile is provided with a value of a user ID ( @xml:id) which is unique within the particular TEI document. All person profiles are stored in the header of the document; thus, they can easily be separated from the body of the document and therefore be hidden from the less privileged users of the data (cf. more explanation on participants - individual, groups- in [[SIG:CMC/Draft: A metadata schema for CMC]])
* Each interaction act is linked to a person profile via the @who attribute, which points to the value of an @xml:id of a <nowiki>person</nowiki> element.
* Instances of user names in segments of a given posting are also linked to a user ID.

Anonymization is a tedious process, but it has already been accomplished over numerous CMC corpora. When it is done, several types of information are kept and coded into feature structures (who did the process? how many characters have been changed, etc.). We will not detail them here. Every time such process is performed a piece of information is replaced by another, such as in the SMS message in (8).
<pre>(8) Bon, d'accord ! Elle est ou miss [_forename_] ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</pre>

In (9.1) we list the type of information which have been anonmyzed in the CoMeRe databaank and the keywords used for replacement and aligned them with TEI elements used to encode them. (9.2) shows an example of use within an email. Corresponding information is encoded within a feature structure whihc has to be declared in the <nowiki><teiheader></nowiki> / <nowiki><encodingDesc></nowiki> / <nowiki><fsdDecl></nowiki>

<pre>(9.1)
[_forename_] <forename>[_forename_]</forename>
[_surname_] <surname>[_surname_]</surname>
[_addName_] <addName>[_addName_]</addName>
[_tel_] <rs type="telephone">[_tel_]</rs>
[_email_] <email>[_email_]</email>
[_url_] <rs type="url">[_url_]</rs>
[_code_] <rs type="code">[_code_]</rs>
[_address_] <address>[_address_]</address>
</pre>
<pre>(9.2)
<post xml:id="cmr-Simu-Aq-At-Inbox-0075" when="2001-05-10T09:53:00"
who="#cmr-Simu-Al9" type="email-message"
ref="#cmr-Simu-Aq-At-Outbox-0033">
<head>
<title>Forum Prep Interculture</title>
[...]
</head>
Salut<name ref="#cmr-Simu-At" type="person"
><forename>Anna</forename></name>, Malheuresement,j?ai un
problème qui affect mon participation.. It is better to explain in
english., Since Simuligne commenced we have here a recently
announced General Election,which was of course delayed by one month
and should have been on May 7th. I am very heavily commited to
contribute to the campaign for my Party and as a result have been
unable to keep contact with you all. Now I find myself unable even
to keep our link up tomorrow evening. This activity will continue
for at least one month and so I must advise that I have decided to
discontinue my participation.Very sorry and best wishes to
Simuligne....regards,<name ref="#cmr-Simu-Al9" type="person"
><forename>Howard</forename><surname><fs
type="anonymisation">
<f name="origfrom"><string>Depositor</string></f>
<f name="anonyString"><string>[_surname_]</string></f>
</fs></surname></name>.. 
</post></pre>

===POS tagging and interactionTerm===
In this section we would like to comment / discuss our previous proposals (table 3, figure 5) related to elements and attributes corresponding to interactionTerms, when facing the task of automatically annotating CMC interactions (POS - Part Of Speech- tags). This comments come from the CoMeRe project which currently undertakes this task.

Attributes listed in table 3 with their values may be extensively used when doing hand annotations. But during an automatic process the transformation into TEI may be simplified in order to reduce the management of graphic variations, for example on interactionWord. Example (10) display in (a) an SMS and in (b) part of the output after processing (once the lexicon has been extended, interactionTerms may also received a @lemma information).

<pre>
(10)
(a)
c vré c les kangourous ki saute banane de Wizou va mdrrrrrrrr bébé :)

(b)
[…] <interactionWord><w ana="#INTERJEC">mdrrrrrrrr</w></interactionWord>
<w ana="#N" lemma="bébé">bébé</w><emoticon><w ana="#INTERJEC">:)</w></emoticon>

(c)
mé Wizou kestu fous ici toi ofait ?

</pre>

Finding addressees may also be difficult because in many CMC environments there is no actual constraint on using addressing markers (more particularly the "@", as shown in another SMS exchange (10.c) where 'Wizou' is the addressee).
But, when considering tweets, it is mandatory to use addressing markers and the Tweet syntax may have to be tagged more explicitly (hashtag, retweet, reference to Twitter account, quotes from a Twitter account, etc.). In (11) a, b and c are examples taken from ''cmr-polititweets-tei-v1''. (11) d, e, f respectively give some foreseen outputs coming from the automatic processing. We here used the existing <nowiki><rs></nowiki> TEI element. Note that in the <nowiki><addresse></nowiki> element, we have not used @who, which must refer to the ID of a participant listed in the <nowiki><teiHeader></nowiki>. Instead of, we used the @ref attribute which value contains the ID given by Twitter.
<pre>(11)
(a) Déjeuner de travail avec @claudebartolone a l'Assemblee Nationale a l'ordre du jour le rôle de la Caisse des dépôt a la SNCM

(b) RT @AvecMennucci: L'équipe #Mennucci en marche! http://t.co/pBtgU1CrJN

(c) RT @marcelvayre: Oh peuchere...L'illusion Gaudin via @Marianne2fr #Marseille #Marseille2014 #Mennucci http://t.co/jYtSTW1gPn

(d)<rs type="twitter-account">
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker>
<addressee ref="IDtwitter"><w ana="#NP>claudebartolone</w></addressee></adressingTerm></rs>

(e)<rs type="twitter-retweet"><w ana="#??>RT</w>
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker>
<addressee ref="IDtwitter"><w ana="#NP>AvecMennucci</w></addressee></adressingTerm><w ana="PONCT">:</w></rs>
<w ana="#DET lemma="la">l</w> <w ana"#N" lemma="équipe">équipe</w> […]

(f)[…] <w ana="#PN">Gaudin</w> <rs type="twitter-ref-account"><w ana="#PREP>via</w>
<adressingTerm><addressMarker><w ana="#??>@</w></addressMarker><addressee ref="IDtwitter"><w ana="#NP>Marianne2fr</w></addressee>
</adressingTerm></rs>
<rs type="twitter-hashtag"><w ana="#??">#Marseille</w></rs></pre>

==References and notes==
<references>
<ref name="Beißwenger"> Beißwenger, M., Ermakova, M., Geyken, A., Lemnitzer, L &, and Storrer, A (2012). "A TEI Schema for the Representation of Computer-mediated Communication", Journal of the Text Encoding Initiative, 3. [http://jtei.revues.org/476] ; DOI : 10.4000/jtei.476</ref>
<ref name="ChanierAlsic">Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audio-synchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61-101. DOI : 10.4000/alsic.270 [http://alsic.revues.org/270]</ref>
<ref name="Ciekanski">Ciekanski, M., Chanier, T (2008). Developing online multimodal verbal communication to enhance the writing process in an audio-graphic conferencing environment. Recall, vol. 20 (2), Cambridge University Press. 162-182. doi:10.1017/S0958344008000426 [http://edutice.archives-ouvertes.fr/edutice-00200851]</ref>
<ref name="WighamRecall">Wigham, C.R. & T. Chanier (2013a). "A study of verbal and nonverbal communication in Second Life. the ARCHI21 experience". ReCALL 25(1), Cambridge Journals. DOI: 10.1017/S0958344012000250 [http://edutice.archives-ouvertes.fr/edutice-00674138]</ref>
<ref name="WighamCall">Wigham, C.R. & T. Chanier (to appear in 2013b). Interactions between text chat and audio modalities for L2 communication and feedback in the synthetic world Second Life. (CALL) Computer Assisted Language Learning. DOI: 10.1080/09588221.2013.851702 [http://edutice.archives-ouvertes.fr/edutice-00862004]</ref>
<ref name="Derik">DeRiK (2013). Description of the DeRiK (Deutsches Referenzkorpus zur internetbasierten Kommunikation) project for CMC in German databank of corpora encoded into TEI. [http://www.empirikom.net/bin/view/Themen/DeRiK]</ref>
<ref name="comere">CoMeRe(2014). Website documentation of the CoMeRe (Communication Médiée par les Réseaux) project. CMC in French databank of corpora encoded into TEI [http://comere.org]</ref>
<ref name="instant">The duration of the typing of a textchat is not encoded here and is not perceveived by other participants. Also in some CMC there exist visual cues of participants engaged in a process of typing in the textchat. But if one wants to take into account these cues, which often play a role in the interaction and participants may refer to it, they would be described as non verbal acts (<nowiki><prod></nowiki>)</ref>
</references>