TABLE OF CONTENTS

• General
• Supported Editor Applications
• Common Editor Setup (applies to all OEMs)
  • Schema-Based Authoring
  • Properties Panel (Attributes & Metadata)
  • Elements Panel (Structured Insertion)
  • Shared Editor Capabilities Across All OEMs
• OEM-Specifics
  • Airbus FlightOps
  • ATR Edora
  • Boeing FTID

General

Yonder provides OEM-specific editor applications tailored to the documentation standards of different aircraft manufacturers.
 Each editor ensures authors work with the correct structure, rules, and UI behavior required by the respective OEM.

This page explains how the different editor applications are organized and how OEM-specific behavior is configured, at a conceptual level.

Supported Editor Applications

Yonder currently provides dedicated editors for:

• Airbus FlightOps
• ATR Edora
• Boeing FTID

Each editor is a separate application but follows the same overall setup and user experience principles.

Common Editor Setup (applies to all OEMs)

All OEM editors share the same foundation:

• Same core editor UI and behavior
• Same set of standard features (e.g. spell check, find & replace, tables, XML view)
• Same concepts for inserting elements and editing properties

OEM-specific differences are handled through configuration, not through different user workflows.

Schema-Based Authoring

Each editor is driven by the OEM’s official XML schemas:

• OEM schemas define which elements, attributes, and structures are allowed
• Yonder extends these schemas where needed to support platform-specific requirements
• Different module types (e.g. description, procedure) are supported within the same editor

From a user perspective:

• You only see valid structures
• Invalid insertions are prevented automatically
• Available actions always match the selected content

Properties Panel (Attributes & Metadata)

Each OEM editor provides a Properties Panel that:

• Displays metadata relevant to the selected element
• Uses dropdowns, text fields, and controlled values
• Shows only attributes that are meaningful for the current element and OEM

The panel adapts automatically depending on:

• The selected element
• The active OEM schema

Elements Panel (Structured Insertion)

The Elements Panel is configured per OEM to:

• Show only elements that are valid in the current context
• Respect OEM-specific structure rules
• Offer consistent insertion options (Here, Above, Below, Replace)

Even though the schemas differ, the authoring experience remains consistent across OEMs.

Shared Editor Capabilities Across All OEMs

All OEM editors include:

• Structured document editing (no raw XML editing required)
• Context-sensitive toolbars and menus
• Real-time validation
• Spell checker and special characters
• Table editing
• XML source view (read-only)
• Find & replace
• Auto-save and manual save

Key Takeaway

Although Airbus, ATR, and Boeing editors are based on different schemas, they all:

• Look and behave the same from a user perspective
• Enforce OEM-specific rules automatically
• Provide a guided, error-resistant authoring experience

Authors do not need to understand schemas or configurations — the editor ensures correctness by design.

OEM-Specifics

Airbus FlightOps

• Uses Airbus-provided DTDs extended for Yonder
• Supports multiple module types within one editor
• Properties Panel and Elements Panel are fully schema-driven
• Editor behavior strictly enforces Airbus authoring rules

From an author’s perspective:

• Airbus terminology and element names are used consistently
• Only Airbus-approved structures are available

ATR Edora

• Uses ATR-provided schemas with Yonder extensions
• Authoring experience mirrors Airbus and Boeing editors
• Same panels, toolbars, and workflows apply

Differences are limited to:

• Schema rules
• Attribute definitions
• Available elements

Boeing FTID

• Uses Boeing schemas extended by Yonder
• Supports Boeing-specific concepts such as aircraft effectivity
• Includes additional internal representations for better structure visibility

For authors:

• Boeing-specific rules are enforced automatically
• Aircraft-related structures behave consistently throughout the editor