<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>From Specification to Standard: A Meta-Terminological Evolution in ASD-STE100 Issue 9</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Daniela Zambrini</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Orlando Chiarello</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Somma Lombardo</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Italy</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>The release of Issue 9 marks the transition of ASD-STE100 Simplified Technical English (STE) from specification to international standard. This paper outlines the key meta-terminological updates, focusing on user information needs, accessibility, and alignment with international terminological standards. The evolution of ASD-STE100 from its legacy to a more structured, user-centric standard is examined, drawing connections to the meta-terminology review conducted in the paper published in the proceedings of MDTT2023. The updates align with FAIR principles, enhancing both usability and interoperability across various industries. This paper focuses on the meta-terminological evolution in Issue 9, addressing challenges such as aligning legacy terminology with linguistic standards and simplifying complex terms for non-expert users, particularly technical writers who may not have a linguistic background. The updates, guided by input from the ASD Simplified Technical English Maintenance Group (STEMG) and STE National and Multi-Country Support Teams (STEST), aim to ensure that the standard remains practical and accessible.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Simplified Technical English</kwd>
        <kwd>ASD-STE100</kwd>
        <kwd>standard</kwd>
        <kwd>meta-terminology</kwd>
        <kwd>subject fields</kwd>
        <kwd>FAIR</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>As a controlled natural language (CNL), ASD-STE100 Simplified Technical English (STE) has
significantly influenced technical documentation, especially in the aerospace and defense sectors.
Its primary purpose is to simplify complex technical texts, ensuring clarity and consistency across
global communication platforms. Technical content written in STE is more accessible to a global
audience, especially non-native English speakers. This is achieved by providing specific rules for
grammar, style, and word usage, alongside a controlled dictionary of approved words.</p>
      <p>
        As technical communication continues to evolve, the need for standardization and alignment
with broader terminological frameworks has grown. Terminology standardization ensures that
both the immediate users (technical writers and translators) and the end users can access and
understand critical documentation with ease. This paper aims to highlight the meta-terminological
evolution in ASD-STE100 Issue 9, focusing on how the shift from specification to standard serves
the user community. This development also links directly to the meta-terminology review initiated
in 2022 and discussed in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <sec id="sec-2-1">
        <title>2.1. Overview of ASD-STE100</title>
        <p>
          ASD-STE100, established in the 1980s as AECMA Simplified English [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ], has grown in scope and
importance over the decades. Originally a Guide (until Issue 2 [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]), and later a Specification (until
Issue 8 [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]), it transitioned into a Standard with Issue 9 [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ].
        </p>
        <p>
          Although STE was initially created for the aerospace and defense sectors (for aircraft
maintenance manuals), it is now being adopted across an increasing range of industries (especially
in the railway, healthcare, automotive, and renewable energy sectors). These further industry
sectors recognize the advantages of using a controlled language to improve the clarity and quality
of their documentation, enhance safety, and support international communication. By minimizing
ambiguity—particularly for readers who are not native English speakers—STE's structured
methodology reduces the risk of human error and ensures that technical content remains clear,
consistent, and reliable. As a result, STE has become a valuable resource well beyond its original
scope. The copyright and trademark of the ASD-STE100 standard are fully owned by the
Aerospace, Security and Defense Industries Association of Europe (ASD) [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ].
        </p>
        <p>The ASD-STE100 document is divided into two parts: the writing rules and the dictionary. The
writing rules (53 rules in 9 sections) provide strict guidelines for grammar and style, while the
dictionary lists approved words and their meaning (in bold uppercase, 875 entries), in addition to
words that are not approved (in bold lowercase, approximately 1400 entries) and their related
approved alternatives, together with a total of approximately 3000 from existing technical
documentation. Special terms that are not included in the dictionary are categorized, depending on
their role in technical documentation and their related subject field. The main challenge with these
terms has been their inconsistency and the lack of alignment of meta-terminology with
contemporary terminological standards. As for legacy meta-terminology, the designations technical
name and technical verb had been historically used to designate such concepts outside the standard
dictionary. Issue 9 seeks to update and harmonize these designations and other terms with
linguistic standards, leading to greater clarity and usability.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Key findings from the 2023 study</title>
        <p>
          In [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], the authors explored the challenges in harmonizing legacy terminology and the possible
methods to be applied. Notably, the FAIR methodology was applied to categorize and standardize
terms related to specific domains or subject fields. The study focused on the subject field
classification, aiming to create a more structured approach.
        </p>
        <p>
</p>
        <p>Subject Field Classification: The 2023 study revealed that the existing subject field
categories were outdated and insufficient for modern technical communication needs. This
led to a proposal to refine these categories and adopt a more structured terminology
management approach. The study also highlighted the need for a structured subject field
classification system that would allow for easier integration of new terms as technical
fields continue to expand.</p>
        <p>
          FAIR Methodology: A critical aspect of this review was the adoption of the FAIR guiding
principles (Findable, Accessible, Interoperable, and Reusable) [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] to create concept entries
that would enhance the findability and reusability of terms in multiple contexts.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Meta-terminology in ASD-STE100 Issue 9</title>
      <sec id="sec-3-1">
        <title>3.1. Objectives of the review</title>
        <p>The meta-terminology review undertaken for Issue 9 was driven by two main goals:

</p>
        <p>Clarity and consistency: The main aim was to simplify and clarify the meta-terminology
used within the document and the technical terminology.</p>
        <p>Harmonization: One of the key findings was that while legacy technical terminology in the
ASD-STE100 document was useful, it lacked consistency with modern terminological
approaches. This led to the proposal of updating the designations technical name and
technical verb.</p>
        <p>The study also highlighted the need for a structured subject field classification system that
would allow for easier integration of new terms as technical fields continue to expand.</p>
        <p>The review also aimed to ensure that all changes would enhance the usability of the standard
without alienating its primary users — technical writers. These professionals, while highly skilled
in their respective fields, do not always have an academic background in linguistics. Thus, the goal
was to keep the changes simple and practical, avoiding overly complex lexicographic terminology
while ensuring that the terms were specific enough to meet the needs of technical documentation.</p>
        <p>
          The review process involved intense collaboration within the STEMG [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] and its seven STEST
[
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. Defining verb types and forms was particularly challenging, as it required balancing linguistic
precision with clarity for technical writers, who often lack formal linguistic training. The
introduction to the dictionary in Issue 9 now includes simple yet accurate definitions of the types
of approved verbs in the dictionary (regular, irregular, irregular auxiliary, and defective modal
verbs).
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Proposed changes</title>
        <p>
          A major change introduced in Issue 9 was the replacement of the term technical name with
technical noun (term), reflecting a shift toward a more standardized terminology approach. This
change was made to improve clarity and to better align with [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], which defines a term as a
“designation that represents a general concept by linguistic means”. This change helps remove
ambiguity, especially for non-expert users, as name could imply something different in a technical
context. Notably, term appears only in the definitions and explanatory text for Rules 1.5 and 1.12.
The addition of noun term in the explanatory text for the new designation emphasizes that while a
technical noun is a term, a term is not always a noun, as it can also include verbs (modification
similarly applied to the explanatory text for technical verbs: “A technical verb is a verb term that
refers to a specified concept or process and is applicable to a subject field.”)
        </p>
        <p>
          This clarification addresses a historical inconsistency in ASD-STE100, as analyzed in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], which
examined the evolution of technical terminology in the specification. In pre-release Issue 0 (1985),
the designation technical term was used for both nouns and other linguistic units, such as numbers
and symbols. However, in Issue 1 (1986), this was changed to technical name, a designation that
remained in use despite the expansion of the category to include abstract concepts, numbers, and
even adjectives for colors. Similarly, the classification for approved verbs outside the dictionary
evolved from manufacturing processes to technical verbs in Issue 1, Revision 2 (2001).
        </p>
        <p>
          While in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] the authors had proposed reinstating technical term as a more accurate alternative,
further deliberations—based on the final submitted Change Form that proposednoun-type term and
verb-type term—led to the adoption of technical noun and the reconfirmation of technical verb in
Issue 9. Furthermore, in the tekom Europe e.V. (European Association for Technical
Communication) terminology database for technical communication [11], technical term and
specialized term are explicitly labeled as not to be used.
        </p>
        <p>
          These meta-terminology changes followed ASD-STE100’s structured change proposal process,
where modifications must be submitted to the STEMG using a Change Form. Each Change Form
undergoes rigorous analysis and discussion during STEMG meetings before acceptance. If
approved, the change is incorporated into the next issue of the standard. The final Change Form
submitted by the authors (who are longstanding STEMG participants) proposed noun-type term and
verb-type term. However, other STEMG participants strongly advocated to retain the adjective
technical, despite the above-mentioned clear-cut definition of term in [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]. Therefore, the shift
from technical name to technical noun and the reconfirmation oftechnical verb in Issue 9 were the
outcomes of an extensive review and structured decision-making process. The final decision
ensures that ASD-STE100 maintains a clear distinction between noun-based and verb-based
controlled vocabulary, while still acknowledging the broader classification of terms within
terminology science.
        </p>
        <p>Other key changes included:

</p>
        <p>Streamlining of subject field categories: The review also resulted in a restructuring of
technical noun categories to make them more accessible and easier to navigate. For
example, new subject field categories, such asLaw and regulations and Animals, plants, and
other life forms have been added under Rule 1.5. A similar restructuring was also applied to
subject field categories for technical verbs in Rule 1.12.</p>
        <p>
          Updating of examples in the dictionary: Examples for the dictionary entries have been
revised to better represent contemporary technical fields, reducing the percentage of legacy
examples related to aerospace and defense (from 15% in [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ] to 3% in [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ]).
        </p>
        <p>These updates improve usability for a wider audience and ensure that terminology and
terminology management are accessible to users from multiple sectors.</p>
      </sec>
      <sec id="sec-3-3">
        <title>3.3. Challenges of the review process</title>
        <p>Defining English verb forms and tenses in a way that was both linguistically accurate and clear for
users sparked thought-provoking debates within the STEMG. These discussions centered around
finding the right balance between precision and usability.</p>
        <p>The challenge was to explain verb forms in a manner that was simple enough for technical
writers to understand and apply without needing an in-depth knowledge of linguistics.
Participants of the STEMG emphasized the importance of maintaining the spirit of ASD-STE100 by
ensuring that its rules remained straightforward and practical for technical writers. While
linguistic precision was considered, simplicity was prioritized to serve the needs of users.</p>
        <p>A further key decision in the review process was to keep the dictionary entry column
designation simple by using the term word instead of terms derived from lexicography, such as
headword or lemma, which have a higher linguistic register. This decision was based on the
understanding that the goal was not to create an academic resource but rather a practical guide for
those who rely on ASD-STE100 in their daily work, such as technical authors, translators, and
editors. Until Issue 7, the dictionary entry column was actually labeled keyword. This choice aligns
with STE’s purpose as a controlled language first and foremost for written technical
communication, not as an academic linguistic resource. While pronunciation is not covered in STE,
the dictionary does include usage examples with both STE and non-STE sentences to guide users.
Other elements of lexicography, such as etymology, are excluded as they are not essential for
technical authors. Regarding verb forms, only the approved inflections appear in dictionary entries.
Unlike general dictionaries, STE does not list true synonyms, adhering to its guiding principle of
"one word, one meaning, one part of speech." When an alternative is suggested, it is either a less
ambiguous synonym—even if not identical in meaning (e.g., “CAN (v)” instead of “MAY (v)”)—or a
word with a different part of speech that leads to a restructured sentence. Additionally, antonyms
are not included in the controlled dictionary, though they may be considered for future revisions
(the release of Issue 10 is scheduled for 2028). Phrasal verbs are strictly prohibited in STE under
Rule 9.3, which states that an approved verb and preposition must not be combined to create a new
phrase with a meaning different from its components. For example, “put out” (as in put out the fire)
introduces ambiguity, so STE requires the use of "extinguish" instead. Only a few phrasal verbs,
such as "put on" and "come on," are permitted with restricted meanings. Collocations are also
unnecessary, provided that the dictionary is used correctly. Finally, as per Rule 1.10, STE excludes
regional terms, slang, and jargon from technical noun usage, ensuring clarity and consistency
across industries</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. User-centric digital terminology design</title>
      <sec id="sec-4-1">
        <title>4.1. User information needs</title>
        <p>The meta-terminology review plays a crucial role in addressing user information needs by
enhancing accessibility and comprehension. By simplifying and standardizing meta-terminology,
Issue 9 makes it easier for technical writers — regardless of their linguistic expertise — to
understand and apply the writing rules consistently. This also aligns with user-centric design
principles, which advocate for designing documentation with the user's needs in mind. As the
standard becomes more accessible, the barrier to entry for non-expert users is lowered, making it
easier to adopt ASD-STE100 in a wide variety of fields.</p>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Terminological standards and harmonization</title>
        <p>
          Harmonization with related ISO standards [12] [13] is a significant aspect of in the review work
carried out for Issue 9. The new structure of technical nouns and technical verbs is not only
consistent with the definition ofterm in [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ] but also with the principles outlined in [14] and [15],
which cover the management of terminology resources.
        </p>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Technical communication and Natural Language Processing</title>
        <p>The improvements in the dictionary entry examples and in the subject field terminology categories
have implications for Natural Language Processing (NLP). These updates make it easier to
automate the processing and management of technical documentation, in particular of texts
written in a Controlled Natural Language. This could lead to more efficient NLP tools that assist
with terminology management, translation, and content generation.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusions and future work</title>
      <p>The harmonization of meta-terminology and the updating of the examples related to dictionary
entries in ASD-STE100 Issue 9 will have long-term benefits for the technical communication field.
Key areas for future work include:

</p>
      <p>Extending FAIR guiding principles: The next step is to further extend the FAIR
methodology [16] across additional domains, ensuring that terminology is standardized and
easily accessible for multiple industries.</p>
      <p>Collaborative tools: There is an opportunity to develop collaborative tools that integrate
with controlled natural languages, enabling real-time updates and collaboration in
terminology management.
</p>
      <p>Exploring AI integration: A task team composed of participants from the STEMG and the
STEST is exploring the potential of Artificial Intelligence (AI) for enhancing the
implementation of Simplified Technical English. Through collaborations with university
research projects, innovative AI-driven tools can be developed to streamline compliance
checks, provide real-time feedback, and automate the adaptation of terminological updates.
These efforts would further align STE with current and future technologies, increasing its
accessibility and usability across industries while promoting interoperability in multilingual
technical communication.</p>
      <p>The transition of ASD-STE100 from specification to standard significantly enhances the
accessibility, clarity, and consistency of the standard itself (for technical writers, the immediate
users) and of the resulting technical documentation (for the readers, the end users). The review of
the categorization of subject fields in Rules 1.5 and 1.12 of Issue 9 addresses the need for updated
terminology and aligns with the guidelines of international standards on technical communication
and terminology management, providing a user-focused design that serves a wide range of users.
The meta-terminology review ensures that ASD-STE100 continues to meet the needs of technical
communicators and supports ongoing development and collaboration in the field.</p>
    </sec>
    <sec id="sec-6">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the authors used ChatGPT-4o in order to: Draft the structure
of the content, paraphrase and reword, complete grammar and spelling checks. After using this
tool, the authors reviewed and edited the content as needed and take full responsibility for the
publication’s content.
[11] tekom Europe, Terminology of Technical Communication, URL:
https://tekom.termtechnologies.com/
[12] ISO 15188:2001 Project management guidelines for terminology standardization
[13] ISO 5127:2017 Information and documentation — Foundation and vocabulary
[14] ISO 12620-1:2022 Management of terminology resources — Data categories — Part 1:</p>
      <p>Specifications
[15] ISO/TS 24634:2024 Management of terminology resources — TermBase eXchange
(TBX)compliant representation of concept relations and subject fields
[16] F. Vezzani, Terminologie numérique: conception, représentation et gestion (p. 238). Peter Lang
International Academic Publishers, 2022</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Zambrini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Chiarello</surname>
          </string-name>
          ,
          <article-title>Subject fields in a Controlled Natural Language: how the evolution of the ASD-STE100 specification led to a proposal for a global structured review of term categories</article-title>
          ,
          <source>in: Proceedings of 2nd International Conference on Multilingual digital terminology today. Design, representation formats and management systems</source>
          , Lisbon, Portugal,
          <year>2023</year>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Association</given-names>
            <surname>Européenne des Constructeurs de Matériel Aérospatial</surname>
          </string-name>
          ,
          <article-title>AECMA Simplified English, Issue 1 - Guide for the preparation of aircraft maintenance documentation in the international aerospace maintenance language</article-title>
          ,
          <source>AECMA</source>
          , Paris, France ,
          <year>1986</year>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <article-title>[3] European Association of Aerospace Industries, AECMA Simplified English, Issue 2 - A guide for the preparation of aircraft maintenance documentation in the international aerospace maintenance language</article-title>
          , AECMA, Brussels, Belgium,
          <year>1995</year>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <article-title>[4] AeroSpace and Defence Industries Association of Europe, ASD-STE100 Simplified Technical English, Issue 8 - International specification for the preparation of technical documentation in a controlled language</article-title>
          ,
          <source>ASD</source>
          , Brussels, Belgium,
          <year>2021</year>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <article-title>[5] AeroSpace, Defence and Security Industries Association of Europe, ASD-STE100 Issue 9 - Simplified Technical English - Standard for technical documentation</article-title>
          , ASD, Brussels, Belgium,
          <year>2025</year>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <article-title>[6] AeroSpace, Defence and Security Industries Association of Europe, URL: www.asd-europe</article-title>
          .org
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Wilkinson</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dumontier</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aalbersberg</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          et al.
          <article-title>The FAIR Guiding Principles for scientific data management and stewardship</article-title>
          .
          <source>Sci Data</source>
          <volume>3</volume>
          ,
          <fpage>160018</fpage>
          <string-name>
            <surname>,</surname>
          </string-name>
          <fpage>2016</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>ASD</given-names>
            <surname>Simplified Technical English</surname>
          </string-name>
          Maintenance Group, URL: https://www.asd-ste100.org/ASD_STEMG.html
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>STE</given-names>
            <surname>Support</surname>
          </string-name>
          <string-name>
            <surname>Teams</surname>
          </string-name>
          , URL: https://www.asd-ste100.org/STEWorkingGroups.html
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          <source>[10] ISO</source>
          <volume>1087</volume>
          :
          <year>2019</year>
          <article-title>Terminology work and terminology science</article-title>
          .
          <source>Vocabulary</source>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>