Topics in Language Resources for Translation ... - ymerleksi - home

More documents

Recommendations

Info

Chapter 10. Standardising multilingual data 159chosen “Data Categories”, as a means of ensuring interoperability between severalmultilingual applications and corpora. Eachtypeofstandardstructureisdescribedby means of a three-tiered information structure that describes:– a metamodel, which represents a hierarchy of structural nodes which are relevantfor linguistic description;– several specific information units that can be associated with each structuralnode of the metamodel;– several relevant annotations that can be used to qualify some part of the valueassociated with a given information unit.4.1 What is a metamodel?A metamodel does not describe one specific format, but acts as a high level mechanismbased on the following elementary notions: structure, information andmethodology. The metamodel can be defined as a generic structure shared byall other formats and which decomposes the organisation of a specific standardinto basic components. A metamodel should be a generic mechanism for representingcontent within a specific context. Actually, a metamodel summarises theorganisation of data.The structuring elements of the metamodel are called “components” and theymay be “decorated” with information units. A metamodel should also comprisea flexible specification platform for elementary units. This specification platformshould be coupled to a reference set of descriptors that should be used to parameterisespecific applications dealing with content.4.2 What is a data category?A metamodel contains several information units related to a given format, whichwe refer to as “Data Categories”. A selection of data categories can be derived as asubset of a Data Category Registry (DCR) (ISO 12620). The DCR defines a set ofdata categories accepted by an ISO committee. The overall goal of the DCR is notto impose a specific set of data categories, but rather to ensure that the semanticsof these data categories is well defined and understood.A data category is the generic term that references a concept. There is oneand only one identifier for a data category in a DCR. All data categories arerepresented by a unique set of descriptors. For example, the data category /languageIdentifier/indicates the name of a language which is described by 2 (ISO639-1) or 3 (ISO 639-2) digits. A Data Category Selection (DCS) is needed in orderto define, in combination with a metamodel, the various constraints that applyto a given domain-specific information structure or interchange format. A DCS
160 Samuel Cruz-Lara et al.and a metamodel can represent the organisation of an individual application, theorganisation of a specific domain.4.3 Methods and representationThe way to actually implement a standard is to instantiate the metamodel incombination with a set of chosen data categories (DCS). This includes mappingsbetween data categories and the vocabularies used to express them (e.g., as an XMLelement or a database field). Data category specifications are, firstly used to specifyconstraints on the implementation of a metamodel instantiation, and secondlyto provide the necessary information for implementing filters that convert oneinstantiation to another. If the specification also contains styles and vocabulariesfor each data category, the DCS then contributes to the definition of a full XMLinformation model which can either be made explicit through a schema representation(e.g., a W3C XML schema), or by means of filters allowing the production ofa “Generic Mapping Tool” (GMT) representation. The architecture of the metamodel,whatever the standard we want to specify, remains unchanged. What arevariable are the data categories selected for a specific application. Indeed, the metamodelcan be considered in an atomic way, in the sense that starting from a stablecore, a multitude of data can be worked out for plural activities and needs.5. Specifying the Multi Lingual Information FrameworkLinguistic structures exist in a wide variety of formats ranging from highly organiseddata (e.g., translation memory) to loosely structured information. The representationof multilingual data is based on the expression of multiple views representingvarious levels of linguistic information, usually pointing to primary data(e.g., part-of-speech (POS) tagging) and sometimes to one another (e.g., references,annotations). The following model identifies a class of document structuresthat could be used to cover a wide range of multilingual formats, and provides aframework that can be applied using XML.All multilingual standards have a rather similar hierarchical structure but theyhave, for example, different terms and methods of storing metadata relevant tothem. MLIF is being designed in order to provide a generic structure that canestablish a basic foundation for all these standards. From this high-level representationwe are able to generate, for example, any specific XML-based format: we canthus ensure the interoperability between several standards and their committedapplications.
Page 3 and 4:
Benjamins Translation Library (BTL)
Page 5 and 6:
8 TMThe paper used in this publicat
Page 7 and 8:
VITopics in Language Resources for
Page 9 and 10:
VIII Topics in Language Resources f
Page 11 and 12:
XTopics in Language Resources for T
Page 13 and 14:
XIITopics in Language Resources for
Page 15 and 16:
2 Lynne Bowker and Michael Barlowde
Page 17 and 18:
4 Lynne Bowker and Michael BarlowFi
Page 19 and 20:
6 Lynne Bowker and Michael Barlow2.
Page 21 and 22:
8 Lynne Bowker and Michael BarlowOn
Page 23 and 24:
10 Lynne Bowker and Michael Barlow4
Page 25 and 26:
12 Lynne Bowker and Michael Barlowb
Page 27 and 28:
14 Lynne Bowker and Michael Barlows
Page 29 and 30:
16 Lynne Bowker and Michael Barlowp
Page 31 and 32:
18 Lynne Bowker and Michael Barlowt
Page 33 and 34:
20 Lynne Bowker and Michael Barlowg
Page 35 and 36:
22 Lynne Bowker and Michael BarlowM
Page 37 and 38:
24 Silvia Hansen-Schirraphenomenon;
Page 39 and 40:
26 Silvia Hansen-Schirratreebank pr
Page 41 and 42:
28 Silvia Hansen-Schirracurrently a
Page 43 and 44:
30 Silvia Hansen-Schirrawhichaltern
Page 45 and 46:
32 Silvia Hansen-Schirra(1) We cont
Page 47 and 48:
34 Silvia Hansen-Schirrarealisation
Page 49 and 50:
36 Silvia Hansen-Schirratranslation
Page 52 and 53:
chapter 3Corpora for translator edu
Page 54 and 55:
Chapter 3. Corpora for translator e
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68:
Page 71 and 72:
58 Belinda Maiahindsight, one can n
Page 73 and 74:
60 Belinda Maiabeen translated by m
Page 75 and 76:
62 Belinda Maiastudy reformulations
Page 77 and 78:
64 Belinda MaiaSearchablecorporaenc
Page 79 and 80:
66 Belinda Maia- Find definition ca
Page 81 and 82:
68 Belinda MaialishaEuropeanMaster
Page 83 and 84:
70 Belinda MaiaMaia, B. and L. Sarm
Page 85 and 86:
72 Carme Colominas and Toni Badiadi
Page 87 and 88:
74 Carme Colominas and Toni Badiala
Page 89 and 90:
76 Carme Colominas and Toni Badiath
Page 91 and 92:
78 Carme Colominas and Toni Badiath
Page 93 and 94:
80 Carme Colominas and Toni BadiaTa
Page 95 and 96:
82 Carme Colominas and Toni BadiaAs
Page 97 and 98:
84 Carme Colominas and Toni BadiaFi
Page 99 and 100:
86 Carme Colominas and Toni Badiaco
Page 101 and 102:
88 Carme Colominas and Toni BadiaVa
Page 103 and 104:
90 Rachélle GautonIzwaini (2003:17
Page 105 and 106:
92 Rachélle Gautonneeded by the Ba
Page 107 and 108:
94 Rachélle GautonThese electronic
Page 109 and 110:
96 Rachélle Gautonthat of Bantu la
Page 111 and 112:
98 Rachélle GautonSeeagainFig.1for
Page 113 and 114:
100 Rachélle GautonLocke, translat
Page 115 and 116:
102 Rachélle GautonHaving to work
Page 117 and 118:
104 Rachélle Gautonmore, after suc
Page 119 and 120:
106 Rachélle GautonMcEnery, A. and
Page 121 and 122: 108 Marie-Josée de Saint Roberta c
Page 123 and 124: 110 Marie-Josée de Saint Robertpre
Page 125 and 126: 112 Marie-Josée de Saint Robertlef
Page 127 and 128: 114 Marie-Josée de Saint Robertcap
Page 129 and 130: 116 Marie-Josée de Saint Robertinf
Page 131 and 132: 118 Marie-Josée de Saint Roberttra
Page 134 and 135: chapter 8Global content managementC
Page 136 and 137: Chapter 8. Global content managemen
Page 148 and 149: chapter 9BEYTransA Wiki-based envir
Page 150 and 151: Chapter 9. BEYTrans 137Trans system
Page 152 and 153: Chapter 9. BEYTrans 1391. Facilitat
Page 154 and 155: Chapter 9. BEYTrans 141lators to ch
Page 156 and 157: Chapter 9. BEYTrans 1435.2 Translat
Page 158 and 159: Chapter 9. BEYTrans 1456. BEYTrans:
Page 160 and 161: Chapter 9. BEYTrans 1476.2.2 Multil
Page 162 and 163: Chapter 9. BEYTrans 149Bey, Y., C.
Page 164 and 165: chapter 10Standardising the managem
Page 166 and 167: Chapter 10. Standardising multiling
Page 186 and 187: chapter 11Tagging and tracing Progr
Page 188 and 189: Chapter 11. Tagging and tracing Pro
Page 208 and 209: chapter 12Linguistic resources and
Page 210 and 211: Chapter 12. Linguistic resources an
Page 222 and 223:
Chapter 12. Linguistic resources an
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
IndexAAfrican language translatorX,
Page 230 and 231:
Index 217Expert Advisory Group onLa
Page 232 and 233:
Index 219open standards 206, 208,21
Page 234 and 235:
Benjamins Translation LibraryA comp
Page 236:
27 Beylard-Ozeroff, Ann, Jana Král
show all

Topics in Language Resources for Translation ... - ymerleksi - home

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?