I would first like to thank my supervisor, Dr. Richard F. E. Sutcliffe, for his constant support. Without his help this project would not come to light today. Many thanks also to the University of Limerick who have at all times provided me with everything that I have needed to develop this work.
I would also like to thank the CASA staff who kindly showed me around their headquarters and provided me with essential material for this research.
Finally, I would like to express my gratitude to my parents and my brother, José, and his wife, Laura, who have always encouraged and supported me in the development of this thesis.

A Controlled Language is a subset of a natural language which has a restricted lexicon and controlled grammatical structures. The objective of a Controlled Language is to improve readability, standardisation, accessibility and translatability of documentation.
In the last 30 years, there has been a steady increase in the design of Controlled Languages and related applications in different domains. A well-known example is the language designed by AECMA (European Association of Aerospace Industries) in order to increase the readability of aircraft maintenance manuals. Some attempts have been made to produce specifications for languages other than English. Examples include FREM (Français
Rationalise Entendu Modulaire) for French aircraft maintenance manuals, ScaniaSwedish for truck maintenance documentation, and Controlled Siemens Documentary German for software documentation. However, no research has been undertaken on the development of a Controlled Spanish.
The objective of the work is to design a Controlled Spanish for aircraft maintenance manuals which is similar to AECMA Simplified English and FREM. The stages involved in the work include the development of a number of writing rules in conjunction with a dictionary, and the design and evaluation of a Controlled Spanish checker to verify conformance with some of the rules. The result comprises the Simplified Technical Spanish
(STS) Specification, which includes 36 rules, the STS General Vocabulary, which consists of a list of 875 words, and the STS Parser which has been designed to identify five different types of error which relate to six rules in the STS Specification.
Being the first of its type, this project intends to be a contribution towards the improvement of the readability and translatability of technical documentation in Spanish.

Chapter 1 – Introduction ..................................................................................................1
1.1 Outline .......................................................................................................................1
1.2 Objectives ..................................................................................................................1
1.3 Controlled Languages................................................................................................1
1.4 The STS Specification...............................................................................................1
1.5 The STS Parser and its Evaluation ............................................................................2
1.6 Structure of the Thesis...............................................................................................3
Chapter 2 – Controlled Languages: An Introduction ...................................................4
2.1 Outline .......................................................................................................................4
2.2 Controlled Languages Background ...........................................................................4
2.3 Definitions of Controlled Language ..........................................................................5
2.4 Controlled Languages and Sublanguages..................................................................5
2.5 Controlled Languages and Style Guides....................................................................6
2.6 AECMA Simplified English (SE) .............................................................................6
2.7 Other Controlled Languages......................................................................................7
2.8 Acceptance and Implementation .............................................................................10
2.9 Summary..................................................................................................................10
Chapter 3 – Controlled Language Checkers.................................................................12
3.1 Outline .....................................................................................................................12
3.2 Controlled Language Checkers ...............................................................................12
3.3 Controlled Language Checkers Currently in Use....................................................12
3.4 Summary..................................................................................................................17
Chapter 4 – STS Design: Objectives and Method ........................................................18
4.1 Outline .....................................................................................................................18
4.2 Aircraft Maintenance Documentation in Spain .......................................................18
4.3 Justification for a Controlled Spanish .....................................................................19
4.4 The Method .............................................................................................................19
4.5 The STS Writing Rules............................................................................................20
4.6 The STS General Vocabulary..................................................................................27
4.7 Summary..................................................................................................................30
Chapter 5 – STS Specification........................................................................................31
5.1 Outline .....................................................................................................................31

5.2 The STS Writing Rules............................................................................................31
5.3 Words ......................................................................................................................32
5.4 Noun Phrases ...........................................................................................................38
5.5 Prepositional Phrases...............................................................................................38
5.6 Verbs........................................................................................................................39
5.7 Sentences .................................................................................................................47
5.8 Procedures ...............................................................................................................50
5.9 Descriptive Writing .................................................................................................53
5.10 Warnings and Cautions..........................................................................................56
5.11 Punctuation and Word Counts...............................................................................58
5.12 The STS General Vocabulary................................................................................61
5.13 Summary................................................................................................................62
Chapter 6 – STS Parser: Description.............................................................................63
6.1 Outline .....................................................................................................................63
6.2 The Robust Layered Parser......................................................................................63
6.3 The Simplified Spanish Parser ................................................................................65
6.4 Checks Built into the Parser ....................................................................................70
6.5 The Grammar...........................................................................................................71
6.7 Summary..................................................................................................................74
Chapter 7 – STS Parser: Evaluation..............................................................................75
7.1 Outline .....................................................................................................................75
7.2 Objectives ................................................................................................................75
7.3 Method.....................................................................................................................75
7.4 Results using Metric 1 .............................................................................................77
7.5 Results using Metric 2 .............................................................................................81
7.6 Conclusions .............................................................................................................82
7.7 Summary..................................................................................................................82
Chapter 8 – Final Conclusions .......................................................................................83
8.1 Introduction .............................................................................................................83
8.2 Objectives ................................................................................................................83
8.3 Key Results..............................................................................................................83
8.4 Future Research.......................................................................................................84
8.5 Summary..................................................................................................................87
Bibliography.....................................................................................................................88
Appendix I – Reference Corpus .....................................................................................93

Appendix II – The STS Writing Rules...........................................................................96
Appendix III – The STS General Vocabulary ..............................................................99
Appendix IV – The Xerox Xelda Spanish Part-of-Speech Tagset.............................104
Appendix V – Reference Corpus Descriptive Sentences for Analysis.......................106
Appendix VI – Reference Corpus Procedural Sentences for Analysis .....................110
Appendix VII – Sample Output Produced by STS Parser on Analysis of Descriptive
Sentences ........................................................................................................................113
Appendix VIII – Sample Output Produced by the STS Parser on Analysis of
Procedural Sentences ....................................................................................................118
Appendix IX – Description of Errors...........................................................................121
Appendix X – Distribution of Error Types in Descriptive Sentences: STS Parser
Results.............................................................................................................................123
Appendix XI – Distribution of Error Types in Procedural Sentences: STS Parser
Results.............................................................................................................................125
Appendix XII – Distribution of Error Types in Descriptive Sentences: Manually
Determined Results........................................................................................................127
Appendix XIII – Distribution of Error Types in Procedural Sentences: Manually
Determined Results........................................................................................................129
Appendix XIV – Distribution of Errors Undetected by the STS Parser in Descriptive
Sentences ........................................................................................................................131
Appendix XV – Distribution of Errors Undetected by the STS Parser in Procedural
Sentences ........................................................................................................................133
Appendix XVI – Controlled-Language Acronyms .....................................................135
Appendix XVII – Controlled Language Research and Development Sites..............138

This chapter starts by stating the objectives of the research. It then outlines the field of
Controlled Languages and describes how a specification for Simplified Technical Spanish was drawn up. It then introduces the Validating Parser which was designed for this language and explains how it was evaluated. Finally, the structure of the thesis is summarised.
The objectives of the work presented here are:
• To develop a controlled Spanish for the aviation industry similar in spirit to AECMA
Simplified English (SE) (AECMA, 1998),
• To build and evaluate a validating parser for the new language.
In order to meet these objectives, a study of controlled languages (CLs) was first carried out.
Following this a corpus of aircraft documentation was obtained and studied, leading to a complete specification for Simplied Technical Spanish (STS). A parser for this language was then developed and its peformance measured. These activities are outlined in the following sections.
A Controlled Language (CL) is a subset of a natural language with a restricted grammar and lexicon. CLs are commonly used in technical domains to reduce ambiguity and to facilitate the translation of technical documentation.
We carried out a thorough study of previous work on CLs paying special attention to
AECMA SE. As will be shown, there are many CLs for English and a growing number for other languages. However, there are many common aspects of these CLs which we were able to adopt in the specification for STS.
In order to develop the controlled Spanish specification, we studied a reference corpus (1.45
MB) kindly provided by Construccciones Aeronaúticas Sociedad Anónima (CASA), the

Introduction 2 leading aircraft manufacturer in Spain (Appendix I). By examining the AECMA specification in detail and by comparing constructs in English with their equivalents in
Spanish it was possible to draw up a specification for STS, the first of its kind for the
Spanish language. The STS Guide contains 39 writing rules which are divided into 9 sections: words, noun phrases, prepositional phrases, verbs, sentences, procedures, descriptive writing, warnings and cautions, and punctuation and word counts.
The following is a summary of the main STS Rules:
•
•
•
•
Use only those words contained in the STS Lexicon,
Do not use different terms for the same item,
Use articles wherever possible,
Do not attach more than three prepositional phrases in a sentence,
•
•
•
Do not use the infinitive with a value other than final or imperative,
Do not use the past participle with a value other than adjectival,
Do not use the present participle with a value other than modal,
•
•
•
Do not use the subjunctive mood,
Avoid the use of the passive,
The sentence length limit for descriptive sentences is 30, while it is 25 for procedural sentences,
• Use accents (´) wherever needed, also in capital letters.
See Appendix II for the complete version of the STS Rules.
The STS Lexicon is composed of a technical terms database and a General Vocabulary. The database is divided into technical names and manufacturing processes. The General
Vocabulary contains 875 words. Having developed the specification, the next step was to build a validating parser for it.
The Robust Layered Parser (Sutcliffe, 2000) was taken as a basis for the STS Parser design.
This is a simple parser but it is easily adapted to different languages and very suitable for applications requiring a partial analysis. The linguistic features of other CL checkers currently in use were studied, focussing in particular on the Boeing Simplified English
Checker (BSEC) (Wojcik, Harrison and Bremer, 1993). This led to a specification for a parser which would detect five types of error. These are directly related to Rules 6.1 & 7.1,

Introduction 3
1.1, 4.3, 3.1 and 6.2 respectively (See Appendix IX).
Following the development of a parser to meet the above specification, an evaluation was carried out using two different metrics. The first measures its performance relative to the five errors which it was designed to detect. The second measures its performance relative to all errors in the test collection, including those which the parser was not designed to detect.
Under Metric 1, Precision and Recall figures of 0.87 and 0.97 respectively were recorded.
The figures under Metric 2 were 0.87 and 0.68 respectively. These results suggest that the performance with respect to the five chosen errors types is quite good, but that additional checks should be added in order to generate a production system for use by technical writers.
Chapter 2 is an introduction to the field of CLs and includes a literary review of previous work undertaken in this field. In Chapter 3 we find an analysis of the most important CL tools and a description of some checkers currently in use. Chapter 4 explains the method followed for the design of STS Specification and the creation of the General Vocabulary.
Chapter 5 presents the specification and vocabulary themselves. Chapter 6 then describes the STS Validating Parser. An evaluation of it is presented in Chapter 7. Finally, Chapter 8 summarises the work undertaken, draws conclusions and makes recommendations for future research.

This chapter gives an overview of Controlled Languages (CLs). It starts by investigating the background of CLs. Then it discusses some definitions adopted in the literature and establishes the differences between CLs and sublanguages, and CLs and style guides respectively. Next, the main features of AECMA Simplified English and a brief description of other CLs is presented. Finally, the issue of acceptance and implementation of CLs is addressed.
The notion of CL was first proposed by C. K. Ogden, a British writer and linguist, in his book Basic English, A General Introduction with Rules and Grammar (Ogden, 1932). Basic
English was a subset of the English language which, with 850 words, intended to be able to give the sense of anything which might be said in English. At the time, Odgen´s objective was to create a language which would allow people of different countries to intercommunicate easily. Basic English differed from previous attempts to construct universal languages in that it was a perfectly well-formed part of English, rather than some entirely artificial or hybrid construction such as Esperanto (Janton, 1994).
Although Basic English was never popular in the 1930’s, the idea was taken on later in the
1970’s by multinational companies such as Caterpillar, Ericsson, Kodak and Xerox. By using a controlled English, their objective was to write technical manuals which service engineers and mechanics with limited English skills could easily read, thus avoiding translation costs. Although this was the first intention, two important additional benefits were discovered with CLs: firstly, improvement of readability not only for non-native speakers, but also for native speakers of English and, secondly, better results when using machine translation (MT) and translation memory (TM) applications.
As a consequence of the advantages that a CL can offer, there has been a steady increase in the design of CLs and related applications in different domains in the last thirty years. While the majority of work on CLs has focused on English, some attempts have been made to produce specifications for other languages. Examples include GIFAS Français Rationalisé
(Lux, 1998), a CL for French aircraft maintenance manuals, ScaniaSwedish (Almqvist and

Controlled Languages: An Introduction 5
Hein, 1996), a CL for truck maintenance documentation, Controlled Siemens Documentary
German (Schachtl, 1998) for software documentation and Controlled Chinese (Zhang and
Shiwen, 1998). However, while shallow parsers have been developed for Spanish (e.g. Gala
Pavia, 1999), as well as grammar checkers (e.g. Ramírez and Sánchez, 1996), little research has been undertaken on the development of a controlled Spanish.
There are many definitions in the literature on CLs and they are all very similar. Here are some examples:
Van der Eijck, De Koning and Van der Steen (1996: 64)
Controlled languages are constructed languages that have precise coverage bounds and are designed to satisfy linguistic constraints such as greatly reduced ambiguity.
Hayes, Maxwell and Schmandt (1996: 84)
The kinds of control usually considered include restricting the vocabulary used in a document, restricting the allowable meanings of particular words or phrases, restricting the kinds of syntactic constructions that may be used, and restricting the overall complexity of sentences. A collection of restrictions of these kinds is said to define a Controlled English (CE).
Heald and Zajac (1998: 124)
A Controlled Language is an extreme application of writing rules as expounded in technical writing manuals.
Huijsen (1998: 2)
A controlled language is an explicitly defined restriction of natural language that specifies constraints on lexicon, grammar, and style.
In summary, the objective of a controlled language is to improve readability, standardisation, accessibility and translatability of documentation. This is achieved through increased terminological consistency and standardisation, generally simplified sentence structure, and standardised document format and layout.
A sublanguage is the language used in a specific domain, such as the special set of terms and language used by those knowledgeable of biology, geology, or artificial intelligence.
Each of these domains has a vocabulary and grammatical structures specific to its needs.
According to Kittredge (1996) this idea of sublanguage would coincide with the concept of
“natural sublanguage”. The critical difference between a CL and a sublanguage is that the

Controlled Languages: An Introduction 6 terms, syntax and semantics of a CL are actively and purposefully proscribed, generally with particular objectives in mind, while the restrictions of a sublanguage are unspecified and evolve naturally.
There are similarities between CLs and style guides, as both aim to allow information to be transmitted accurately, quickly and economically. However, CLs are designed with other additional objectives: the usability, retrieveability, extractability, and translatability of documents. Also, style guides have fewer constraints on vocabulary and grammatical constructions than CLs, making them less restricted. Lux (1998) has shown that style guides are predecessors of controlled languages.
AECMA SE comprises a restricted vocabulary of 1,565 words with an additional set of 57 rules for using that vocabulary (AECMA, 1998). SE originated when in 1979 the
Association of European Airlines (AEA) asked the European Association of Aerospace
Industries (AECMA) to investigate the readability criteria of its aircraft maintenance documentation. Through its Documentation Working Group (DWG), AECMA set up a project group called the Simplified English Working Group (SEWG), to research the problem and provide a solution. SE was the result of this initiative.
After analysing existing texts, a draft list of verbs was identified in 1983. The Aerospace
Industries Association (AIA) of America also joined the project. In 1986 an initial issue of the SE Guide was made (AECMA Document PSC-85-16598). In 1987, the Airline
Transport Association (ATA) of America, in its Specification 100 (the “Definitive
Reference” for commercial aircraft support documentation) made AECMA SE a mandatory requirement. In 1995, the SE Guide was re-issued with many new features (Farrington,
1996).
The author of SE can use only three sources of words. Firstly there are Approved Words from the SE Guide. These constitute the base vocabulary which contains 1,565 words. There are 196 verbs in the base vocabulary and these are approved in four forms: the infinitive, the third person singular, the past simple and the past participle. Manufacturers then add
Technical Names and Manufacturing Processes to the base vocabulary. For the Boeing
Simplified English Checker these comprise 7,000 extra terms (Wojcik, 1998).

Controlled Languages: An Introduction 7
There are 57 Writing Rules in the SE Guide (AECMA, 1998). The following are some of the better known ones:
• A sentence length limit of 20 words (25 for descriptive text),
• A paragraph limit of 6 sentences,
• A compound noun length limit of 3 words,
• A prohibition on progressive be and perfective have,
• A prohibition on the passive in procedures (discouraged in descriptions),
• A prohibition on the –ing form of the verb,
• A requirement that sequential steps be in separate sentences,
• A requirement that words only be used in their approved sense,
• A recommendation that articles be used where possible.
Some examples of controlled languages in English other than AECMA SE are:
• Agilent Technologies English (Smartny, 2002),
• Attempto Controlled English (ACE) (Fuchs and Schwitter , 1996),
• Boeing Technical English (Wojcik, Holmback, and Hoard, 1998),
• Caterpillar Technical English (Kamprath, Adolphson, Mitamura, and Nyberg,
1998),
• Diebold Controlled English (Moore, 2000),
• Ericsson English (Ericsson, 2000),
• General Motors CASL (Means and Godden, 1996),
• Global English (Means, Chapman and Liu, 2000),
• Kodak English (Kodak, 2000),
• Nortel Standard English (Smartny, 2002),
• Océ Technologies English (Smartny, 2002),
• Perkins PACE (Douglas and Hurst , 1996),
• Xerox MCE (Xerox, 2001).
Examples in other languages include:
• Controlled Chinese (Zhang and Shiwen, 1998),
• Controlled Siemens Documentary German (Schachtl, 1998),
• GIFAS FR for French (Barthe, 1998),
• ScaniaSwedish (Almqvist and Hein, 1996).

Controlled Languages: An Introduction 8
In the next few lines, we give a brief description of the CLs mentioned above.
The Chemical Analysis Group of Agilent Technologies (Smartny, 2002) has adopted a
Controlled English to write materials for Mass Spectrometry and Gas chemical analysis equipment.
Attempto Controlled English (ACE) (Fuchs and Schwitter, 1996) is a subset of English with restricted grammar, a domain-specific vocabulary, and a small set of construction and interpretation principles.
Fuchs and Schwitter (1996:125)
ACE is a computer processable subset of English for writing requirements specifications. …Domain specialists can express their concepts in ACE in a direct and natural way using the objects of the language as abstract entities.
Specifications written in ACE are textual views of formal specifications in logic.”
Boeing Technical English (Wojcik, Holmback, and Hoard, 1998), is a general-purpose controlled English writing standard intended to result in clear and precise technical documents. The idea originates from Boeing’ s need to improve the readability and consistency of a wide variety of documents for customers of different linguistic backgrounds.
Caterpillar Technical English (CTE) (Kamprath, Adolphson, Mitamura, and Nyberg,
1998): is the Controlled English developed at Caterpillar corporation for heavy machinery documentation. The first controlled language developed at Caterpillar was called Caterpillar
Fundamental English (CFE) which later became CTE.
Diebold Controlled English (Moore, 2000) is a specification whose objective is to facilitate a translation process that uses human translators. It comprises a vocabulary and a set of grammar rules.
Ericsson English (Pathinfo, 2002) is the CL used for maintenance manuals relating to
Ericsson equipment.
General Motors uses two different CL systems each intended for different purposes:
Controlled Automotive Service Language (CASL) and Global English (GE). Controlled
Automotive Service Language (CASL) (Means and Godden, 1996) is a CL that restricts

Controlled Languages: An Introduction 9 grammar and terminology of vehicle service information in order to achieve high-quality machine translation into French.
Global English (GE) (Means, Chapman and Liu, 2000) is a CL which consists of 15 rules.
It has been adopted by General Motors University (GMU) for all their training courses for
English in the U.S. and overseas, and to facilitate translation. The objective is to improve comprehension for non-native speakers of English and to improve translatability.
Kodak International Service Language (KISL) (Kodak,2000) is the CL used at Kodak for their maintenance manuals. The main concept behind KISL is “one word, one meaning”. It has a vocabulary of around 1,000 words.
Nortel Standard English (Smartny, 2002) is a controlled English vocabulary for telephony global customer documentation. Nortel Networks is a rapidly growing manufacturer of telephony equipment.
Océ Technologies English (Smartny, 2002) is a CL to write global product support documentation. Océ Technologies, B. V. is a multinational Dutch manufacturer of highspeed copiers. The Océ line of copiers are well-known for their reliability and are thus used for applications such as is printing credit card and customer billing statements.
Perkins Approved Clear English (PACE) (Douglas and Hurst , 1996) is the CL for Perkins
International Limited, based in Peterborough, England. PACE was based on the Caterpillar model. It consists of a lexicon of approximately 2,500 words, together with a set of ten writing rules (Pym 1990):
1. Keep sentences short.
2. Omit redundant words.
3. Order the parts of the sentence logically.
4. Do not change construction in mid-sentence.
5. Take care with the logic of “and” and “or”.
6. Avoid elliptical constructions.
7. Do not omit constructions or relatives.
8. Adhere to the PACE dictionary.
9. Avoid strings of nouns.
10. Do not use –ing unless the word appears thus in the PACE dictionary.

Controlled Languages: An Introduction 10
Finally, Xerox Multinational Customised English (MCE) (Xerox, 2001) is a CL for its documentation division.
Turning to languages other than English, Controlled Chinese (CC) (Zhang and Shiwen,
1998), is a precisely defined subset of Chinese. It has a restricted lexicon and grammar. The objective is to make all aspects of Chinese text manipulation easier.
Controlled Siemens Documentary German (CSDG) (Schachtl, 1998) is a Controlled
German developed at Siemens Corporation to improve the translatability of its technical documents, thus allowing the use of their machine translation tool TopTrans.
GIFAS Français Rationalisé (FR) (Barthe, 1998) is a CL for the French aerospace industry. It was originally based on AECMA SE. The objective of FR is to improve the quality of aircraft documentation in French.
ScaniaSwedish (Almqvist and Hein, 1996) is a Controlled Swedish for truck maintenance documentation. By writing in ScaniaSwedish, the technical writers would like to facilitate a high quality translation of documentation into seven European languages in a full version, and partly into three others.
There has been some resistance to using CLs because of the difficulties many authors face when first using CL tools. Both the CL itself and the checking/correction tools must be learned, and this can be frustrating or inconvenient for engineers and technical writers
(Goyvaerts, 1996; Godden, 1998). However, CLs do meet their objectives:
Holmback, Shubert and Spyridakis (1996:168)
With relatively complex documents, the use of SE (Simplified English) will significantly improve comprehension…(and) translations of the SE
(Simplified English) versions of the procedures produced significantly higher ratings for style match and significantly fewer minor omissions than translations of the non-SE versions.
In this chapter we presented the background of CLs and gave a brief description of the various CLs in English and other languages. Frequently, those organisations that adopt a CL develop tools which help them to use it for their documentation. In the next chapter, we

Controlled Languages: An Introduction 11 explain what language technology can do to facilitate the use of CLs and describe some of the most important CL checkers being used at present.

In this chapter, we first present a general description of the most common tools used by technical writers to help them comply with a CL specification. Then we discuss the key linguistic features of the main CL checkers implemented in a number of companies.
The most commonly used tools to help technical writers in their process of writing in a CL are grammar checkers, terminology checkers, style checkers and alternative generators. A
CL checker usually integrates some or all of these tools.
CL grammar checkers indicate whether the controlled text is grammatical or not by performing text parsing and pattern matching against a set of pre-defined grammar rules. CL terminology checkers specify whether the words used in the controlled text are allowed or not by using a terminology database against which the text is checked. CL terminology databases are usually developed through corpus analysis. They may be general, domain specific, or company specific. CL style checkers analyse document types, formats, and layouts. Some of the stylistic conventions which can be checked are date and currency formats, table formats, and spelling variants. CL alternative generators provide a possible phrase or sentence which can substitute for one which does not conform to the specifications of the CL. In most cases, a modification of the original text will be sufficient, but in some cases, an entirely new sentence or expression will be necessary.
The Boeing Simplified English Checker (BSEC) is used to check text conformance with
AECMA SE. It is a CL application that has been in production since 1990. It uses a grammar formalism based on Generalised Phrase Structure Grammar (Gazdar, 1985). A set of over 350 rules is used to achieve a broad coverage of English technical writing (Wojcik,
Harrison and Bremer, 1993). It is based on a bottom-up, left-corner parser which first generates a forest of parses, each taking a different interpretation of the input and then makes a best guess of the correct syntactical analysis.

Controlled Language Checkers 13
ERROR TYPES
POS
NON-SE
MISSING ARTICLE
PASSIVE
TWO-COMMAND
ING
COMMA ERROR
WARNING/CAUTION
DESCRIPTION
A known word is used in incorrect part of speech
An unapproved word is used
Articles must be used wherever possible in SE
Passives are usually illegal
Commands may not be conjoined when they represent sequential activities. Simultaneous commands may be con-joined
Progressive participles may not be used in SE
A violation of comma usage
Warnings and cautions must appear in a special format. Usually, an error arises when a declarative sentence has been used where an imperative one is required.
Figure 3.1 Error Types Detected by Boeing Simplified English Checker
(Wojcik, Harrison and Bremer, 1993)
Some of the more important requirements of AECMA Simplified English that the BSEC can detect are: sentence length (20 or 25 words), paragraph length (6 sentences), noun cluster length (3 words or less), missing articles (based on count and mass distinctions), unapproved verbal auxiliaries (passive, progressive, perfect, modals), unapproved –ing participles, multiple commands in a single sentence, and warning, caution and note errors.
Figure 3.1 shows a list of the error types detected by BSEC.
No other Simplified English checker is as complete or accurate in support of Simplified
English requirements as BSEC. The Boeing checker also catches some grammatical and stylistic errors that are not explicitely addressed in the SE standard. Among other things, it detects subject-verb agreement errors, double word errors, misspelled words and punctuation problems.

Controlled Language Checkers 14
Figure 3.2 The Boeing Meaning-Based Checker Architecture
(Holmback, Duncan, and Harrison, 2000)
Boeing has also developed an experimental Meaning-Based Checker (BMBC) to generate more accurate analyses. The BMBC builds on the syntax-based BSEC by adding the capability 1) to determine when an approved word is used in an unapproved meaning and 2) to select only those alternatives for an ambiguous unapproved word that are appropriate for the meaning in which it is used (Holmback, Duncan and Harrison, 2000).
POS
Noun
Verb
WORD noise extinguish
APPROVED MEANING unwanted sound stop combustion
UNAPPROVED MEANINGS electronic interference turn off
Adj clear
Prep
Adv by together
Tech
Noun application
Tech Adj telescopic without blockage manner in one place piece of software with a specific purpose retracting into transparent obvious near at the same time result or action of applying seeing with a telescope
Table 3.3 Some Simplified English Word Sense Restrictions in BMBC.
(Holmback, Duncan, and Harrison, 2000)

Controlled Language Checkers 15
Therefore, the Simplified English Checker can detect approved and unapproved word senses, although in limited fashion. The Boeing Meaning-Based Architecture is illustrated in
Figure 3.2. Table 3.3 shows examples of SE word sense restrictions.
The Controlled Automotive Service Language Checker (CASLChecker) was first developed at General Motors by LANT nv/sa in 1993 (Godden, 2000). The starting point for the development of CASLChecker was the existing Metal parser and grammar (Lamiroy and
Gebruers, 1989). Its aim was to increase the readability and translatability of English service language in the automotive sector. The CASLChecker helps authors and editors to comply with the CASL English rules and terminology and it reduces the time to get authors and editors trained in CASL English.
In general terms, the CASL conformance checker has a number of capabilities from a lexical and syntactic point of view (Means and Godden, 1996). Lexically, it recognises words which do not belong to the CASL vocabulary, it recommends approved CASL synonyms for some non-CASL-approved words (e.g, use ‘generator’ instead of ‘alternator’ ), and it provides examples to show right and wrong usage. Syntactically, the CASLChecker identifies structures which violate CASL restrictions (e.g. gapped constructions), and informs users of syntactic errors (e.g. passives). It provides right and wrong usage examples for specific error types and gives a recommended rewrite for the sentence for errors with a strong diagnosis. For example, the CASLChecker can recognise instances of the present progressive aspect and automatically correct these to the simple present tense.
MULTILINT originated as a research and development project, sponsored by the German
Ministry of Economy in the 1990’ s. The main purpose of the work was to integrate linguistic intelligence into the processing of technical documents. In this case, the automotive sector was the application domain as BMW AG was one of the project partners.
The objective of using the MULTILINT Controlled German Checker was mainly to improve the translatability and readability of technical documentation.
From a linguistic point of view, the MULTILINT system works as follows. First, the system
MPRO decomposes the words and provides their analysis in terms of inflection, derivation and composition using a list of 20,000 morphemes for German. Abbreviations and acronyms are also taken into account in this process. Second, syntactic analysis is undertaken by

Controlled Language Checkers 16 applying a number of NLP tools integrated in the MULTILINT system. They are capable of checking spelling, syntax, style and terminology (Reuther and Schmidt-Wigger, 2000).
There are also tools which can check the translatability of the text.
An example tool is the Source Text Control tool, which supports the author during the production of a document. The tool ensures conformance with a linguistic specification that includes orthographic, terminological, syntactic and semantic correctness. The Foreign
Language Glossary tool produces on the basis of the input text a domain specific glossary in the target language which is similar to a morpho-lexical translation. The Translation
Memory Control tool (TMCON) checks whether the text for translation has already been translated. Finally, the Informative Machine Translation Tool (MT) produces a translation of those sentences that meet specific requirements such as not being too long, not having spelling or syntax errors and including lexical categories that are part of the MT dictionary.
ClearCheck is an interactive checker which helps authors decide whether their writing conforms with CTE. If it does not, the system suggests how to achieve conformance. The checker was developed in the 1990’ s and has undergone several updates. The underlying system of ClearCheck is the KANTOO system (KANT Object-Oriented). The main components of KANTOO include (Kamprath, Adolphson, Mitamura. and Nyberg, 1998):
• The Language Translations Database (LTD): A database for rapid development and efficient maintenance of target language terminology banks.
• The Lexicon Maintenance Tool (LMT): An application for maintenance of CTE terminology.
• The KANTOO Analyzer: A re-implementation of the KANT analyser, which is used for grammar checking and analysis during translation.
• The KANTOO Generator: A re-implementation of the target language translations engine.
• The Knowledge Maintenance Tool (KMT): A graphical user interface which allows real time browsing, editing, and incremental update of the knowledge sources used during analysis and generation (lexicon, grammars, domain model, mapping rules, etc.).
The Diebold Controlled English Checker has two basic components: the lexical database and a checking tool (Moore, 2000).

Controlled Language Checkers 17
The lexical database is the most widely used component. It feeds the checker, corporate glossary and translation glossaries. The checker was built by Carnegie Group/ Logica and is used by technical writers throughout the corporation. Its two main features are: the browser interface and the parsing software. While the checker gives recommendations for a sentence, the writer needs to edit the material at the level of meaning.
This chapter outlined the possible types of linguistic analysis which can be used in a CL tool. It then described some of the CL checkers currently being used. Before describing our own validating parser, we first explain in the next chapter the objectives and method we have followed for the design of a Simplified Technical Spanish.

In this chapter we start by giving a brief description of how technical documentation is developed in Spanish. We then present a justification for the creation of STS, which is a controlled Spanish Specification for the aerospace industry and describe the method used for its design.
In Spain, Maintenance documentation for civil aircraft must comply with an American
Specification: Air Transport Association of America (ATA) Spec. No. 100, Specification for
Manufacturers’ Technical Data. This document indicates a number of recommendations concerning what type of information the technical manual should contain including its style and terminology as well as other aspects related to paragraphing and outlining, person and voice, nomenclature and abbreviations, titles, warnings, cautions and notes. ATA added a new requirement for technical documentation of civil aircraft in 1986, which is that writing rules and vocabulary shall be in accordance with the AECMA Simplified English Document
No. PSC-85-16598 (Farrington, 1996).
The case of technical documentation for military aircraft is different. A few years ago, military maintenance documentation was written in Spanish according to national standards.
Such is the case of the military aircraft CN-235 maintenance manual, which is the core of our reference corpus. However, nowadays, there is a tendency to write technical manuals in
English in order to produce manuals that can be exported easily with no language problems.
There is also another reason: The involvement of several countries in the development of military aircraft makes it necessary to produce documentation in a language that is understandable to all of them, in this case, English. Therefore, it is very common to find documents in English for European military aircraft, which in addition comply with a
European specification produced and issued by AECMA, known as AECMA 1000D -
International Specification for Technical Publications Utilising a Common Source Data
Base. This specification is very similar to ATA Spec. No. 100.

STS Design: Objectives and Method 19
There are basically two options which a Spanish aircraft manufacturer can follow when it comes to dealing with the development of documentation for their aircraft:
OPTION A: 1. Train Spanish technical writers to write in Simplified English (SE).
OPTION B: 1. Train Spanish technical writers to write in a controlled Spanish (STS).
2. Set up a group of translators to translate into Simplified English (SE).
The advantage of Option A is that you do not need a translation of documentation into SE.
However, there are a number of disadvantages:
1. You cannot provide documentation in Spanish for technicians in Spain.
2. You cannot provide the maintenance manuals of the aircraft in Spanish when sold over to a Spanish-speaking country.
3. Spanish technical writers must have a good command of the English language to be able to write in SE, which is not always the case.
4. The training costs for learning to use SE can be high.
5. It is not guaranteed that the end result will be of a sufficiently high standard.
The advantages of Option B are:
1. It is much easier for a technical writer to write in his or her mother tongue.
2. The result is likely to be better than in Option A.
3. It is possible to provide the Spanish technicians with documentation in their own language. This is particularly advantageous for those whose English is not good enough.
4. It offers the company the option of providing other Spanish speaking countries with clear and precise technical documentation in their own language.
The disadvantage of Option B is that it is necessary to translate into SE for customers from non-Spanish speaking countries. However, once the language has been controlled, translation becomes a tractable task.
In summary, we find two main reasons for the creation of a controlled Spanish:
1. To improve readability in documentation for native Spanish speakers.
2. To improve translation results in the documentation for non-Spanish speakers
The initial method used to design a controlled Spanish was to find equivalents in Spanish for the Writing Rules and Vocabulary of SE. This involved using the AECMA SE Guide as

STS Design: Objectives and Method 20 a basis and working back into Spanish. At the beginning one may think that this is only a question of transposition from English into Spanish. However, when we started to apply the rules and to look at the reference corpus (see Appendix I), there were more differences between English and Spanish than we expected. In the next lines we explain in more detail the process involved in developing the Simplified Technical Spanish (STS) Writing Rules and the General Vocabulary.
In order to develop the STS Writing Rules, we followed the following steps: First, we considered a potential writing rule for STS taken from the SE AECMA Guide. Secondly, we decided if the rule was applicable to Spanish. In order to reach to a decision, we tried to find evidence in the reference corpus. If we found examples in which the rule was infringed and the sentence in question caused ambiguity, the rule was adopted in STS. If on the contrary, the nature of Spanish language did not allow the rule to be applied, it was disregarded.
During the development of the STS Writing Rules, we came across some cases which required particular attention in the Spanish language. One example is the use of accents (´).
Such cases gave us evidence to produce new rules which are only applicable to STS.
This section summarises the results of our analysis for the development of the STS Writing
Rules. STS contains 39 such rules divided into nine categories:
1. Words,
2. Noun Phrases,
3. Prepositional Phrases,
4. Verbs,
5. Sentences,
6. Procedures,
7. Descriptive Writing,
8. Warnings and Cautions,
9. Punctuation and Word Counts.
In contrast, SE contains 57 Writing Rules, divided into nine families, but not exactly the same ones as in STS:
1. Words,
2. Noun Phrases,

STS Design: Objectives and Method 21
3. Verbs,
4. Sentences,
5. Procedures,
6. Descriptive Writing,
7. Warnings and Cautions,
8. Punctuation and Word Counts,
9. Writing Practices.
A tenth family (Writing Practices) is planned for the future when there is more practical experience of writing in STS.
In the next paragraphs, we analyse those rules related to words, noun phrases and verb groups in SE and explain what decisions were involved in accepting or disregarding each of the rules in STS. The rules relating to other categories have not been explicitly commented upon as they are essentially the same in SE and STS.
There are 13 rules in SE related to words:
1.1 Choose the words for procedures from:
-Approved words in the Dictionary,
-Words that qualify as Technical Names,
-Words that qualify as Manufacturing Processes.
1.2 Use approved words from the Dictionary only in the part of speech given.
1.3 Keep to the approved meaning of a word in the Dictionary. Do not use the word with any other meaning.
1.4 Use only those forms of verbs and adjectives shown in the Dictionary.
1.5 You can use words that are Technical Names.
1.6 Use a Technical Name only as a noun or an adjective, not as a verb.
1.7 Use the official name (shortened if necessary).
1.8 Do not use different Technical Names for the same thing.
1.9 If you have a choice, use the shortest and simplest name.
1.10 You can use verbs that are Manufacturing Processes.
1.11 Use Manufacturing Processes only as verbs, not as nouns or adjectives (unless the noun form qualifies as a Technical Name).
1.12 Once you choose the words to describe something, continue to use these same words
(particularly Technical Names).
1.13 Make your instructions as specific as possible.

STS Design: Objectives and Method 22
The rules applicable to Spanish are 1.1, 1.3, 1.8 and 1.13.
It is necessary to mention that Rule 1.1 has changed slightly in STS. While in SE it only applies to procedural writing, in STS it relates to both procedural and descriptive writing 1 .
The reason why we have not included Rule 1.2 is that in Spanish the problem of a word representing several categories is not so common. A noun and a verb will never be mistaken as they have different forms, in contrast to what happens with the English language. For instance, in English the word “ Test” can function as a noun or as a verb. In AECMA SE the word “ TEST” is approved as a noun but not as a verb. There are two equivalent words for test in Spanish: as a noun Test = Prueba, as a verb Test = Probar, therefore, there is no place for confusion with the part of speech.
Rule 1.4 had to be left out. Showing all the approved forms of verbs and adjectives is possible in English because there are not very many, but Spanish is an inflected language with many different forms of the same base word. For example, in reference to verbs in SE, it is possible to specify all the moods and tenses that are approved (infinitive, imperative, simple present, simple past, and future), in all persons and numbers. The last form is the past participle, which in SE can only be used as an adjective. An example of an SE verb entry is:
STOP (V), STOPS, STOPPED, STOPPED
The equivalent in Spanish would be:
PARAR
PARANDO
[Infinitive]
[Gerund]
PARADO, PARADA [Past Participle Masculine/Feminine]
PARA, PARAN [Third Person Singular, Third Person Plural of the Present Simple]
Even though fewer verb tenses are allowed in Spanish, an entry for the verb STOP
[“ PARAR” ] would need six approved forms, which could be weighty for the dictionary. For this reason, we have decided to include in the dictionary only the infinitive. Technical writers are supposed to know the corresponding forms for the other allowed verb tenses in
1 All comments in respect of AECMA SE are relative to Issue 1, Revision 1, 1998.

STS Design: Objectives and Method 23
STS. In the rare case that they do not know, they can always consult a standard Spanish grammar book.
In reference to adjectives, we also find more permitted forms in STS than in SE. The reason is that adjectives in Spanish are inflected to express gender and number, which is not the case in English. For example for the approved forms of the adjective SAFE in English:
SAFE (Adj), SAFER [Comparative], SAFEST [Superlative]
There are the following forms in Spanish:
SEGURO [Masculine] / SEGURA [Feminine] (Adj)
MÁS SEGURO / MÁS SEGURA
MENOS SEGURO / MENOS SEGURA
IGUAL DE SEGURO / IGUAL DE SEGURA [Comparative]
EL MÁS SEGURO / LA MÁS SEGURA [Superlative]
To the forms above we would need to add the plural ones, resulting in a total of 20 forms of the adjective. Once again, we argue that only the adjective in masculine form should be included, and that it is unnecessary to include all the possible forms in the dictionary.
We have decided not to include Rule 1.5 You can use words that are Technical Names because this rule is already implied by Rule 1.1.
Rule 1.6 Use a Technical Name only as a noun or an adjective, not as a verb does not apply to Spanish because a Technical Name cannot function as a verb.
Rule 1.7 Use the official name (shortened if necessary) is not included as the dictionary of common words and the domain-specific dictionary are restricted to official names and are therefore not supposed to contain any unofficial ones.
Regarding Rule 1.9 If you have a choice, use the shortest and simplest name, we have ensured that this is the case by constructing a lexicon in which only the shortest and simplest names have been included. As a result, Rule 1.9 is redundant.
We have decided not to include Rule 1.10 You can use verbs that are Manufacturing
Processes because this rule is already implied by Rule 1.1.

STS Design: Objectives and Method 24
Rule 1.11 Use Manufacturing Processes only as verbs, not as nouns or adjectives (unless
the noun form qualifies as a Technical Name) is not applicable to Spanish because a
Manufacturing Process can never be a noun or adjective in Spanish.
Rule 1.12 Once you choose the words to describe something, continue to use these same
words (particularly Technical names) is not necessary. There is simply no option to use different words to explain the same thing because synonyms are not allowed in STS. The lexicon cannot include any synonyms, and all words that are allowed are contained in the lexicon.
SE has a separate section in the SE Guide for these rules. They are:
2.1 Do not make noun clusters of more than three nouns.
2.2 Clarify noun clusters that are Technical Names with one of these two methods:
-Use hyphens to show the relationship between the most closely related words;
-Explain the noun cluster. Then, if possible, use a shorter name after the initial explanation.
2.3 When appropriate, use an article (the, a, an) or a demonstrative adjective (this, these) before a noun.
The STS Guide has an equivalent section to Noun Phrases to cover Rule 2.3. The other rules of the section have been included in a new one called Prepositional Phrases because the difficulties inherent in noun clusters are different in Spanish.
In English technical language, it is common to see phrases made from several nouns which are called noun clusters. The headword is usually at the end of the noun cluster and if this is very long, it can be confusing for the reader because it is difficult to distinguish which are the nouns that modify or describe the main one. An example is:
Runway light connection resistance calibration
In Spanish, nouns are not really clustered together. The main word comes first and the modifiers come afterwords in the form of prepositional phrases. When there are more than three prepositional phrases together it is difficult to understand which prepositional phrase modifies which. As a result, the overall meaning of the sentence is hard to comprehend. An example is:

STS Design: Objectives and Method 25
2 Se enciende el módulo ENG FIRE [en la central] [de aviso] [de fallos] [de la cabina] [de pilotos] [...] [Doc_26-11-00]
3 {“ ENG FIRE” caption comes on in the cockpit warning annunciator panel and warning signs flash.}
There are ways of simplifying this complex structure. For example, you can use relative clauses:
Se enciende el módulo ENG FIRE en la central de aviso de fallos que hay en la cabina de pilotos.
SE has 7 rules in relation to verbs:
3.1 Use only those forms of the verb that are listed in the Dictionary.
3.2 Use the approved forms of the verb to make only:
-The infinitive,
-The imperative,
-The simple present,
-The simple past tense,
-The future tense.
3.3 Use the past participle only as an adjective, either with a noun or after the verbs TO BE,
TO BECOME.
3.4 Do not use the past participle with a form of the verb HAVE to make an unapproved tense.
3.5 Do not use the past participle of a verb with a helping verb to make a complex verb.
3.6 Use the active voice. Use only the active voice in procedural writing, and as much as possible in descriptive writing.
3.7 If there is an approved verb to describe an action, use the verb (not a noun or other part of speech).
The verb system in English is quite different to the verb system in Spanish. In consequence, the rules applicable to STS are Rule 3.2, Rule 3.6 and Rule 3.7. Many new rules had to be added in order to cover the requirements of Spanish. A summary is indicated below.
Rule 3.1 is a repetition of Rule 1.4. Therefore, it has not been included in the STS Guide.
We decided not to list the forms in the STS Dictionary, as discussed in Section 4.5.2.
2 [] Square brackets have been inserted as prepositional phrase delimiters.

STS Design: Objectives and Method 26
Rule 3.2 was modified greatly because the Spanish verb system is quite different from the
English one. With reference to the personal forms of the verb, the allowed tenses are the present and the future. There are no instances of the simple past tense in the reference corpus and therefore it has not been considered necessary. In fact, procedures will require mainly the use of the infinitive with an imperative value (instructions). For descriptions technical writers use the present simple and in some instances the future, but not the past simple, which is more used in literature than in technical documentation.
In contrast to English, the imperative in Spanish does not coincide in form with the infinitive. However, technical writers use the infinitive form to express an imperative value in Spanish technical documents. Therefore, the imperative tense has not been included.
With reference to the non-personal forms of the verb, the allowed tenses are the infinitive, the past participle and the gerund. The infinitive is allowed only in those cases in which it denotes an imperative value or a value of purpose. An example of the infinitive with an imperative value (instructions) is:
No exponer el cilindro extintor a temperaturas por encima de los 70 ºC.
[Doc_26-21-11]
{Do not expose the extinguisher cylinder to temperatures above 70 ºC.}
An example of the infinitive with a purpose value is:
El piloto tira de la palanca para energizar el sistema. [Doc_26-21-00]
{The pilot pulls the handle to supply power to the system.}
There is ambiguity between in the two cases described above. While the infinitive with a purpose value will always have the “ para” particle {to}, the infinitive with an imperative value does not have any particle in front of it.
In order to avoid ambiguity, the infinitive used with any other value should be changed into a personal form of the verb.
The past participle is only allowed with an adjectival value. An example is:
3 {}Curly brackets have been used to include the translation of the examples.

STS Design: Objectives and Method 27
Las tarjetas impresas están colocadas en paralelo dentro de una caja de acero inoxidable herméticamente cerrada. [Doc_26-11-00]
{The circuit boards are installed in sandwich form within a hermetically sealed stainless steel case.}
The gerund and progressive participle are not permitted in SE. However, in Spanish we find it very useful when we need to express the way in which to perform an action. Therefore, the gerund is allowed in such cases in STS. An example is:
La alarma acústica puede anularse, pulsando cualquiera de los interruptores de las luces principales de aviso de fallos. [Doc_26-11-00]
{The audible alarm may be cancelled by pressing either of the master warning sign switches.}
In order to avoid ambiguity, the gerund used with any other value should be changed into a personal form of the verb.
In Spanish there are constructions called Perífrasis Verbales {Verbal Periphrases} which have also been accepted within the STS guide. A verbal periphrasis is a syntactical construction which consists of two or more contiguous verbs, none of which are any of the auxiliary verbs used to form complex verb tenses. Of all the combined verbs, one is the main verb (a non-personal verb form: infinitive, gerund or past participle) and the others are helping verbs. At present, the allowed verbal periphrases in STS are:
V. ESTAR + PAST PARTICIPLE [Only the forms está and están]
V. PODER + INFINITIVE [Only the forms puede and pueden]
With regard to the approved moods, the subjunctive was prohibited. The nature of technical documentation requires the use of the indicative (descriptions) and the imperative
(instructions), as they add accuracy to the text. The use of the subjunctive mood can lead to unspecific statements.
Rules 3.3, 3.4 and 3.5 are not stated explicitly, but they are implicit within the other rules related to verb tenses in STS.
Work on the STS General Vocabulary involved finding equivalents for the words approved in SE or rather for the notions that the SE words express. This implied the study of the words in their natural context and therefore a thorough analysis of the reference corpus. At

STS Design: Objectives and Method 28 present the dictionary consists of a list of 875 words without clauses. It is envisaged that definitions could be added in a future project.
When the translation for a word resulted in several synonyms, the most commonly used word in the reference corpus was chosen. “ One word, one meaning” was the most important criterion in the choice of most SE words. There were cases in which a single word in SE corresponded to various words in Spanish, depending on the precise context of use. A good example is the verb remove:
REMOVE (v) To “ take” or move something away from its initial position
As a consequence, in SE you find:
(1) remove an indicator from the aircraft (i.e. remove the screws etc that attach it),
(2) remove equipment after maintenance (i.e. push it off ),
(3) remove sharp edges (i.e. eliminate them).
In Spanish, one word is not enough to explain all these concepts.
In case (1) remove means to separate an item (a constituent part of the aircraft) from its next higher assembly. This involves removing the attaching parts and then taking the item away.
The most suitable word in Spanish would be quitar.
In case (2) remove means to move something so that it is no longer where it was before.
Maintenance equipment is not part of the aircraft, thus the word quitar is not completely adequate. There is a better word which expresses that meaning: retirar.
In case (3) remove means to make a substance or material disappear. For that, the most appropriate word in Spanish is eliminar.
Some other examples are:
Attach
Expand
(fasten)
(stick)
(join)
(trailer)
= sujetar
= pegar
= unir
= acoplar
(general)
(number)
(wings)
= expandir
= aumentar
= desplegar

STS Design: Objectives and Method 29
Fume (smoke)
(gas)
(steam)
= humo
= gas
= vapor
Melt
Point
(metal)
(snow)
(chemical)
(end)
(location)
= fundir
= derretir
= dissolver
= punta
= punto
Push
Release
(press)
(button)
(general)
(brake)
(grip)
= empujar
= pulsar
= desenganchar
= soltar
= aflojar
There are also cases in which for two or even three words in English we have only one word in Spanish. Some examples are 4 :
Time (n)/ Weather (n)
For (pre) / During (pre)
5 Thru (prep) /Until (prep)
Entrance (n) / Entry (n)
= Tiempo
= Durante
= Hasta
= Entrada
Adjust (v) / Tune (v) = Ajustar
Glossy (adj) / Bright (adj) / Shiny (adj) = Brillante
As (pre) / How (adv)
Bend (n) / Curve (n)
= Como
= Curva
From (pre) / Of (pre)
At (pre) / In (pre)
Turn (v) / Wind (v)
Do (v) / Make (v)
= De
= En
= Girar
= Hacer
More (adj) / Plus (pre) = Más
4 The codes in round brackets are (n)=noun, (v)=verb, and (adj)=adjective.

STS Design: Objectives and Method 30
Approved (adj) /Permitted (adj)
Put (v) / Set (v)
Rear (adj) / Subsequent (adj)
Overhaul (n) / Servicing (n)
Face (n) / Surface (n)
= Permitido
= Poner
= Posterior
= Revisión
= Superficie
It is also necessary to add that the choice of the STS writing rules has an impact on the choice of words. For example, if the subjunctive is not permitted in STS, there is no point in approving the conjunction “ hasta que” as an equivalent for “ until” or “ a menos que” as an equivalent for “ unless” , because they are followed by a sentence with a verb in the subjunctive, and are therefore unusable.
One of the limitations of using the SE dictionary as the basis for developing the STS dictionary is the fact that there may be words commonly used in Spanish technical manuals that have not been included because they happen not to be mentioned in the reference corpus. Therefore, an analysis based on a much larger corpus might result in a dictionary which was slightly different. In any case, we consider that our approach is still valid and its coverage is wide enough to represent most of the cases the technical writer may encounter.
In this chapter we presented a justification for the design of STS and explained how the SE guide was taken as the basis of analysis for its design. We discussed each of the main rules in turn and decided whether it was applicable to STS or not. Having explained the rationale behind the work, the next chapter presents a full version of the STS Guide, comprising both the Writing Rules and the General Vocabulary.
5 Note that “ thru (prep)” has a different meaning to “ through (prep)” . Both words are included in the
AECMA Guide. Thru means from X to Y “ inclusive” , e.g.: do steps 4 thru 10, and through means from one end or side to the other, “ by way of” , e.g.: the fluid goes through the tube.

This chapter presents a guide for the preparation of aircraft maintenance documentation in
STS. The purpose of this specification is to explain the rules and features of STS. This document is similar in structure to AECMA Document: PSC-85-16598, which describes the
AECMA SE specification (AECMA, 1998).
Although, the organisation of the STS Guide is complicated in nature, we have organised the material in two main parts to reduce its complexity. In the first part, we discuss the STS
Writing Rules while in the second part, we present the General Vocabulary.
The STS Writing Rules are discussed in the following sections:
1. WORDS,
2. NOUN PHRASES,
3. PREPOSITIONAL PHRASES,
4. VERBS,
5. SENTENCES,
6. PROCEDURES,
7. DESCRIPTIVE WRITING,
8. WARNINGS AND CAUTIONS,
9. PUNCTUATION AND WORD COUNTS.
First, we state each of the rules; then, we give a brief explanation of it followed by an example and its translation into English. Each of the examples represents an illegal STS version and its corresponding STS-compliant adaptation. All of the examples are taken from the reference corpus (see Appendix I). Warnings and Cautions examples appear in capital letters as this is an inherent rule of STS and AECMA SE specification. All the STS rules are also collected in a quick-reference list in Appendix II.

STS Specification 32
A
General
Vocabulary
B
Technical
Terms
The words which belong to Group A are included in the STS General Vocabulary. The second part of this chapter presents the list of the words included in this dictionary.
The words which belong to Group B are Technical Names (B.1) and Manufacturing
Processes (B.2).
Group B.1. Technical Names (20)
A word is a Technical Name if it belongs to one of the following 20 categories:
1. Names in the official parts information: (for example Illustrated Parts Catalogue or
engineering drawing):
Indicador de Descarga de Sobrepresión, Cilindro Extintor, Válvula de
Distribución
6 {Overpressure Discharge Indicators, Extinguishers Cylinders, Distribution
Valves}
2. Names of locations on the aircraft:
Ala, cabina, fuselaje
{Wing, cabin, fuselage}
6 Translations will be included in curly brackets.

STS Specification
3. Names of tools or equipment:
Palancas FIRE, cilindro extintor, manómetro
{FIRE levers, extinguisher cylinder, pressure gauge}
4. Names of materials, consumables, and unwanted matter:
Carga de pólvora, agente extintor, nitrógeno
{Powder charge, extinguisher agent, nitrogen}
5. Names of aircraft support facilities:
Aeropuerto, hangar, pista
{Airport, hangar, apron}
6. Names of circuits or systems, their parts and locations in them:
Sistema de extinción de incendios de motor, panel de interruptores automático, unidad de control FIRE
{Engine fire extinguisher system, circuit breaker panels, FIRE Control Unit}
7. Mathematical, scientific, and engineering terms:
Temperatura, presión, densidad
{Temperature, pressure, density}
8. Navigation and flying terms:
Altitud, latitud, aire
{Altitude, latitude, air}
9. Units of measurement or dial markings:
Grados (ºC), minutos (´), segundos (´´)
{Degrees (C) , minutes (´), seconds (´´)}
10. Numbers:
Dos, 1500, primero.
{Two, 1500, first}
33

STS Specification
11. Names of persons, groups, or bodies:
Construcciones Aeronáuticas Sociedad Anónima (C.A.S.A), controlador aéreo, copiloto
{Construcciones Aeronáuticas Sociedad Anónima (C.A.S.A), air controller, copilot}
12. Parts of the body:
Cabeza, pulmón, ojos
{Head, lung, eyes}
13. Common personal effects:
Gafas, mechero, ropa
{Glasses, cigarette lighter, clothing}
14. Medical terms:
Hepatitis, mareo, irritación cutánea
{Hepatitis, dizziness, skin irritation}
15. Documents, manuals or parts of manuals:
Diagrama, tabla, manual
{Diagram, table, manual}
16. Names, headings and topics used in specifications:
Generalidades, descripción de componentes, operación del sistema
{General, component description, system operation}
17. Names of technical records, standards, specifications, regulations:
Especificación AECMA 1000-D, AECMA Simplified English, Simplified
Technical Spanish
{AECMA Specification 1000-D, AECMA Simplified English, Simplified
Technical Spanish}
18. Environmental conditions:
Turbulencia, lluvia, tormenta
{Turbulence, rain, storm}
34

STS Specification 35
19. Colours:
Verde, azul, rojo
{Green, blue, red}
20. Damage terms:
Deformación, fractura, abrasión
{Deformation, fracture, abrasion}
Group B.2. Manufacturing Processes (6)
A word is a Manufacturing Process if it belongs to one of the following 6 categories:
1. Removes material:
Perforar, esmerilar, escariar
{Drill, grind, ream}
2. Adds material:
Aislar, reencauchar, remetalizar
{Insulate, retread, remetal}
3. Attaches material:
Soldar, remachar, doblar
{Weld, rivet, crimp}
4. Changes the mechanical strength, the structure, or the physical properties of a material:
Magnetizar, energizar, curar
{Magnetize, energisize, cure}
5. Changes the surface finish of a material:
Pulir, planchear, bruñir
{Polish, plate, burnish}
6. Changes the shape of a material:
Soldar, troquelar, extruir
{Cast, stamp, extrude}

STS Specification 36
At present the dictionary does not offer an approved definition for each of the words. That is something to be done in future research. However, we give here an example definition which illustrates the structure to follow when assigning the meaning to the words in the STS
General Vocabulary. In the following, we have selected the word “ facilita”:
El sistema de extinción de incendios de motor facilita a la tripulación los medios para sofocar cualquier incendio que se pueda producir en los dos motores. 7 [Doc_26-21-00]
{The engine fire extinguishing system installed on the aircraft supplies the flight crew with the facility to extinguish a fire in either engine.}
The verb “ facilitar” has the following approved meaning:
Hacer fácil o posible la ejecución de una cosa o la consecución de un fin.
(RAE, 1992) 8
{To make something easy or possible}
In the example, “ facilitar” has been used with an unapproved meaning, i.e.: “ dar” {To provide}
WRITE:
El sistema de extinción de incendios de motor da a la tripulación los medios para sofocar cualquier incendio que se pueda producir en los dos motores.
NOT:
El sistema de extinción de incendios de motor facilita a la tripulación los medios para sofocar cualquier incendio que se pueda producir en los dos motores.
7 We insert in brackets the document from which we have extracted the example. See Appendix I for document code identification. For example: Doc_26-21-00 corresponds to Chapter 26, Section 11 and
Subject Number 00.
8 This is an example taken from Diccionario de la Real Academia Española,1992. La Real Academia
Española (RAE) constitutes the linguistic authority for the Spanish language in Spain and South
America. RAE adopts a prescriptive approach towards the Spanish language.

STS Specification 37
In uncontrolled documentation, you can sometimes find different technical terms that refer to the same item.
Elemento sensor de incendios {Firewire detector element}
Sensor
Sensor de incendios
Elemento
{Detector}
{Firewire detector}
{Element}
The previous terms are interchanged within the manual [Doc_26-11-00], as they refer to the same item. Needless to say, this can be an important source for semantic ambiguity, especially when the term “ elemento” is used in the same document to refer to a different item:
El sensor se divide en dos bucles: uno que pasa alrededor de la zona superior del motor, y el otro por el fondo de la góndola para vigilar la parte inferior de la zona del motor. Los elementos están conectados con el cableado del avión a través de receptáculos de mamparos [ . . .]
{The detector is divided into two loops, one is routed around the upper area of the engine, the other loop is attached to the bottom of the nacelle to monitor the lower area of the engine zone. The elements are interfaced to the aircraft wiring through bulkhead receptacles […]}
In the above example, what does “ elementos ” {elements} refer to? It is quite ambiguous, but it could refer to “ bucles” {loops} , the only plural substantive mentioned before. If such is the case, later on, we find that “ elemento” {element} refers to “ el elemento sensor de incendios”
{Firewire detector element}:
El elemento está conectado para formar un bucle continuo […]
{The element is connected to form a continuous loop […]}
It is necessary to be consistent and use the same technical term for the same item or manufacturing process, otherwise we may construct ambiguous sentences, as in the case above.

STS Specification 38
Articles and demonstratives make the text more specific, which helps to avoid ambiguity.
The writer may be tempted not to use them because the text will sound more official or the text will be shorter. However, the end result may be ambiguity.
WRITE:
EL INDICADOR DE PRESIÓN HIDRÁULICA DD3 NO OPERA,
ESTANDO LAS MOTOBOMBAS FUNCIONANDO.
NOT:
INDICADOR DE PRESIÓN HIDRÁULICA DD3 NO OPERA,
ESTANDO MOTOBOMBAS FUNCIONANDO. [Doc_29-30-00]
{HYDRAULIC PRESSURE INDICATOR DD3 FAILS TO OPERATE WITH
PUMPS RUNNING.}
Exemption:
When we need to write a series of nouns, it is not necessary to write the article or demonstrative in front of each noun:
EFECTUAR LA OPERACIÓN DE MANTENIMIENTO EN LOS
MANDOS MECÁNICOS DE VUELO, SUPERFICIES DE MANDO
PRIMARIOS DE VUELO, TRENES DE ATERRIZAJES Y
COMPUERTAS DE CARGA [...] [Doc_29-00-00].
{PROCEED WITH MAINTENANCE WORK NEAR MECHANICAL FLIGHT
CONTROLS OR PRIMARY FLIGHT CONTROL SURFACES, LANDING
GEARS AND CARGO DOOR […]}
In Spanish, you can use one or more nouns in order to describe or modify another noun with

STS Specification 39 the help of a preposition. These word structures consist of several combined prepositional phrases. When there are more than three prepositional phrases together, it is sometimes difficult to understand which prepositional phrase modifies which. As a result, the overall meaning of the sentence is hard to comprehend. There are ways to convey these complex structures in a clearer form. For example, you may use relative clauses as in the following
(prepositional phrases are underlined):
WRITE:
Se enciende el módulo ENG FIRE en la central de aviso de fallos que hay en la cabina de pilotos.
NOT:
Se enciende el módulo ENG FIRE en la central de aviso de fallos de la cabina de pilotos [...] [Doc_26-11-00]
{"ENG FIRE" caption comes on in the cockpit warning annunciator panel and warning signs flash [...]}
rd
rd
rd
rd
The next few paragraphs give examples of the different verb tenses allowed in STS.
The Present Simple should be used only in the third person singular and the third person plural:

STS Specification 40
Cuando la temperatura supera un nivel crítico en la góndola, la unidad de control transmite señales de aviso de fallo a los instrumentos indicadores de la cabina de pilotos. [Doc_26-11-00]
{Should the temperature within the nacelle rise to a critical level, the control unit transmits warning signals to indicating devices within the cockpit.}
The Future Simple should be used only in the third person singular and the third person plural:
El resultado será el mismo que en los pasos (a) y (e). [Doc_26-21-00]
{Results (will be) as steps (a) thru (e).}
In Spanish, you express commands with a specific verb tense called the imperative tense.
Nevertheless, for technical documentation, we use the infinitive form for commands or instructions.
9 NO EXPONER EL CILINDRO EXTINTOR A TEMPERATURAS POR
ENCIMA DE LOS 70 ºC. [Doc_26-21-11]
{DO NOT EXPOSE THE EXTINGUISHER CYLINDER TO TEMPERATURES
ABOVE 70 ºC.}
By ‘final value’ we mean to use the infinitive to introduce a subordinate clause which expresses the aim of an action (oración subordinada adverbial final).
El piloto tira de la palanca para energizar el sistema. [Doc_26-21-00]
{The pilot pulls the handle to supply power to the system.}
Those cases in which the infinitive is not used with an imperative or a modal value should be avoided. Use a personal form of the verb instead. In the following example the infinitive
“ Cortar” has been used with other than the imperative or the final value. For that reason, we have changed the infinitive into a personal form of the verb, i.e., the present simple:
9
The form that actually appears in [Doc_26-21-11] is “ NO SE DEBE EXPONER EL CILINDRO
EXTINTOR A TEMPERATURAS POR ENCIMA DE LOS 70 ºC” . However, the verbal periphrasis
DEBER + INFINITIVE ( MUST + INFINITIVE ) is illicit. For this reason, the approved version of the sentence is chosen. To understand the concept of verbal periphrasis refer to Section 5.6.2.

STS Specification 41
WRITE:
El piloto tira de la palanca para energizar el sistema y, como consecuencia, produce los resultados siguientes: - Corta el suministro de combustible al motor [...].
NOT:
El piloto tira de la palanca para energizar el sistema, produciendo los resultados siguientes: - Cortar el suministro de combustible al motor [...].
[Doc_26-21-00]
{The pilot pulls the handle to supply power to the system and produces the following results: - Shuts off the engine fuel supply [...].}
The past participle in Spanish may function as an adjective (see example below) or as a verb to introduce a subordinate clause. In this guide, we accept the past participle only with its adjectival value.
Las tarjetas impresas están colocadas en paralelo dentro de una caja de acero inoxidable herméticamente cerrada. [Doc_26-11-00]
{The circuit boards are installed in sandwich form within a hermetically sealed stainless steel case.}
When the past participle does not have an adjectival value, it is necessary to introduce a relative clause to be compliant with STS. When the past participle does not have an adjectival value, it functions as a verb. In this case, we use relative clauses to avoid ambiguity. A relative clause usually starts with a relative pronoun, generally QUE {that} + a verb in a personal form.
WRITE:
La cabeza actuadora está formada por una palanca actuadora, una boquilla y una palanca de control que se acciona por el pulgar.
NOT:
La cabeza actuadora está formada por una palanca actuadora, una boquilla y una palanca de control accionada por el pulgar. [Doc_26-22-00]
{The operating head is made up of an actuating handle, a nozzle, and a thumboperated control lever.}

STS Specification 42
By ‘modal value’ we mean those cases in which the present participle is used to introduce a subordinate clause that specifies the way of how to obtain a result:
La alarma acústica puede anularse, pulsando cualquiera de los interruptores de las luces principales de aviso de fallos. [Doc_ 26-11-00]
{The audible alarm may be cancelled by pressing either of the master warning sign switches.}
There are many other ways in which the present participle may be used in Spanish, but they generate ambiguity, see the example below:
Los elementos están conectados con el cableado del avión a través de receptáculos de mamparos, quedando conectados a las unidades de control
WC11 (WC12) [...] [Doc_26-11-00]
{The elements are interfaced to the aircraft wiring through bulkhead receptacles and are connected to control units WC11 (WC12) [...]}
It is not clear if the subject of the verb “ quedando” refers to “ elementos” (elements) or
“ receptáculos de mamparos” (bulkhead receptacles). In this case the use of the present participle has clearly caused ambiguity.
It is also common to find instances of sentences in which the present participle is used when an action takes place before another action. However, this is non-complaint with STS. In those cases, it is recommended to use linking words such as, como consecuencia
{consequently}, así {thus}, etc. plus the verb in an approved personal form. The above example thus becomes:
WRITE:
Los elementos están conectados con el cableado del avión a través de unos receptáculos de mamparos. Como consecuencia, los elementos se conectan a las unidades de control WC11 (WC12) [...]
{The elements are interfaced to the aircraft wiring through bulkhead receptacles and are connected to control units WC11 (WC12) [...]}
Table 1 represents a summary of the approved tenses in STS. The non-personal forms are only permitted in certain cases, as explained above. These cases are shown in the table

STS Specification 43 under the term ‘Value’ .
Approved Tense
Present Simple
Future Simple
Infinitive
Present participle
Past Participle
Value
Present
Future
Imperative & Final
Modal
Adjectival
Table 5.1. Approved Tenses and their Value
In Spanish, a verbal periphrasis is a syntactical construction that consists of two or more contiguous verbs, none of which are any of the auxiliary verbs used to form complex tenses.
Of the combined verbs, one is the main one (a non-personal form verb: infinitive, present participle or participle) and the other/s are helping verbs. Currently, STS permits the following verbal periphrases:
- V. ESTAR + PAST PARTICIPLE [Only the forms está and están]
La cabeza actuadora está formada por una palanca actuadora, una boquilla y una palanca de control [...]. [Doc_26-22-00]
{The operating head is made up of an actuating handle, a nozzle, and a control lever [...].}
- V. PODER + INFINITIVE [Only the forms puede and pueden]
UNA EXPLOSIÓN ACCIDENTAL PUEDE CAUSAR DAÑOS.
[Doc_26-21-11]
{ACCIDENTAL DETONATION OF A CARTRIDGE CAN CAUSE INJURY.}
In Spanish, the verb can be instantiated in three different moods: indicative, subjunctive and imperative. Each of the moods has its own inflection:
• The indicative mood is used to express mainly real facts.
• The subjunctive mood relates to possibilities, but never to real facts. When it is not clear

STS Specification 44 when an action is going to take place, i.e., in cases when details are unspecified, the subjunctive mood is used.
• The imperative mood is exclusively used to give orders or ask for something in a commanding way.
The very nature of technical documentation requires the use of the indicative, as it adds accuracy to the text. The imperative mood is necessary to state instructions. Although we do not use the imperative mood form explicitly in this guide, it is implicitly used when we use the infinitive to write instructions. As the subjunctive mood leads towards unspecific statements it can not be used in STS.
WRITE:
Corregir cuando es necesario. [Indicative Mood; 3 rd Person Singular]
NOT:
Corregir según sea necesario. [Subjunctive Mood; 3 rd Person Singular]
[Doc_29-30-11]
{Take remedial action as required.}
In an active sentence, the subject does the action of the verb:
Dos manocontactores (4) [Subject] envían el aviso de insuficiente presión en la bomba a la central de aviso de fallos en la cabina del piloto [...].
{Two pressure switches [Subject] relay the warning of low pump pressure to the flight compartment central warning panel [...].}
In a passive sentence, the subject receives the action of the verb. The agent does the action of the verb and is usually introduced by the particle “ por” in Spanish.
El aviso de insuficiente presión en la bomba [Subject] es enviado a la central de aviso de fallos en la cabina de pilotos por dos manocontactores
(4) [Agent] [...]. [Doc_29-10-00]
{Warning of low pump pressure [Subject] is relayed to the flight compartment central warning panel by two pressure switches (4) [Agent] […].}

STS Specification 45
The syntactic structure of the passive voice in Spanish is as follows:
(1) Traditional Passive [Pasiva]
PASSIVE SUBJECT + [V. SER+ P. PARTICIPLE] + (COMPLEM.) + [“ POR” +AGENT]
If we take as example the previous sentence, the following is the equivalent to each of the traditional passive constituents:
PASSIVE SUBJECT [El aviso de insuficiente presión en la bomba]
V. SER [es]
PAST PARTICIPLE [enviado]
COMPLEMENTS
“ POR”
AGENT
[a la central de aviso de fallos en la cabina del piloto]
[por]
[dos manocontadores]
(2) Reflexive Passive [Pasiva Refleja]
Reflexive Passives are a type of sentence that use the particle “ SE” in order to cover up for the agent of the action. Therefore, semantically, they do not have a subject, but they do have a subject syntactically. They always lack the presence of the agent as this is embodied by the particle “ SE” .
PASSIVE SUBJECT + “ SE” + VERB (Personal Form) + (COMPLEMENTS)
In the example:
El módulo ENG FIRE se enciende en la central de aviso de fallos de la cabina de pilotos [Doc_26-11-00].
{“ ENG FIRE” caption comes on in the cockpit warning annunciator panel.} the following is the equivalent to each of the reflexive passive constituents:
PASSIVE SUBJECT [El módulo ENG FIRE]
“ SE” [se]
VERB
COMPLEMENTS
[enciende]
[en la central de aviso de fallos de la cabina de pilotos]

STS Specification 46
Also,
- “ SE” + VERB (Personal Form) + PASSIVE SUBJECT + (COMPLEMENTS)
In the example:
Se enciende el módulo ENG FIRE en la central de aviso de fallos de la cabina de pilotos. [Doc_26-11-00]
{“ ENG FIRE” caption comes on in the cockpit warning annunciator panel.} the following is the equivalent to each of the reflexive passive constituents:
“ SE”
VERB
[se]
[enciende]
PASSIVE SUBJECT [El módulo ENG FIRE]
COMPLEMENTS [a la central de aviso de fallos de la cabina de pilotos]
The traditional Spanish passive construction has the same structure as the passive in
English. However, the traditional passive does not occur as frequently in Spanish as it does in English. Instead, it is very common to find the reflexive passive.
As mentioned in Rule 4.4, it is highly recommended to use the active voice in STS. In order to achieve this, we now explain how to change a traditional passive into an active construction in Spanish.
PASSIVE SUBJECT + [V.SER [Tense “ X” ] + [V. “ Y” [Tense PP] + OC + [“ POR” AGENT]
ACTIVE SUBJECT + [V.” Y” [Tense “ X” ]] + COMPLEMENT + OC
Figure 5.1 De-Passivisation of a Spanish Sentence
V stands for verb; “ X” is a variable for any of the personal from verb tenses approved in
STS, e.g. present simple or future simple; “ Y” stands for any of the approved verbs in STS;
PP stands for Past Participle; OC stands for Other Complements.

STS Specification 47
Transformation Phase
Passive
[“ POR” + AGENT]
[V. SER [tense X] + V. Y [tense PP]]
PASSIVE SUBJECT
(OC)
Example:
Active
ACTIVE SUBJECT
[V.Y [tenseX]]
COMPLEMENT
(OC)
ACTIVE VOICE: Un desplazamiento [...] + es + transmitido + por un transmisor
PASSIVE VOICE: Un transmisor + transmite + un desplazamiento [...]
PASSIVE VOICE: {Displacement […] is relayed by a transmitter }
ACTIVE VOICE: {A transmitter relays displacement […]}
The primary function of a verb is to describe an action.
WRITE:
NOT:
El relé de avido de peligro se enegiza e indica el aviso en la cabina de pilotos.
El relé de aviso de peligro se energiza y facilita una indicación de aviso en la cabina de pilotos. [Doc_26-11-00].
{A warning relay will then energize, giving a warning indication in the cockpit.}
Spanish is a language which permits rather long sentences because of the great variety of subordinate structures that can be combined. This can increase the complexity of the technical document as the reader can easily be overwhelmed by long sentences. If we write a topic per sentence, the result will automatically be a text with shorter sentences.

STS Specification 48
WRITE:
El subconjunto de refrigeración del aceite (1) es de construcción monobloque. Este subconjunto tiene unas placas, unas barras y unas aletas laterales.Las placas están colocadas de forma alterna. Las barras y las aletas laterales están contenidas en un conjunto de conducto de aire (14). Este conjunto tiene una válvula bypass (17) en su parte superior. La válvula bypass tiene dos bocas hidraúlicas (15) y (16). La boca (15) sirve para conectar la tubería (12) de entrada del fluido purgado de la caja y la boca
(16) sirve para conectar el depósito hidraúlico del avión.
NOT:
El subconjunto de refrigeración del aceite (1) es de construcción monobloque y consta de unas placas colocadas de forma alterna, unas barras y aletas laterales, contenidas en un conjunto de conducto de aire (14).
Una válvula bypass (17) se encuentra montada en la parte superior del conjunto, y tiene dos bocas hidráulicas (15) y (16). La boca (16) se utiliza para la conexión de la tubería (12) de entrada del fluido purgado de la caja, y la boca (15) sirve para la conexión con el depósito hidráulico del avión.
[Doc_21-10-00]
{The oil cooler subassembly (1) is of monoblock construction and consists of alternately stacked plates, side bars and fins encased within an air duct assembly
(14). A bypass valve (17) is installed at the top of the assembly and is provided with two hydraulic ports (15), (16). Port (16) provides connection for the case drain fluid inlet pipeline (12), and port (15) connection to the aircraft hydraulic reservoir.}
If necessary, break up your sentences and use connecting words which indicate the relationship between them. Example: Además {in addition}, sin embargo {however}, como consecuencia, {consequently}, etc.
WRITE:
La indicación se anula. Como consecuencia, los interruptores de prueba vuelven a la posición OFF.

STS Specification 49
NOT:
La indicación se anula volviendo los interruptores de prueba a la posición
OFF. [Doc_26-11-00]
{The indication is cancelled by returning the test switches to the OFF position.}
When two actions happen simultaneously or almost at the same time, you can coordinate the two sentences to show this effect. If you use the same sentence structure for coordination, the overall result will be a clearer text.
WRITE:
Se enciende el módulo ENG FIRE en la central de aviso de fallos de la cabina de pilotos y parpadean las luces principales de aviso de fallos.
NOT:
Se enciende el módulo ENG FIRE en la central de aviso de fallos primaria de la cabina de pilotos y las luces principales de aviso de fallos parpadean.
[Doc_26-11-00]
{"ENG FIRE" caption comes on in the cockpit warning annunciator panel and warning signs flash.}
In some cases, we may think that by omitting words such as determiners, the resulting text may sound more official. However, this practice is not recommended because it may lead to ambiguity.
WRITE:
El sistema de frenado está equipado con un sistema anti-skid, que permite emplear el máximo de presión hidráulica en todas las condiciones.
Or:
Este sistema está equipado con un sistema anti-skid, que permite emplear el máximo de presión hidráulica en todas las condiciones.

STS Specification 50
NOT:
Está equipado con un sistema anti-skid, que permite emplear el máximo de presión hidráulica en todas las condiciones. [Doc_29-00-00]
{The normal braking system applies hydraulic brake pressure to all four main wheel brakes and has an anti-skid system to let maximum brake pressure be used in all conditions.}
If you omit the subject (a noun phrase), the reader will not know what things are referred to.
Similarly, if you omit the verb, the reader will not know which action is to be performed.
The maximum length of procedural sentences is 25 words. (Refer to Section 9 for the rules about word count).
WRITE:
(1) Energizar la dirección de rueda de morro. (seven words)
(2) Operar cinco veces el sistema de dirección en ambas direcciones, con la rueda de mando de dirección y en intervalos de 30 segundos. (twentythree words)
NOT:
Energizar la dirección de rueda de morro y, con la rueda de mando de dirección, operar cinco veces el sistema de dirección en ambas direcciones, con intervalos de 30 segundos entre operaciones. (thirty-two words)
[Doc_29-00-00]
{Switch on nosewheel steering, and with the steering handwheel, operate the steering system five times in both directions with a 30 second interval between each operation.}
If you write several instructions in the same sentence, you will overwhelm your reader.
Therefore, it is convenient to write one instruction at a time. This will allow an instruction to

STS Specification 51 be carried out before the next is started.
WRITE:
1. Cerrar las boquillas de purgado (2).
2. Quitar los tubos de purgado (3).
3. Apretar las boquillas de purgado (2).
4. Frenar con alambre nuevo.
NOT:
Cerrar las boquillas de purgado (2), quitar los tubos de purgado (3), apretar las boquillas de purgado (2) y frenar con alambre nuevo. [Doc_29-10-00]
{Close bleed nipples (2), remove bleed tubes (3), tighten bleed nipples (2) and secure with new lockwire.}
There are cases when two instructions or more are done simultaneously. In these cases, you can write them all in the same sentence:
Durante la operación de los frenos, comprobar si las tuberías hidráulicas vibran, y vigilar el indicador (2) de cantidad de fluido hidráulico. [Doc_29-
00-00]
{During operation, check hydraulic pipelines for vibration and monitor hydraulic quantity indicator (2).}
WRITE :
DESECHAR EL FLUIDO HIDRAÚLICO DRENADO O PURGADO DEL
AVIÓN. NO VOLVER A UTILIZAR ESTE FLUIDO EN LOS SISTEMAS DEL
AVIÓN.

STS Specification 52
NOT:
EL FLUIDO HIDRAÚLICO DRENADO O PURGADO DEL AVIÓN DEBE SER
DESECHADO, NO DEBE VOLVER A UTILIZARSE EN LOS SISTEMAS DEL
AVIÓN. [Doc_29-00-00]
{HYDRAULIC FLUID DRAINED FROM THE AIRCRAFT HYDRAULIC POWER
SYSTEM MUST NOT BE USED AGAIN IN THE AIRCRAFT SYSTEM.}
- Girar [Infinitive with commanding value] la palanca FIRE L ENG WB7 de EFSS a DISCH 2 (DCHA). Se enciende [Present simple, third person
singular] el aviso luminoso DISCH en el indicador WB11. [Doc_26-21-00]
{- Turn FIRE L ENGINE WB7 EFSS handle to DISCH 2 (Right). WB11 indicator lighted caption DISCH comes on.}
ANTES DE SUMINISTRAR ENERGÍA ELÉCTRICA AL AVIÓN,
ASEGURARSE DE QUE ESTÁN AISLADOS TODOS LOS CIRCUITOS
SOBRE LOS QUE SE TRABAJA. [Doc_29-30-11]
{BEFORE ELECTRICAL POWER IS APPLIED TO THE AIRCRAFT, MAKE SURE
THAT ELECTRICAL CIRCUITS UPON WHICH WORK IS IN PROGRESS ARE
ISOLATED.}
Avoid abstractions such as:
EL EQUIPO PUEDE DAÑARSE SI LAS SEÑALES CONTIENEN PARTES
METÁLICAS.
{DAMAGE TO THE EQUIPMENT CAN OCCUR IF THE LABELS CONTAIN
METALLIC PARTS.}

STS Specification 53
WRITE:
ASEGURARSE DE QUE LAS SEÑALES NO CONTIENEN PARTES
METÁLICAS PARA EVITAR DAÑOS AL EQUIPO. [CASA_CAUTIONS_LIST]
{MAKE SURE THAT THE SIGNS DO NOT CONTAIN METALLIC PARTS TO AVOID
DAMAGE TO THE EQUIPMENT.}
The number of words permitted in descriptive writing is higher than the number allowed in procedural writing because descriptive text is generally more complex. Refer to Section 5.11 for word counts.
FIRST VERSION (UNCONTROLLED)
El subconjunto de refrigeración del aceite (1) es de construcción monobloque y consta de unas placas colocadas de forma alterna, unas barras y aletas laterales, contenidas en un conjunto de conducto de conducto de aire (14). Una válvula bypass (17) se encuentra montada en la parte superior del conjunto, y tiene dos bocas hidraúlicas (15) y (16). La boca
(16) se utiliza para la conexión de la tubería (12) de entrada del fluido purgado de la caja y la boca (15) sirve para la conexión con el depósito hidráulico del avión.
[Doc_29-10-00]
Sentence 1: 34 words,
Sentence 2: 21 words,
Sentence 3: 34 words.
IMPROVED VERSION (CONTROLLED)
El subconjunto de refrigeración del aceite (1) es de construcción monobloque. Tiene unas placas colocadas de forma alterna, unas barras y unas aletas laterales, las cuales están contenidas en un conjunto de conducto de aire (14). En su parte superior, este conjunto tiene una válvula bypass a la que se unen dos bocas hidráulicas (15) y (16). La boca (15) se usa para conectar con el depósito hidráulico del avión y la boca (16) para conectar la tubería (12) de entrada del fluido purgado de la caja.

STS Specification 54
Sentence 1: 11 words,
Sentence 2: 25 words,
Sentence 3: 21 words,
Sentence 4: 30 words,
{The oil cooler subassembly (1) is of monoblock construction and consists of alternately stacked plates, side bars and fins encased within an air duct assembly
(14). A bypass valve (17) is installed at the top of the assembly and is provided with two hydraulic ports (15), (16). Port (16) provides connection for the case drain fluid inlet pipeline (12), and port (15) connection to the aircraft hydraulic reservoir.}
If you present several topics in the same paragraph, the reader may be overwhelmed with different ideas. This makes it difficult to assimilate the information. Therefore, the reader will be able to comprehend the message more clearly if the writer presents only one topic per paragraph. (See the example following Rule 7.4)
In descriptive writing, paragraphs are used to show the logic of the text. Each paragraph represents a complete unit of information, which starts with a topic sentence, followed by more detailed information on the topic itself. If the topic requires more than a paragraph to be detailed, separate your topic into subtopics and deal with each subtopic in a different paragraph. (See example below Rule 7.4)
If you present new and complex information quickly, you will overload your reader with information. The reference corpus presents a considerable amount of descriptive text in an overwhelming way. The evidence for this is that the average paragraph length is very low (4 sentences). In consequence it is likely that a lot of complex and new information is being presented quickly in very long sentences.

STS Specification 55
FIRST VERSION (UNCONTROLLED)
Los contactos del interruptor DISCH 2 de WB7, se cierran para conectar los
28 V c.c., a través de la borna V de WB7a, al indicador de descarga WB9, encender la luz DISCH, y aplicar energía para detonar el extintor automático izquierdo, WB5, por la salida izquierda, vaciando completamente el agente extintor en la zona del motor izquierdo. [Doc_26-
21-00]
IMPROVED VERSION (CONTROLLED)
Los contactos del interruptor DISCH 2 de WB7 se cierran para:
- conectar los 28 V c.c. al indicador de descarga WB11, a través de la borna k de WB7a,
- encender la luz DISCH y
- aplicar energía para detonar el extintor automático derecho, WB6, por la salida izquierda.
Como consecuencia, el agente extintor derecho se vacía completamente en la zona del motor izquierdo.
{WB7, DISCH 2 switch contacts close to connect 28V dc via WB7a pin K to
WB11 discharge indicator causing DISCH light to come on and applies power to
WB6 "R ENG" automatic fire extinguisher left outlet which totally empties the right extinguisher into the left engine zone.}
Long paragraphs may confuse the reader about the general idea the writer is trying to convey.
By repeating the concept, the writer can add coherence and consistency to the text as the relationship between sentences and paragraphs will be clearly stated.
WRITE:
[El subconjunto de refrigeración del aceite (1) ] Tiene unas placas colocadas de forma alterna, unas barras y unas aletas laterales, las cuales

STS Specification 56 están contenidas en un conjunto de conducto de aire (14). En su parte superior, este conjunto tiene una válvula bypass a la que se unen dos bocas hidráulicas (15) y (16). [Doc_29-10-00]
NOT:
[El subconjunto de refrigeración del aceite (1) ] Tiene unas placas colocadas de forma alterna, unas barras y unas aletas laterales, las cuales están contenidas en un conjunto de conducto de aire (14). En su parte superior, éste tiene una válvula bypass a la que se unen dos bocas hidráulicas (15) y (16).
{The oil cooler subassembly (1) has alternately stacked plates, side bars and fins encased within an air duct assembly (14). A bypass valve (17) is installed at the top of this and is provided with two hydraulic ports (15), (16).}
Warnings and cautions are usually part of procedural texts. A warning means that the technician can be injured or even die if the instructions are not followed correctly. A caution means the equipment can be damaged.
It is important that the technician knows from the start which is the procedure to follow in order to avoid the danger and/or damage. Give the command first and then the supporting information.
WRITE:
PRECAUCIÓN: LIMPIAR A FONDO, LO ANTES POSIBLE, TODAS LAS
SUPERFICIES METÁLICAS EXPUESTAS AL AGENTE EXTINTOR. LOS
EXTINTORES TIPO AGUA CONTIENEN UN AGENTE ANTICONGELANTE
MEZCLADO CON EL CONTENIDO DE AGUA. EL AGENTE
ANTICONGELANTE PUEDE CORROER LAS SUPERFICIES METÁLICAS.
NOT:
PRECAUCIÓN: LOS EXTINTORES TIPO AGUA CONTIENEN UN AGENTE
ANTICONGELANTE MEZCLADO CON EL CONTENIDO DE AGUA. EL
AGENTE ANTICONGELANTE PUEDE CORROER LAS SUPERFICIES
METÁLICAS. LIMPIAR A FONDO, LO ANTES POSIBLE, TODAS LAS

STS Specification 57
SUPERFICIES METÁLICAS EXPUESTAS AL AGENTE EXTINTOR. [Doc_26-
22-00]
{CAUTION: IN WATER TYPE EXTINGUISHERS, AN ANTI-FREEZE AGENT IS
MIXED WITH THE WATER CONTENT. THE ANTI-FREEZE AGENT CAN CORRODE
METAL SURFACES. THOROUGHLY CLEAN ALL METAL SURFACES THAT HAVE
BEEN EXPOSED TO THE EXTINGUISHING AGENT AS SOON AS POSSIBLE.}
The previous example is abstract. In order to make it more specific we could write something like:
PRECAUCIÓN: LIMPIAR A FONDO, LO ANTES POSIBLE, TODAS LAS
SUPERFICIES METÁLICAS EXPUESTAS AL AGENTE EXTINTOR PARA
EVITAR LA CORROSIÓN DE LAS SUPERFICIES METÁLICAS. LA CAUSA
DE LA CORROSION ES EL AGENTE ANTICONGELANTE QUE ESTA
CONTENIDO EN EL AGENTE EXTINTOR.
{CAUTION: THOROUGHLY CLEAN ALL METAL SURFACES THAT HAVE BEEN
EXPOSED TO THE EXTINGUISHING AGENT AS SOON AS POSSIBLE TO AVOID
THE CORROSION OF THE METAL SURFACES. THE CAUSE OF THE CORROSION
IS THE ANTI-FREEZE AGENT CONTAINED IN THE EXTINGUISHING AGENT.}
If we put the condition first, the technician will know that there is something to check before he or she performs an action. This will avoid the action being carried out without taking into account the necessary condition.
WRITE:
ANTES DE CONECTAR O DESCONECTAR EL CABLE DE PRUEBA DE
SUMINISTRO DE ENERGÍA, ASEGURARSE DE QUE LA ELECTRICIDAD
DE LA RED ESTÁ APAGADA.
{BEFORE YOU CONNECT OR DISCONNECT THE TEST-SET POWER-SUPPLY
CABLE, MAKE SURE THAT THE MAINS ELECTRICAL SUPPLY IS OFF.}

STS Specification 58
NOT:
ASEGURARSE DE QUE LA ELECTRICIDAD DE LA RED ESTÁ APAGADA
ANTES DE CONECTAR O DESCONECTAR EL CABLE DE PRUEBA DE
SUMINISTRO DE ENERGÍA. [CASA_WARNING LIST]
{MAKE SURE THAT THE MAINS ELECTRICAL SUPPLY IS OFF BEFORE YOU
CONNECT OR DISCONNECT THE TEST-SET POWER-SUPPLY CABLE}
FIRST VERSION (UNCONTROLLED)
Desconectar del receptáculo (11) el conector (2) del indicador de aviso de temperatura/interruptor de la motobomba; del receptáculo (10), el conector
(4) del manómetro indicador de presión hidraúlica; del receptáculo (9), el conector (5) del manómetro indicador de presión del freno; del receptáculo
(6), el conector (3) del manómetro indicador de presión del freno de emergencia; y del receptáculo (12), el conector (13) del indicador de cantidad de fluido hidraúlico. [Doc_29-30-11]
IMPROVED VERSION (CONTROLLED)
Desconectar:
-del receptáculo (11), el conector (2) del indicador de aviso de temperatura/interruptor de la motobomba;
-del receptáculo (10), el conector (4) del manómetro indicador de presión hidraúlica;
-del receptáculo (9), el conector (5) del manómetro indicador de presión del freno;
-del receptáculo (6), el conector (3) del manómetro indicador de presión del freno de emergencia;
-y del receptáculo (12), el conector (13) del indicador de cantidad de fluido hidraúlico.
{Disconnect pump switch/temperature warning indicator connector (2) from receptacle (11), hydraulic pressure indicator gage connector (4) from receptacle
(10), brake pressure indicator gage connector (5) from receptacle (9), emergency brake pressure indicator gage connector (3) from receptacle (6), and hydraulic quantity indicator gage connector (13) from receptacle (12).}

STS Specification 59
Examples :
1. Operación del Sistema (fig.6) [Doc_26-21-00]
{System Operation (fig.6)}
2. Desconectar del receptáculo (11), el conector (2) del indicador de aviso de temperatura/interruptor de la motobomba. [Doc_29-30-11]
{Disconnect pump switch/temperature warning indicator connector (2) from receptacle (11).}
3. Los cilindros extintores WB5 (WB6) son de forma semiesférica.
[Doc_26-21-00]
{The extinguisher cilindres WB5 (WB6) are semi-spherical in shape.}
4. E. Prueba
(1) Quitar los clips de seguridad con banderola.
(2) Meter los interruptores automáticos.
(3) Efectuar el ajuste/prueba. [Doc_26-21-11]
{E. Test
(1) Remove safety clips and tags.
(2) Close circuit breakers.
(3) Do adjustment/test}

STS Specification 60
ANTES DE APLICAR PRESIÓN AL SISTEMA DE ENERGÍA HIDRAÚLICA,
ASEGURARSE DE QUE LA POSICIÓN DE TODOS LOS MANDOS
CORRESPONDEN CON LA POSICIÓN REAL DE LOS SERVICIOS QUE
CONTROLAN. [Doc_29-00-00]
WRITE:
Descripción y Operación
NOT:
Descripcion y Operacion. [Doc_26-11-00]
{Description and Operation}
WRITE:
DETECCIÓN DE SOBRETEMPERATURA E INCENDIOS DE MOTOR
NOT:
DETECCION DE SOBRETEMPERATURA E INCENDIOS DE MOTOR
[Doc_26-11-00]
{ENGINE FIRE AND OVERHEAT DETECTION}
Cada cilindro contiene 2 kg (4,50 lb) de agente extintor presurizado por nitrógeno. (12 words – “ 2” counts as one word; “ (4,50 lb)” counts as one word) [Doc_26-21-00]
{Each cylinder contains 2 Kg (4,50 lbs) of extinguishing agent pressurized by nitrogen.}

STS Specification 61
La presión normal de carga es de 700 psi, aproximadamente. (10 words –
“ psi” counts as one word) [Doc_26-21-00]
{Normal charge pressure is around 700 psi.}
The example below represents a four-sentence paragraph:
El subconjunto de refrigeración del aceite (1) es de construcción monobloque. Tiene unas placas colocadas de forma alterna, unas barras y unas aletas laterales, las cuales están contenidas en un conjunto de conducto de aire (14). En su parte superior, este conjunto tiene una válvula bypass a la que se unen dos bocas hidráulicas (15) y (16). La boca (15) se usa para conectar con el depósito hidráulico del avión y la boca (16) para conectar la tubería (12) de entrada del fluido purgado de la caja.
{The oil cooler subassembly (1) is of monoblock construction and consists of alternately stacked plates, side bars and fins encased within an air duct assembly
(14). A bypass valve (17) is installed at the top of the assembly and is provided with two hydraulic ports (15), (16). Port (16) provides connection for the case drain fluid inlet pipeline (12), and port (15) connection to the aircraft hydraulic reservoir.}
We have now completed the discussion of the STS Writing Rules. Please refer to Appendix
II for a summary of all the STS rules.
The General Vocabulary shows all the words that are approved for use in Simplified
Technical Spanish. It also contains a few of the most common technical terms. The rest of these – both technical names and manufacturing processes – have been excluded. They constitute a different database which is usually the terminology database of the company.
Our terminology database for this project is composed of CASA terms. The General
Vocabulary consists of a list of 875 words. All the words in this dictionary are from aerospace technical manuals.

STS Specification 62
The development of the General Vocabulary involved finding equivalents for the words approved in SE, as well as the study of the words in their context by making use of the reference corpus. Refer to Section 4.6 in the previous chapter for further details of the method followed. See Appendix III for a complete list of words included in the STS dictionary. This only constitutes the first draft of the STS General Vocabulary as there may be additional words that technical writers consider necessary. In that case, new words can be included by consensus.
This chapter presented the STS specification. The next chapter describes the features and capabilities of a validating parser which has been develop for STS.

This chapter presents a parser which is capable of checking conformance with some of the
STS Writing Rules. First, a previously developed system called the Robust Layered Parser is described. The main differences between this and the STS parser are then outlined. Next, a complete description of the STS parser is given together with a specification of the checks that it can carry out. A brief description of the types of constructs included in the STS grammar is then given.
Following the experience of the SIFT information retrieval project (Hyland, Koch, Sutcliffe and Vossen, 1996) an algorithm was devised and implemented for providing partial parses.
In one project a detailed grammar for technical English was written and evaluated using the system which is known as the Robust Layered Parser (Sutcliffe, 2000). In this section, we describe the strategy underlying the system. The parser scans the text repeatedly analysing different constructs each time. Its operation can be summarised as follows:
1. The input to be analysed is first tagged for part-of-speech using a separate system, such as the Brill Tagger (1992). The result is a list of tokens and separate punctuation.
2. The parser scans the tagged input n times trying to analyse portions of it each time;
3. Each scan looks for instances of one construct. Corresponding to that construct is a context-free grammar. For n scans, therefore, there are n different grammars;
4. A construct recognised in a particular scan must be defined in terms of some combination of constructs recognised in previous scans (i.e. non-terminal symbols) together with zero or more tagged words (i.e. terminal symbols);
5. If an instance of a construct is found in the input to a scan, the instance is replaced by the parse tree for the construct;
6. The result of parsing is the output produced by the last scan.
To understand these stages, Sutcliffe (2000) provides an example of an English sentence:
‘save the file under a new name with the same extension’.
We will now explain how this sentence is analysed.

STS Parser: Description 64
1. The output of Part-of-Speech Analysis is: [save/’VB’, the/’DT’, file/’NN’, under/’IN’, a/’DT’, new/’JJ’, name/’NN’, the/’DT’, with / ’IN’, the/’DT’ same/’JJ’, extension/’NN’].
2. After this comes Noun Phrase Analysis. The tagged input is scanned looking for instances of noun phrases. the/’DT’, file/’NN’ is recognised as a noun phrase for which the analysis is [cnp, [np, [det, the/’DT’], [], [], [cn,
[ns, [n, file/ ’NN ’]]]]]. The/’DT’, file/’DT’ is therefore replaced by this analysis. Two other noun phrases are recognised in this pass: a/ ’DT’, new/’JJ’, name/’NN’ and the/’DT’, same/’JJ’, extension/’NN’.
3. Prepositional Phrase Analysis is now carried out, using as input the output produced from the previous scan. This now contains a mixture of terminal symbols and nonterminal symbols such as this Coordinated Noun Phrase ( cnp ): [cnp, [np, [det, a/’DT’], [], [adj, new/’JJ’], [cn, [ns, [n, name/’NN’]]]]].
As already stated, such parses are equivalent to non-terminal symbols which can potentially be recognised by future scans. During Prepositional Phrase Analysis, constructs denoted Coordinated Prepositional Phrase ( cpp ) are recognised. These broadly comprise a preposition (usually tagged IN ) followed by a Coordinated Noun
Phrase ( cnp ). One instance of such a sequence is under / ’IN’ followed by the cnp construct just discussed. The two are thus replaced by a parse of the resulting cpp,
[cpp, [pp, [cp, [p, under/’IN’]], [cnp, [np, [det, a/’DT’],
[], [adj, new/’JJ’], [cn, [ns, [n, name /’NN’]]]]]]]. A similar process is carried out on with / ’IN’ and [cnp, [np, [det, the/’DT’], [], [adj, same/’JJ’], [cn, [ns, [n, extension/’NN’]]]]] resulting in their replacement by [cpp, [pp, [cp,
[p, with/’IN’ ]], [cnp, [np, [det, the/ ’DT’], [], [adj, same/’JJ’],
[cn, [ns, [n, extension/’NN’]]]]]]].
4. The final stage of processing is Verb Group Analysis. The output from the previous stage complete with its parses for instances of cnp and cpp is scanned once more looking for verb groups. Save/ ’VB’ is duly recognised and replaced with [[cvg, vg, [v, save/’VB’]].

STS Parser: Description 65
The output of the entire parsing process is the result produced by the final scan, in this case
Verb Group Analysis. It comprises a list of parse trees corresponding to constructs recognised together with any tagged terminal symbols which were not recognised as part of any construct.
The Robust Layered Parser was used as a basis for the STS parser by taking the basic algorithm, developing a new grammar, designing an appropriate series of parses and finally implementing a number of grammatical checks based on the parser output.
Input
Document
STS
Grammar
Term
Recognition
Parsing
P-O-S
Tagging
Sentence
Length
Passive
Voice
Conformance
Checking
Words in
Lexicon
No. of
Commands
Ouput
Document
Figure 1. The STS Parser Architecture
PP-
Attatchment
The main changes made in order to develop the STS Parser were as follows:
1.
2.
3.
4.
The Spanish part-of-speech tagger within the Xerox Xelda system (Xelda, 2002) rather than the Brill tagger was used.
A pre-processing task to perform term recognition was added.
A different set of grammars was developed. (See Table 6.1 for the grammar constructs).
A different set of parsing passes based on the new grammars was adapted. The old passes were for Coordinated Noun Phrases (cnp), Coordinated Prepositional Phrases

STS Parser: Description 66
5.
(cpp) and Coordinated Verb Groups (cvg) in English. The new passes are for Noun
Phrases (snp), Prepositional Phrases (pp) and Verb Groups (vg) in Spanish.
Finally, post-processing routines to carry out a number of checks were developed:
The checks include Sentence Length, Words in Dictionary, Number of Prepositional
Phrases Modifying a Noun, Passive Voice and Multiple Commands in a Sentence.
Here we present a sentence from our reference corpus and explain exactly what happens to it during the pre-processing, parsing and post-processing stages.
Se enciende el módulo ENG FIRE en la central de aviso de fallos de la cabina de pilotos.
{"ENG FIRE" caption comes on in the cockpit warning annunciator panel.”}
The first stage of analysis requires Part-of-Speech tagging. We used the Xerox Xelda tagger which has 54 tags. See Appendix IV which shows the Spanish Part-of-Speech Tagset.
After running the Xelda tagger on the sentence we obtain the following output:
[Se/SE,enciende/VERBFIN,el/DETSG,módulo/NOUNSG,ENG/NOUNS
G,FIRE/NOUNSG,en/PREP,la/DETSG,central/NOUNSG,de/PREP,av iso/NOUNSG,de/PREP,fallos/NOUNPL,de/PREP,la/DETSG,cabina
/NOUNSG,de/PREP,pilotos/NOUNPL,./SENT]
Term recognition comes next. The system incorporates a previously developed term recognition package which is applied to the tagged sentences. It uses a database of terms which is specified by hand following a study of the reference corpus. In our sample
ENG_FIRE has been recognised as a term and thus appears as: 'ENG_FIRE'/'NOUNSG'.
The output after this stage is the input for parsing:
[Se/SE,enciende/VERBFIN,el/DETSG,módulo/NOUNSG,ENG_FIRE/
NOUNSG,en/PREP,la/DETSG,central/NOUNSG,de/PREP,aviso/NOU
NSG,de/PREP,fallos/NOUNPL,de/PREP,la/DETSG,cabina/NOUNSG
,de/PREP,pilotos/NOUNPL,./SENT]
Now the parsing process starts. The first pass is Noun Phrase Analysis. The tagged input is scanned looking for instances of noun phrases ( snp
). Six Noun Phrases are recognised and assigned the following analysis. The number within each snp indicates the type of noun phrase.

STS Parser: Description 67
Noun Phrase 1: el'/'DETSG','módulo'/'NOUNSG','ENG_FIRE'/'NOUNSG'
Analysis 1: snp( 5, [el/DETSG, módulo/NOUNSG, ENG_FIRE/NOUNSG] )
Noun Phrase 2:
'la'/'DETSG', 'central'/'NOUNSG'
Analysis 2: snp( 10, [ la/DETSG , central/NOUNSG ] )
Noun Phrase 3:
'aviso'/'NOUNSG'
Analysis 3: snp( 12, [aviso/NOUNSG] )
Noun Phrase 4: 'fallos'/'NOUNPL'
Analysis 4: snp( 12, [fallos/NOUNPL] )
Noun Phrase 5: 'la'/'DETSG','cabina'
Analysis 5: snp( 10, [la/DETSG, cabina/NOUNSG] )
Noun Phrase 6: 'pilotos'/'NOUNPL'
Analysis 6: snp( 12, [pilotos/NOUNPL] )
Portions of the input sentence are therefore replaced by the six analyses, while the rest of the words in the sentence are left unchanged. The result is as follows:
['se'/'SE','enciende'/'VERBFIN', snp(5, [el/DETSG, módulo/NOUNSG, ENG_FIRE/NOUNSG] ),
'en'/'PREP', snp( 10, [ la/DETSG , central/NOUNSG] ),
'de'/'PREP', snp( 12, [aviso/NOUNSG] ),
'de'/'PREP', snp( 12, [fallos/NOUNPL] ),
'de'/'PREP', snp( 10, [la/DETSG, cabina/NOUNSG] ),
'de'/'PREP', snp( 12, [pilotos/NOUNPL] ),./SENT]
During Prepositional Phrase Analysis, constructs denoted pp are recognised. One instance of such a sequence is a preposition followed by an snp which we have analysed in the previous scan. The two are thus replaced by a parse of the resulting pp . In our example, the system recognises five pp s, whose analyses are as follows:
Prepositional Phrase 1:
'en'/'PREP', snp( 10, [ la/DETSG , central/NOUNSG ] )
Analysis 1: pp( 1 , [ en/PREP, snp( 10, [ la/DETSG , central/NOUNSG ] ) ] )

STS Parser: Description 68
Prepositional Phrase 2:
’de’/’PREP’, snp( 12, [aviso/NOUNSG] )
Analysis 2: pp( 1 , [ de/PREP, snp( 12, [aviso/NOUNSG] ) ] )
Prepositional Phrase 3:
’de’/’PREP’ , snp( 12, [fallos/NOUNPL] )
Analysis 3: pp( 1 , [ de/PREP, snp( 12, [fallos/NOUNPL]) ] )
Prepositional Phrase 4:
’de’/’PREP’, snp( 10, [la/DETSG, cabina/NOUNSG] )
Analysis 4: pp( 1 , [ de/PREP, snp( 10, [la/DETSG, cabina/NOUNSG] ) ] )
Prepositional Phrase 5:
’de’/’PREP’, snp( 12, [piloto/NOUNPL] )
Analysis 5: pp( 1 , [ de/PREP, snp( 12, [pilotos/NOUNPL] ) ] )
These analyses result in the following output for the second scan:
[’se’/’SE’,’enciende’/’VERBFIN’, snp (5,[el/DETSG, módulo/NOUNSG, ENG_FIRE/NOUNSG] ), pp( 1 , [ en/PREP, snp( 10, [la/DETSG , central/NOUNSG] ) ] ), pp( 1 , [ de/PREP, snp( 12, [aviso/NOUNSG] ) ] ), pp( 1 , [ de/PREP, snp( 12, [fallos/NOUNPL]) ] ), pp( 1 , [ de/PREP, snp( 10, [la/DETSG, cabina/NOUNSG] ) ] ), pp( 1
, [ de/PREP, snp( 12, [pilotos/NOUNPL] ) ] ),./SENT]
The third scan looks for instances of prepositional-phrase sequences ( ppseq ). This construct has been added to the grammar in order to identify those cases in which more than three prepositional phrases are attached, a situation which violates the STS rules. There is a case of prepositional-phrase attachment in our example:

STS Parser: Description 69 pp( 1 , [ en/PREP, snp( 10, [ la/DETSG , central/NOUNSG
] ) ] ), pp( 1 , [ de/PREP, snp( 12, [aviso/NOUNSG] ) ]
), pp( 1 , [ de/PREP, snp( 12, [fallos/NOUNPL]) ] ), pp(
1 , [ de/PREP, snp( 10, [la/DETSG, cabina/NOUNSG] ) ] ), pp( 1 , [ de/PREP, snp( 12, [pilotos/NOUNPL] ) ] )
Analysis: ppseq( 5, [[en/PREP, [el/DETSG, central/NOUNSG]],
[de/PREP, [aviso/NOUNSG]], [de/PREP, [fallos/NOUNPL]],
[de/PREP, [el/DETSG, cabina/NOUNSG]], [de/PREP,
[pilotos/NOUNPL]]]])
This analysis results in the following:
[’se’/’SE’,’enciende’/’VERBFIN’, snp ( 5,[el/DETSG, módulo/NOUNSG, ENG_FIRE/NOUNSG] ), ppseq( 5, [[en/PREP,
[la/DETSG, central/NOUNSG]], [de/PREP, [aviso/NOUNSG]],
[de/PREP, [fallos/NOUNPL]], [de/PREP, [la/DETSG, cabina/NOUNSG]],[de/PREP, [pilotos/NOUNPL]] ),./SENT)
This output is then used as input for the last scan, which looks for verb group ( vg ). One verb group is recognised:
Verb Group : 'se'/'SE','enciende'/'VERBFIN'
Analysis
: vg3([se/SE, enciende/VERBFIN]).
This analysis is then replaced in the sentence and the final parsing output is:
[vg3([se/SE, enciende/VERBFIN]), snp(5,[el/DETSG, módulo/NOUNSG, ENG_FIRE/NOUNSG] ), ppseq( 5, [[en/PREP,
[la/DETSG, central/NOUNSG]], [de/PREP, [aviso/NOUNSG]],
[de/PREP, [fallos/NOUNPL]], [de/PREP, [la/DETSG, cabina/NOUNSG]], [de/PREP, [pilotos/NOUNPL]] ),./SENT] )
Once the parsing is finished, a number of post-processing checks are carried out. These involve verifying sentence length, checking words in the STS lexicon, counting the number of prepositional phrases modifying a noun, detecting instances of the passive voice and looking for multiple commands in a sentence. In our example, the system outputs only one error which relates to the number of prepositional phrases attached to each other. The error reads:

STS Parser: Description 70
Error: Sentence ‘se enciende el módulo en la central de aviso de fallos de la cabina de pilotos’ contains more than 3 attached pps [[en/PREP, [la/DETSG, central/NOUNSG]], [de/PREP, [aviso/NOUNSG]], [de/PREP,
[fallos/NOUNPL]], [de/PREP, [la/DETSG, cabina/NOUNSG]],
[de/PREP, [pilotos/NOUNPL]]] which is not allowed.
In the next section, we describe each of the conformance checks which the system can perform.
There are five conformance checks. Each one tries to find cases in which a particular STS rule is infringed. The checks are carried out after the parsing process in the following order:
1. Sentence Length,
2. Words in Dictionary,
3. Passive Voice,
4. Number of Prepositional Phrases Modifying a Noun,
5. Multiple Commands in a Sentence.
The Sentence Length check counts the number of words in the sentence. It distinguishes between descriptive and procedural sentences. If the sentence is descriptive the maximum number of words allowed is 30. In the case of procedural sentences, the number of allowed words is reduced to 25. Punctuation is not counted in this process. If the number of words has been exceeded, the system outputs an error message. This check tries to account for
Rule 6.1 and Rule 7.1 in Sections 6 and 7 respectively of the STS Guide (Appendix III).
The Dictionary check verifies that all words in the sentence are valid. To carry out this task this routine makes sure that all the words in the sentence, except those which have been recognised as technical terms, are in the STS Dictionary database. If there are words which are not in this database, an error message will be output for such words. This check implements Rule 1.1 in Section 1 of the STS Guide.
The Passive Voice check identifies those cases in which a passive voice sentence has been included. The system searches for constructs of type vg1 in the grammar. If one of these constructs is detected an error message is output. This check tries to apply Rule 4.4 in
Section 4 of the STS Guide.

STS Parser: Description 71
The Number of Prepositional Phrases Modifying a Noun check searches for those cases in which there are more than three adjacent prepositional phrases in a sentence. When an instance is found an error message similar to our example sentence above is output. This check correspond to Rule 3.1 in Section 3 of the STS Guide. The objective is to reduce cases of structural ambiguity.
Finally, the Multiple Commands in a Sentence check counts the number of commands in a procedural sentence. If there is more than one, an error message is output because according to Rule 6.2 in Section 6 of the STS Guide, only one instruction per sentence is permitted.
The grammar constructs that the system uses to apply this check are ppseq s of type 4 or higher.
Table 6.1 lists the conformance checks that the system can perform and links them to the constructs in our grammar.
CHECKS
Sentence Length
Words in Dictionary
Passive Voice
Number of PPs Modifying a
Noun
Number of Commands
GRAMMAR CONSTRUCTS
N/A
N/A vg1 ppseq ( 3 or higher) vg5
Table 6.1. Type of Checks and Their Corresponding Constructs in the Grammar
The grammar used as the basis for the parser was a grammar in Spanish developed by
Leonardo Gómez called Gramática Didáctica del Español (Gómez, 1999). Based on the checks we wanted the parser to detect we developed a hierarchy of grammar constructs. We now present four tables which list the different types of construct which the STS grammar recognises together with a description of each. See appendix IV, the Xerox Xelda Spanish
Part-of-Speech Tagset, for description clarification.

STS Parser: Description
NOUN PHRASE
CONSTRUCTS snp1 snp2 snp3 snp4
DESCRIPTION
DETPL NUM NOUNPL ADJPL
DETQUANTPL NUM NOUNPL ADJPL
DETSG NOUNSG ADJSG
DETPL NOUSNPL ADJPL snp5 snp6 snp7 snp8 snp9
DETSG NOUNSG NOUNSG
DETPL NOUSNPL NOUSNPL
DETSG NOUNSG ADJSG
DETQUANTSG NOUNSG ADJSG snp10 snp11 snp12 snp13
DEQUANT NOUNSG ADJSG
DETQUANTPL NOUSNPL ADJPL
DETSG NOUNSG
DETPL NOUNPL
NOUNSG snp14 NOUNPL
Table 6.2 Description of Noun Phrase Constructs
PREPOSITIONAL PHRASE
CONSTRUCTS
DESCRIPTION pp1 pp2
PREP snp(n)
PREPDET snp(n)
Table 6.3 Description of Prepositional Phrase Constructs
72

STS Parser: Description
PREPOSITIONAL PHRASE
SEQUENCES ppseq1 ppseq2 ppseq3 ppseq4 ppseq5 ppseq6 ppseq7 ppseq8 ppseq9 ppseq10
DESCRIPTION
One prepositional phrase of any type
Sequence of 2 prepositional phrases
Sequence of 3 prepositional phrases
Sequence of 4 prepositional phrases
Sequence of 5 prepositional phrases
Sequence of 6 prepositional phrases
Sequence of 7 prepositional phrases
Sequence of 8 prepositional phrases
Sequence of 9 prepositional phrases
Sequence of 10 prepositional phrases
Table 6.4 Description of Prepositional Phrase Sequence
VERB PHRASE
CONSTRUCTS
Vg1 (Passive Voice)
Vg2 (Verbal Perifrasis)
Vg3 (Finite Form with “ SE” )
Vg4 (Finite Form)
Vg5 (Command)
Vg6 (Auxiliary)
DESCRIPTION
SER PAPSG and SER PAPPL
ESTAR PAPSG and ESTAR PAPPL
SE VERBFIN
VERBFIN
VERBINF
AUX
Table 6.5 Description of Verbal Phrase Sequence
73

STS Parser: Description 74
This chapter first presented the Robust Layered Parser which was the starting point for developing the STS Parser. It described the main differences between these parsers and explained the parsing algorithm in detail by means of an example. It then discussed some of the post-processing tasks before providing details of the grammar constructs used for this project. The next chapter will evaluate the performance of the parser.

This chapter describes the evaluation of the STS Parser. It starts by setting out the objectives of the assessment and then explains the method followed to carry it out. Finally, it presents and analyses the results obtained.
The objective was to assess the parser using two metrics, namely (1) its performance relative to the errors it is specifically designed to detect and (2) its performance relative to all errors in the test sentences. The first metric establishes the extent to which the parser meets its design criteria while the second measures the appropriateness of the criteria themselves. For example, a good performance under (1) coupled with a poor result under (2) would suggest that the parser is not checking for enough error types.
The evaluation of the parser was carried out in the following manner: Firstly, we selected
100 sentences from the reference corpus, 50 of which were descriptive and the other 50 procedural sentences. These contained examples of all error types detectable by the parser, although a few of them did not contain any of these errors.
Next, we went through each sentence by hand determining all the errors present. These included all the five types of error detectable by the parser (Appendices XII and XIII), plus any other errors found (Appendix XIV and XV). The following stage was to run the sentences through the parser. Then, we compared the output of the parser (Appendices X and XI) with the results of the manual analysis.
Following standard practice in parser evaluation (Grishman, Macleod and Sterling, 1992), the Precision and Recall measures of information retrieval (van Rijsbergen, 1979) were used to summarise the results.

STS Parser: Description 76
Precision = number of errors correctly reported by parser divided by the total number of errors reported.
Recall = number of errors correctly reported by parser divided by the total number of errors established by manual analysis.
In the case of Metric 1, only errors of types 1-5 in Table 7.1 are counted. In the case of
Metric 2, all errors found during manual analysis are included 10 .
Error type Description
1
2
3
4
5
Sentence length is greater than 25 (procedural sentences)/30 words(descriptive sentences)
(Rule 6.1 & 7.1)
Word not in the STS General Vocabulary or the terminology database
(Rule 1.1)
Passive construction used
(Rule 4.3)
3 attached prepositional phrases occur
(Rule 3.1)
Number of commands in the sentence is higher than one
(Rule 6.2)
Table 7.1 STS Parser Conformance Checks
10 This material has also been also included within the table in Appendix IX.

STS Parser: Description
Sentence
Type
Descriptive
Reported
Errors
104
Correctly Reported
Errors
96
77
Actual
Errors
98
Precision Recall
0.92 0.97
Procedural 51 40 42 0.78 0.95
All 155 136 140 0.87 0.97
Table 7.2 Results under Metric 1
From the results in Table 7.2, it can be concluded that the parser meets in some measure its design criteria having 0.87 corresponding to its Precision and 0.97 relative to its Recall.
Precision is lower than Recall because of the nineteen cases of incorrectly reported errors.
Eight occur within the descriptive sentences and the other eleven within the procedural sentences. These represent 12.25% of the total number of errors. Now we show an example of each of these error types in descriptive sentences.
In sentence 5, the STS Parser detects the following error:
Error: ’unidad_de_control_transmite’ in sentence ’Cuando la temperatura supera un nivel crítico en la góndola , la unidad de control transmite señales de aviso de fallo a los instrumentos indicadores de la cabina de pilotos .' is not in the main dictionary or in the compound dictionary.
The error here originates from the term recognition package of the system which has joined a technical name (unidad_de_control) plus a technical verb (transmit) and considers both entities to be a single term. As a consequence, the parser outputs Error Type 2.
We find a similar example in descriptive sentences 19 and 20.
In sentence 12, the system gives the following output:

STS Parser: Description 78
Error: ’/sobretemperatura’ in sentence ’Si la temperatura aumenta suficientemente ( condición de incendio /sobretemperatura excesiva )
, la polarización negativa es compensada y el rectificador ( SCR ) conduce .' is not in the main dictionary or in the compound dictionary.
The system fails to identify the “ /” symbol as a different entity from the word
“ sobretemperatura” . As a consequence, the word is not found in the STS dictionary.
In sentence no. 14, we find the following error message:
Error: Sentence 'El elemento está conectado para formar un bucle continuo , y constituye un detector continuo que da un aviso en el caso de detectar condiciones de excesiva sobretemperatura o de incendio , y anula el aviso para restablecer las condiciones de espera , cuando la temperatura ambiente del bucle desciende por debajo del nivel de rearme del sistema .' contains more than 2 commands, which is not allowed.
In this case, the parser incorrectly assigns Error Type 5 to the sentence. In the majority of cases the parser considers the infinitives in a descriptive sentence to have an imperative value when in fact it usually has a final value. Another similar example occurs in descriptive sentences 25, 38 and 44. In sentence 25, the error is originally generated by the Xelda
Tagger which assigned incorrectly the tag “ VERBINF” to the word “ ambar” , which is in fact a singular noun and thus should have the tag “ NOUNSG” :
Error: Sentence 'Cuando la temperatura del fluido es más alta de 100
Cº , un interruptor de temperatura ( 12 ) se encarga de transmitir el aviso de exceso de temperatura del fluido a la central de aviso de fallos de la cabina de pilotos , iluminándose la luz ambar HOT
HYD OIL .' contains more than 2 commands, which is not allowed
Turning to the incorrectly reported errors in the procedural sentences, the parser outputs
Error Type 1 for sentence 2. This is incorrect because the sentence does not have more than
25 words. The reason is that round brackets have been considered as individual words. The same type of incorrectly reported error occurs in sentences 7, 17, 18, 22, 28, 30 and 32.

STS Parser: Description 79
The other three incorrectly reported errors, similarly to those in descriptive sentences 5, 19 and 20, are due to errors generated by the term recognition package and occur in procedural sentences 6, 9 and 34.
2 3 4 5 Other Error
Type
Descriptive
1
21
14.68%
Procedural 7
12.72%
51
35.66%
8
14.54%
11
7.69%
0
0%
15
10.48%
5
9.09%
0
0%
22
40.00%
45
31.46%
13
23.63%
All 28 59 11 20 22 58
14.14% 29.79% 5.55% 10.10% 11.11% 29.29%
Table 7.3 Error Type Occurrences in Descriptive and Procedural Sentences
Table 7.3 shows that Error Type 2 is the most common in descriptive sentences (35.66%) while it is Error Type 5 that is the most frequent in procedural sentences (40%). The least common error in descriptive sentences is Error Type 5 with 0 occurrences, while in procedural sentences it is Error Type 3 also with 0 occurrences. If we observe all the sentences independently of their type, the most recurrent error is Type 2, followed by the
“ other” error type category with a very similar figure. Table 7.4 lists errors of the latter type which are intrinsically undetectable by the parser. This material is also included in
Appendix XIV.

STS Parser: Description
Error Type
6
7
8
9
10
11
12
13
Description
A word has been used with an unapproved meaning
(Rule 1.2)
Inappropriate omission of an article or a demonstrative adjective
(Rule 2.1)
The verb tense used is illicit or the infinitive, past participle and/or gerund have been used with an unapproved value
(Rule 4.1)
An unapproved verbal periphrasis has been used
(Rule 4.2)
The subjunctive mood has been used
(Rule 4.3)
A noun has been used to express an action, rather than a verb
(Rule 4.5)
The structures used between coordinated sentences differ
(Rule 5.3)
A list of more than two items occurs which should be a tabular layout
(Rule 9.1)
Table 7.4 Errors Undetectable by the STS Parser
80

STS Parser: Description
Sentence
Type
Descriptive
Reported
Errors
104
Correctly Reported
Errors
96
Procedural 51 40
81
Actual
Errors
143
Precision Recall
0.92 0.67
57 0.78 0.70
All 155 136 200 0.87 0.68
Table 7.5 Results under Metric 2
Table 7.5 summarises the results using Metric 2, which indicates the appropriateness of the
STS Parser design criteria. We can observe that the Recall figures under Metric 2 are lower than those under metric 1. 68% of the total number of errors are detected by the STS Parser.
This figure shows that although the parser is still useful, it can be improved if we add new conformance checks which are able to detect errors of types 6 to 13.
Sentence
Type
6 7 8 9 10 11 12 13
Descriptive 1 10 25 1 3 4 1 0
2.22% 22.2% 55.55% 2.22% 6.66% 8.88% 2.22% 0%
Procedural 0 7 3 1 2 0
0% 46.66% 20% 6.66% 13.33% 0%
0 2
0% 13.33%
All 1 17 28 2 5 4 1 2
1.66% 28.33% 46.66% 3.33% 8.33% 6.66% 1.66% 3.33%
Table 7.6 Undetectable Error Type Occurrences in Descriptive and Procedural Sentences

STS Parser: Description 82
Table 7.6 shows the distribution of undetectable error types in both procedural and descriptive sentences. We can observe that the most common error in descriptive sentences is Error 8, while in procedural sentences is Error 7. The least common error in descriptive sentences is Error Type 13 with 0 occurrences, while in procedural sentences it is Error
Types 11 and 12 also with 0 occurrences.
With reference to the evaluation of the STS Parser under Metric 1, we can say that it is reasonably accurate with Precision and Recall figures of 0.87 and 0.97 respectively. This indicates that the STS Parser meets in great measure its design criteria. The way to improve its performance under Metric 1 would be to correct the tokeniser and the term recogniser.
With regard to the results obtained under Metric 2, the STS Parser has a lower score. This shows that the system can be improved by developing strategies that make it capable of detecting new error types. For example, by adding checks for errors of Types 7 and 8, we could improve the performance of the parser considerably, making the parser a more appropriate tool for the development of STS compliant aircraft manuals.
This chapter described how the STS parser was evaluated, reported the results found and identified the most important checks which could be added to a future version. The next chapter outlines the final conclusions of the work presented here.

This chapter presents the final conclusions of the project. We begin by re-stating the objectives and summarising the work which has been carried out. We then outline the key results and examine potential areas for future research.
The objectives of the present work can be summarised as follows:
1. Create a CL specification for the Spanish language in order to improve readability and translatability of technical documentation in Spanish.
2. Develop a controlled Spanish checker to help technical writers implement the CL specification.
In order to achieve these two objectives, various tasks were carried out:
• Previous work on CLs was investigated;
• A method for the design of a Spanish CL specification was established;
• Research concerning the linguistic features of currently used CL Checkers was carried out;
• A specification for STS was drawn up;
• A validating parser for STS was built and evaluated.
This project has contributed towards the improvement of technical documentation in
Spanish as it is the first Simplified Spanish specification that has been developed for a technical domain. The STS Parser could form the basis of a tool for technical writers to help them implement the STS Rules.
The STS Specification comprises 36 rules which are organised in 9 different sections:
Words, Noun Phrases, Prepositional Phrases, Verbs, Sentences, Procedures, Descriptive
Writing, Warnings and Cautions, and Punctuation and Word Counts. These rules set out guidelines for developing aircraft technical manuals which are easy to read and to translate.

Final Conclusions 84
The STS Parser has been designed to identify five different type of error which relate to six different rules in the STS Specification. The performance of the present parser is reasonable and areas for further improvements have already been identified.
Future work could improve both the STS Specification and the validating parser. With regard to the STS Specification, it does not currently include the meanings of the words contained in the STS General Vocabulary. In order to apply Rule 1.2 it is necessary to assign a single meaning to each of the words in this dictionary, in order to avoid ambiguity.
This would imply first giving definitions to words in the STS General Vocabulary. These could be adapted from the dictionary of the Spanish Language Royal Academy which is the principal authority for the Spanish language. Secondly, we would need to associate a meaning with each of the technical terms in our terminology database. This would involve the study of each term followed by agreement among technical terminologists as to which meaning to assign to it. This should not be a very difficult task as the meanings of words belonging to technical domains are already restricted.
Improving the STS Parser would involve adding new checks to take account of the eight error types identified in Table 7.4. Some of these would involve overcoming a number of difficulties, while others would be relatively easy to implement. We now consider each error type in turn.
Error Type 6, is concerned with the use of a word with an unapproved meaning. In order to detect such a use we would first need to assign a meaning to each of the words in the STS
General Vocabulary and the technical terms in the database as mentioned above. It would then be necessary to establish for each use of a word in context what its semantic sense was and hence determine whether the usage was approved or not. The field of Word Sense
Disambiguation has been active for many years with early approaches exploiting dictionary entries and later ones adopting statistical techniques. While the latter might work quite well in controlled contexts this is not proven and the detection of this type of error is therefore an open research question.
The development of a module to detect Error 7, in which an article or a demonstrative adjective has been omitted, would require the specification of new grammar constructs which established clearly the use of determiners in Spanish. This would not be easy because

Final Conclusions 85 the rules for the use of determiners are normally stated in general terms and there tend to be many exceptions which would be difficult to account for.
With regard to Error 8, which involves a case of using an illicit verb tense or a non-personal verb form with unapproved value, we would need to detect two main aspects: the tense and the values of the non-personal verb forms. We would need to develop a grammar construct that detects both of the verb tenses permitted in STS, namely the present simple and the future simple. The parser would then output as an error other unidentified verb tenses. In order to detect the values of non-personal verb forms, such as the infinitive, present and past participle, we could develop grammar constructs that account for the use of accepted and unaccepted values. For example, in the case of the infinitive, we would develop a grammar construct in which we have the preposition “ para” {to} followed by the infinitive. In this case, the infinitive would be identified as having a final and not an imperative value because it is preceded by the preposition “ para” . Then, we would write other grammar constructs for the cases in which the infinitive is not allowed, for example those cases of the infinitive with a nominal value. In these, the infinitive appears at the very beginning of the sentence and functions as the subject of the sentence: infinitive 11 (+ complements) + verb in personal form + complements. A sample sentence of this type is:
Subir la temperatura es inapropiado en este caso.
{To raise the temperature is inappropriate in this case.}
After identifying the grammar construct the parser can be programmed to output an error message for those cases which are not allowed in STS. At present, the parser does not have that function yet, and this is the reason for the cases of incorrectly reported Error 5.
In the case of the past participle with an adjectival value, it would be necessary to create a grammar construct in which the past participle functioned fully as an adjective. For example structures of the type determiner + noun + past participle + verb tense in personal form + complements would be identified as valid. In other cases, which would also have their corresponding grammar constructs, an error message would be generated.
Turning to the gerund, it would be difficult to identify the cases in which it has a modal (i.e. approved) value because there are not many distinctive syntactic identifiers for it. Therefore it can be confused with other values of the gerund.
11 Complements are optional in this case.

Final Conclusions 86
With regard to Error 9, which involves the use of illicit verbal periphrases, we would need to develop grammar constructs for the verbal periphrases used in technical Spanish. We would then need to develop a check that is able to detect the grammar constructs which do not correspond to the approved verbal periphrases.
Detection of Type 10 errors, namely cases in which the subjunctive has been used, would require the creation of grammar constructs capable of identifying all the tenses in subjunctive mood in Spanish.
Error 11, which implies the use of a noun to express an action, would involve the creation of a database for the most common cases of such nouns so that when the parser identifies one of those, an error message is generated.
Error 12 is concerned with the use of different structures in the same coordinated sentence.
Detection of this error would involve a detailed study of the constructions which participate in coordination in technical Spanish as well as the development of heuristics for characterising them.
Finally, Error 13 is concerned with the absence of tabular layout in lists of more than two items in a noun phrase. We would need to design a module in the parser which is able to count the number of nouns in a noun phrase and when this number is higher than two a tabular layout would need to be requested.
We can conclude by stating that some of the checks to be added to the parser might involve more difficulties than others, but most of them would be feasible with a certain degree of success. What is definite is that the grammar would need to be expanded considerably to account for all the cases previously described.
Another possible line of research would be to create strategies to extrapolate the STS
Specification to other technical domains such as the automotive field, the medical domain, etc. Many of the existing rules could probably be adopted in such domains, although at present this remains a hypothesis.

Final Conclusions 87
In this chapter we re-stated the objectives of the project before outlining the key results. We then discussed some areas of future research focussing in particular on incremental improvements to the parser.

AECMA (1998): AECMA Simplified English, Issue 1, Revision 1. AECMA Document: PSC-
85-16598. A Guide for the Preparation of Aircraft Maintenance Documentation in the
International Aerospace Maintenance Language, Brussels: AECMA.
Almqvist, I. and Hein, S. A. (1996): ‘Defining ScaniaSwedish – A Controlled Language for
Truck Maintenance’ , Proceedings of the First International Workshop on Controlled
Language Applications (CLAW96), Leuven, Belgium: Katholieke Universiteit Leuven Centre
for Computational Linguistics 26-27 March, 1996, 159-165.
Barthe, K. (1998): ‘GIFAS Rationalised French: Designing one Controlled Language to
Match Another’ , Proceedings of the Second International Workshop on Controlled
Language Applications (CLAW98), Pittsburgh, Pennsylvania: Carnegie Mellon University,
Language Technologies Institute, 21-22 May, 1998, 87-102.
Brill, E. (1992): ‘A Simple Rule-Based Part-of-Speech Tagger’ , Proceedings of the Third
Conference on Applied Natural Language Processing, ANLP, Trento, Italy, 1992.
Douglas, S. and Hurst, M (1996): ‘Controlled English Support for Perkins Approved Clear
English (PACE)’ , Proceedings of the First International Workshop on Controlled Language
Applications (CLAW96), Leuven, Belgium: Katholieke Universiteit Leuven Centre for
Computational Linguistics 26-27 March, 1996, 106-114.
Ericsson (2000): http://www.ericsson.com
Farrington, G. (1996): ‘AECMA Simplified English: an Overview of the International
Aircraft Maintenance Language’ , Proceedings of the First International Workshop on
Controlled Language Applications (CLAW96), Leuven, Belgium: Katholieke Universiteit
Leuven Centre for Computational Linguistics 26-27 March, 1996, 1-21.
Fuchs, N. E. and Schwitter R. (1996): ‘Attempto Controlled English (ACE)’ , Proceedings of the First International Workshop on Controlled Language Applications (CLAW96), Leuven,
Belgium: Katholieke Universiteit Leuven Centre for Computational Linguistics 26-27
March, 1996, 124-136.

Bibliography 89
Gala Pavia, N. (1999): ‘Using the Incremental Finite-State Architecture to Create a Spanish
Shallow Parser’ , Proceedings of the Fifteenth Conference SEPLN (Spanish Society for
Natural Language Processing), Lleida (Spain), 1999. http://www.xrce.xerox.com/Publications/Attachments/1999-050/SEPLN99gala.pdf
Gazdar, G., Klein, E., Pullum, G. and Sag, I. (1985): Generalized Phrase Structure
Grammar, Cambridge MA: Harvard University Press.
Godden, K. (1998): ‘Controlling the Business Environment for Controlled Language’ ,
Proceedings of the Second International Workshop on Controlled Language Applications
(CLAW98), Pittsburgh, Pennsylvania: Carnegie Mellon University, Language Technologies
Institute, 21-22 May, 1998, 185-190.
Godden, K. (2000): ‘The Evolution of CASL Controlled Authoring at General Motors’ ,
Proceedings of the Third International Workshop on Controlled Language Applications
(CLAW 2000), Seattle, Washington, 29-30 April, 2000, 14-19.
Gómez Torrego, L. (2000): Gramática Didáctica del Español, Madrid: Ediciones SM.
Goyvaerts, P. (1996): ‘Controlled English, curse or Blessing? – A User´s Perspective’ ,
Proceedings of the First International Workshop on Controlled Language Applications
(CLAW96), Leuven, Belgium: Katholieke Universiteit Leuven Centre for Computational
Linguistics 26-27 March, 1996, 137-142.
Grishman, R., Macleod, C., and Sterling, J. (1992): ‘Evaluating parsing strategies using standardised parse files’ , Proceedings of the Third ACL Conference on applied Natural
Language Processing, Trento, Italy, 156-161.
Hayes, P., Maxwell, S. and Schmandt L.(1996): ‘Controlled English Advantages for
Translated and Original English Documents. Proceedings of the First International
Workshop on Controlled Language Applications (CLAW96), Leuven, Belgium: Katholieke
Universiteit Leuven Centre for Computational Linguistics 26-27 March, 1996, 84.
Heald, I. and Zajac, R. (1998): ‘Compounds Nouns in Simplified English’ , Proceedings of the Second International Workshop on Controlled Language Applications (CLAW98),

Bibliography 90
Pittsburgh, Pennsylvania: Carnegie Mellon University, Language Technologies Institute,
21-22 May, 1998, 124.
Holmback, H., Duncan, L. and Harrison, P. (2000): ‘A Word Sense Checking Application for Simplified English’ , Proceedings of the Third International Workshop on Controlled
Language Applications (CLAW 2000), Seattle, Washington, 29-30 April, 2000, 120-133.
Holmback, H., Shubert, S and Spyridakis, J. (1996): ‘Issues in Conducting Empirical
Evaluations of Controlled Languages’ , Proceedings of the First International Workshop on
Controlled Language Applications (CLAW96), Leuven, Belgium: Katholieke Universiteit
Leuven Centre for Computational Linguistics 26-27 March, 1996, 166-177.
Huijsen, W. (1998): ‘Controlled Language – An Introduction’ , Proceedings of the Second
International Workshop on Controlled Language Applications (CLAW98), Pittsburgh,
Pennsylvania: Carnegie Mellon University, Language Technologies Institute, 21-22 May,
1998, 2.
Hyland, P., Koch, H.-D., Sutcliffe, R. F. E., Vossen, P. (1996): ‘Selecting Information from
Text (SIFT)’ , Final Report (LRE-62030 Deliverable D61). Luxembourg, Luxembourg:
Commission of the European Communities, DGXIII/E5. Limerick, Ireland: University of
Limerick.
Janton, P. (1994): Esperanto: Language, Literature and Community, New York: State
University of New York Press.
Kamprath, C., Adolphson, E., Mitamura, T. and Nyberg, E. (1998): ‘Controlled Language for Multilingual Document Production: Experience with Caterpillar Technical English’ ,
Proceedings of the Second International Workshop on Controlled Language Applications
(CLAW98), Pittsburgh, Pennsylvania: Carnegie Mellon University, Language Technologies
Institute, 21-22 May, 1998, 51-61.
Kittredge, R. (1996): ‘A Path from Sublanguage to Controlled Language’ , Abstract in
Proceedings of the First International Workshop on Controlled Language Applications
(CLAW96), (p. 178). Leuven, Belgium: Katholieke Universiteit Leuven Centre for
Computational Linguistics 26-27 March, 1996, 178.
Kodak (2000): http://www.kodak.com

Bibliography 91
Lamiroy, B. and Gebruers, R. (1989): ‘Syntax and Machine Translation: The METAL project’, Lingvisticae Investigationes 13(2), 307-332.
Lux, V. (1998): Elaboration d’un Français Rationalisé Entendu Modulaire (FREM) pour
les Manuels de Maintenance d’Aéronefs, Unpublished Ph.D. Thesis, University of Paris.
Means, L. and Godden, K. (1996): ‘The Controlled Automative Service Language (CASL)
Project’ , Proceedings of the First International Workshop on Controlled Language
Applications (CLAW96), Leuven, Belgium: Katholieke Universiteit Leuven Centre for
Computational Linguistics 26-27 March, 1996, 106-114.
Means, L., Chapman, P. and Liu, A. (2000): ‘Training for Controlled Language Processes’ ,
Proceedings of the Third International Workshop on Controlled Language Applications
(CLAW 2000), Seattle, Washington, 29-30 April, 2000, 51-61.
Moore, C. (2000): ‘Controlled Language at Diebold, Incorporated’ , Proceedings of the
Third International Workshop on Controlled Language Applications (CLAW 2000), Seattle,
Washington, 29-30 April, 2000, 51-61.
Odgen, C. K. (1932): Basic English, A General Introduction with Rules and Grammar,
London: Paul Treber & Co. Ltd..
Ramírez, F. and Sánchez, F. (1996): ‘Is linguistic Information Enough for Grammar
Checking?’ , Proceedings of the First International Workshop on Controlled Language
Applications (CLAW96), Leuven, Belgium: Katholieke Universiteit Leuven Centre for
Computational Linguistics 26-27 March, 1996, 216-225.
Real Academia Española (2001): Diccionario de la Lengua Española, Madrid: Espasa
Calpe.
Reuther, U. and Schmidt-Wigger, A. (2000): ‘Designing a Multi-Purpose CL Application’ ,
Proceedings of the Third International Workshop on Controlled Language Applications
(CLAW 2000), Seattle, Washington, 29-30 April, 2000, 72-82.
Schachtl, S. (1998): ‘Controlled Siemens Documentary German and TopTrans’ , Technical
Communication Forum, http://www.tc-forum.org/topictr/tr9contr.htm

Bibliography 92
Smartny (2002): http://www.smartny.com/
Sutcliffe, R. F. E. (2000): ‘Using a Robust Layered Parser to Analyse Technical Manual
Text’ , Cuadernos de Filología Inglesa, 9(1), 167-189. Número Monográfico: Corpus-based
Research in English Language and Linguistics, Murcia, Spain: University of Murcia.
Van der Eijck, P., De Koning, M. and Van der Steen, G. (1996): ‘Controlled Language
Correction and Translation’ , Proceedings of the First International Workshop on Controlled
Language Applications (CLAW96), Leuven, Belgium: Katholieke Universiteit Leuven Centre
for Computational Linguistics 26-27 March, 1996, 64. van Rijsbergen, C. J. (1979): Information Retrieval, London: Butterworths.
Wojcik, R. (1998): ‘AECMA Simplified English and Controlled Language Checkers’ , The
ELRA Newsletter.
Wojcik, R., Harrison, P. and Bremer, J. (1993): ‘Using Bracketed Parses to Evaluate a
Grammar Checking Application’ , Proceedings of the Thirty First Annual Meeting of the
Association for Computational Linguistics, Ohio State University, 22-26 June, 1993, 38-45.
Wojcik, R., Holmback, H. and Hoard, J. (1998): ‘Boeing Technical English: An Extension of AECMA SE beyond the Aircraft Maintenance Domain’ , Proceedings of the Second
International Workshop on Controlled Language Applications (CLAW98), Pittsburgh,
Pennsylvania: Carnegie Mellon University, Language Technologies Institute, 21-22 May,
1998, 114-123.
Xelda (2002): XeLDA: ‘Xerox Linguistic Development Architecture’ , http://www.xrce.xerox.com/ats/xelda/
Xerox (2001): http://www.xrce.xerox.com
Zhang, W. and Shiwen, Y. (1998): ‘Construction of a Controlled Chinese Lexicon’ ,
Proceedings of the Second International Workshop on Controlled Language Applications
(CLAW98), (Pittsburgh, Pennsylvania: Carnegie Mellon University, Language
Technologies Institute, 21-22 May, 1998, 159-173.

VOL.
NO.
CHP.
NO
SEC.
NO.
SUBJ.
NO.
SECTION NAME
[SPANISH]
SECTION NAME
[ENGLISH]
7 26 11 00
DETECCIÓN DE
SOBRETEMPERATU-
RA E INCENDIOS DE
MOTOR
Descripción & Operación
ENGINE FIRE AND
OVERHEAT
DETECTION
Description & Operation
8
8
8
8
26
26
26
26
21
21
22
21
00
EXTINCIÓN DE
INCENDIOS DE
MOTOR
Descripción & Operación
ENGINE FIRE
EXTINGUISHING
Description & Operation
00
EXTINCIÓN DE
INCENDIOS DE
MOTOR
Ajuste/Prueba
ENGINE FIRE
EXTINGUISHING
Adjustment/Test
00
EXTINCIÓN DE
INCENDIOS PORTÁTIL
EN EL INTERIOR DEL
AVIÓN
Descripción & Operación
AIRCRAFT INTERIOR
PORTABLE FIRE
EXTINGUISHING
Description & Operation
11
CILINDRO EXTINTOR,
WB5 (WB6)
Desmontaje/Montaje
EXTINGUISHER
CYLINDER, WB5
(WB6)
Removal/Installation
1
CASA CN-235 MANUAL DE MANTENIMIENTO, 1997.

Appendix I 94
8
11
11
11
11
11
11
11
26
29
29
29
29
29
29
29
21
00
00
00
10
10
30
30
11
CILINDRO EXTINTOR,
WB5 (WB6)
Inspección/Comprobación
EXTINGUISHER
CYLINDER, WB5
(WB6)
Inspection/Check
00
00
00
ENERGÍA
HIDRÁULICA
Descripción & Operación
HIDRAULIC POWER
Description & Operation
ENERGÍA
HIDRÁULICA
Servicio
ENERGÍA
HIDRÁULICA
Ajuste/Prueba
HIDRAULIC POWER
Servicing
HIDRAULIC POWER
Adjustment/Test
00
00
00
SISTEMA PRINCIPAL
DE ENERGÍA
HIDRÁULICA
Investigación de Averías
HIDRAULIC POWER –
MAIN SYSTEM
Troubleshooting
SISTEMA PRINCIPAL
DE ENERGÍA
HIDRÁULICA
Servicio
HIDRAULIC POWER –
MAIN SYSTEM
Servicing
SISTEMA DE
INDICACIÓN DE
ENERGÍA
HIDRÁULICA
Investigación de Averías
HIDRAULIC POWER –
INDICATING
SYSTEMS
Troubleshooting
11
UNIDAD DE CONTROL
DEL SISTEMA
HIDRÁULICO ZD126
H&DRAULIC S&STEM
CONTROL UNIT ZD126
Desmontaje/Montaje Removal/Installation

Appendix I 95
11
11
29
29
10
10
13
UNIDAD MODULAR
Inspección/Comprobación
11
DEPÓSITO
Montaje/Desmontaje
MODULE UNIT
Inspection/Check
RESERVOIR
Removal/Installation

Section 1: Words
Rule 1.1 STS can only contain words which belong to either group A or B.
Rule 1.2 Use words in the General Vocabulary only with their approved meaning.
Rule 1.3 Do not use different Technical Terms for the same thing.
Section 2: Noun Phrases
Rule 2.1 When appropriate, use an article (definite [el, la, lo, los, las] or indefinite [un, una, uno, unos]) or a demonstrative adjective ([este, esta, esto, estos, estas, ese, esa, eso, esos, esas, aquel, aquella, aquello, aquellos, aquellas]) before a noun .
Section 3: Prepositional Phrases
Rule 3.1 Do not use more than three contiguous prepositional phrases to modify another noun phrase or prepositional phrase.
Section 4: Verbs
Rule 4.1 Use the verbs in the STS General Vocabulary and those verbs of Manufacturing
Processes to make only the following tenses:
-The Present Simple [3 rd person singular and 3 rd person plural],
-The Future Simple [3 rd person singular and 3 rd person plural],
-The Infinitive [with an imperative value],
-The Infinitive [with a final value],
-The Past Participle [with an adjectival value],
-The Gerund [with a modal value].
Rule 4.2 You may use verbal periphrases.
Rule 4.3 Use only the indicative mood.
Rule 4.4 Use only the active voice in procedural writing and as much as possible in descriptive writing.
Rule 4.5 Use an approved verb to express an action, rather than a noun or other parts of speech.

Appendix II 97
Section 5: Sentences
Rule 5.1 Keep to one topic per sentence.
Rule 5.2 Use connecting words to join consecutive sentences that contain related thoughts.
Rule 5.3 Use a similar structure between coordinated sentences.
Rule 5.4 Do not omit words to keep your sentences shorter.
Section 6: Procedures
Rule 6.1 Keep procedural sentences as short as possible (25 words maximum).
Rule 6.2 Write only one instruction per sentence.
Rule 6.3 Write more than one instruction per sentence only when more than one action is done at the same time.
Rule 6.4 In an instruction, write the verb in the infinitive form with its imperative value.
Rule 6.5 When descriptive text appears in a procedure, you can use the third person of the present simple.
Rule 6.6 If you start an instruction with a descriptive statement (dependent phrase or clause), you must separate the statement from the rest of the instruction with a comma.
Rule 6.7 Make your instructions as specific as possible.
Section 7: Descriptive Writing
Rule 7.1 Keep sentences in descriptive writing as short as possible (30 words maximum).
Rule 7.2 Each paragraph must have only one topic.
Rule 7.3 Each paragraph must start with a topic sentence.
Rule 7.4 Present new and complex information slowly.
Rule 7.5 Keep paragraphs short (maximum 8 sentences).
Rule 7.6 Avoid the use of referring expressions such as pronouns and deictic determiners, instead repeat the concept.
Section 8: Warnings and Cautions
Rule 8.1 Start a warning or a caution with a simple and clear command.
Rule 8.2 Be specific in a warning or caution.
Rule 8.3 If a condition is necessary before the technician continues, put the condition first in the warning or caution.

Appendix II 98
Section 9: Punctuation and Word Counts
Rule 9.1 Use colons ( : ) and dashes ( - ) to make tabular layouts.
Rule 9.2 Use round brackets:
1. To make cross-references to illustrations and/or text,
2. To quote letters or numbers that identify items on an illustration or in a text,
3. To mark text for which separation by commas is not sufficient,
4. To indicate the correct breakdown level of procedural substeps.
Rule 9.3 Write warnings and cautions always in capital letters.
Rule 9.4 Write the accent mark ( ´ ) in all the words that require it, including capital letters.
Rule 9.5 When you count words for sentence length, the following items count as one word:
A number {(1, 2, 3 … )}
An alphanumeric identifier {(4,50 lb), (WB7)… }
An abbreviation or an acronym {psi, A.E.C.M.A., F., … }
Rule 9.6 When demarcating sentences in order to compute their length, the full stop (.) is the only end-of-sentence marker.

Appendix III 99 aislamiento aislar ajustar al aire libre al azar aleatorio algo alguno alimentar alinear alrededor de alternativo alto altura amarrar análogo ancho a a lo largo de a lo largo del eje a lo largo del radio a través de a través de abajo abierto abrasivo abrir absorber acceso accidental accidentalmente accidente aceptar acoplar acoplarse acumularse adaptar adecuado adelante adyacente aerotransportado afilado afín agente agitar aguas abajo aguas arriba agujero ahí
anchura angular anormal antes de antes de que anular añadir apagado apagar apagarse aparcar aparecer aparente aparentemente apertura aplicable aplicar apretar aprobación aproximadamente aproximado apuntar aquellas aquellos aquí asegurarse
áspero atrás aumentar aunque automáticamente automático autoridad auxiliar ayudar bajar bajo básico bastante beber bloqueado bloquear bobina borde borde dentado borrar brillante bueno burbuja cabeza cada caducado caer calcular cálculo calibrar calibre calidad caliente calor cambiar cambio cantidad capa capacidad cargar carretear casi causa causar cerca cercana cerrar cerrar con picaporte ciclo circuito cerrado circular código coger colgar color comer comienzo como comparar completamente componente comprimir compuesto con con claridad con energía hidráulica con la energía de un neumático con regularidad con seguridad concentración condensación

Appendix III condición conducir conectar conexión constante constatemente contaminación contener contenido continuamente continuar continuo contorno contra contrario controlar copia corrección correctamente correcto corregir correspondiente corriente de aire cortar corto cosa cual cuando cuidado cuidadosamente curva chasquido chispa dañado dar datos de de forma brillante de forma digital de forma insatisfactoria de forma intermitente de forma lineal de forma longitudinal de forma manual de forma repentina de forma satisfactoria de forma simétrica de forma uniforme de nuevo de otro modo debajo de deber debido a debido a que débil desconectar desconocido desde desde que desechar desenvolver desinflar desmontar desperfecto desplegar después después de detectar deteriorarse deterioro detrás de débil dimensión débilmente decir decisión defectuoso delante de delantero demasiado dentro derecho derramar desacoplar desafilado desarmar desatascado descarga eléctrica diferencia diferente digital digitalizar dirección directamente disminuir disponible distancia dividir doblar donde drenar durante duro echar efecto el eléctrico electromagnéticamente electromagnético electrónicamente electrónico
100 entre enviar equilibrar equipo equitativamente equitativo equivalente error escribir escuchar esférico espacio especial especialmente especificado espera esquina estable estándar estar conforme estas este estimación elemento elevado elevar eliminación eliminar ella ellas ello ellos emergencia empapar empujar emsamblaje en en el interior de en frente de en la dirección de las agujas del reloj en medio de en popa encaminamiento encender encenderse encendido encima encontrar energía energizar enganchado enlace entrada entrar

Appendix III estos estructura estructural estructuralmente evitar exacto examinar excesivo exceso explosión explosivo exterior externo fácil fácilmente fecha fila filtrado fina final flecha flexible fluido fluir flujo fondo forma formar frecuente frecuentemente fresco frío frotar fuego fuente fuera fuera de fuera de borda fuerte fumar función funcionamiento defectuoso gas gases de escape general girar golpear golpear ligeramente gota gradualmente gran gruesa grupo haber hablar hacer hacer hacer permanecer en tierra hacerse hacia hacia abajo hacia arriba hacia atrás hasta hecho helar herida herramienta hidráulico holgadamente horizontal horizontalmente húmedo humo identificación identificar ignorar igual iluminación importante incidencia incidente inclinar incorrectamente incorrecto incrementar incremento independientemente indicación indicador indicar inferior inflamable inflar informe inicial inicialmente inmediatamente insatisfactorio inspección instalación instalar instrucción instrumento intensidad intentar intercambiable intercambiar
101 lámina laminación laminado largo las lateral lateralmente leer lejos lejos de lentamente lento liberar libremente ligeramente ligero interfaz interior intermitente interno intervalo inútil investigación ir irregular irregularmente izquierdo juego de junto la la parte superior lado límite limpiar limpiar con un chorro de fluido limpio lineal líquido local localmente longitud longitudinal los lubricar lugar llama llenar lleno magnéticamente magnético mal mantener mantenimiento manual

Appendix III muestra multiplicar muy necesario neumático neutral ningún nivel nivelado no no deseado no solicitado nombre normal normalmente nosotros nuevo número o obedecer objeto obligatorio observar marca más masa matar mate material máximo mayoría mecánicamente mecánico mecanismo mediano médico medir mejor menos mezclar mínimo mirar moderadamente moderado modo momentáneamente montar morro movible móvil movimiento movimiento libre mucho muchos muesca permanentemente permitido permitir pero persona personal pesado pesar peso pieza pintar plano poco común poder poner poner en marcha poner una etiqueta ponerse por por electricidad por fuera por la borda por lo tanto partícula pasar paso pasta pegajoso pegar peligroso pensar peor pequeño percibir pérdida perdido periodo permanecer permanente obstrucción obstruido ocurrir oir oler opcional operación operar otro output par paralelo parar parte parte delantera parte posterior punto que que queda quemar quien químicamente químico radial radioactivo ranura rápidamente rápido raya recibir recomendar recorrido recto redondeado reflejo registrar regular remiendo remitir por separado por último porque posible posiblemente posición post posterior pre precaución precisión preparar presión presionar prevenir primero principal probablemente problema procedimiento producir profundidad programar prolongación propiedad proporción protección provisionales prueba pulir pulverización punta
102

Appendix III semicircular sensible señal separación ser si siempre símbolo simétrico similar simultáneamente sin sincronizado síntoma sistema sobre sobre el eje solamente solapo sólido sólo soltar solución romper ruido saber salida salir satisfactorio se seco secuencia secundario seguir según seguridad seguro selección sellar remolcar rendimiento reparación reparar repaso repentino repostar resistente respirar resultado retorcer retracción retraer revisión riesgo rígido tipo tira tirar de tocar todo tolerancia total trabajo transmitir transparente transportar trasladar tus
último un una unas unidad uniforme unión unir uno unos sonido soplar su suave subensamblaje subir sucio suelo suelto suficiente sujetar sujeto suma suministrar suministro superficie superior sus sustitución sustituir sustraer también tan ... como tarea telescópico temporal temporalmente tener terciaria terminar tiempo típico usado usar usted utilizable vaciar vacío valor vapor velocidad venenoso venir ver vertical verticalmente vibración vida visión visual visualización visualmente volumen volver voz vuelo vuelta y zona
103

TAG
+ADJ
+ADJPL
+ADJSG
+ADV
+ADVADJ
+ADVINT
+ADVNEG
+ADVREL
+AUX
+AUXINF
+AUXINFCL
+CM
+COMO
+CONADV
+CONJ
+DETPL
+DETQUANT
+DETQUANTPL
+DETQUANTSG
+DETSG
+DIG
+HAB
+HABINF
+HABINFCL
+INTERJ
+ITEM
+NOUN
+NOUNPL
+NOUNSG
DESCRIPTION
Invariant adjective
Plural adjective
Singular adjective
Adverb
Adverb, modifying an adjective
Interrogative adverb
Negation “ no”
Relative adverb
Finite auxiliary “ ser” or “ estar”
Intinitive “ ser” , “ estar”
Infinitive “ ser” , “ estar” with clitic
Comma
Reserved for word “ como”
Adverbial conjunction
Conjunction
Plural determiner
Invariant quantifier
Plural quantifier
Singular quantifier
Singular determiner
Numerals (digits)
Finite auxiliary “ haber”
Infinitive “ haber”
Infinitive “ haber” with clitic
Interjection
List item marker
Invariant noun
Plural noun
Singular noun
EXAMPLE
Beige; mini
Pequeños; nacionales
Pequeño; nacional
Siempre; directamente
Muy [importante]
Adónde; cómo;
No
Cuanta; cuantos
Es; fui; estaba
Estar, ser
Serme; estarlo
,
Como
Adonde; cuando
Y; o, si; porque
Los; las; estas; tus
Bastante; cada, demás
Unas; ambos; muchas
Un; una; ningún; poca
El; la; este; mi
45; IX
Han; hubo; hay
Haber
Haberle; habérseme
Ah; bravo; olé a); A.
Bragazas; fénix
Piezas, aviónes
Pieza; avión

Appendix IV
+NUM
+PAPPL
+PAPSG
+PREDETPL
+PREDETSG
+PREP
+PREPDET
+PRON
+PRONCLIT
+PRONDEM
+PRONINT
+PRONPOS
+PRONREL
+PROP
+PUNCT
+QUE
+SE
+SENT
+VERBFIN
+VERBIMP
+VERBIMPCL
+VERBINF
+VERBINFCL
+VERBPRP
+VERBPRPCL
105
Numerals (spelled out)
Past participle, plural
Past participle, singular
Plural pre-determiner
Singular pre-determiner
Preposition
Preposition + determiner
Pronoun
Clitic pronoun
Demonstrative pronoun
Interrogative pronoun
Possessive pronoun diez; siete; doscientos
Contenidos; hechas
Privado; fundada
Todas [las]; todos [los]
Toda [la]; todo [lo]
En; de; para
Al; del; dentro del
Ellos; todos; nadie; yo
Le; la; te; me, os; nos
Eso; esto; aquello
Qué; quién; cuánto
(el) mío; (las) vuestras
Relative pronoun
Proper name
(lo) cual; quien; cuyo
María, José
Punctuation (other than CM or SENT) ¿ { “
Reserved for word “ que” Que
Reserved for word “ se”
Sentence final punctuation
Finite verb form
Se
. ? ; : !
Tiene; pueda; dicte
Verb imperative
Imperative with clitic
Verb infinitive
Infinitive with clitic
Present participle
Present participle with clitic
Escuchad; oye
Déjame; sígueme
Evitar; tener; conducir
Hacerse; suprimirlas
Siendo; tocando
Haciéndoles; tomándolas

1. Se enciende el módulo ENG FIRE en la central de aviso de fallos de la cabina de pilotos y las luces principales de aviso de fallos parpadean.
2. Todos los acoplamientos hidráulicos están situados en la parte posterior de la unidad modular, y consta de bocas de entrada de presión de las bombas (13), una boca de salida de servicio (10), una boca de salida de presión al depósito (15), unas bocas de entrada de drenaje (11) de la caja de la bomba, una boca de entrada a presión (1) del depósito, unas bocas de alimentación (12) de las bombas, una boca de entradade retorno (8) del fluido y una boca de salida de retorno (9) del fluido.
3. Los elementos están conectados con el cableado del avión a través de receptáculos de mamparos, quedando conectados a las unidades de control WC11 (WC12) instaladas en el conjunto del armario eléctrico IZQ (DCH) del fuselaje central.
4. El aviso de insuficiente presión en la bomba es enviado a la central de aviso de fallos en la cabina de pilotos por dos manocontadores (4), que están situados en la parte superior de la unidad modular.
5. Cuando la temperatura supera un nivel crítico en la góndola, la unidad de control transmite señales de aviso de fallo a los instrumentos indicadores de la cabina de pilotos.
6. El subconjunto de refrigeración del aceite (1) es de construcción monobloque y consta de unas placas colocadas de forma alterna, unas barras y aletas laterales, contenidas en un conjunto de conducto de aire (14).
7. El sistema se rearma volviendo el interruptor de prueba seleccionando a la posición
OFF.
8. El flujo de fluido desde las motobombas es enviado a la boca de alta presión (7), a una presión de 211 Kg/cm2 (3000 psi).
9. El sensor de incendios es un elemento flexible que lleva un tubo capilar fino de acero inoxidable que contiene un electrodo central separado y aislado de las paredes del tubo por un material semiconductor sensible al calor con un coeficiente de resistencia negativo.
10. La descarga de presión rompe el disco verde del indicador de descarga de sobrepresión situado en el recubrimiento exterior del avión que de este modo indica que la descarga del cilindro es debida a la sobrepresión.
11. Al sacar el pasador para bloqueo (1), se liberan la palanca directora (5) y la palanca actuadora (2), simultáneamente.
12. Si la temperatura aumenta suficientemente (condición de incendio/sobretemperatura excesiva), la polarización negativa es compensada y el rectificador (SCR) conduce.

Appendix V 107
13. La energía del bucle se usa para modificar la polarización de la compuerta de un rectificador controlado por un cristal de silicio (SCR) que controla la operación del relé de aviso de fallo de las unidades de control, y forma así la base de la operación del sistema.
14. El elemento está conectado para formar un bucle continuo, y constituye un detector continuo que da un aviso en el caso de detectar condiciones de excesiva sobretemperatura o de incendio, y anula el aviso para restablecer las condiciones de espera, cuando la temperatura ambiente del bucle desciende por debajo del nivel de rearme del sistema.
15. En el caso de sobrepresión peligrosa en el cilindro extintor, causada probablemente por temperaturas anormalmente altas, el agente de extinción es liberado automáticamente a la atmósfera a través de una tubería de descarga de presión.
16. El sistema se rearma, y anula automáticamente la indicación de alarma en el caso de que cesen las condiciones de sobretemperatura o incendio.
17. Dos manocontactores (10), conectados por medio de cables eléctricos a la central de aviso de fallos de la cabina de pilotos, indican suministro con la presión insuficiente desde cualquiera de las dos motobombas.
18. Los cambios de cantidad de fluido en el interior del cilindro producen un desplazamiento del conjunto del émbolo interior, que es transmitido por medio de un transmisor (10) a un indicador de contenido, situado en la cabina de pilotos, y a otro indicador de contenido (8) situado en el depósito.
19. La unidad de control suministra una corriente alterna de forma de onda asimétrica al bucle del sensor de incendios que recibe, almacena y descarga energía eléctrica cuya capacidad aumenta a medida que aumenta la temperatura ambiente del sensor de incendios.
20. El elemento sensor de incendios está conectado a la unidad de control, que es alimentada con 28 V c.c. y está protegida por los interruptores automáticos WC1
(WC2), WC3 (WC4).
21. Un contacto evita que el circuito de aviso de incendios proporcione indicación de aviso de incendio y el otro contacto activa el módulo de fallo en la central de avisos de fallo secundaria de la cabina para mostrar que existe una avería en el sistema.
22. La presión del fluido filtrado es conducida asimismo a través de la boca (6) hacia el depósito hidráulico.
23. La presión del sistema es indicada desde el transmisor (17) al indicador de presión hidráulica, situado en el tablero superior de la cabina de pilotos.
24. Una unidad modular proporciona un distribuidor para la conexión a los servicios hidraúlicos principales y a los que son operados por energía hidráulica.
25. Cuando la temperatura del fluido es más alta de 100 Cº, un interruptor de temperatura (12) se encarga de transmitir el aviso de exceso de temperatura del fluido a la central de aviso de fallos de la cabina de pilotos, iluminándose la luz ambar HOT HYD OIL.

Appendix V 108
26. Un termostato interior envía avisos de sobretemperatura del motor a los indicadores de sobretemperatura de los indicadores luminosos de la bomba, situados en el panel de la unidad de control HYDRAULIC SYST.
27. La alarma acústica puede anularse, pulsando cualquiera de los interruptores de las luces principales de aviso de fallos.
28. Esta sección contiene los procedimientos de investigación de averías para el sistema principal de energía
29. A medida que sube la temperatura del fluido y desciende la presión, se cierra la válvula bypass (17) dirigiendo el flujo del drenaje de la caja a través del conducto de refrigeración de aire (14), antes de regresar al depósito hidráulico del avión por la boca (15.
30. Si se registra una sobrepresión dentro del cilindro del depósito, una válvula de seguridad (4), ajustada a 7,7 Kg/cm 2 (110 psi) libera el exceso de presión.
31. La boca (16) se utiliza para la conexión de la tubería (12) de entrada del fluido purgado de la caja, y la boca (15) sirve para la conexión con el depósito hidráulico del avión.
32. Dos válvulas de distribución conectadas en las tuberías de salida de descarga del cilindro extintor dirigen al agente extintor hacia el motor adecuado.
33. Dos indicadores de descarga de sobrepresión instalados en el recubrimiento exterior del avión dan indicación visual sobre si el cilindro exterior correspondiente ha descargado o no, por causa de la sobrepresión.
34. Al pulsar el vástago de descarga de la válvula de toma de muestras (15) se permite que una parte del fluido que se encuentra en los pasos de retorno del interior de la unidad modular pase a través de la válvula hasta un recipiente para muestras de fluido.
35. Las pérdidas de fluido salen a través de la boca de drenaje de pérdidas (7), que se encuentra en la parte inferior del alojamiento.
36. Las palancas pueden ser seleccionadas para cualquiera de las dos descargas, izquierda o derecha, permitiendo dos disparos en la zona seleccionada.
37. Los cilindros extintores van asegurados al soporte del avión por tres orejetas de soporte (6) separadas 120ºC.
38. El sistema de extinción de incendios de motor facilita a la tripulación los medios para sofocar cualquier incendio que se pueda producir en los dos motores.
39. Una vez que se ha detonado el extintor, el fluido extintor se evacuará completamente.
40. Cuando el motor eléctrico está en operación, el fluido hidráulico del depósito hidráulico del avión entra en el conjunto de bomba (3) a través de la boca de entrada
(5).
41. El sistema se rearma, y anula automáticamente la indicación de alarma en el caso de que cesen las condiciones de sobretemperatura o incendio.

Appendix V 109
42. Las dos motobombas están interconectadas, proporcionando así presión al sistema en el caso de fallo de una motobomba.
43. Debe tenerse cuidado al manejar los cilindros extintores porque los cartuchos de descarga contienen una pequeña carga explosiva.
44. El piloto tira de la palanca para energizar el sistema, produciendo los resultados siguientes: Cortar el suministro de combustible al motor, cerrando la válvula de corte de combustible.
45. La indicación se anula volviendo los interruptores de prueba a la posición OFF.
46. La consideración de ambas propiedades elimina la posibilidad de falsos avisos de peligro de incendios, y aumenta la seguridad e integridad del sistema.
47. El sistema lleva dos cilindros exteriores situados en el centro y debajo de la sección de la carena posterior del ala.
48. Cuando el elemento sensor está sujeto a condiciones de sobretemperatura o incendio, su resistencia cae y se eleva su capacidad eléctrica.
49. Dos bombas hidráulicas, activadas por medios de energía eléctrica, constituyen la principal fuente de energía.
50. Suenan avisos acústicos en la cabina de pilotos.

1. Quitar la unión (8) de la tubería de descarga de presión, del acoplamiento (2) del cilindro.
2. Quitar los tornillos (13), las arandelas (12) y soltar la unidad de cilindro (1) del conjunto de soporte de montaje (11).
3. Quitar las sujeciones provisionales y examinar los cables en cuanto a daños, seguridad de fijación y señales de corrosión.
4. Quitar y desechar el alambre de frenado de la unión (8).
5. Sacar el cilindro (1) con cuidado del conjunto de soporte de montaje (11), y poner puentes de seguridad con banderola en las conexiones eléctricas (4) del cartucho.
6. Soportar en peso la unidad de control (8), y conectar el conector (13) del manómetro indicador de cantidad de fluido hidráulico al receptáculo (12); el conector (3) del manómetro indicador de presión del freno de emergencia, al receptáculo (6); el conector (5) del manómetro indicador de presión del freno, al receptáculo (9); el conector (4) del manómetro indicador de presión hidráulica, al receptáculo (10), y el conector (2) del indicador de aviso de temperatura/interruptor de motobomba, al receptáculo (11).
7. Quitar las tapas de protección (4) de los acoplamientos rápidos de las tomas de presión (1) y de retorno (5) de la unidad modular.
8. Aplicar la cinta indicadora de temperatura al cilindro (1) del depósito de fluido hidráulico.
9. Comprobar visualmente la zona de montaje de la unidad de control del sistema hidráulico, por si presentan señales de daños o corrosión.
10. Colocar avisos de peligro, advirtiendo al personal de la zona sobre el trabajo que se está realizando.
11. Comprobar el sistema de energía e indicaciones hidráulicas, después de haber sustituido cualquier componente o durante el procedimiento de investigación de averías.
12. Conectar la unión (8) de la tubería de descarga de presión al acoplamiento (2) del cilindro.
13. Quitar las tapas/tapones de protección de tuberías de los adaptadores de los mamparos cortafuego izquierdo y derecho.
14. Determinar el buen estado de funcionamiento de las tuberías de distribución del sistema.

Appendix VI 111
15. Quitar y desechar el alambre de frenado de las boquillas de purgado (2) del depósito hidráulico (1).
16. Poner tubos de purgado (3) en las boquillas de purgado (2), y meter los extremos libres de los tubos en el recipiente de drenaje (4) sumergiéndolos en fluido hidráulico.
17. Poner las tapas de protección (4) de los acoplamientos rápidos de las tomas de presión (1) y de retorno (5) de la unidad modular.
18. Comprobar visualmente los botones indicadores en rojo de los filtros de drenaje de la caja (1), de presión (2) y de retorno (3).
19. Interrumpir el suministro de fluido hidráulico al freno de la hélice del motor derecho.
20. Desconectar una de las baterías de uno de los contenedores de los extintores de fuego.
21. Desconectar del receptáculo (11) el conector (2) del indicador de aviso de temperatura/interruptor de la motobomba; del receptáculo (10), el conector (4) del manómetro indicador de presión hidráulica; del receptáculo (9), el conector (5) del manómetro indicador de presión del freno; del receptáculo (6), el conector (3) del manómetro indicador de presión del freno de emergencia; y del receptáculo (12), el conector (13) del indicador de cantidad de fluido hidráulico.
22. Quitar las uniones (9) y (10) de la tubería de descarga, de los acoplamientos (3) de la unidad de descarga.
23. Desconectar las tuberías difusoras de los adaptadores de los mamparos cortafuego de los motores izquierdo y derecho.
24. Reparar o sustituir según sea necesario.
25. Quitar y desechar el alambre de frenado de la unión (8).
26. Obtener acceso al sistema hidráulico en la carena derecha de tren de aterrizaje del avión.
27. Volver la palanca a la posición central y meterla a la posición cerrada.
28. Poner el soporte de montaje (14) en el depósito de repuesto con los bulones (21) y las arandelas (22).
29. Retraer y extender el tren de aterrizaje cinco veces, con intervalos de 30 segundos entre operaciones.
30. Soportar en peso el depósito y poner los tornillos (7) en los soportes (6) y (14) de montaje del depósito.
31. Limpiar y examinar el conjunto de soporte de montaje (11) en cuanto a daños, seguridad de fijación y señales de corrosión.

Appendix VI 112
32. Cerrar las boquillas de purgado (2), quitar los tubos de purgado (3), apretar las boquillas de purgado (2) y frenar con alambre nuevo.
33. Energizar la dirección de rueda de morro y, con la rueda de mando de dirección, operar cinco veces el sistema de dirección en ambas direcciones, con intervalos de
30 segundos entre operaciones.
34. Soltar los broches rápidos (7), y sacar la unidad de control (8) del sistema hidráulico hasta separarla de la superficie de montaje (1) del tablero superior.
35. Liberar la presión del banco de pruebas hidráulicas, y desconectar el banco de pruebas del avión.
36. Examinar las conexiones eléctricas del extintor de incendios, y comprobar que los dos fusibles de los extintores IZQ y DCH están fundidos.
37. Conectar la GPU y energizar el sistema eléctrico del avión.
38. Presurizar al nivel correcto, si fuera necesario.
39. Poner tapas de protección para tuberías en los extremos descubiertos.
40. Quitar la unión (8) de la tubería de descarga de presión, del acoplamiento (2) del cilindro.
41. Conectar los terminales eléctricos en los receptáculos del cartucho de los cilindros extintores.
42. Drenar todo el fluido hidráulico del depósito.
43. Retirar los avisos de peligro.
44. Examinar los indicadores de los elementos de filtro de la unidad modular por si hay indicación de obstrucción.
45. Limpiar todo el fluido derramado en la zona del depósito, utilizando un paño limpio y exento de pelusas.
46. Tirar del depósito para sacarlo de las orejetas (8) de montaje.
47. Quitar y desechar el alambre de frenado de las boquillas de purgado (2), y meter los extremos libres de los tubos en el recipiente de drenaje (4) sumergiéndolos en fluido hidráulico.
48. Desenergoizar el sistema eléctrico del avión y desconectar la GPU.
49. Conectar la unidad de potencia exterior (GPU) y energizar el sistema eléctrico del avión.
50. Colocar avisos de peligro.

Error: Sentence 'Se enciende el módulo ENG FIRE en la central de aviso de fallos de la cabina de pilotos y las luces principales de aviso de fallos parpadean .' contains more than 3 pps
[[en/PREP,[la/DETSG,central/NOUNSG]],[de/PREP,[aviso/NOUNSG]],[de/PR
EP,[fallos/NOUNPL]],[de/PREP,[la/DETSG,cabina/NOUNSG]],[de/PREP,[pil otos/NOUNPL]]] which is not allowed.
[vg3([Se/SE,enciende/VERBFIN]),snp(5,[el/DETSG,módulo/NOUNSG,ENG_FIR
E/NOUNSG]),ppseq(5,[[en/PREP,[la/DETSG,central/NOUNSG]],[de/PREP,[av iso/NOUNSG]],[de/PREP,[fallos/NOUNPL]],[de/PREP,[la/DETSG,cabina/NOU
NSG]],[de/PREP,[pilotos/NOUNPL]]]),y/CONJ,snp(4,[las/DETPL,luces/NOU
NPL,principales/ADJPL]),ppseq(2,[[de/PREP,[aviso/NOUNSG]],[de/PREP,[ fallos/NOUNPL]]]),vg4([parpadean/VERBFIN]),. /SENT]
Error: Length of sentence 'Todos los acoplamientos hidráulicos están situados en la parte posterior de la unidad modular , y consta de bocas de entrada de presión de las bombas ( 13 ) , una boca de salida de servicio ( 10 ) , una boca de salida de presión al depósito ( 15 ) , unas bocas de entrada de drenaje ( 11 ) de la caja de la bomba , una boca de entrada a presión ( 1 ) del depósito , unas bocas de alimentación ( 12 ) de las bombas , una boca de entrada de retorno ( 8 ) del fluido y una boca de salida de retorno
( 9 ) del fluido .' is greater than 30 words.
Error: 'consta' in sentence 'Todos los acoplamientos hidráulicos están situados en la parte posterior de la unidad modular , y consta de bocas de entrada de presión de las bombas ( 13 ) , una boca de salida de servicio ( 10 ) , una boca de salida de presión al depósito ( 15 ) , unas bocas de entrada de drenaje ( 11 ) de la caja de la bomba , una boca de entrada a presión ( 1 ) del depósito , unas bocas de alimentación ( 12 ) de las bombas , una boca de entrada de retorno ( 8 ) del fluido y una boca de salida de retorno
( 9 ) del fluido .' is not in the main dictionary or in the compound dictionary.
[Todos/PREDETPL,snp(4,[los/DETPL,acoplamientos/NOUNPL,hidráulicos/AD
JPL]),vg6([están/AUX]),situados/PAPPL,ppseq(2,[[en/PREP,[la/DETSG,pa rte/NOUNSG,posterior/ADJSG]],[de/PREP,[la/DETSG,unidad_modular/NOUNS
G]]]),,/CM,y/CONJ,vg4([consta/VERBFIN]),ppseq(3,[[de/PREP,[bocas_de_ entrada/NOUNSG]],[de/PREP,[presión/NOUNSG]],[de/PREP,[las/DETPL,bomb as/NOUNPL]]]),(/PUNCT,13/DIG,)/PUNCT,,/CM,una/DETQUANTSG,snp(12,[boc a_de_salida/NOUNSG]),ppseq(1,[[de/PREP,[servicio/NOUNSG]]]),(/PUNCT,
10/DIG,)/PUNCT,,/CM,una/DETQUANTSG,snp(12,[boca_de_salida/NOUNSG]),p pseq(2,[[de/PREP,[presión/NOUNSG]],[al/PREPDET,[depósito/NOUNSG]]]),
(/PUNCT,15/DIG,)/PUNCT,,/CM,unas/DETQUANTPL,snp(12,[bocas_de_entrada
/NOUNSG]),ppseq(1,[[de/PREP,[drenaje/NOUNSG]]]),(/PUNCT,11/DIG,)/PUN
CT,ppseq(2,[[de/PREP,[la/DETSG,caja/NOUNSG]],[de/PREP,[la/DETSG,bomb a/NOUNSG]]]),,/CM,una/DETQUANTSG,snp(12,[boca_de_entrada/NOUNSG]),pp
2
Only the first ten analyses have been included in order to avoid an excessive number of pages in this appendix.

Appendix VII 114 seq(1,[[a/PREP,[presión/NOUNSG]]]),(/PUNCT,1/DIG,)/PUNCT,ppseq(1,[[d el/PREPDET,[depósito/NOUNSG]]]),,/CM,unas/DETQUANTPL,snp(12,[bocas_d e_alimentación/NOUNSG]),(/PUNCT,12/DIG,)/PUNCT,ppseq(1,[[de/PREP,[la s/DETPL,bombas/NOUNPL]]]),,/CM,una/DETQUANTSG,snp(12,[boca_de_entrad a/NOUNSG]),ppseq(1,[[de/PREP,[retorno/NOUNSG]]]),(/PUNCT,8/DIG,)/PUN
CT,del/PREPDET,fluido/PAPSG,y/CONJ,una/DETQUANTSG,snp(12,[boca_de_sa lida/NOUNSG]),ppseq(1,[[de/PREP,[retorno/NOUNSG]]]),(/PUNCT,9/DIG,)/
PUNCT,del/PREPDET,fluido/PAPSG,. /SENT]
Error: Length of sentence 'Los elementos están conectados con el cableado del avión a través de receptáculos de mamparos , quedando conectados a las unidades de control WC11 ( WC12 ) instaladas en el conjunto del armario eléctrico IZQ ( DCH ) del fuselaje central .' is greater than 30 words.
Error: 'quedando' in sentence 'Los elementos están conectados con el cableado del avión a través de receptáculos de mamparos , quedando conectados a las unidades de control WC11 ( WC12 ) instaladas en el conjunto del armario eléctrico IZQ ( DCH ) del fuselaje central .' is not in the main dictionary or in the compound dictionary.
[snp(11,[Los/DETPL,elementos/NOUNPL]),vg6([están/AUX]),conectados/PA
PPL,con/PREP,el/DETSG,cableado/PAPSG,ppseq(2,[[del/PREPDET,[avión/NO
UNSG]],[a través de/PREP,[receptáculos_de_mamparos/NOUNSG]]]),,/CM,quedando/VERBPRP,c onectados/PAPPL,a/PREP,las/DETPL,snp(12,[unidades_de_control/NOUNSG]
),WC11/PROP,(/PUNCT,WC12/PROP,)/PUNCT,instaladas/PAPPL,ppseq(2,[[en/
PREP,[el/DETSG,conjunto/NOUNSG]],[del/PREPDET,[armario_eléctrico/NOU
NSG]]]),IZQ/PROP,(/PUNCT,DCH/PROP,)/PUNCT,ppseq(1,[[del/PREPDET,[fus elaje/NOUNSG]]]),central/ADJSG,. /SENT]
Error: Length of sentence 'El aviso de insuficiente presión en la bomba es enviado a la central de aviso de fallos en la cabina de pilotos por dos manocontadores ( 4 ) , que están situados en la parte superior de la unidad modular .' is greater than 30 words.
Error: Sentence 'El aviso de insuficiente presión en la bomba es enviado a la central de aviso de fallos en la cabina de pilotos por dos manocontadores ( 4 ) , que están situados en la parte superior de la unidad modular .' contains a passive construction
[es/AUX,enviado/PAPSG] which is not allowed.
Error: Sentence 'El aviso de insuficiente presión en la bomba es enviado a la central de aviso de fallos en la cabina de pilotos por dos manocontadores ( 4 ) , que están situados en la parte superior de la unidad modular .' contains more than 3 pps
[[a/PREP,[la/DETSG,central/NOUNSG]],[de/PREP,[aviso/NOUNSG]],[de/PRE
P,[fallos/NOUNPL]],[en/PREP,[la/DETSG,cabina/NOUNSG]],[de/PREP,[pilo tos/NOUNPL]]] which is not allowed.
[snp(10,[El/DETSG,aviso/NOUNSG]),de/PREP,insuficiente/ADJSG,snp(12,[ presión/NOUNSG]),ppseq(1,[[en/PREP,[la/DETSG,bomba/NOUNSG]]]),vg1([e s/AUX,enviado/PAPSG]),ppseq(5,[[a/PREP,[la/DETSG,central/NOUNSG]],[d e/PREP,[aviso/NOUNSG]],[de/PREP,[fallos/NOUNPL]],[en/PREP,[la/DETSG, cabina/NOUNSG]],[de/PREP,[pilotos/NOUNPL]]]),por/PREP,dos/NUM,snp(13
,[manocontadores/NOUNPL]),(/PUNCT,4/DIG,)/PUNCT,,/CM,que/QUE,vg6([es tán/AUX]),situados/PAPPL,ppseq(2,[[en/PREP,[la/DETSG,parte/NOUNSG,su perior/ADJSG]],[de/PREP,[la/DETSG,unidad_modular/NOUNSG]]]),. /SENT]

Appendix VII 115
Error: Length of sentence ’Cuando la temperatura supera un nivel crítico en la góndola , la unidad de control transmite señales de aviso de fallo a los instrumentos indicadores de la cabina de pilotos .' is greater than 30 words.
Error: 'unidad_de_control_transmite' in sentence 'Cuando la temperatura supera un nivel crítico en la góndola , la unidad de control transmite señales de aviso de fallo a los instrumentos indicadores de la cabina de pilotos .' is not in the main dictionary or in the compound dictionary.
[Cuando/CONADV,snp(10,[la/DETSG,temperatura/NOUNSG]),vg4([supera/VER
BFIN]),un/DETQUANTSG,snp(12,[nivel_crítico/NOUNSG]),ppseq(1,[[en/PRE
P,[la/DETSG,góndola/NOUNSG]]]),,/CM,snp(10,[la/DETSG,unidad_de_contr ol_transmite/NOUNSG]),snp(13,[señales/NOUNPL]),ppseq(2,[[de/PREP,[av iso/NOUNSG]],[de/PREP,[fallo/NOUNSG]]]),a/PREP,los/DETPL,snp(12,[ins trumentos_indicadores/NOUNSG]),ppseq(2,[[de/PREP,[la/DETSG,cabina/NO
UNSG]],[de/PREP,[pilotos/NOUNPL]]]),. /SENT]
Error: Length of sentence 'El subconjunto de refrigeración del aceite ( 1 ) es de construcción monobloque y consta de unas placas colocadas de forma alterna , unas barras y aletas laterales , contenidas en un conjunto de conducto de aire ( 14 ) .' is greater than 30 words.
Error: 'consta' in sentence 'El subconjunto de refrigeración del aceite ( 1 ) es de construcción monobloque y consta de unas placas colocadas de forma alterna , unas barras y aletas laterales , contenidas en un conjunto de conducto de aire ( 14 ) .' is not in the main dictionary or in the compound dictionary.
Error: 'colocadas' in sentence 'El subconjunto de refrigeración del aceite ( 1 ) es de construcción monobloque y consta de unas placas colocadas de forma alterna , unas barras y aletas laterales , contenidas en un conjunto de conducto de aire ( 14 ) .' is not in the main dictionary or in the compound dictionary.
[snp(10,[El/DETSG,subconjunto_de_refrigeración_del_aceite/NOUNSG]),(
/PUNCT,1/DIG,)/PUNCT,vg6([es/AUX]),ppseq(1,[[de/PREP,[construcción_m onobloque/NOUNSG]]]),y/CONJ,vg4([consta/VERBFIN]),de/PREP,unas/DETQU
ANTPL,snp(13,[placas/NOUNPL]),colocadas/PAPPL,ppseq(1,[[de/PREP,[for ma/NOUNSG]]]),alterna/ADJSG,,/CM,unas/DETQUANTPL,snp(13,[barras/NOUN
PL]),y/CONJ,snp(13,[aletas/NOUNPL]),laterales/ADJPL,,/CM,contenidas/
PAPPL,en/PREP,un/DETQUANTSG,snp(12,[conjunto/NOUNSG]),ppseq(2,[[de/P
REP,[conducto/NOUNSG]],[de/PREP,[aire/NOUNSG]]]),(/PUNCT,14/DIG,)/PU
NCT,. /SENT]
[snp(10,[El/DETSG,sistema/NOUNSG]),vg3([se/SE,rearma/VERBFIN]),volvi endo/VERBPRP,snp(10,[el/DETSG,interruptor_de_prueba/NOUNSG]),selecci onando/VERBPRP,ppseq(1,[[a/PREP,[la/DETSG,posición_OFF/NOUNSG]]]),.
/SENT]
Error: Sentence 'El flujo de fluido desde las motobombas es enviado a la boca de alta presión ( 7 ) , a una presión de 211 Kg/cm2 ( 3000 psi ) .' contains a passive construction [es/AUX,enviado/PAPSG] which is not allowed.
[snp(10,[El/DETSG,flujo/NOUNSG]),de/PREP,fluido/PAPSG,ppseq(1,[[desd e/PREP,[las/DETPL,motobombas/NOUNPL]]]),vg1([es/AUX,enviado/PAPSG]), ppseq(1,[[a/PREP,[la/DETSG,boca/NOUNSG]]]),de/PREP,alta/ADJSG,snp(12
,[presión/NOUNSG]),(/PUNCT,7/DIG,)/PUNCT,,/CM,a/PREP,una/DETQUANTSG,

Appendix VII 116 snp(12,[presión/NOUNSG]),de/PREP,211/DIG,Kg/cm2/PROP,(/PUNCT,3000/DI
G,psi/ADJ,)/PUNCT,. /SENT]
Error: Length of sentence 'El sensor de incendios es un elemento flexible que lleva un tubo capilar fino de acero inoxidable que contiene un electrodo central separado y aislado de las paredes del tubo por un material semiconductor sensible al calor con un coeficiente de resistencia negativo .' is greater than 30 words.
Error: 'lleva' in sentence 'El sensor de incendios es un elemento flexible que lleva un tubo capilar fino de acero inoxidable que contiene un electrodo central separado y aislado de las paredes del tubo por un material semiconductor sensible al calor con un coeficiente de resistencia negativo .' is not in the main dictionary or in the compound dictionary.
Error: Sentence 'El sensor de incendios es un elemento flexible que lleva un tubo capilar fino de acero inoxidable que contiene un electrodo central separado y aislado de las paredes del tubo por un material semiconductor sensible al calor con un coeficiente de resistencia negativo .' contains more than 3 pps
[[de/PREP,[las/DETPL,paredes/NOUNPL]],[del/PREPDET,[tubo/NOUNSG]],[p or/PREP,[un/DETQUANTSG,material_semiconductor/NOUNSG,sensible/ADJSG]
],[al/PREPDET,[calor/NOUNSG]],[con/PREP,[un/DETQUANTSG,coeficiente_d e_resistencia/NOUNSG,negativo/ADJSG]]] which is not allowed.
[snp(10,[El/DETSG,sensor/NOUNSG]),ppseq(1,[[de/PREP,[incendios/NOUNP
L]]]),vg6([es/AUX]),snp(7,[un/DETQUANTSG,elemento/NOUNSG,flexible/AD
JSG]),que/QUE,vg4([lleva/VERBFIN]),snp(7,[un/DETQUANTSG,tubo/NOUNSG, capilar/ADJSG]),fino/ADJSG,ppseq(1,[[de/PREP,[acero_inoxidable/NOUNS
G]]]),que/QUE,vg4([contiene/VERBFIN]),snp(7,[un/DETQUANTSG,electrodo
/NOUNSG,central/ADJSG]),separado/PAPSG,y/CONJ,aislado/PAPSG,ppseq(5,
[[de/PREP,[las/DETPL,paredes/NOUNPL]],[del/PREPDET,[tubo/NOUNSG]],[p or/PREP,[un/DETQUANTSG,material_semiconductor/NOUNSG,sensible/ADJSG]
],[al/PREPDET,[calor/NOUNSG]],[con/PREP,[un/DETQUANTSG,coeficiente_d e_resistencia/NOUNSG,negativo/ADJSG]]]),. /SENT]
Error: Length of sentence 'La descarga de presión rompe el disco verde del indicador de descarga de sobrepresión situado en el recubrimiento exterior del avión que de este modo indica que la descarga del cilindro es debida a la sobrepresión .' is greater than
30 words.
Error: 'debida' in sentence 'La descarga de presión rompe el disco verde del indicador de descarga de sobrepresión situado en el recubrimiento exterior del avión que de este modo indica que la descarga del cilindro es debida a la sobrepresión .' is not in the main dictionary or in the compound dictionary.
Error: Sentence 'La descarga de presión rompe el disco verde del indicador de descarga de sobrepresión situado en el recubrimiento exterior del avión que de este modo indica que la descarga del cilindro es debida a la sobrepresión .' contains a passive construction [es/AUX,debida/PAPSG] which is not allowed.
[snp(10,[La/DETSG,descarga/NOUNSG]),ppseq(1,[[de/PREP,[presión/NOUNS
G]]]),vg4([rompe/VERBFIN]),snp(3,[el/DETSG,disco/NOUNSG,verde/ADJSG]
),ppseq(1,[[del/PREPDET,[indicador_de_descarga_de_sobrepresión/NOUNS
G]]]),situado/PAPSG,ppseq(2,[[en/PREP,[el/DETSG,recubrimiento/NOUNSG
,exterior/ADJSG]],[del/PREPDET,[avión/NOUNSG]]]),que/QUE,ppseq(1,[[d e/PREP,[este/DETSG,modo/NOUNSG]]]),vg4([indica/VERBFIN]),que/QUE,snp

Appendix VII 117
(10,[la/DETSG,descarga/NOUNSG]),ppseq(1,[[del/PREPDET,[cilindro/NOUN
SG]]]),vg1([es/AUX,debida/PAPSG]),ppseq(1,[[a/PREP,[la/DETSG,sobrepr esión/NOUNSG]]]),. /SENT]

[vg5([Quitar/VERBINF]),snp(10,[la/DETSG,unión/NOUNSG]),(/PUNCT,8/DIG
,)/PUNCT,ppseq(3,[[de/PREP,[la/DETSG,tubería/NOUNSG]],[de/PREP,[desc arga/NOUNSG]],[de/PREP,[presión/NOUNSG]]]),,/CM,ppseq(1,[[del/PREPDE
T,[acoplamiento/NOUNSG]]]),(/PUNCT,2/DIG,)/PUNCT,ppseq(1,[[del/PREPD
ET,[cilindro/NOUNSG]]]),. /SENT]
Error: Length of sentence 'Quitar los tornillos ( 13 ) , las arandelas ( 12 ) y soltar la unidad de cilindro ( 1 ) del conjunto de soporte de montaje ( 11 ) .' is greater than 25 words.
Error: Sentence 'Quitar los tornillos tornillo ( 13 ) , las arandelas ( 12 ) y soltar la unidad de cilindro ( 1 ) del conjunto de soporte de montaje ( 11 ) .' contains more than 2 commands, which is not allowed
[vg5([Quitar/VERBINF]),snp(6,[los/DETPL,tornillos/NOUNPL,tornillo/NO
UNPL]),(/PUNCT,13/DIG,)/PUNCT,,/CM,snp(11,[las/DETPL,arandelas/NOUNP
L]),(/PUNCT,12/DIG,)/PUNCT,y/CONJ,vg5([soltar/VERBINF]),snp(10,[la/D
ETSG,unidad/NOUNSG]),ppseq(1,[[de/PREP,[cilindro/NOUNSG]]]),(/PUNCT,
1/DIG,)/PUNCT,ppseq(2,[[del/PREPDET,[conjunto/NOUNSG]],[de/PREP,[sop orte_de_montaje/NOUNSG]]]),(/PUNCT,11/DIG,)/PUNCT,. /SENT]
Error: Sentence 'Quitar las sujeciones provisionales y examinar los cables en cuanto a daños , seguridad de fijación y señales de corrosión .' contains more than 2 commands, which is not allowed
[vg5([Quitar/VERBINF]),snp(4,[las/DETPL,sujeciones/NOUNPL,provisiona les/ADJPL]),y/CONJ,vg5([examinar/VERBINF]),snp(11,[los/DETPL,cables/
NOUNPL]),ppseq(1,[[en cuanto a/PREP,[daños/NOUNPL]]]),,/CM,snp(12,[seguridad/NOUNSG]),ppseq(1,[[d e/PREP,[fijación/NOUNSG]]]),y/CONJ,snp(13,[señales/NOUNPL]),ppseq(1,
[[de/PREP,[corrosión/NOUNSG]]]),. /SENT]
Error: Sentence 'Quitar y desechar el alambre de frenado de la unión
( 8 ) .' contains more than 2 commands, which is not allowed
[vg5([Quitar/VERBINF]),y/CONJ,vg5([desechar/VERBINF]),snp(10,[el/DET
SG,alambre_de_frenado/NOUNSG]),ppseq(1,[[de/PREP,[la/DETSG,unión/NOU
NSG]]]),(/PUNCT,8/DIG,)/PUNCT,. /SENT]
Error: Length of sentence 'Sacar el cilindro ( 1 ) con cuidado del conjunto de soporte de montaje ( 11 ) , y poner puentes de seguridad con banderola en las conexiones eléctricas ( 4 ) del cartucho .' is greater than 25 words.
Error: Sentence 'Sacar el cilindro ( 1 ) con cuidado del conjunto de soporte de montaje ( 11 ) , y poner puentes de seguridad con
3
Only the first ten analyses have been included in order to avoid an excessive number of pages in this appendix.

Appendix VIII 119 banderola en las conexiones eléctricas ( 4 ) del cartucho .' contains more than 2 commands, which is not allowed
[vg5([Sacar/VERBINF]),snp(10,[el/DETSG,cilindro/NOUNSG]),(/PUNCT,1/D
IG,)/PUNCT,ppseq(3,[[con/PREP,[cuidado/NOUNSG]],[del/PREPDET,[conjun to/NOUNSG]],[de/PREP,[soporte_de_montaje/NOUNSG]]]),(/PUNCT,11/DIG,)
/PUNCT,,/CM,y/CONJ,vg5([poner/VERBINF]),snp(13,[puentes/NOUNPL]),pps eq(3,[[de/PREP,[seguridad/NOUNSG]],[con/PREP,[banderola/NOUNSG]],[en
/PREP,[las/DETPL,conexiones/NOUNPL,eléctricas/ADJPL]]]),(/PUNCT,4/DI
G,)/PUNCT,ppseq(1,[[del/PREPDET,[cartucho/NOUNSG]]]),. /SENT]
Error: Length of sentence 'Soportar en peso la unidad de control ( 8
) , y conectar el conector ( 13 ) del manómetro indicador de cantidad de fluido hidráulico al receptáculo ( 12 ) ; el conector (
3 ) del manómetro indicador de presión del freno de emergencia , al receptáculo ( 6 ) ; el conector ( 5 ) del manómetro indicador de presión del freno , al receptáculo ( 9 ) ; el conector ( 4 ) del manómetro indicador de presión hidráulica , al receptáculo ( 10 ) , y el conector ( 2 ) del indicador de aviso de temperatura/interruptor de motobomba , al receptáculo ( 11 ) .' is greater than 25 words.
Error: 'unidad_de_control_(' in sentence 'Soportar en peso la unidad de control ( 8 ) , y conectar el conector ( 13 ) del manómetro indicador de cantidad de fluido hidráulico al receptáculo ( 12 ) ; el conector ( 3 ) del manómetro indicador de presión del freno de emergencia , al receptáculo ( 6 ) ; el conector ( 5 ) del manómetro indicador de presión del freno , al receptáculo ( 9 ) ; el conector
( 4 ) del manómetro indicador de presión hidráulica , al receptáculo
( 10 ) , y el conector ( 2 ) del indicador de aviso de temperatura/interruptor de motobomba , al receptáculo ( 11 ) .' is not in the main dictionary or in the compound dictionary.
Error: Sentence 'Soportar en peso la unidad de control ( 8 ) , y conectar el conector ( 13 ) del manómetro indicador de cantidad de fluido hidráulico al receptáculo ( 12 ) ; el conector ( 3 ) del manómetro indicador de presión del freno de emergencia , al receptáculo ( 6 ) ; el conector ( 5 ) del manómetro indicador de presión del freno , al receptáculo ( 9 ) ; el conector ( 4 ) del manómetro indicador de presión hidráulica , al receptáculo ( 10 ) , y el conector ( 2 ) del indicador de aviso de temperatura/interruptor de motobomba , al receptáculo ( 11 ) .' contains more than 2 commands, which is not allowed
[vg5([Soportar/VERBINF]),ppseq(1,[[en/PREP,[peso/NOUNSG]]]),snp(10,[ la/DETSG,unidad_de_control_(/NOUNSG]),8/DIG,)/PUNCT,,/CM,y/CONJ,vg5(
[conectar/VERBINF]),snp(10,[el/DETSG,conector/NOUNSG]),(/PUNCT,13/DI
G,)/PUNCT,ppseq(1,[[del/PREPDET,[manómetro/NOUNSG]]]),indicador/ADJS
G,ppseq(3,[[de/PREP,[cantidad/NOUNSG]],[de/PREP,[fluido_hidráulico/N
OUNSG]],[al/PREPDET,[receptáculo/NOUNSG]]]),(/PUNCT,12/DIG,)/PUNCT,;
/SENT,snp(10,[el/DETSG,conector/NOUNSG]),(/PUNCT,3/DIG,)/PUNCT,ppseq
(1,[[del/PREPDET,[manómetro/NOUNSG]]]),indicador/ADJSG,ppseq(2,[[de/
PREP,[presión/NOUNSG]],[del/PREPDET,[freno_de_emergencia/NOUNSG]]]),
,/CM,ppseq(1,[[al/PREPDET,[receptáculo/NOUNSG]]]),(/PUNCT,6/DIG,)/PU
NCT,;/SENT,snp(10,[el/DETSG,conector/NOUNSG]),(/PUNCT,5/DIG,)/PUNCT, ppseq(1,[[del/PREPDET,[manómetro/NOUNSG]]]),indicador/ADJSG,ppseq(2,
[[de/PREP,[presión/NOUNSG]],[del/PREPDET,[freno/NOUNSG]]]),,/CM,ppse q(1,[[al/PREPDET,[receptáculo/NOUNSG]]]),(/PUNCT,9/DIG,)/PUNCT,;/SEN
T,snp(10,[el/DETSG,conector/NOUNSG]),(/PUNCT,4/DIG,)/PUNCT,ppseq(1,[
[del/PREPDET,[manómetro/NOUNSG]]]),indicador/ADJSG,ppseq(1,[[de/PREP
,[presión/NOUNSG]]]),hidráulica/ADJSG,,/CM,ppseq(1,[[al/PREPDET,[rec

Appendix VIII 120 eptáculo/NOUNSG]]]),(/PUNCT,10/DIG,)/PUNCT,,/CM,y/CONJ,snp(10,[el/DE
TSG,conector/NOUNSG]),(/PUNCT,2/DIG,)/PUNCT,ppseq(2,[[del/PREPDET,[i ndicador/NOUNSG]],[de/PREP,[aviso/NOUNSG]]]),de/PREP,temperatura/int erruptor/PROP,ppseq(1,[[de/PREP,[motobomba/NOUNSG]]]),,/CM,ppseq(1,[
[al/PREPDET,[receptáculo/NOUNSG]]]),(/PUNCT,11/DIG,)/PUNCT,. /SENT]
Error: Length of sentence 'Quitar las tapas de protección ( 4 ) de los acoplamientos rápidos de las tomas de presión ( 1 ) y de retorno
( 5 ) de la unidad modular .' is greater than 25 words.
[vg5([Quitar/VERBINF]),las/DETPL,snp(12,[tapas_de_protección/NOUNSG]
),(/PUNCT,4/DIG,)/PUNCT,ppseq(3,[[de/PREP,[los/DETPL,acoplamientos/N
OUNPL,rápidos/ADJPL]],[de/PREP,[las/DETPL,tomas/NOUNPL]],[de/PREP,[p resión/NOUNSG]]]),(/PUNCT,1/DIG,)/PUNCT,y/CONJ,ppseq(1,[[de/PREP,[re torno/NOUNSG]]]),(/PUNCT,5/DIG,)/PUNCT,ppseq(1,[[de/PREP,[la/DETSG,u nidad_modular/NOUNSG]]]),. /SENT]
[vg5([Aplicar/VERBINF]),snp(10,[la/DETSG,cinta_indicadora_de_tempera tura/NOUNSG]),ppseq(1,[[al/PREPDET,[cilindro/NOUNSG]]]),(/PUNCT,1/DI
G,)/PUNCT,ppseq(1,[[del/PREPDET,[depósito_de_fluido_hidráulico/NOUNS
G]]]),. /SENT]
,[cartucho/NOUNSG]]]),. /SENT]
Error: 'unidad_de_control_del' in sentence 'Comprobar visualmente la zona de montaje de la unidad de control del sistema hidráulico , por si presentan señales de daños o corrosión .' is not in the main dictionary or in the compound dictionary.
Error: 'presentan' in sentence 'Comprobar visualmente la zona de montaje de la unidad de control del sistema hidráulico , por si presentan señales de daños o corrosión .' is not in the main dictionary or in the compound dictionary.
[vg5([Comprobar/VERBINF]),visualmente/ADV,snp(10,[la/DETSG,zona_de_m ontaje/NOUNSG]),ppseq(1,[[de/PREP,[la/DETSG,unidad_de_control_del/NO
UNSG,sistema_hidráulico/NOUNSG]]]),,/CM,por/PREP,si/CONJ,vg4([presen tan/VERBFIN]),snp(13,[señales/NOUNPL]),ppseq(1,[[de/PREP,[daños/NOUN
PL]]]),o/CONJ,snp(12,[corrosión/NOUNSG]),. /SENT]
Error: 'Colocar' in sentence 'Colocar avisos de peligro , advirtiendo al personal de la zona sobre el trabajo que se está realizando .' is not in the main dictionary or in the compound dictionary.
Error: 'realizando' in sentence 'Colocar avisos de peligro , advirtiendo al personal de la zona sobre el trabajo que se está realizando .' is not in the main dictionary or in the compound dictionary.
[vg5([Colocar/VERBINF]),snp(13,[avisos/NOUNPL]),ppseq(1,[[de/PREP,[p eligro/NOUNSG]]]),,/CM,advirtiendo/VERBPRP,ppseq(3,[[al/PREPDET,[per sonal/NOUNSG]],[de/PREP,[la/DETSG,zona/NOUNSG]],[sobre/PREP,[el/DETS
G,trabajo/NOUNSG]]]),que/QUE,se/SE,vg6([está/AUX]),realizando/VERBPR
P,. /SENT]

ERROR TYPE
1
2
3
4
5
6
7
8
9
10
DESCRIPTION
Sentence length is greater than 25 words (procedural sentences) or 30 words (descriptive sentences)
(Rule 6.1 & 7.1)
Number of words which are not in the STS general vocabulary or the terminology database
(Rule 1.1)
Sentence contains a passive construction
(Rule 4.3)
Sentence contains more than 3 attached prepositional phrases
(Rule 3.1)
Number of commands in the sentence is higher than one
(Rule 6.2)
A word has been used with an unapproved meaning
(Rule 1.2)
Inappropriate omission of an article or a demonstrative adjective
(Rule 2.1)
The verb tense used is illicit or the infinitive, past participle and/or gerund have been used with an unapproved value
(Rule 4.1)
An unapproved verbal periphrasis has been used
(Rule 4.2)
The subjunctive mood has been used
(Rule 4.3)

Appendix IX
12
13
11
A noun has been used to express an action, rather than a verb
(Rule 4.5)
The structures used between coordinated sentences differ
(Rule 5.3)
A list of more than two items occurs which should be a tabular layout
(Rule 9.1)
122

SENT. NO. 1 2 3 4 5
29
30
31
32
25
26
27
28
21
22
23
24
17
18
19
20
33
34
35
36
37
38
13
14
15
16
9
10
11
12
7
8
5
6
1
2
3
4
0 0 0 1 0
1 1 0 0 0
1 1 0 0 0
1 0 1 1 0
1 1 0 0 0
1 2 0 0 0
0 0 0 0 0
0 0 1 0 0
1 1 0 1 0
1 1 1 0 0
0 1 0 0 0
0 2 1 0 0
1 1 0 0 0
1 2 0 0 1
1 1 1 0 0
0 1 0 0 0
1 1 0 1 0
1 1 1 0 0
1 2 0 1 0
1 1 1 0 0
1 3 0 1 0
0 1 1 0 0
0 0 1 0 0
0 2 1 0 0
1 0 0 1 1
1 0 0 1 0
0 1 0 1 0
0 0 0 1 0
1 3 0 1 0
1 1 0 0 0
1 2 0 0 0
0 2 0 0 0
1 1 0 0 0
1 3 0 0 0
0 1 0 0 0
0 0 0 0 0
0 1 0 0 0
0 3 0 0 1
4 See Appendix IX for Error Code Descriptions.
NO. OF
REPORTED
ERRORS
5
2
3
2
2
1
3
2
5
2
1
3
3
3
4
3
1
0
2
4
1
4
3
1
2
4
1
3
3
3
0
1
2
3
1
2
2
3
2
1
2
2
5
2
1
3
3
3
3
2
3
1
2
3
NO. OF
CORRECTLY
REPORTED
ERRORS
1
2
2
3
1
2
3
3
0
1
1
3
1
0
2
4
1
3
5
2
3
2

Appendix X
43
44
45
46
39
40
41
42
47
48
49
50
TOTAL
RESULTS
0 2 0 0 0
1 0 0 0 0
0 1 0 0 0
0 1 0 0 0
0 2 0 0 0
1 0 0 0 1
0 0 0 0 0
0 1 0 0 0
0 1 0 0 0
0 2 0 0 0
0 1 0 0 0
0 0 0 0 0
24 55 10 11 4
0
1
2
2
2
1
1
1
1
2
1
0
104
0
1
2
1
2
1
1
1
1
2
1
0
96
124

SENT. NO. 1 2 3 4 5
29
30
31
32
25
26
27
28
21
22
23
24
17
18
19
20
33
34
35
36
37
38
13
14
15
16
9
10
11
12
7
8
5
6
1
2
3
4
0 0 0 0 0
1 0 0 0 1
0 0 0 0 1
0 0 0 0 1
1 0 0 0 1
1 1 0 0 1
1 0 0 0 0
0 0 0 0 0
0 2 0 0 0
0 2 0 0 0
0 1 0 0 0
0 0 0 1 0
0 0 0 0 0
0 0 0 0 0
0 0 0 0 1
1 0 0 0 1
1 0 0 0 0
1 0 0 0 0
0 0 0 1 0
0 0 0 0 0
1 0 0 0 0
1 0 0 0 0
0 0 0 0 0
0 1 0 0 1
0 0 0 0 1
0 0 0 1 0
0 1 0 0 0
1 0 0 0 0
0 0 0 0 1
1 0 0 0 1
0 0 0 0 1
1 0 0 0 1
1 1 0 0 1
1 1 0 0 1
0 0 0 0 1
0 0 0 0 1
0 0 0 0 1
0 0 0 0 0
5 See Appendix IX for Error Code Descriptions.
NO. OF
REPORTED
ERRORS
1
0
1
1
1
0
0
2
0
0
1
0
1
2
0
0
NO. OF
CORRECTLY
REPORTED
ERRORS
0
1
1
1
1
1
1
2
0
0
2
2
1
1
3
2
1
0
1
1
1
1
1
2
1
2
1
1
1
1
1
1
0
2
1
1
1
0
1
1
3
3
1
0
1
2
0
0
1
1
2
2
1
0
2
3
0
2
1
1

Appendix XI
43
44
45
46
39
40
41
42
47
48
49
50
0
0
0
0
0
0
0
0
1
0
0
0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
1 0 0 0
0 0 0 0
0 0 0 1
0 0 0 1
0 0 0 1
1 0 0 0
TOTAL
RESULTS 15 12 0 3 21
1
0
0
0
0
0
0
0
2
1
1
1
51
1
0
0
0
0
0
0
0
2
1
1
1
40
126

SENT. NO. 1 2 3 4 5
29
30
31
32
25
26
27
28
21
22
23
24
17
18
19
20
33
34
35
36
37
38
13
14
15
16
9
10
11
12
5
6
7
8
1
2
3
4
0 0 0 1 0
1 1 0 0 0
1 1 0 0 0
1 0 1 1 0
0 0 0 1 0
1 2 0 0 0
0 0 0 0 0
0 0 1 0 0
1 1 0 1 0
1 1 1 0 0
0 1 0 0 0
0 1 1 0 0
1 1 0 0 0
1 2 0 1 0
1 1 1 0 0
0 1 0 0 0
1 1 0 1 0
1 1 1 1 0
1 1 0 1 0
1 0 1 0 0
1 3 0 1 0
0 1 1 0 0
0 0 1 0 0
0 2 1 0 0
1 0 0 1 0
1 0 0 1 0
0 1 0 1 0
0 0 0 1 0
1 3 0 1 0
0 1 0 0 0
1 2 0 1 0
0 2 0 0 0
1
1
0
0
0
0
1
3
1
0
1
3
6 See Appendix IX for Error Code Descriptions.
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
TOTAL
NO. OF
ERRORS
4
2
5
1
2
2
2
1
5
2
1
3
3
4
3
2
2
4
1
1
1
3
3
1
2
4
1
2
3
3
1
3
0
1
1
2
2
3

Appendix XII
43
44
45
46
39
40
41
42
47
48
49
50
TOTAL
RESULTS
0 2 0 0 0
1 0 0 0 0
0 1 0 0 0
0 1 0 0 0
0 2 0 0 0
0 0 0 0 0
0 0 0 0 0
0 1 0 0 0
0 1 0 0 0
0 2 0 0 0
0 1 0 0 0
0 0 0 0 0
21 51 11 15 0
0
1
2
0
2
1
1
1
1
2
1
0
98
128

SENT. NO. 1 2 3 4 5
29
30
31
32
25
26
27
28
21
22
23
24
17
18
19
20
13
14
15
16
9
10
11
12
5
6
7
8
1
2
3
4
33
34
35
36
37
38
39
7 See Appendix IX for Error Code Descriptions .
0 0 0 0 0
0 0 0 0 1
0 0 0 0 1
0 0 0 0 1
1 0 0 0 1
1 0 0 0 1
0 0 0 0 0
0 0 0 0 0
0 1 0 0 0
0 2 0 0 0
0 1 0 0 0
0 0 0 1 0
0 0 0 0 0
0 0 0 0 0
0 0 0 0 1
1 0 0 0 1
0 0 0 0 0
0 0 0 0 0
0 0 0 1 0
0 0 0 1 0
1 0 0 0 0
0 0 0 0 0
0 0 0 0 0
0 1 0 0 1
0 0 0 0 1
0 0 0 1 0
0 1 0 0 1
0 0 0 0 0
0 0 0 0 1
0 0 0 0 1
0 0 0 0 1
0 0 0 0 1
1 1 0 0 1
1 0 0 0 1
0 0 0 0 1
0 0 0 0 1
0 0 0 0 1
0 0 0 0 0
0 0 0 0 0
1
2
0
1
2
1
0
0
1
1
0
1
0
1
2
0
1
1
2
1
0
0
1
1
1
3
2
1
1
0
0
1
2
0
TOTAL
NO. OF
ERRORS
0
1
2
1
1

Appendix XIII
44
45
46
47
40
41
42
43
48
49
50
TOTAL
RESULTS
0 0 0 1 0
0 0 0 0 0
0 0 0 0 0
0 0 0 0 0
0 0 0 0 0
0 1 0 0 0
0 0 0 0 0
1 0 0 0 1
0 0 0 0 1
0 0 0 0 1
0 0 0 0 0
8 10 3 9 27
0
2
0
1
1
0
0
0
1
1
0
42
130

18
19
20
21
14
15
16
17
22
23
SENTENCE
NO.
1
2
3
8
9
10
11
6
7
4
5
12
13
36
37
38
39
32
33
34
35
28
29
30
31
24
25
26
27
ERROR TYPES
8 See Appendix IX for Error Code Descriptions .
7, 8
8
10
7
7, 8
0
0
7, 11
0
8
8
8
0
8
0
8
8
8
0
0
12
7
8
8
8, 11
8, 10
0
6
8
8
0
11
8
7, 8
7
0
8
8
11
TOTAL NO. OF
ERRORS
1
1
1
1
1
0
1
0
1
1
1
0
0
0
2
2
0
1
1
2
1
0
1
1
1
1
0
2
0
1
2
1
1
0
1
2
1
1
1

Appendix XIV
44
45
46
47
40
41
42
43
48
49
50
TOTAL RESULTS
7
8
8
8
7
10
8
9
0
8
7
6, 7, 8, 9, 10, 11, 12
1
1
1
1
0
1
1
1
1
1
1
45
132

18
19
20
21
14
15
16
17
22
23
SENTENCE
NO.
1
2
3
8
9
10
11
6
7
4
5
12
13
36
37
38
39
32
33
34
35
28
29
30
31
24
25
26
27
ERROR TYPES
9 See Appendix IX for Error Code Descriptions .
0
0
0
13
0
0
0
0
0
0
0
0
7
0
7
13
0
0
0
8, 9
7, 8
0
7
0
0
10
0
0
0
7
7
0
0
0
7
10
0
0
0
TOTAL NO. OF
ERRORS
0
0
1
2
2
0
0
0
1
1
0
0
1
0
1
0
0
0
0
0
0
0
0
1
0
0
0
0
0
1
1
0
0
0
1
0
0
1
0

Appendix XV
44
45
46
47
40
41
42
43
48
49
50
TOTAL RESULTS
0
0
0
8
0
0
0
0
0
0
0
7. 8, 9, 10, 13
0
0
0
1
0
0
0
0
0
0
0
15
134

CLAW
CMT
CMU
CS
CSDG
CTE
CE
CFE
CGI
CL
CASL
CAT
CC
CCITT
CCL
ACE
AEA
AECMA
AIA
AMT
ATA
BMBC
BSEC
Attempto Controlled English
Association of European Airlines
Association Européenne des Constructeurs de Matériel Aérospatial
Aerospace Industries Association
(Machine translation system based on KANT technology)
Airline Transport Association
Boeing Meaning Based Checker
Boeing Simplified English Checker
Controlled Automotive Service Language
Computer Assisted Translation
Controlled Chinese
Consultative Committee for International Telegraph and Telephony
Centre for Computational Linguistics (Univ. of Leuven, Belgium)
Controlled English
Caterpillar Fundamental English
Carnegie Group, Inc.
Controlled Language, Computational Linguistics
Controlled Language Application Workshop
Center for Machine Translation
Carnegie Mellon University
Computer Science
Controlled Siemens Documentary German
Caterpillar Technical English

KBMT
KISL
LRE
LTG
MAHT
MCE
Appendix XVI
FAA
FR
GE
GIFAS
GM
GRAAL
GRIL
HTML
IR
KANT
DBMS
DFKI
DocSTEP
DTD
DTP
DWG
EC
EDMS
EGSC
136
DataBase Management System
Deutsches Forschungszentrum für Künstliche Intelligenz GmbH
Product Document Creation and Management using STEP
Document Type Definition
Desk Top Publishing
Document Working Group (of AECMA)
European Commission
Electronic Document Management System
Enhanced Grammar, Style, and Content Checker
Federal Aviation Administration (American)
Français Rationalisé
Global English
Groupment des Industries Françaises Aéronautique et Spatiales
General Motors
Reusable Grammars for Automatic Analysis of Languages
Language Industries Research Group
HyperText Markup Language
Interlingua Representation, Information Retrieval
Knowledge-based, Accurate Translation for Technical
Documentation
Knowledge-Based Machine Translation
Kodak International Service Language
Linguistic Research and Engineering
Language Technology Group, Human Communications Research
Centre, Univ. of Edingburgh
Machine-Assisted Human Translation
Multilingual Customised English

Appendix XVI
SEMG
SGML
SL
STS
TL
TMI
TSNLP
MLAP
MT
NL
NLG
NLP
PACE
SE
SEC
SECC
MultiLingual Action Plan
Machine Translation
Natural Language
Natural Language Generation
Natural Language Processing
Perkins Approved Clear English
Simplified English
Simplified English Checker
Simplified English Grammar and Style Checker/Corrector
Simplified English Maintenance Group (of AECMA)
Standard Generalized Markup Language
Source Language
Simplified Technical Spanish
Target Language
Theoretical and Methodological Issues in Machine Translation
Test Suites for NLP Applications
137

This appendix lists websites of organisations engaged in research related to controlled languages. Because work on controlled languages often involves the use of general tools and resources such as grammars, parsers and lexicons, we have also included references to some sites providing these.
SRI Artificial Intelligence Center NLP Program
Multimedia/Multimodal Interface Group
Spoken Language Systems Group
Written Language Systems Group http://wwwold.ai.sri.com/natural-language/
FASTUS Extraction tool
GEMINI parser/interpreter
ATIS airline information retrieval tool
TIPSTER
Command Talk, spoken language interface for military applications
Massive online publications library covering very broad range of linguistics and computation topics. Search on ‘extraction’ brings up 15 titles
Focus: tool and data development, standardization, and validation; seems to be focused on spoken corpora
Centre for Computational Linguistics – Katholieke Universiteit Leuven http://www.kuleuven.ac.be
Machine Translation: EUROTRA, METAL
Controlled Language: ALCOGRAM Controlled English Grammar, SECC Simplified
English Checker/Corrector
Publications: three publications on controlled language
Focus: language specifications and machine translation
University of Cambridge NLP Group http://www.cl.cam.ac.uk/Research/NL
Alvery Natural Language Tools include a morpohological analyser, parser, grammar, and

Appendix XVII 139 lexicon
Publications are numerous, across broad range of NLP subjects, no specific references under
‘tools’
Focus: more basic lexical and grammar-related research
Microsoft Research NLP Group http://research.microsoft.com
NL Analysis System
Controlled Language: MS Office Grammar Checker, Encarta IR system
Publications search on “ natural language” brings up 40 articles
Focus: tools for Microsoft products
Austrian Research Institute for Artificial Intelligence http://www.ai.univie.ac.at/oefai/nlu
Unification Grammar, HPSG Grammar for German, NL Generation, Computational morphology
Publications: minimal
Xerox Research Centre Europe http://www.xrce.xerox.com
Finite state algorithms, grammars (LFG), lexical sense disambiguation
Publications: fairly large library of publications covering broad range of linguistics and computing topics
Focus: generally more basic research than CL
Xerox Parc Research Center
Natural Language and Technology Group http://www2.parc.com/istl/groups/nltt
LinguistX (from InXight)
Controlled Language: Grammar Writer’ s Workbench for LFG
Xerox Linguistics Environment Project
Parallel Grammar Project
Publications numerous
Focus: theoretical and applied work on grammar formalisms, parsing, generation, and morphology

Appendix XVII
Carnegie Mellon Univ. Language Technologies Institute
(and Center for Machine Translation) http://www.lti.cs.cmu.edu
Numerous MT projects, past development of Caterpillar Controlled English
Controlled Language: Caterpillar Controlled English
Publications numerous
Focus: MT, past contributions to CLAW and other CL activities
DFKI – German Research Center for Artificial Intelligence http://www.dfki.uni-sb.de
FLAG Flexible Language and Grammar Checker
PAGE Platform for Advanced Grammar Engineering (core engine)
PERFECTION—NL Generation system
TG\2 NL Generation system
UNL Text Generation/MT System
VerbMobil—Speech-to-Speech System
Publications several hundred publications listed
Focus on applied projects, with interest in CL and special interest in generation
University of Edinburgh Human Communications Research Center
Language Technology Group http://www.ltg.ed.ac.uk
Range of projects in linguistics and computation
Controlled Language work: Intelligent Authoring Aids
Several publications specifically on CL, contributions to CLAW.
140