Defining the online interaction space and the TEI
Transcription
Defining the online interaction space and the TEI
TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org SIG : Compurer-Mediated Communication Defining the online interaction space and the TEI structure for CoMeRe corpora Version 2 Version 31st December, Thierry Chanier How to cite this document: Chanier, T. & Jin, K. (2013) Defining the online interaction space and the TEI structure for CoMeRe corpora. Projet CoMeRe (Communication Médiée par les Réseaux), IR Corpus-écrits. [ http://corpuscomere.org/ , comere-is-tei-v2 ] Participants : Thierry Chanier Participants :.Kun JIN -1- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Contenu 1. Online interaction space ............................................................................................................. 4 1.1. First definition ................................................................................................................................... 4 1.2. General considerations ..................................................................................................................... 4 1.3. Environment, temporal organization, multimodality and location .................................................. 4 1.3.1. General considerations .............................................................................................................................. 4 1.4. Notion of interaction......................................................................................................................... 8 1.4.1. General considerations .............................................................................................................................. 8 1.4.2. TEI description ........................................................................................................................................... 9 1.5. TEI and corpora assembling interaction spaces .............................................................................. 11 2. CMC textual types with simple interaction spaces ................................................................... 13 2.1. Type of divisions.............................................................................................................................. 13 2.2. Textchat........................................................................................................................................... 13 2.2.1. General features of the environment ...................................................................................................... 14 2.2.2. Structure of a textchat message: "post" element ................................................................................... 15 2.2.3. Interactions spaces within the environment ........................................................................................... 16 2.3. SMS ................................................................................................................................................. 17 2.3.1. General features of the environment ...................................................................................................... 17 2.3.2. Structure of an SMS message: "post" element ....................................................................................... 18 2.3.3. Interactions spaces within the environment ........................................................................................... 19 2.4. Email ................................................................................................................................................ 20 2.5. Forum .............................................................................................................................................. 21 3. More complex interaction space............................................................................................... 23 3.1. Distinct interactions spaces within one common framework ........................................................ 23 3.2. General features of the environment ............................................................................................. 24 3.3. Interactions spaces within the environment .................................................................................. 28 4. Anonymisation et identification participants............................................................................ 30 4.1. Identifier les participants ................................................................................................................ 30 4.2. Anonymisation dans les corpus déposés ........................................................................................ 30 4.2.1. Anonymisation dans smsalpes................................................................................................................. 31 4.2.2. Anonymisation dans smslareunion.......................................................................................................... 31 4.2.3. Anonymisation dans Mulce ..................................................................................................................... 32 4.2.4. Anonymisation dans Alipe ....................................................................................................................... 32 4.3. Anonymisation dans CoMeRe ......................................................................................................... 33 5. Déclarer en TEI des annotations faites à la main : Corpus smslareunion ................................. 35 5.1. Rappel des consignes données par Gudrun .................................................................................... 35 5.2. Choix des annotations en TEI .......................................................................................................... 36 5.2.1. Déclaration des annotations dans le teiheader ....................................................................................... 36 5.2.2. Annotations simples : transposition orthographique .............................................................................. 37 6. Other things............................................................................................................................... 40 -2- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 7. Appendix.................................................................................................................................... 41 8. References ................................................................................................................................. 42 Audience for this document This document presents information on the way CoMeRe has encoded in TEI its first 4 corpora at the end of 2013. It has a double audience: • Colleagues from the TEI-CMC group, in order to develop a common schema. We expect them to directly write into this document for feedback (revision or highlights, change the date and add your name on the front page • Colleagues from the CoMeRe project, more particularly members of the quality group This document has been written after having examined current draft papers coming from the IRCOM/ORTOLANG French community on oral corpora and the corresponding European ISO/DIN -3- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 1. Online interaction space 1.1. First definition 1.2. General considerations An interaction space (IS) is an abstract concept, located in time (with a beginning and ending data with absolute time, hence a time frame) where interactions among a set of participants happen within an online location. The online location is defined by the properties of the set of environments used by this 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. Groups are object of study in online interaction (cf. CSCL analysis based on Social Network Analysis – SNA- (Reffay & Chanier, 2003) and are extensively studied in online interactions). The range of types of interactions (and their related locations) is widespread. On one end we find a simple type with one environment based on one modality / tool (e.g., one email system, or textchat system, etc. Then complex environments such as Learning Management Systems (LMS) where several type of communication modalities are integrated (see hereafter example with the LMS WebCT which uses only textual modalities synchronous – textchat – and asynchronous –email and forum -). At the other end, one interaction space may appear in locations related to several environments used during the same period (eg. a blog plus a conference system, an LMS plus a conference system -see figure 2 – etc.). Identifying participant within TEI There exists a strong recommendation among researchers working on oral corpora and from ORTOLANG / CLARIN that a participant should have a unique identifier among, not only one corpus, but a repository of corpora. We will call it PUI (Personal Unique Identifier). Secondly a participant may use several aliases / pseudonyms within one corpus. We will consider that an alias is local to a corpus. In CMC almost every act (eg, post, u, etc.) will have an author identified by @who, which corresponds to an @xml:id. We cannot oblige an encoder to put into the @who the PUI. It may be the alias. But we should find clear links among @xml:ids in the TEIHEADER: the participant unique identifier and all her/his related aliases 1.3. Environment, temporal organization, multimodality and location 1.3.1. General considerations An environment may be synchronous or asynchronous, mono or multimodal. Multimodality refers to environments which offer several tools of interaction, integrated within the same interface. Every tool uses one mode of communication (“mode” word sense here refers to semiotics) (eg: oral, text, icon, non-verbal) and one modality (word sense here refers to HCI -4- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Human Computer Interaction) (eg: a textchat has a specific textual modality, different from the modality of collective word processor; 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 mode are used and/or several modalities 1. An environment offers to the participants one or more locations/ places for interacting: eg 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 Second Life, a location may be an island or a plot, even a very small plot. A plot may be divided into small sub-plots where verbal communications (textchat, audio) is impossible from one to another. In Second Life, verbal communication among participants is only possible within a given distance. When participants are too remote, they cannot participate on the same textchat nor communicate in the audio mode. 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. Note that one participant may be at the same in different locations (ubiquity). In Second Life, s/he can be on an island interacting with other participants and, simultaneously, communicating with a textchat with a remote participant (into another location/place). In this case, other participants of the island ignore this exchange. We have 2 interaction spaces which are connected, because one participant interacts within the same time frame and the same environment. Lastly, an interaction space is an abstract space where interaction occurs. When the same participants interact over several weeks, different sessions of interactions will occur. They can be included in the same TEI file (which will then behave a teiCorpus structure.) with beginning and ending time (see figure 4). Moreover one session may be analyzed (and transcribed) as a list of sequences (cf. oai:mulce.org:mce-copeas-letec-all). This raises 2 questions: 1) how the overall organization can be described at a metadata level? (?) 2) How will transcription fit into one another? 1 We should not make a confusion between 1) the necessity of giving a reference to the environment used (we should maybe give a label attached to it, label defined in a general taxonomy (see figure 2 with the reference to Mulce terminology defined in vdex format and online)) and 2) the description of the set of tools used within this environment and the particular event which have been transcribed see figure 3. Personally I am not very interested within the TEI-CMC with building a taxonomy for 1) ; but deciding how to described 2) is of crucial importance, because it then relates to the structure of the interactions. See figure 4 as a kind of taxonomy for these tools. -5- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org <platforms id="mce-copeas-letec-platforms"> <annotation> <langstring xml:lang="fr"> *********** PLATFORMS Liste environnements Copeas La description de ces environnements avec interfaces et fonctionnalités, articles en parlant est dans les documents joints au Learning Design. Lyceum tournait sur les serveurs de The Open University WebCT sur ceux de Universite de Franche-Comte. Les interactions decrites ici concernent presque uniquement Lyceum</langstring> </annotation> <platform id="lyceum2005"> <name>Lyceum</name> <type> <source_doc>http://lrl-diffusion.univbpclermont.fr/mulce/metadata/vdex/mce_platform.xml</source_doc> <value_doc> <langstring xml:lang="en">Audio-graphic conference</langstring> </value_doc> </type> <version>3.5</version> <url>http://lyceum.open.ac.uk/install/</url> <designer>The Open university</designer> <server>http://lyceum.open.ac.uk/install/</server> </platform> <platform id="webCT2005"> <name>WebCT</name> <type> <source_doc>http://lrl-diffusion.univbpclermont.fr/mulce/metadata/vdex/mce_platform.xml</source_doc> <value_doc> <langstring xml:lang="en">Asynchronous LMS</langstring> </value_doc> </type> <version>3.8</version> <url>http://www.blackboard.com/us/</url> <designer>WebCT - Canada Vancouver</designer> <server>http://webct.univ-fcomte.fr:8080</server> </platform> </platforms> Figure 2: example of 2 environments, used by the same set of participant within the same course, described at a metadata level in oai:mulce.org:mce-copeas-lectec-all (Chanier et al., 2009). XML format Mulce-struct -6- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Metadata level <tool tool_type="chat" id="tpc" platform_ref="lyceum2005" ld_refs="env-lyceum_communication"/> <tool tool_type="audio" id="tpa" platform_ref="lyceum2005" ld_refs="env-lyceum_communication"/> <tool tool_type="vote" id="v" platform_ref="lyceum2005" ld_refs="env-lyceum_communication"/> <tool tool_type="production" id="prod" platform_ref="lyceum2005" ld_refs="env-lyceum_prod"/> <tool tool_type="raise_hand" id="lm" platform_ref="lyceum2005" ld_refs="env-lyceum_communication"/> <tool tool_type="presence" id="as" platform_ref="lyceum2005" ld_refs="env-lyceum_communication"/> <tool tool_type="brief_absence" id="abs" platform_ref="lyceum2005" ld_refs="env-lyceum_communication"/> Schema level <xs:element name="brief_absence_act"> <xs:annotation> <xs:documentation>acte pour signifier une absence momentanée</xs:documentation> </xs:annotation> <xs:complexType> <xs:attribute name="content" use="required"> <xs:simpleType> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="away"/> <xs:enumeration value="back"/> </xs:restriction> </xs:simpleType> </xs:attribute> </xs:complexType> </xs:element> Interaction level <acts> equivalent to a div level? <act id="a_1554" tool_ref="tpa"> <author ref="TutR"/> <act_type> <audio_act> <language>eng</language> <content_transcript> <content>ok + well we can ask euh + research team to take note of that euh + we try to put the euh grab to use the grabscreen function and we've got an error + so we'll just have to use the screen euh on a on a + separate window + euh on our desktop</content> </content_transcript> </audio_act> </act_type> <beginning_date>2005-01-25T11:37:08</beginning_date> <ending_date>2005-01-25T11:37:28</ending_date> </act> <act id="a_1555" tool_ref="prod"> <author ref="TutR"/> <act_type> <prod_act doc_type="whiteboard"> <rank>4</rank> <p_action action="open"/> <content>Whiteboard: Untitled 3</content> </prod_act> </act_type> <beginning_date>2005-01-25T11:37:27</beginning_date> <ending_date>2005-01-25T11:37:27</ending_date> <comment>nobody</comment> </act> </acts> Figure 3 : Tools and interactions (set of acts), one with audio modality and the second one coming from a collective word processor Sources: oai:mulce.org:mce-copeas-lectec-all and associated XML format Mulce-struct, with schema (mce_sid.xsd), -7- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 1.4. Notion of interaction 1.4.1. General considerations Participants are in the same interaction space when they can interact (but not necessarily do it, cf. lurkers). They interact through input devices, which will not be taken into account here (microphone, keyboard, mouse, gloves, etc.), which let them use the modality tools and output devices (again not described here), mainly producing visual or oral signals. Hence when they cannot hear nor see the other participants’ actions, they are not in the same interaction space. Of course, participants may not be participants during the whole time frame of the IS. They can enter late, or leave early. Since at one given time there is one set of participants, particular attention should be given to the description of entering or leaving an IS. An interaction space (IS) may include other interactions spaces. The top IS will have a time frame which includes the time frames of the entire sub ISs. The same conditions apply to participants, plus the fact that some participants have to be members of several ISs, otherwise there is no rationale for building such top IS. In an interaction space, 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; some nonverbal ones cf. figure 5 for Second Life were kinetic ones, which are generally considered as having a communicative feature, represent only a subtype). Other may not be directly communicative, but represent the cause of communicative reaction / interaction (see example of figure 6). 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 not relevant. A much more important distinction may be made between an IS where only one modality (tool) is used by participants, and an IS where several occur. In section 2.1 we start presenting some examples of mono modality environment where actions may occur en bloc or not (for the latter case, see for example a usual oral discussion in Skype). Then the corresponding IS may have an enbloc nature (referred to as div type of thread or logfile CMC DWDS) or not. Note that the mono modality has to be of a verbal and communicative nature (textchat, audio, etc.), otherwise it would not be part of our CMC concern. A more complicated case appears when an IS uses several modalities. Then we may have verbal (speech, textchat) and nonverbal acts. Actions will not all occur enbloc. The main purpose of transcriptions is to describe inter-relations among acts and within acts: the participant’s utterance may be re-planned when s/he talks depending on some specific acts occurring (see Wigham& Chanier, 2013b). We also need a general term for actions which are either nonverbal or produced within collective tools (where language may play an important role with tools allowing them: word processor, semantic maps, whiteboard, etc.). Let us call this element prod. -8- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Figure 5: example of non-verbal acts in Second Life as encoded by (Wigham & Chanier, 2013) 1.4.2. TEI description An interaction space may be described at 2 very different levels: o 1) the meta level (see figure 4, figure 2 and figure3) ; o 2 the interactions per themselves (i.e. the set of acts, see figure 6 and examples in section 2). 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 divisions2: • for forum, blog, ?? with different tools and then o child element : post with different types • div type =”logfile” for textchat, SMS, ?? with different tools o child element : post with different types for example within a textchat • for audiochat o child element : u see chapter TEI on speech • (see figure 6, (Wigham & Chanier, 2013a), (Wigham & Chanier, 2013b), (Chanier, vetter, 2006)) o child element : post o child element : u o child element : prod (for vote, raise_hand, brief_absence_act , all collective tools – wordprocessor, semantic map, whiteboard, etc. - nonverbal communication as in figure 5) 3. div type=”thread” div type =”oral-discourse" div type=”multi-modalities” 2 Maybe some incoherence in our text. In the next section we present a different view on type of divisions which correspond to monomodal textual modalities. 3 Question : If we put so many modalities within prod its organization may be quite complex Instead of using one only type prod, should be distinguished between a) iconic ones (vote, raise_hand, brief_absence_act), b) the type of nonverbal ones as in Figure 5 ; and c) the ones belonging to collective tools (wordprocessor, semantic map, whiteboard). I -9- TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org In figure 4, we illustrate a way for describing types and subtypes of acts (post, prod). We should not aim at having a common description in the TEI-CMC group. Every environment has got its own affordances and researchers may have different views when transcribing or analyzing. On the contrary, we should have a common way of describing them 4. Elements than cannot be used as an act of type prod “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 • activity: • “marks any communicative phenomenon, not necessarily vocalized, for example a gesture, frown, etc”. Has been designed as integrated inside u , 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. • incident: kinesic: “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 we cannot follow. These elements, related to an utterance, are not really considered as being part in the interaction, at the same level as the utterance’s one (however, it is possible to use them - kinesic, incident - at this level; but their description is very poor). Their naming is also unacceptable and cannot refer to concepts we have mentioned here. Redefining the semantics of element « p » • p: “(paragraph) marks paragraphs in prose”. In our case, the element p is a mandatory sub-element of post. It implies that its contents will correspond to a piece of textual information produced either by a human or a system. It does not imply that the structure of this piece of textual information is equivalent to a paragraph (i.e. made up of sentences, etc.). would not spend too much time on this issue, and the Mulce experience shows that once we have a clear way of describing things then everyone can do a s/he pleased and descriptions will be readable and processable. 4 Question: how do we fix a set of value within a modality? For example see figure 3 for brief_absence_act and its values d fixed in the XSD associated schema? Will it be in a relax NG file? One per project? Should we use feature structures, like the way did in ALIPE corpus? - 10 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org <act id="a_8731" tool_ref="prod"> <author ref="AT2"/> <act_type> <prod_act doc_type="text_doc"> <rank>1</rank> <object>paragraph</object> <p_action action="modify" content="substance"/> <content>I depend entirely on donations, sponsorship and affiliate links to help cover the substantial coasts of hosting and developing tis web site. For Monday 24th</content> </prod_act> </act_type> <beginning_date>2005-01-24T10:43:15</beginning_date> <ending_date>2005-01-24T10:43:18</ending_date> </act> <act id="a_8732" tool_ref="prod"> <author ref="AT3"/> <act_type> <prod_act doc_type="text_doc"> <rank>1</rank> <object>paragraph</object> <p_action action="modify" content="substance"/> <content>I depend entirely on donations, sponsorship and affiliate links to help cover the substantial coasts of hosting and developing tis web site.</content> </prod_act> </act_type> <beginning_date>2005-01-24T10:43:39</beginning_date> <ending_date>2005-01-24T10:43:54</ending_date> </act> <act id="a_8733" tool_ref="tpa"> <author ref="AT7"/> <act_type> <audio_act> <language>eng</language> <content_transcript> <content>ok thank you</content> </content_transcript> </audio_act> </act_type> <beginning_date>2005-01-24T10:43:42</beginning_date> <ending_date>2005-01-24T10:43:43</ending_date> <comment>AT3 efface la phrase écrit par amand</comment> </act> Figure 6 : example 2 of interaction between 3 (AT2, AT3, AT7) participants (AT2, AT3) which did production acts corresponding to writing in the common word-processor and an oral comment of AT7 about these changes. Source : oai:mulce.org:mce-copeas-letec-all, XML format Mulce-struct 1.5. TEI and corpora assembling interaction spaces The TEI may be applied to our encoding, structuration and diffusion of our online interaction corpora for at least two very different reasons (we admit from the beginning the necessity of using a standard and guarantying interoperability): a text is built for: o Describing textually the characteristic of the interaction space: metadata, which can be very detailed, on the time frame, participants, environments, etc. o Gathering the (textual) transcription of interactions which happened through the various modalities of the environment(s). When the interaction space is limited to one textual environment, based on one modality, then the corpus coincides with the TEI file. In other cases, the TEI file is only one component of the corpus, which includes files related to images (cf. blogs), audio, video files. The TEI file will always include the complete list of attached file. Then the corpus is included into a package, and the content packaging should be standard (we use the IMS-CP in Mulce). - 11 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Properties of a theoretical framework Following MacLaughlin (1987) our theoretical framework should have a definitional adequacy, an explanatory power and based on operational definitions. I may also add that its assets should also include extensiveness. Hence it should be able to describe and take into account all the various types of CMC we have been actually working on: emails, forums, textchats, multimodal environments, blogs, SMS, tweets, etc. Operational definition implies: • Do not try to include every kind of environment we are thinking of, but have never closely worked upon, nor collected data. • Discussion on TEI cannot be separated of the fact that we have taken commitment to produce / release actual corpora encoded in TEI at a short term (one or two years). • Every piece of annotation brought by the collector of a corpus should not be lost when converting the corpus into TEI. • Overgeneration of new elements should be discouraged. The example of the TEI chapter about on “simple analytic mechanism) is a good counter-example. It introduces numerous terms which people from NLP will ignore because they have their ones. - 12 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 2. CMC textual types with simple interaction spaces In this section we only consider macro-structures, not micro-structures. We consider CMC types based on textual mode (SMS, textchat, email and forum). Interaction spaces will be quite simple, because environments are restricted to only one tool, i.e. one modality, used by participants. In CoMeRe we have 3 such corpora based on one single modality: • cmr-getalp_org • cmr-smsalpes • cmr-smslareunion corpus (Falaise, 2013): corpus based on one textchat environment with 80 IRC channels (hence 80 TEI files), 1,37Go, 4 millions of messages / posts. corpus (Antoniadis, 2013): corpus of 22 000 SMSs corpus (Ledungen, 2013): 15 000 SMSs. After having described textchat and SMS environment, we introduce two other modalities based on textual mode, email and forum. They will be used in a more complex interaction space in the next section. 2.1. Type of divisions Following Beißwenger & al. (2012) we started including types of post belonging to one modality into division (element div) of type logfile for textchat and thread for discussion forum. In the next section where several modalities are intertwined, we find it more convenient to categorize division by modality (ie. chat, forum, email). These different types of division relate to different structures / schemas. As it will become noticeable when reading this section, we define different structures corresponding to each modality (hence more than 2). The limitation to the first two types may then not be applicable. Question: Decision has to be made about different types of divisions (see 1.4.2 for a different viewpoint). 2.2. Textchat Every act (events, messages / post) is considered as being produced enbloc. It has a timestamp, an author (PUI or system or unknown), an xml:id, which cannot be n (because n is not necessarily unique in a document). It has no duration. Structure of a post (for further details see the specific section): (2.1) <post xml:id="cmr-get-c043-a21693" when-iso="2004-03-18T14:09" who="#cmr-getc043-p39174" alias="cortex_taff" type="chat-message"> <p>Apres je vé faire ma physique c aussi les equation bilan</p> </post> Examples will be taken out of the cmr-getalp_org corpus (Falaise, 2014): 80 files, 1,37Go, 4 millions of messages / posts. One TEI file, here cmr-getalp_org--p-u-r- corresponds to a canal (IRC Chanel) which has a main topic of discussion. - 13 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 2.2.1. General features of the environment This IRC textchat is a mono modal environment (textual mode). It includes only one modality (the chat). Textchat environments may vary. Hence it is a necessity to describe the system functionalities, which are closely connected to affordances which participants may use to interact. General features of textchat modality (2.2) <textClass> <keywords scheme="OLAC"> <term type="olac:linguistic-field">applied_linguistics</term> <term type="olac:linguistic-field">discourse_analysis</term> <term type="olac:linguistic-field">text_and_corpus_linguistics</term> <term type="olac:linguistic-type">primary_text</term> <term type="olac:discourse-type">dialogue</term> </keywords> <keywords scheme="NA" xml:lang="fr-FR"> <term>Communication Médiée par les Réseaux</term> <term>CoMeRe</term> <term>clavardage</term> </keywords> <keywords scheme="NA" xml:lang="en"> <term>Computer Mediated Communication</term> <term>CMC</term> <term>textchat</term> <term>IRC </term> </keywords> </textClass> <textDesc xml:lang="en-GB"> <channel mode="w" xml:lang="en-GB"><term ref="#texchatepiknet">textchat</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>Canal généraliste.</note></purpose> </textDesc> Affordances of a particular textchat environment (2.3) describes part of the environment (Here IRC EpikNet) in the teiHeader, the taxonomy of messages. There exist textchat messages, messages corresponding to a system command, or to an event. Type event has several subtypes. (2.3) <classDecl> <taxonomy> <category xml:id="texchat-epiknet"> <catDesc>Definition of the modality textchat. Type of messages used in cmrgetalp_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"> <catDesc>un utilisateur vient de se connecter</catDesc> </category> <category xml:id="deconnexion"> <catDesc>un utilisateur vient de se déconnecter</catDesc> - 14 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org </category> <category xml:id="changementpseudo"> <catDesc>un utilisateur vient de changer de pseudo; au lieu d'un sousélément "auteur", on alors deux sous-éléments "pseudosource" et "pseudocible"</catDesc> </category> <category xml:id="action"> <catDesc>"action" (en principe purement verbale) d'un utilisateur, et explicitement annoncée en tant que telle</catDesc> </category> <category xml:id="changementmode"> <catDesc>un utilisateur change de statut</catDesc> </category> <category xml:id="kick"> <catDesc>un utilisateur (disposant du statut approprié) vient de kicker (« éjecter») un autre utilisateur</catDesc> </category> <category xml:id="autre"/> </category> </category> </taxonomy> </classDecl> 2.2.2. Structure of a textchat message: "post" element Part of the description a textchat turn, given in (2.5), maybe applied to any kind of textchat environment. But particularities imposed by a specific environment (here, again, IRC EpikNet) have to detailed in order to guide further research analyses (see explanation on attributes @who @alais). (2.5) <editorialDecl> <normalization> <p>for details about encoding before TEI, see the attached document <idno>cmr-getalp_org-tei-v1-manuel.pdf</idno></p> […] </normalization> <stdVals> <p>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.</p> </stdVals> <segmentation> <p><gi>post</gi> correspond to textchat turns</p> </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> - 15 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org <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> 2.2.3. Interactions spaces within the environment After having defined general features of the environment, let us describe where and when it has been used, then the participants. Location and time frame Here is in (2.6) other information which describes the general location of the server, then a particular channel with its time frame. 80 other channels (in distinct TEI files) have described in a similar way. (2.6) <profileDesc> <creation> <date from="2004-02-03" to="2004-04-09"/> <location type="online_environement"> <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> Participants In these open IRC channels, it is very difficult to identify unique participants. Two figures are given: number of connected people (here 117; number of people who got in or out) and number of participants: number of participants with a distinct ID (here 38) computed out of distinct aliases Since a participant may choose and use (at different times) several aliases, it is impossible to accurately determined how actual different participant interacted in the channel. However changing regularly their alias is common habits in this type of chat. Hence we collected aliases attached to the same ID. See also (15) , description of attribute who. (2.7) gives an extract of the teiHeader. Participant with ID cmr-get-c024-p45906 has been processed as being different from participant with ID cmr-get-c024-p45905. They both share - 16 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org some common aliases. Impossible to tell whether it is the same person. Here they are considered as 2 people. (2.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> Examples of interactions In (2.8) participants talk about their school work, then someone comes in, changes her/his alias and someone else gives her/him extra rights on the channel. (2.8) <post xml:id="cmr-get-c043-a21693" when-iso="2004-03-18T14:09" who="#cmr-getc043-p39174" alias="cortex_taff" type="chat-message"> <p>Apres je vé faire ma physique c aussi les equation bilan</p> </post> <post xml:id="cmr-get-c043-a21694" when-iso="2004-03-18T14:09" who="#cmr-getc043-p39174" alias="cortex_taff" type="chat-message"> <p>Aujourd'hui c la journée equation</p> </post> <post xml:id="cmr-get-c043-a21697" when-iso="2004-03-18T14:11" who="#cmr-getc043-p36208" alias="roulie" type="chat-message"> <p>lol</p> </post> <post xml:id="cmr-get-c043-a21704" when-iso="2004-03-18T14:18" who="#cmr-getc043-p48191" alias="_Coolman_" type="chat-event" subtype="changementpseudo"> <p>Changement de pseudo: _Coolman_ -&gt; Mega-Link</p> <add><code>alias_change(_Coolman_,Mega-Link)</code></add> </post> <post xml:id="cmr-get-c043-a21705" when-iso="2004-03-18T14:18" who="#unknow" type="chat-event" subtype="changementmode"> <p>#Rhone-alpes:changement de mode(s) '+o Mega-Link' par [email protected]</p> </post> 2.3. SMS 2.3.1. General features of the environment General features of textchat modality Collecting SMS is a hard process. In order to protect private life, participants living in one specific agreed in 2 of our corpora (smslareunion and smsalpes, respectively 12 000 and 22 000 messages) to send a copy of their messages to a server. These conditions imply that the correspondent / addressee is not known, neither the exact time of the original message. In (2.9) the name of the society which collected the SMS and sent them to the research lab is cited. Interaction is reduced to one addressee (Note the difference (interaction element) with the chat one). (2.9) <textClass> - 17 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org <keywords scheme="OLAC"> […] <keywords scheme="NA" xml:lang="fr-FR"> <term>Communication Médiée par les Réseaux</term> <term>CoMeRe</term> <term>texto</term> </keywords> <keywords scheme="NA" xml:lang="en"> <term>Computer Mediated Communication</term> <term>CMC</term> <term>Short Message Service</term> </keywords> </textClass> <textDesc xml:lang="en-GB"> <channel mode="w" xml:lang="en-GB"><term ref="#sms">Short Message Service</term></channel> <constitution>The harvest of SMS requires the intervention of a technical partner, Cirrus Informatique, which took in charge the reception of SMS and the transfer to the LCF</constitution> <derivation type="original"/> <domain><note>domain of a message : business or domestic</note></domain> <factuality type="fact"/> <interaction type="complete" active="single"/> <preparedness type="spontaneous"/> <purpose>open, i.e. several possible purposes</purpose> </textDesc> Affordances of a particular textchat environment Nothing particular for the SMS in (2.10) (2.10) <classDecl> <taxonomy> <category xml:id="sms"> <catDesc>Definition of the modality SMS. Type of messages used in SMS.</catDesc> </category> </taxonomy> </classDecl> 2.3.2. Structure of an SMS message: "post" element Since the addressee is not known (as explained in (2.11)), the interaction cannot really be studied. Language used in SMS (with varieties coming out French-France and French-pidgin) may "only" be a subject of study. (2.11) <tagsDecl> <namespace name="XXX"> <tagUsage gi="post">one post corresponds to one SMS.<list> <item><att>xml:id</att>ID of the posting.</item> <item> <att>when</att>is date of message collected by the system, it depend on the date the participant send to the system, but not a date of the conversation. Accordingly, one participant may have sent her messages to her correspondents at different times, but may have assembled her messages and send them together to the server.</item> <item> <att>who</att>is telephone number anonymized. Hence one ID identifies one participant over the whole corpus. If messages sent by the same participant (sender) may be studied, it should be noted that we have no information about the receiver.</item> <item> <att>type</att>type of message cf. taxonomy. </item> </list></tagUsage> - 18 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org </namespace> </tagsDecl> <classDecl> <taxonomy> <category xml:id="sms"> <catDesc>Definition of the modality SMS. Type of messages used in SMS.</catDesc> </category> </taxonomy> </classDecl> 2.3.3. Interactions spaces within the environment Location and time frame In (2.12) we distinguish date and location of people in charge of collecting the data (creation) and the participant location and times (settingDesc). (2.12) <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> Participants (2.13) <particDesc> <listPerson> <head>No information on participants except their IDs and the fact that they live in <region>La Réunion</region>. Before giving her/his SMS, the participant accepted the consent form explicited in <gi>availability</gi>.</head> <person xml:id="cmr-slr-c001-p001"/> <person xml:id="cmr-slr-c001-p002"/> <person xml:id="cmr-slr-c001-p003"/> <person xml:id="cmr-slr-c001-p004"/>< […] - 19 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Examples of interactions As already mentioned it is not really possible to study interactions among participants, but we can follow some authors and their idiosyncratic ways of typing. (2.14) selects 2 different participants and 2 different messages each. For the sake of easy reading, We removed the researcher's annotation (see specific section on annotations hereafter. (2.14) <post xml:id="cmr-slr-c001-a11644" when-iso="2008-06-16T11:59:00" who="#cmrslr-c001-p868" type="sms"> <p>à k e l a d r e s e n v o y e r d e s f l e u r s ?</p> </post> […] <post xml:id="cmr-slr-c001-a11647" when-iso="2008-06-16T12:00:39" who="#cmrslr-c001-p868" type="sms"> <p>e n f o n t d e n t i s t e</p> </post> […] <post xml:id="cmr-slr-c001-a00011" when-iso="2008-04-14T10:17:11" who="#cmrslr-c001-p010" type="sms"> <p>é@??$?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é</p> […] <post xml:id="cmr-slr-c001-a00304" when-iso="2008-04-15T20:23:59" who="#cmr-slr-c001-p010" type="sms"> <p>...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.</p> 2.4. Email General consideration on the environment, the interaction space will be presented in the next section (3). Here we only consider the post structure. Structure of an email message: "post" element An email has the same basic structure than SMS and chat turn (author, ID, date & time, type). But several other features need to be added: Whether the message was sent in reply of another (post @ref) Subject (head > title ) , main addressee(s) (head > listPerson > person > event @type="SendTo"), addressee who receive a copy of the message (head > listPerson > person > event @type="CopyTo"),, o addressee as black carbon copy (head > listPerson > person > event @type="BCopyTo"), y. o Some LMS (Learning Management systems) used also to provide another feature telling which read the message (open it) (head > listPerson > person > event @type="Read"),. o Eventually an email may have an attached file (trailer > ref @type= "attached_file "). o o o o In order to avoid creating new attribute or element, we decided to include this information in a head and a trailer element. These are elements of div. The definition of post needs to be modified. - 20 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org (2.15) <post xml:id="cmr-Simu-Aq-At-Outbox-0004" when="2001-05-01T10:26:00" who="#cmrSimu-At" type="email-message" ref="#cmr-Simu-Aq-At-Inbox-0003"> <head> <title>mon bio</title> <listPerson> <person corresp="#cmr-Simu-Al2"> <event type="SendTo" /> <label>SendTo</label> </person> <person corresp="#cmr-Simu-Al2"> <event type="Read" when="2001-05-01T10:26:00"> <label>Read</label> </event> </person> </listPerson> </head> <p>Bonjour<name ref="#cmr-Simu-Al2" type="person"><forename>Bruce</forename></name>, .et merci de m'avoir éclairé sur la nature de votre travail. Il ne me semble pas moins passionnant pour autant, et cela doit être une tâche infinie d'anticiper sur les causes des pannes possibles... il doit y avoir tellement de possibilités. A propos des accents, il me semble que les personnes qui utilisent les claviers anglais ont du mal à en mettre dans le courriel. Cela dit, il n'est pas interdit d'ouvrir un fil de discussion sur les accents dans le forum, je suis sûre que vous aurez du succès, car il me semble que c'est une question qui préoccuppe tout le monde ! Amicalement, <name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name> </p> <trailer> <ref type="attached_file">symbols.xls</ref> </trailer> </post> 2.5. Forum General consideration on the environment, the interaction space will be presented in the next section (3). Here we only consider the post structure. Each message / posting is in a thread is either the first message of the thread or can be a response to another one. It has the corresponding features. The difference is simply made by the @ref: a message without a @ref opens a thread. A message which has a @ref is an answer to another message and consequently included into a thread. (2.16) is a message included in a thread, a respond to a previous message (see ref). Several participants read it (list has been shortened here). Therese is an attached file. Note, that in Simuligne, every participant who is mentioned in a message (or textchat or email) has been identified: Laurence herself in her signature and Nick to whom she responded. - 21 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org (2.16) <post xml:id="cmr-Simu-Gall_e2a2_hymne-234" when="2001-06-06T08:17:00" who="#cmr-Simu-Gn2" type="forum-message" ref="#cmr-Simu-Gall_e2a2_hymne-209"> <head> <title>constitution des groupes</title> <listPerson> <person corresp="#cmr-Simu-Gt"> <event type="Read" when="2001-06-06T08:17:00"> <label>Read</label> </event> </person> [….] </head> <p><name ref="#cmr-Simu-Gl4" type="person"><forename>Nick</forename></name>, Est ce que c'est de l'humour anglais? Tu risques de le regretter Amicalement <name ref="#cmr-Simu-Gn2" type="person"><forename>Laurence</forename></name></p> <trailer> <ref type="attached_file">symbols.xls</ref> </trailer> </post> - 22 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 3. More complex interaction space 3.1. Distinct interactions spaces within one common framework The corpus entitled cmr-simuligne has been built out of all interaction data coming from an online language learning experiment, Simuligne. Data have been extracted from the LETEC (learning and teaching corpus) Simuligne (Reffay et al., 2009). 67 participants (language learners, teachers, natives – i.e. language experts - ) followed the same learning scenario, but were divided into 4 groups. Hence there were 4 distinct interactions spaces, where people did the same activities, on the same platform, namely anLMS. Participants in one group could only communicate with members of the group. These top level interaction spaces have been encoded as distinct "texts" (text element), each included within one TEI element and the whole within a teiCorpus file. Every text is organized around sets of learning activities. An activity structure (included into a div of the type "ActivityStructure" (in reference of the terminology used by the standard IMS-LD) can be composed of a set of learning activities or one learning activity. Consequently division of type of ActivityStructure can be nested. A learning activity may include one or several modalities (email, chat or forums). For example, figure 3.1.a displays the different level of the division cmr-Simu-Ga-SG (type ActivityStructure), the top level activity structure, down to the basic learning activity cmrSimu-GA-E2A2_read_hymne (type ActivityStructure). This learning activity used only one forum. All its messages have been included in a division of type forum (cmr-SimuGall_e2a2_hymne). Figure 3.1.b displays the structure of another learning activity which used 2 modalities for communications, forum and textchat. During this activity, interactions happened in one forum and 3 chat rooms, corresponding to the 4 divisions listed in the figure (one of type forum and three of type chat). - 23 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org a b Figure 3.1: Nested activity structures (a) and example of one learning activity based on 2 modalities and 4 locations (b). 3.2. General features of the environment General features of interaction and substance of the corpus In the profileDesc, where we used to define the kind of interaction afforded by environment based on only one modality, we define (3.1) the way the corpus has been built and the general interaction framework and we refer to the LMS, entitled WebCT - 24 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org (3.1) <textClass> <keywords scheme="OLAC"> <term type="olac:linguistic-field">applied_linguistics</term> <term type="olac:linguistic-field">discourse_analysis</term> <term type="olac:linguistic-field">text_and_corpus_linguistics</term> <term type="olac:linguistic-type">primary_text</term> <term type="olac:discourse-type">dialogue</term> </keywords> <keywords scheme="NA" xml:lang="fr-FR"> [….] </keywords> <keywords scheme="NA" xml:lang="en"> <term>Computer Mediated Communication</term> <term>CMC</term> <term>LMS</term> <term>discussion forum</term> <term>email</term> <term>textchat</term> <term>online language learning</term> <term>LETEC</term> </keywords> </textClass> <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> Affordances of the LMS environment (3.2) displays the definition of the environment, the LMS entitled WebCT, and then its 3 modalities (textchat, email – not detailed here, and forum). Note that it is not a general definition of the LMS, but of subpart of it related to communication tools. Contrastingly with examples in the previous section the kind of interaction afforded by one modality has been described within the taxonomy (element textDesc). - 25 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org (3.2) <classDecl> <taxonomy> <category xml:id="WebCT"> <catDesc>WebCT Online Learning Management System,version 3.1.0.8, 2001. In this corpus are described communication tools (all textual modalities) of the LMS.</catDesc> <category xml:id="ActivityStructure"> <catDesc>The Interaction Spaces of one learning group is included in one <gi>text</gi>. It is organized around set of learning activities. An activity structure (included into a <gi>div</gi>) <ref target="IMS-LD"/>can be composed of set of learning activties or one learning activity (hence <gi>div</gi> of Activity structure can be nested. A learning activity may include one or several modalities (email, chat or forums), here after described.</catDesc> <category xml:id="chat"> <catDesc>Interactions (sets of elements <gi>post</gi>)) in the modality textchat are organized in chatrooms (<gi>div</gi>level), which have a title. Hereafter are types of posts. <textDesc xml:lang="en-GB"> <channel mode="w" xml:lang="en-GB"><term>textchat</term></channel> <constitution>Messages typed by participants inside a chatroom.</constitution> <derivation type="original"/> <domain type="education"/> <factuality type="fact"/> <interaction type="complete" active="plural" passive="many"><note>Synchronous discussion tool. All members of a group can chat within a chatroom. Chatrooms can only be opeend and closed by tutors / teachers.</note></interaction> <preparedness type="spontaneous"/> <purpose degree="high"><note>related to the guidelines of the learning activity</note></purpose> </textDesc> </catDesc> <category xml:id="chat-message"/> <category xml:id="chat-event"> <category xml:id="connexion"> <catDesc>participant enters into the textchat room</catDesc></category> <category xml:id="deconnexion"> <catDesc>participant leaves the textchat room</catDesc></category> </category> <category xml:id="email"> <catDesc>The email is a communication tool integrated within the LMS. Sets of email messages are in a (<gi>div</gi>). […] </catDesc> </category> <category xml:id="email-message"> <catDesc>if a message (<gi>post</gi>) has a <att>ref</att>, then it is a response to a previous one. More details, see <gi>tagsDecl</gi></catDesc> </category> <category xml:id="forum"> <catDesc>A discussion forum has a title and is composed of a set of threads (each one with a title). Sets of messages corresponding to one forum are assembled in one (<gi>div</gi>). <textDesc xml:lang="en-GB"> <channel mode="w" xml:lang="en-GB"><term>form</term></channel> <constitution>Messages typed by participants inside the discussion forum tool of the LMS.</constitution> <derivation type="original"/> <domain type="education"/> <factuality type="fact"/> <interaction type="complete" active="plural" passive="many"><note>Asynchronous discussion tool. All participants within a group can read a message and answer to it. They can also open a thread. Only tutors / teachers can open a forum. Information about who read (opened) a message in a forum is not given by the LMS but has been computed from the internal data base.</note></interaction> <preparedness type="spontaneous"/> <purpose degree="high"><note>related to the guidelines of the learning activity</note></purpose> </textDesc></catDesc> <category xml:id="forum-message"> <catDesc>The first message of a thread is encoded as a <gi>post</gi> which has no <att>ref</att>. Other messages respond to a previous message with an ID given in <att>ref</att>, are thus included in a thread. More idetails, see <gi>tagsDecl</gi></catDesc> </category> […]> - 26 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Structure of "post" element, divisions and "text" (3.3) explains how text, div have been used, the post structure, and for the latter details the structure of the head. (3.3) <tagsDecl> <namespace name="TEI-CMC"> <tagUsage gi="text">One per group for its Interaction Space</tagUsage> <tagUsage gi="div">Divisions have several purposes depending on the <att>type</att> see <gi>classDecl</gi> for details.</tagUsage> <tagUsage gi="post">one post corresponds to one eamil message or one forum message or one texchat turn. <list> <item><att>xml:id</att>ID of the post.</item> <item> <att>when</att>date of the message when created, given by the system</item> <item> <att>who</att>id of the author of the message. Every participant has been describedin the <gi>particDesc</gi>.</item> <item> <att>type</att>type of the post cf. taxononomy. </item> <item><att>ref</att>reference to the post ID to which the current post responded to (for email and forum)</item> <item><gi>head</gi> contains all the rest of the structure of the post, which cannot be described as TEI elements because of the current limited adequacy of TEI to CMC. It is a provisional decision taken in order to limit the number of new elements. These new elements or attributes may appear when the TEI-CMC agrees upon them. <list> <item><gi>title</gi> Title of the forum, or subject of an email.</item> <item><gi>listPerson</gi> list of adressees , one <gi>person</gi> per people and <gi>event</gi> identify the communication feature attached to her/him <list> <item><att>type</att><val>SendTo</val> addressee(s) of an email</item> <item><att>type</att><val>Read</val> who opened (read?) an email or a forum message ?</item> </list></item> </list></item> </list></tagUsage> <tagUsage gi="trailer">At the end of a post when there is an attached file</tagUsage> </namespace> </tagsDecl> - 27 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 3.3. Interactions spaces within the environment Location and time frame (3.4) <creation> <date from="2001-04-09" to="2001-07-06"/> <location type="online_environement"> <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> Description of participants and groups The description of participants is also more complex as shown in the extract (3.5). Every individual participant is described in more details. Every group is listed and the organization and membership of each group appears within the listRelation element. This is fundamental information when one wants to study the interaction among participants of the interaction space. - 28 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org (3.5) <particDesc> <listPerson> <person role="learner" xml:id="Gl1"> <sex>female</sex> <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> - 29 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 4. Anonymisation et identification participants This section has not yet been translated into English. 4.1. Identifier les participants Indiquons tout d'abord que dans les études sur les interactions en ligne, il est important de savoir, lorsqu'un auteur de message / tour de parole mentionne un autre participant, de qui il s'agit exactement. Ce participant étant identifié sans ambiguïté par son code. Ainsi dans le corpus Mulce ce travail d'indentification avait été fait. (4.1) entête du message de courriel non reproduit ici <mcesid:content> Merci beaucoup, <anony:actordesignation actorref="At" person="real" process="CR_18oct07"> <anony:firstname correct="exact" modified="false" type="complete">Anna</anony:firstname> </anony:actordesignation> J'ai reçu mon bio, merci, mais je ne vois pas de commentaires - peut-être circulent-ils encore quelque part dans le cyberespace? à bientôt <anony:actordesignation actorref="Al5" person="real" process="CR_18oct07"> <anony:firstname correct="exact" modified="false" type="complete">Marja</anony:firstname> </anony:actordesignation> P.S. J'aime bien votre 'coucou' - vous êtes tous très sympas à Besançon! Ici, dans mon champ suffolkais (je peux dire ça?), j'entends le coucou tout le temps pendant le mois de mai. </mcesid:content> Il peut être transposé ainsi en TEI. (4.2) <post xml:id="cmr-Simu-Aq-At-Inbox-0008" when="2001-05-02T14:19:00" who="#cmrSimu-Al5" type="email-rMessage" ref="#cmr-Simu-Aq-At-Outbox-0005"> <head> <address ref="#cmr-Simu-At" type="to"/> <title>Votre bio</title> <listPerson> <person corresp="#cmr-Simu-Al5"> <event type="Read" when="2001-0502T14:19:00"> <label>Read</label> </event> </person> <person corresp="#cmr-Simu-At"> <event type="Read" when="2001-0502T14:19:00"> <label>Read</label> </event> </person> </listPerson> </head> <p>Merci beaucoup,<name ref="#cmr-Simu-At" type="person"><forename>Anna</forename></name> J'ai reçu mon bio, merci, mais peut-être circulent-ils encore quelque part dans le cyberespace? à bientôt <name ref="#cmr-Simu-Al5" type="person"><forename>Marja</forename></name> P.S. J'aime bien votre 'coucou' - vous êtes tous très sympas à Besançon! Ici, dans mon champ suffolkais (je peux dire ça?), j'entends le coucou tout le temps pendant le mois de mai. </p></post> Dans le corps de (4.2) on introduit les éléments name et forename pour indiquer qu'il est fait mention dans le message d'un prénom, Anna, et que ce prénom est celui de l'acteur cmrSimu-Al5. Idem pour Marja. On notera le type de name correspondant à une personne. 4.2. Anonymisation dans les corpus déposés Le but de l'anonymisation n'est pas d'enlever toute information permettant d'identifier un individu, ce qui pourrait entraîner des pertes d'information préjudiciables quand ce n'est pas - 30 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org nécessaire de masquer ces informations. Il est d'enlever toute information susceptible de nuire à un individu. Ainsi, par mesure de précaution supprime-t-on tous les patronymes, les numéros de téléphones, lei de travail, si nécessaire, etc. Mais cette opération ne peut des traduire par un simple effacement d'information. Dans le but de préserver au mieux les informations du corpus, l'information effacée doit être remplacée par une autre information qui indique la nature de ce qui a été enlevé. De plus, il convient d'indiquer qui a opéré cette anonymisation. Ce processus pouvant intervenir à différents stades de traitement d'un corpus. Dans CoMeRe, nous avons dû travailler sur cette question en prenant en compte les travaux effectués par les dépositeurs des corpus. Examinons les d'abord. 4.2.1. Anonymisation dans smsalpes Extrait des indications du dépositeur : (4.3) Contenu : Il s’agit de la version anonymisée des sms. L’anonymisation opérée concerne les : NOM Nom propre BLOG Adresse de blog CB Coordonnées bancaires URL Adresse de site Internet personnel MAIL Adresse e-mail ADR Adresse d'habitation personnelle RECHARGE Numéros de recharge mobile TEL Numéro de téléphone COM Numéro de communication CODE Codes divers, digicodes, etc. PRENOM Prénom ou diminutif SURNOM Surnoms personnels désignant un individu Les parties anonymisées sont remplacées par : ***étiquette anonymisation_nb de caractères de la séquence anunymisée*** Lorsque l’anonymisation concerne un prénom, on y ajoute le n° d’ordre du lexique des prénoms du corpus : ***PRENOM_n° d’ordre_nb de caractères de la séquence anonymisée*** Exemple : (4.4) <id> 563 <Id_Envoyeur>288726353160825</Id_Envoyeur> <Texte_Anonymise>Bonjour ***PRENOM_93_6***, c'est ***PRENOM_1050_7*** et les 3 zigotos, on est en retard, ***PRENOM_1166_4******PRENOM_1166_5******PRENOM_1166_6******PRENOM_1166_4*** aussi, on se depeche, mais tu peux dormir un peu/te promener. On est la ds 25 min ? Les autres vers 11h15 !</Texte_Anonymise> </id> 4.2.2. Anonymisation dans smslareunion (4.5) Anonymisations {PRENOM} {NOM} {num_tél} - 31 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 4.2.3. Anonymisation dans Mulce Exemple : (4.6) <message idmess="i78" mess_pere="inull" date="4 5 2001" jour="Vendredi" heure="9h50" nom_auteur="Al5">Merci <Actordesignation ActorRef = “At” person = “Real” process = “demoCR070513”><Firstname Type = “Complete” Correct = “exact” Same = “True”>Anna</firstname></Actordesignation>! J'ai les deux navigateurs sur mon ordi - Netscape et Internet Explorer, et donc la prochaine fois je vais télécharger avec Netscape. J'ai toujours préféré Internet Explorer, je ne sais pas pourquoi - mais je peux toujours m'arranger!! <Actordesignation ActorRef = “Al5” person = “Real” process = “demoCR070513”><Firstname Type = “Complete” Correct = “exact” Same = “True”>Marja</firstname><Lastname Type = “Complete” Correct = “exact” Same = “False”> Golly</Lastname></Actordesignation></message> 4.2.4. Anonymisation dans Alipe Alipe (Liégeoiss, Chanier & Chabanal, 2013) est un corpus oral qui ne fait pas partie de CoMeRe, mais ayant été développé au LRL, nous y avions déjà introduit en TE une description de l'anonymisation. En voici un extrait de description dans le TeiHeader. - 32 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org (4.7) <fsDecl type="anonymisation"> <fsDescr>L'anonymisation est utilisée afin de préserver le caractère privé de certains passages des enregistrements. Ce codage permettra de donner une idée au lecteur sur le contexte original.</fsDescr> <fDecl name="Identity" xml:id="Ity"> <fDescr>Nous contextualiserons l'anonymisation en précisant s'il s'agit : - d'une personne : Pers - d'une entreprise : Busi - d'un évènement personnel et confidentiel, comme une maladie ou un décès : Event - d'une adresse ou d'un lieu : Place </fDescr> <vRange> <vAlt> <symbol value="Pers"/> <symbol value="Busi"/> <symbol value="Event"/> <symbol value="Place"/> </vAlt> </vRange> </fDecl> <fDecl name="Original" xml:id="Ori"> <fDescr>Nous contextualiserons l'anonymisation informant le type d'information qui a été anonymisée parce qu'elle permettait d'identifier une personne, une entreprise ou un évènement. Nous indiquerons s'il s'agit : - d'un prénom : Name - d'un patronyme : Surname - d'un nom d'entreprise : BusiName d'un rôle : Role - d'un lieu : PlaceName De plus, la transcription originale sera remplacée dans le corps du texte par un élément qui permettra la référence. Par exemple, si nous modifions un prénom féminin, nous mettrons dans le corps du texte [_Chloe1_]. Si nous modifions l'adresse du lieu de travail de la mère, nous mettrons dans le corpus du texte [_Adresse-de-Mot_]. Ainsi, nous utiliserons toujours le même élément afin de se référer à la même personne ou au même lieu. </fDescr> <vRange> <vAlt> <symbol value="Name"/> <symbol value="Surname"/> <symbol value="Role"/> <symbol value="BusiName"/> <symbol value="PlaceName"/> </vAlt> </vRange> </fDecl> </fsDecl> Ainsi utilisé : (4.8) 4.3. Anonymisation dans CoMeRe De façon à prendre ne considération l'ensemble des travaux menés par les dépositeurs de corpus CoMeRe, nous allons utiliser, comme dans Alipe une structure de traits de la façon suivante. Le code de (4.9) fait partie du teiHeader de nos corpus. Nous pouvons ainsi : indiquer qui a fait l'anonimysation, renseigner le type d'information qui a été enlevée, la remplacer dans le texte par une infirmation répétant cette information, préserver les informations de smsalpes sur le nombre d'occurrences et le nombre de caractères. - 33 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org (4.9) <fsdDecl> <fsDecl type="anonymisation"> <fsDescr>XXX</fsDescr> <fDecl name="anonyString"> <fDescr>XXX</fDescr> <vRange> <vAlt> <string>[_forename_]</string> <string>[_surname_]</string> <string>[_addName_]</string> <string>[_tel_]</string> <string>[_email_]</string> <string>[_url_]</string> <string>[_code_]</string> <string>[_address_]</string> </vAlt> </vRange> </fDecl> <fDecl name="origfrom"> <vRange> <vAlt> <string>Depositor</string> <string>Editor</string> </vAlt> </vRange> </fDecl> <fDecl name="numCharacter"> <vRange> <numeric value="1" max="100000000" trunc="true"/> </vRange> </fDecl> <fDecl name="numOrder"> <vRange> <numeric value="1" max="100000000" trunc="true"/> </vRange> </fDecl> </fsDecl> </fsdDecl> En voici des exemples d'application dans nos corpus. (4.10) est un extrait de smsalpes. (4.10) <post xml:id="cmr-smsalpes-c001-a8" when-iso="2010-10-01" who="#cmr-smsalpes-c001-p288726353160825" type="sms"> <p>Bon, d'accord ! Elle est ou miss <fs type="anonymisation"> <f name="numOrder"><numeric value="522"/></f> <f name="numCharacter"><numeric value="5"/></f> <f name="origfrom"><string>Depositor</string></f> <f name="anonyString"><string>[_forename_]</string></f> </fs> ? Usa ? On se retrouve ds 1 coin sympa ? Qu'est-ce qui t'arrange ?</p> </post> - 34 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 5. Déclarer en TEI des annotations faites à la main : Corpus smslareunion This section has not yet been translated into English. 5.1. Rappel des consignes données par Gudrun Informations contenues dans les colonnes du fichier Excel : Colonne 1 : N° SMS attribué suivant l’apparition au mois de mai Colonne 2 : ID = numéro de téléphone véritable ou codé (selon les entreprises) Colonne 3 : DATE de réception des SMS par le site de l’enquête (et non de leur envoi véritable forcément) Colonne 4 : sms original anonymisé (cf. plus bas) Colonne 5 : sms transorthographié & balisé (cf. plus bas) Colonne 6 : 2° transcription pour 'flottant' (Fc = version pour le créole / Ff = version pour le français) Colonne 7 : traductions pour le créole vers le français Colonne 8 : traduction pour les autres langues (en l’occurrence, un passage en hindi) Balises de langues <a xxx /a> : passage en anglais <c xxx /c> : passage en créole <f xxx /f> : passage en français <F xxx /F> : passage en « flottant », i.e. interprétable comme étant du français et du créole ; dans ce cas, la colonne principale contient l’interprétation première, et la colonne à côté contient la seconde, même si dans beaucoup de cas de figure, c’est le statut de « flottant » qui prévaut (impossibilité de trancher pour l’une ou l’autre langue). La double transcription figure pour révéler ce statut particulier (très fréquent dans les zones franco-créolophones). Quand il est possible, la transcription Fc donne la version créole et dans la colonne suivant Ff la version française. Si la graphie ne change pas, il n’y a que la version F. <h xxx /h> : passage en hindi Autres balises <s xxx /s> : smiley Omissions Forclusif de négation : [ne] Pronoms sujet : [je], [tu], [il] Pronoms compléments : [le], [lui], [en], [y] Prépositions : [à], [sur] Complémenteur : [que] Autres : [c’est], [peux], … - 35 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 5.2. Choix des annotations en TEI Nous avons fait le choix d'insérer ces annotations du chercheur dans le message SMS, donc dans le post à la suite du contenu proprement dit du SMS. Ces ajouts figurent dans l'élément reg qui étiquette le travail de transposition orthographique. Il y a une première transposition complète du message. Le chercheur peut avoir essayé d'identifier les langues avec certitude ou non ("flottant"). Le flottant peut ensuite être réinterprété dans l'élément add. Une partie de traduction en français peut également figurer dans ce dernier élément. Nous n'avons ainsi rien perdu de l'annotation manuelle du chercheur. Mais attention celle-ci peut être incomplète. 5.2.1. Déclaration des annotations dans le teiheader (5.1) <tagsDecl> <namespace name="TEI-CMC"> <tagUsage gi="post">one post corresponds to one SMS.<list> <item><att>xml:id</att>ID of the posting.</item> […] </tagUsage> <tagUsage gi="reg">This element appears inside the <gi>post</gi> and is used to encode, after the content of the SMS, the manual annotation. See <gi>interpretation</gi>. <list> <item>The attribute <att>type</att><val>transortho</val> indicate that it corresponds to a normalization, from an orthographic standpoint, of the content of the SMS</item> <item><gi>del</gi>corresponds to an omitted word like <w>ne</w>, <w>je/tu/il</w>], <w>le/lui/en/y</w>, <w>à/sur</w>, <w>que/c'est/peux</w>, etc. </item> <item><gi>seg</gi> <att>xml:lang</att> phrase normalized either in French or French pidgin (Créole de la Réunion)</item> <item><gi>seg</gi> <att>cert</att> phrase (labelled as "flottant") where there is some uncertainty about which language has been used. When <val>unknown</val>, language cannot be determined. When <val>medium</val>, the researcher guesses that it can be either French or Pidgin (see the <att>xml:lang</att>).</item> </list></tagUsage> <tagUsage gi="add">This element appears inside <gi>reg</gi>, after the main orthographic interpretation.<list> <item><att>type</att><val>F</val>specify an alternate interpretation of a previous phrase ("flottant")which has been attributed to a given language: Pidgin if the previous version was French, or vice-versa. This time the <gi>seg</gi> appears with an <att>cert</att> and a reduced degree of certainty: <val>low</val></item> <item><att>type</att><val>trad</val>: translation in French of part of the SMS (not necessarily the whole contents of the SMS). There is no indication of the coverage of the translation, i.e. whether it is a full or partial translation</item> </list></tagUsage> </namespace> </tagsDecl> - 36 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 5.2.2. Annotations simples : transposition orthographique Le tableau 5.1 indique comment apparaît les annotations du chercheurs dans Excel sur une exemple, puis (5.2) comment cela a été traduit en TEI. Col4 Oui gé pas fé exprès, pas vu... Bon app. Col5 Oui j' [ne] ai pas fait exprès, pas vu... Bon app'. Col6 Col7 Col8 Tableau 1 : colonnes du tableur portant sur un message (5.2) <post xml:id="cmr-slr-c001-a12569" when="2008-06-30T08:13:15" who="#cmr-slr-c001-p000844" type="sms"> <p>Oui gé pas fé exprès, pas vu... Bon app</p> <reg type="transortho">Oui j' <del>ne</del> ai pas fait exprès, pas vu... Bo app'.</reg> L'annotation est incluse dans le message. Pour ce faire, on utilise l'élément reg afin d'indiquer qu'il s'agit d'une régularisation de type transposition orthographique. On notera que les crochets autour de l'omission ont été enlevés et l'élément del inséré. Col4 A cet heur de la nui,ma brume de pensée inonde mn espri d1 seule image,la tienne. Col5 <f A cette heure de la nuit, ma brume de pensée inonde mon esprit d’une seule image, la tienne /f> Col6 Col7 Col8 Tableau 2: autre exemple provenant du tableur et sa traduction en (5.3) (5.3) <post xml:id="cmr-slr-c001-a2837" when="2008-05-01T02:14:26" who="#cmr-slr-c001-p000320" type="sms"> <p>A cet heur de la nui,ma brume de pensée inonde mn espri d1 seule image,la tienne.</p> <reg type="transortho"><seg xml:lang="fra"> A cette heure de la nuit, ma brume de pensée inonde mon esprit d’une seule image, la tienne</seg></reg> </post> Une indication de langue étant donnée, elle est codée suivant l'ISO 639-2. La partie sur laquelle porte cette annotation est balisée avec l'élément seg. - 37 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Col4 Coucou.Ou coné out maraine i arive 2m1? Col5 <F Coucou. /F> <c Ou koné out marraine i ariv demin ?/c> Col6 Col7 tu sais que ta marraine arrive demain? Col8 Tableau 3 : exemple avec sa traduction en (5.4) (5.4) <post xml:id="cmr-slr-c001-a2847" when="2008-05-01T08:43:30" who="#cmr-slr-c001-p000426" type="sms"> <p>Coucou.Ou coné out maraine i arive 2m1?</p> <reg type="transortho"><seg cert="unknown">Coucou.</seg><seg xml:lang="cpf">Ou koné out marraine i ariv demin ?</seg> <add type="trad"><seg xml:lang="fra"> tu sais que ta marraine arrive demain?</seg></add></reg> L'indication de la partie du message comme "flottante" ne donne pas d'indication sur le fait que ce pourrait provenir du créole réunionnais ou du français de France ce segment est donc noté comme ayant un trait de certitude inconnu. Le second segment est lui en créole, noté cpf pour indiquer qu'il s'agit d'un créole dérivé du français. La traduction en français de France est traitée comme un ajout aux annotations précédentes (add de type trad). On notera que cette traduction est partielle, puisque le terme Coucou est absent. Col4 Merci.toi osi. Col5 <Ff Merci. /Ff> <f Toi aussi. /f> Col6 <Fc Mèrsi. /Fc> Col7 Col8 Tableau 4 : exemple avec sa traduction en (5.5) (5.5) <post xml:id="cmr-slr-c001-a2838" when="2008-05-01T05:45:02" who="#cmr-slr-c001p000463" type="sms"> <p>Merci.toi osi.</p> <reg type="transortho"><seg xml:lang="fra" cert="medium"> Merci. </seg><seg xml:lang="fra"> Toi aussi. </seg><add type="F"><seg xml:lang="cpf" cert="low">Mèrsi.</seg></add></reg> Le premier flottant est indiqué comme pouvant être du français. On l'indique avec un degré de certitude égal à medium. L'interprétation de ce flottant dans la colonne suivante est traitée comme un ajout (de type F) et cette fois l'indication du fait que cela peut être du créole avec un degré de certitude bas (low). Cette lecture alternative entre pour Merci pourrait être noté en TAI avec un cela compliquerait les traitements. - 38 - choice, mais TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org Col4 La kaz Col5 <Fc La kaz /Fc> Col6 <Ff La case /Ff> Col7 Col8 Tableau 5 : exemple avec sa traduction en (5.6) (5.6) <post xml:id="cmr-slr-c001-a2851" when="2008-05-01T09:04:52" who="#cmr-slr-c001-p000348" type="sms"> <p>La kaz</p> <reg type="transortho"><seg xml:lang="cpf" cert="medium">La kaz</seg><add type="F"><seg xml:lang="fra" cert="low">La case</seg></add></reg> Cas identique avec simple inversion des probabilités d'interprétation entre français et créole. Col4 Oui ver20h mc do st benoit vu ke mi mange la ba. tu mange avan de venir? Tu me sone kan t la? Col5 <Ff Oui vers 20h Mac Do Saint Benoît vu que /Ff> <c mi manj la ba. /c> <f Tu manges avant de venir ? tu me sonnes quand t’es là ? /f> Col6 <Fc Wi vèr 20h Mac Do Sin Benoi vu ke /Fc> Col7 je mange là-bas Col8 Tableau 6 : exemple avec sa traduction en (5.7) (5.7) <post xml:id="cmr-slr-c001-a2860" when="2008-05-01T09:49:36" who="#cmr-slr-c001-p000424" type="sms"> <p>Oui ver20h mc do st benoit vu ke mi mange la ba. tu mange avan de venir? Tu me sone kan t la?</p> <reg type="transortho"><seg xml:lang="fra" cert="medium">Oui vers 20h Mac Do Saint Benoît vu que </seg> <seg xml:lang="cpf">mi manj la ba.</seg> <seg xml:lang="fra">Tu manges avant de venir ? tu me sonnes quand t’es là ? </seg><add type="F"><seg xml:lang="cpf" cert="low"> Wi vèr 20h Mac Do Sin Benoi vu ke</seg></add><add type="trad"><seg xml:lang="fra">je mange là-bas</seg></add></reg> </post> Dans l'exemple (5.7), on trouve un premier ajout concernant l'interprétation du flottant, puis un deuxième ajout correspondant à une traduction partielle en français. - 39 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 6. Other things Please ignore the contents of this section. Blog A blog is a multimodal text. It can contain images, videos, etc. It has a title, etc. It contains postings of 2 types: “billet” / main message and “commentaires” / comments attached to a billet. A billet may have a label, keywords, categories, etc. Which TEI element should be chosen for describing it. Its channel will have the “m” value and we will have (Ex10) <posting xml:id=”10403-blogue” synch=”#TL2501” who=”#Strophe21” type=”#blogmessage”> <header> <elements for label, keyworks , categories, > <p>!f3</p></posting> </posting> <posting xml:id=”10404-blogue” synch=”#TL2501” who=”#Srtt” type=”#blog-comment” @father=”#10403-blogue “ etc..> Oral discussion If participants use, for example, Skype only orally (i.e. ignore other modalities such as the textchat, then interaction among participants may be described within a division, but certainly not a thread nor logfile, because acts does not appear as en bloc actions. Of course the speech part of TEI should be used. (Ex11) <div type= ?? … > <u who=..> <u ..> </div> Environment with multi-modalities Warning: the enbloc nature is a very strong commitment. It implies that acts occurred in the corresponding interaction space will be dramatically different from non enbloc acts in multimodal environment. It implies that there is no link to(att.duration.w3c (@dur)) (att.duration.iso (@dur-iso)), att.timed (@start, @end). In Mulce we never adopted this standpoint, but considered everything at the same level with act having all a @start, but not necessarily an @end. Annotations Important decisions should be made for CoMeRe about the way of annotating corpora before January 2014. On the beginning of 2014 NLP processing will start. There is an ongoing discussion between French researchers of IRCOM and ORTOLANG on one side and the ISO/DIN European group. They discuss about the way of adding tiers (cf. ELAN software) of annotation (phono, morpho, POS, etc.) to the u element and have relationships with tools than help describing these tiers of annotations. - 40 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 7. Appendix Absolute time Time attached to interaction acts may be given in absolute or relative format (with respect to the beginning time of a video or audio file, where the later beginning time is defined in absolute format), but times for interaction space must be given in absolute format in order to allow computation between interactions occurring in different spaces or other contextual events. ISO 1801 must be used, eg: 2005-04-22T01:00:00-05:00 or 2005-04-22T06:00:00Z Of course seconds or fractions of seconds may be added. Data should also comply to this standard recommended by the W3C): YYY-MM-DD. Time is defined by the network server. Different time zones among participants interacting may be noted as a property attached to the description of participants. Mode, change • Attribute @mode : extension to icone, nonverbal, etc. - 41 - TEI-CMC (http://wiki.tei-c.org/index.php/SIG:Computer-Mediated_Communication), CoMeRe (Communication Médiée par les Réseaux, http://comere.org 8. References 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 Chanier, T. & Wigham, C.R. (2011). (editors) Learning and Teaching Corpus (LETEC) of ARCHI21. Mulce.org : Clermont Université. [oai:mulce.org:mce-archi21-letec-all ; http://repository.mulce.org] Chanier, T., Reffay, C., Betbeder, M-L., Ciekanski, M. & Lamy, M-N. (2009) . LETEC (Learning and Teaching Corpus) Copéas. Mulce.org : Clermont Université. [oai:mulce.org:mce-copeas-letec-all ; http://repository.mulce.org] Chanier, T., Vetter. A. (2006). "Multimodalité et expression en langue étrangère dans une plate-forme audiosynchrone". Apprentissage des langues et Système d'Information et de Communication (Alsic), vol. 9. pp 61101. DOI : 10.4000/alsic.270 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. 162182. doi:10.1017/S0958344008000426 http://edutice.archives-ouvertes.fr/edutice-00200851 Falaise, A. (under structuration, 2014). Corpus CoMeRe on textchat channel of the GetAlp community. cmrgetalp_org Reffay, C. , Chanier, T.(2003)."How social network analysis can help to measure cohesion in collaborative distance-learning", Proceeding of Computer Supported Collaborative Learning conference (CSCL'2003), June, Bergen, Norway. Kluwer Acedemic Publisher. pp 343-352 ; http://edutice.archives-ouvertes.fr/edutice00000422 Reffay, C. Chanier, T. Lamy, M.-N. & Betbeder, M.-L. (2009). LETEC (Learning and Teaching Corpus) Simuligne. Mulce.org : Clermont Université. [http://repository.mulce.org, oai:mulce.org:mce.simu.all.all] 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 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 - 42 -