0% found this document useful (0 votes)

33 views445 pages

Task Card Standard Generalized Markup Language Technical Guide

The TC SGML Technical Guide is a comprehensive document detailing the Task Card Standard Generalized Markup Language for various Boeing aircraft models, with the latest revision being 26 as of January 2021. It includes information on export control regulations and provides a change record highlighting updates made in this revision. The document is prepared and controlled by the Digital Technical Data Support team and is intended for internal use within Boeing.

Uploaded by

Jivendra Kumar

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

33 views445 pages

Task Card Standard Generalized Markup Language Technical Guide

Uploaded by

Jivendra Kumar

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 445

TC SGML Technical Guide

Task Card Standard Generalized Markup

Language Technical Guide

Models: 717, 737-300/400/500, 737-600/700/800/900,

737-7/8/8200/9/10, 747-400, 747-8, 757, 767, 777-200/300, 777-8/9,
MD10, MD11, MD80, MD90, P-8
Copyright © 2021 The Boeing Company
All Rights Reserved

NOTE: This is revision 26 of the Task Card SGML Technical Guide.

This Technical Guide has been developed to the TCBOE DTD, version
19, level 4 dated October 3, 2014.
(-//BOEING//DTD TASKCARD-BOEING-VER19-LEVEL4//EN)

ECCN: 9E991

Export of this technology is controlled under the United States Export Administration Regula-
tions (EAR) (15CFR 300-774). An export license may be required before it is used for develop-
ment, production or use by foreign persons from specific countries. The controller of this data has
the individual responsibility to abide by all export laws.

For questions please contact the Information Data Architecture and Test (IDAT) group, by creating a
Service Request (SR) through MyBoeingFleet (MBF). Select the following fields: Product Type =
Digital Data Support
Product Line = (appropriate model option) and
Product = SGML

Rev #26 01/13/21 D6-82973

Page -1
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE: Task Card SGML Technical Guide

THIS DOCUMENT IS
CONTROLLED BY: Digital Technical Data Support (T5C0)

ALL REVISIONS TO THIS DOCUMENT SHALL BE APROVED BY THE SIGNATORIES

PRIOR TO RELEASE.

PREPARED ON: Adobe FrameMaker+SGML 7.0

PREPARED BY: Jowene Prouty-Black

FILED UNDER: \\NW\data\Technical_Guides\

ORIGINAL RELEASE DATE: January 29, 2003

REVIEWED BY: Joshua Bink T5B0 12 January 2021

Joshua Bink Org. Number Date

APPROVED BY: Warley Brown T5C0 12 January 2021

Warley Brown Org. Number Date

Rev #26 01/13/21 D6-82973

Page -2
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CHANGE RECORD

1.0 This section defines the detailed CR changes incorporated for Revision 26.

Affected Element/
Page Change Description

ALL pages Updated revision level from 25 to 26.

cover page 1. Changed revision level from 25 to 26.

2. Updated copyright from 2020 to 2021.
3. Added 777-8/9 to the model list.
signature page 1. Updated “Reviewed By” from Gary Wong to Joshua Bink.
2. Updated “Reviewed By” and “Approved By” dates.

entrty Updated wording in section 1.2.5.b.

revst_revend 1. Updated example in section 1.3.3.

2. Added new section 1.3.4 with an example of a numbering change.
3. Added new section 1.3.5 with an example of an element who’s
attributes were revised.
4. Updated Boeing Application Rules 1.4f and 1.4g.

Rev #26 01/13/21 D6-82973

Page -3
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

Table of Contents

Organization of this Guide

All elements represented in the Task Card DTD are documented individually to
explain how Boeing tags the data that pertains to the element. The documentation for
each element is organized into sections. Below is a description of the type of
information contained in each of those sections.

1.0 ELEMENT NAME

Section 1.0 provides the element that is represented in the Task Card DTD and its full
name. For example:
Section 1.0 ELEMENT NAME
graphic - GRAPHIC

Element Full Name

1.1 ELEMENT CONTENT

Section 1.1 provides a snapshot of how the element is represented in the DTD,
followed by a description of the element. For example:
Section 1.1 ELEMENT CONTENT
<!ELEMENT task- - ( effect, title, %g.r;, regulatory*
Snapshot of DTD %w.c;, note*, tfmatr?, topic*,
graphic* ) >

The task element identifies a task (prime AMTOSS division). A task tag only covers one
configuration of a task, e.g., task 29-11-53-400-802 and task 29-11-53-400-803 may be two
Element Description configurations of tasks that perform the same action. They are separately identified with two different
task tags. The task element appears in the context of the following elements

ENTITY ELEMENT
task

Rev #26 01/13/21 D6-82973

Page -8
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

INTRODUCTION

1.2 ATTRIBUTE MARKUP RULES

Section 1.2 provides the ATA DTD snapshot of any attributes the element might have.
It also includes a table which describes how Boeing supports each attribute. Following
the table is the definition for each attribute, and any specific Boeing specifications that
were applied. For example:

Section 1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT task - - ( effect, title, %g.r;, regulatory*
%w.c;, note*, tfmatr?, topic*,
graphic* ) >
<!ATTLIST task
chappref CDATA #IMPLIED
chapnbr NUMBER #REQUIRED
sectnbr NUMBER #REQUIRED
subjnbr NUMBER #REQUIRED
Snapshot of DTD func CDATA #REQUIRED
seq CDATA #REQUIRED
confltr CDATA #IMPLIED
varnbr NUMBER #IMPLIED
alunqi CDATA #IMPLIED
pgblknbr NUMBER #IMPLIED
confnbr NUMBER #IMPLIED
id ID #REQUIRED >

Attribute Name Always Provided When

Provided Data is Available

chappref X

chapnbr X

sectnbr X
Table Showing
Boeing’s Application subjnbr X
of Attributes func X

seq X

confltr X

varnbr X

alunqi X

pgblknbr X

confnbr X

id X

Rev #26 01/13/21 D6-82973

Page -9
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

INTRODUCTION

SubSection 1.2.1 Attribute: chapnbr

Attribute Definition Description: Chapter Prefix (chappref) is a unique identifier for chapters with multiple types.
This identifier is used with the amtoss numbering scheme as defined in the ATA Spec 2200.
(XX-xx-xx-xx-xxx-xxx-xxx-xxx).

Boeing Specifications/ Boeing Application Rules:

Application Rules 1. chappref is an implied attribute, therefore it will be supplied in the eMOD data on a best
effort basis.

1.3 ELEMENT CONTEXT MARKUP RULES

Section 1.3 describes all the structures in which elements can occur. Included are
examples of the printed data, followed by the SGML source. When an element has no
examples available, section 1.3 will not be supplied. For example:

Section 1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the Task Card.
Each example begins with a sample of the printed data, followed by an example of the SGML
markup, if available.

SubSection 1.3.1 Element: tcbody

<!ELEMENT tcbody - - (tccat?, taskproc?, mpditem*,
pretsmry?, hazmtlst?, (task* | refext*))>

Printed Example:
Functionally check the Lower Lobe Attendant Rest (LLAR) Back-
up Lighting System Battery Pack for proper capacity (perform
time loading test).

Printed Example INTERVAL NOTE:

TASK 05-00-01-800-801
1. Recording and Control of the Lives of Parts
A. The following equipment is used to record and control the lives
of parts.

SUBTASK 05-00-01-861-001
(1) Standard Equipment
(a) Vibro-engraving tool.

Rev #26 01/13/21 D6-82973

Page -10
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

INTRODUCTION

SGML:
<tcbody>
<taskproc>
<para>Functionally check the Lower Lobe Attendant Rest (LLAR) Back-up LIghting System Battery
Pack for proper capacity (perform tim
e loading test).</para>
</taskproc>
<mpditem>
<mpdnbr>05-002-00</mpdnbr>
<taskloc>EXTERNAL</taskloc>
<linspect>DETAILED</linspect>
SGML Markup <title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<taskdesc>
<para>Functionally check the Lower Lobe Attendant Rest (LLAR) Back-up LIghting System Battery
Pack for proper capacity (perform tim
e loading test).</para>
</taskdesc>
<supldata>
<manhours>1.00</manhours>
<nbrpeopl>1</nbrpeopl>
<elaptime>1.00</elaptime>
</supldata>
</mpditem>
<task chapnbr="05" sectnbr="00" subjnbr="01" func="800" seq="801" pgblknbr="6"
id="C479BB14E26BAED29CD99745897CDE86">
<effect effrg="475999" efftext="ZAP ALL">
</effect>

1.4 BOEING IMPLEMENTATION RULES

Section 1.4 describes how elements and attributes will be implemented.

Example:
a. chg=“N” - implies that this is the first time the anchor has been sent to the
customer. Revision date is the manual revision date.
b. chg=“R” - Revision date is the manual revision date.

Rev #26 01/13/21 D6-82973

Page -11
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%DELETED

1.0 ENTITY NAME

%deleted - Deleted

Refer to the deleted and chgdesc elements for the markup rule requirements for
the %deleted entity.

1.1 ENTITY CONTENT

<!ENTITY % deleted "(deleted, chgdesc*)" >

The %deleted entity contains all elements associated with deleted anchors. This entity
includes the elements for—
• deleted - marks the SGML anchor (element) from which data has been deleted.
• chgdesc - Gives the reason for a revision within an anchor or other element.

The elements of the entity %deleted appears in the context of the following element:

ELEMENT

taskcard

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -12
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%G.R

1.0 ENTITY NAME

%g.r - Graphic and Text References

Refer to the refblock, grphcref, refext or refint elements for the markup rule
requirements for the %g.r entity.

1.1 ENTITY CONTENT

<!ENTITY % g.r "(refblock* | (grphcref*, refext*,
refint*))" >

The %g.r entity contains the required DTD structure for a complete text or graphic
reference. This entity includes the elements for—

• Reference block (refblock) is the structure that contains internal and external
references to graphics.
• Graphic reference (grphcref) is the text that describes the referenced material.
• External reference (refext) refers to text or graphics in another manual or
document instance.
• Internal Reference (refint) refers to text elements within a document.

The %g.r entity appears in the context of the following elements:

ELEMENT

task

topic

subtask

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -13
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%REVATT

1.0 ENTITY NAME

%revatt - Revision Attributes

1.1 ENTITY CONTENT

<!ENTITY % revatt
"chg (N|R|U|D) #REQUIRED
key ID #REQUIRED
revdate NUMBER #IMPLIED" >

The entity %revatt contains the group of attributes needed for sending revision
information for incremental updates or a complete re-issue of a manual with revisions.
The revision attributes are applied to each anchor:

ELEMENT

legalntc
taskcard

Revision markup for a non-customized book reflects changes since the last time the
book was published, whether or not a particular customer received the previous issue.
If, for example, an element is unchanged from one revision to the next, the CHG
attribute will have a value of “U”.

NOTE: When an element is marked as unchanged, the REVDATE attribute will

reflect the last time that element was revised.

Revision markup for a customized book reflects all changes since the previous time
the customer received the book. In other words, each new issue received by the
customer becomes the new baseline for that customer’s next issue.

Rev #26 01/13/21 D6-82973

Page -14
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%REVATT

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ENTITY % revatt
"chg (N|R|U|D) #REQUIRED
key ID #REQUIRED
revdate NUMBER #IMPLIED" >

Attribute Name Always Provided Provided When Data

is Available
chg X

key X

revdate X

1.2.1 Attribute: chg

Description: Change attribute values can be:
• N - new anchor. The new anchor must be placed according to the instructions for
inserts.
• D - deleted anchor. Indicates that the anchor designated by the key attribute value is
deleted. If the entire parent anchor is deleted, then its entire content model is
replaced with %deleted.
• R - revised anchor. Indicates that the anchor designated by the key attribute value is
revised. “R” is applicable when anchor content has been changed. “R” is also
applicable when some specific attributes have been changed or in cases where the
process identifies additional changes between the previous and current instance. For
these conditions chg=“R” is supplied but the revision date remains unchanged
(i.e.; the revision date is not the manual revision date).
• U - unchanged anchor. Indicates that the anchor content is unchanged from the last
scheduled revision.

ATA chg attribute assignment rule: All change (chg) attribute values will be assigned
based on the previous scheduled revision.

Boeing Application Rule:

a. The chg attribute will not roll up or down in the anchoring hierarchy of the
document when the data content is changed. However, if an entire anchor is
deleted, then the content model of the anchor shall be replaced with %deleted and
none of the “child anchors” will be supplied.

Rev #26 01/13/21 D6-82973

Page -15
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%REVATT

1.2.2 Attribute: key

Description: The value of the attribute key must:
• be unique within a document.
• never be re-used. ATA guidelines state that the value of the KEY attribute may
never be re-used for different data if the anchor has been deleted. Note, however,
that when an anchor is deleted from a document instance due to effectivity
processing in eMOD, it can be restored by a change in effectivity. In this case, it will
retain its original KEY= value.
• be assigned on creation of the anchor.
• start with an alpha character.
• be assigned by only one institution. Only a data creator will assign the key. If a data
receiver is sending data back to the data producer, and the data receiver is creating
the data, a unique key must be created by adding the three digit ICAO airline code to
the beginning of the key.

1.2.3 Attribute: revdate

Description:
• An attribute REVDATE is associated to each anchor and defines the last revision
date for the anchor.
• For initial issue of a document, the revision date is the manual revision date.
• Revision date should not change if only the “chg” attribute value of the anchor has
changed from “R” to “U”.
• chg=“R” - Revision date is the manual revision date, except in cases where the
process identifies additional changes between the previous and current instance.
For these conditions chg=“R” is supplied but the revision date remains unchanged
(i.e.; the revision date is not the manual revision date).

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -16
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%REVATT

1.3.1 Element: legalntc

<!ELEMENT legalntc - - (exprtcl | cpyrght | proptary | geninfo)+>
<!ATTLIST legalntc
%revatt; >

LEGALNTC - %REVATT Rules

Change Original Sched Increv Usage

Value Issue Rev
“N” X Occurs only on original issue.

“R” X Occurs when data within the Legal Notice is changed.

Occurs on all other issues of the manual.

“D” X Occurs when the legalntc is deleted.

“U” X Occurs when legalntc contents are unchanged.

Printed Example:

Reference the legalntc element for examples of the printed text.

SGML:

Reference the legalntc element for examples of the SGML.

1.3.2 Element: taskcard

TASKCARD -- %REVATT Rules

Change Original Sched Increv Usage

Value Issue Rev

“N” X Occurs only on original issue.

“R” X Occurs when data within the taskcard is changed.

“D” X Occurs when the taskcard is deleted.

“U” X Occurs when taskcard contents are unchanged.

Rev #26 01/13/21 D6-82973

Page -17
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%REVATT

Printed Example:

Reference the taskcard element for examples of the printed text.

SGML:

Reference the taskcard element for examples of the SGML.

1.4 BOEING IMPLEMENTATION RULES

a. chg=“N” - implies that this is the first time the anchor element has been sent to the
customer. Revision date is the manual revision date.
b. chg=“R” - Revision date is the manual revision date.
c. chg=“D” - Revision date is the manual revision date.
d. chg=“U” - The revision date is the last scheduled revision date greater than or
equal to the date the anchor element was first sent to the customer.
e. ATA guidelines state that the value of the KEY attribute may never be re-used for
different data if the anchor has been deleted. Note, however, that when an anchor is
deleted from a document instance due to effectivity processing in eMOD, it can be
restored by a change in effectivity. In this case, it will retain its original KEY=
value.
f. Values for the KEY attribute have the form “T” followed by up to 10 alpha
numeric values, as in “T0000012345”.
g. Values for the REVDATE attribute have the form “YYYYMMDD”.
h. The supported values for the CHG attribute are “N”, “R”, “U” and “D”.
i. If an anchor is new or deleted, its parent anchor will be marked as revised
(CHG=“R”), and will contain the appropriate <revst> and <revend> tags.
j. Per ATA rules, the CHG attribute does not propagate upwards or downwards in the
document’s anchor hierarchy when content is changed; however, if a child anchor
is added or deleted, the parent anchor’s change attribute marked as revised (i.e.,
CHG=“R”).
k. An anchor’s revision attributes will be updated under any of the following
conditions:
• when a non-anchor child is revised (e.g., when the title changes)
• when one or more of the anchor’s child anchors are added or deleted.

Rev #26 01/13/21 D6-82973

Page -18
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%TEXT

1.0 ENTITY NAME

%text - Text Structures of an Element

Refer to the para, table, unlist, numlist and note elements for the markup rule
requirements for the %text entity.

1.1 ENTITY CONTENT

<!ENTITY % text "(para | note | table | unlist
| numlist)+" >

The entity %text contains structures commonly found in the text of an element:
• paragraph (para) -- a set of sentences presented as one block of information.
• note -- used to identify a “note.”
• table -- a group of information defined as entries.
• unnumbered list (unlist) -- a list of information in which items are not numbered
(ordered).
• numbered list (numlist) -- a list of information in which items are numbered
(ordered).

The entity %text appears in the context of the following elements:

ELEMENT

intnote
apapnote

eappnote

acpanote

taskproc

taskdesc

pretopic

warning

caution

note
entry

l1item - l7item

ftnote

Rev #26 01/13/21 D6-82973

Page -19
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%TEXT

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -20
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%W.C

1.0 ENTITY NAME

%w.c - Warnings and Cautions

Refer to the warning and caution elements for the markup rule requirements for
the %w.c entity.

1.1 ENTITY CONTENT

<!ENTITY % w.c "(warning*, caution*)" >

The entity %w.c contains the required DTD structure for a Warning and Caution. The
Warning and Caution elements are grouped together because, if they both exist,
Warning must always come before Caution.
• warning -- this element is used to identify a “warning”
(ATA Spec. 2200 definition: A warning calls attention to required
procedures/limits for avoiding personal injury)
• caution -- this element is used to identify a “caution”.
(ATA Spec. 2200 definition: A caution calls attention to required
procedures for avoiding damage to equipment)

The entity %w.c appears in the context of the following elements:

ELEMENT

task

topic

subtask

entry

l1item - l7item

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -21
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

%YESORNO

1.0 ENTITY NAME

%yesorno - Yes or No Choice

Refer to the grphcref, toc, table, tgroup, colspec, spanspec, row, and entry elements
for the markup rule requirements for the %yesorno entity.

1.1 ENTITY CONTENT

<!ENTITY % yesorno "NUMBER" >

This entity displays a value of either “1” or “0” [“1” meaning “yes” (on), “0” meaning
“no” (off)].

For example: Column Separators (colsep) and Row Separators (rowsep) in tables may
either be (on) or (off). The %yesorno entity value on the attributes colsep and rowsep
would then be either “1” or “0”.

The %yesorno entity appears in the context of the following elements:

ELEMENT

grphcref

table

tgroup

colspec

spanspec

row

entry

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -22
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ACDATA

1.0 ELEMENT NAME

acdata - Access Panel Data

1.1 ELEMENT CONTENT

<!ELEMENT acdata - - (acpan*, acpanote*) >

The acdata element defines the list of access panels and their accompanying note. The
acdata element appears in the context of the following elements:

ELEMENT

mainhead

cchead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -23
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ACDATA

1.3.1 Element: mainhead

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -24
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ACDATA

1.3.2 Element: cchead

<!ELEMENT cchead - - (skill+, workarea+, reltask*, specnote?,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

SGML:
<taskcard cardnbr="07-007-00-01" mprog="RAR" chg="N" key="T0000018580">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<cchead>
<skill>ELEC</skill>
<workarea>LWR FUSELAGE</workarea>
• • •
<acdata>
<acpan>114AC</acpan>
<acpanote>
<para>This is an access note.</para>
</acpanote>
</acdata>
</cchead>

Rev #26 01/13/21 D6-82973

Page -25
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ACPAN

1.0 ELEMENT NAME

acpan - Access Panels

1.1 ELEMENT CONTENT

<!ELEMENT acpan - - (#PCDATA) >

The acpan element defines the list of access panels and synthetic access to be opened
or removed in order to perform the task. The acpan element appears in the context of
the following element:

ELEMENT

acdata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -26
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ACPAN

1.3.1 Element: acdata

<!ELEMENT acdata - - (acpan*, acpanote*) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -27
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ACPANOTE

1.0 ELEMENT NAME

acpanote - Access Panel or Synthetic Access Note

1.1 ELEMENT CONTENT

<!ELEMENT acpanote - - (%text;) >

The acpanote element defines the access panel or synthetic access note which
accompanies the access panel. The acpanote element appears in the context of the
acdata element.

ELEMENT

acdata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -28
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ACPANOTE

1.3.1 Element: acdata

<!ELEMENT acdata - - (acpan*, acpanote*) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -29
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

AMMREF

1.0 ELEMENT NAME

ammref - Reference to the AMM

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT ammref - - (refblock, trnbr?) >

The ammref element defines reference to the AMM within TRs. The ammref element
appears in the context of the following element.

ELEMENT

taskcard

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -30
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

APAPDATA

1.0 ELEMENT NAME

apapdata - Airplane Applicability Data

1.1 ELEMENT CONTENT

<!ELEMENT apapdata - - (apapplic*, apapnote*) >

The apapdata element is the list of airplane applicabilities and their accompanying
notes. The apapdata element appears in the context of the following elements:

ELEMENT

mainhead

cchead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -31
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

APAPDATA

1.3.1 Element: mainhead

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<mainhead>
<source>MRB</source>
<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
• • •
<tasktype>DETAILED</tasktype>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<apapdata>
<apapplic>200</apapplic>
</apapdata>
<enapdata>
<engappl>715B1</engappl>
</enapdata>
<zone>100</zone>
<acdata>
<acpan>110AL</acpan>
</acdata>
</mainhead>

Rev #26 01/13/21 D6-82973

Page -32
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

APAPDATA

1.3.2 Element: cchead

<!ELEMENT cchead - - (skill+, workarea+, reltask*, specnote?,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

SGML:
<taskcard cardnbr="06-005-00-01" mprog="RAR" chg="N" key="T0000017831">
<effect effrg="001999" efftext="ZAP ALL"> effrg="001999">
</effect>
<cchead>
<skill>ELEC</skill>
<workarea>LWR FUSELAGE</workarea>
<tasktype>REPLACE</tasktype>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<apapdata>
<apapplic>ALL</apapplic>
<apapnote>
<para>Airplanes with Lower Lobe Attendant Rest installed.</para>
</apapnote>
</apapdata>
<enapdata>
<engappl>ALL</engappl>
</enapdata>
<zone>120</zone>
</cchead>

Rev #26 01/13/21 D6-82973

Page -33
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

APAPNOTE

1.0 ELEMENT NAME

apapnote - Airplane Applicability Note

1.1 ELEMENT CONTENT

<!ELEMENT apapnote - - (%text;) >

The apapnote element is the airplane applicability note. The apapnote element appears
in the context of the following element.

ELEMENT

apapdata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -34
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

APAPNOTE

1.3.1 Element: apapdata

<!ELEMENT apapdata - - (apapplic*, apapnote*) >

Printed Example:

SGML:
<taskcard cardnbr="06-005-00-01" mprog="RAR" chg="N" key="T0000017831">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<cchead>
<skill>ELEC</skill>
<workarea>LWR FUSELAGE</workarea>
<tasktype>REPLACE</tasktype>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<apapdata>
<apapplic>ALL</apapplic>
<apapnote>
<para>Airplanes with Lower Lobe Attendant Rest installed.</para>
</apapnote>
</apapdata>
<enapdata>
<engappl>ALL</engappl>
</enapdata>
<zone>120</zone>
</cchead>

Rev #26 01/13/21 D6-82973

Page -35
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

APAPPLIC

1.0 ELEMENT NAME

apapplic - Airplane Applicability

1.1 ELEMENT CONTENT

<!ELEMENT apapplic - - (#PCDATA) >

The apapplic element is the general reference to the applicable airplane model. The
apapplic element appears in the context of the following element.

ELEMENT

apapdata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -36
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

APAPPLIC

1.3.1 Element: apapdata

<!ELEMENT apapdata - - (apapplic*, apapnote*) >

NOTE: Examples of apapplic are: ALL, 200, 300, 2IGW.

Printed Example:

SGML:
<taskcard cardnbr="06-005-00-01" mprog="RAR" chg="N" key="T0000017831">
<effect effrg="001999">
</effect>
<cchead>
<skill>ELEC</skill>
<workarea>LWR FUSELAGE</workarea>
<tasktype>REPLACE</tasktype>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<apapdata>
<apapplic>ALL</apapplic>
<apapnote>
<para>Airplanes with Lower Lobe Attendant Rest installed.</para>
</apapnote>
</apapdata>
<enapdata>
<engappl>ALL</engappl>
</enapdata>
<zone>120</zone>
</cchead>

Rev #26 01/13/21 D6-82973

Page -37
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

AWLIMIT

1.0 ELEMENT NAME

awlimit - Airworthiness Limitation

1.1 ELEMENT CONTENT

<!ELEMENT awlimit - - (#PCDATA) >

The awlimit element identifies a phrase in a fatigue task card that indicates there is an
airworthiness limitation requirement against the task. The awlimit element appears in
the context of the following element.

ELEMENT

mpditem

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -38
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

AWLIMIT

1.3.1 Element: mpditem

<!ELEMENT mpditem - - (mpdnbr, taskloc?, linspect?, title?,
taskdesc?, ch5tskno?, awlimit?,
supldata) >

Printed Example: The mpditem information does not appear on the printed taskcard.

SGML:
<taskcard cardnbr="06-001-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000017823">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
. . .
<mpditem>
<mpdnbr>06-001-00</mpdnbr>
<taskloc>EXTERNAL</taskloc>
<linspect>GENERAL VISUAL</linspect>
<title>test</title>
<taskdesc>
<para>Even more testing</para>
</taskdesc>
<awlimit>AIRWORTHINESS LIMITATION</awlimit>
<supldata>
<manhours>5.00</manhours>
<nbrpeopl>2</nbrpeopl>
<elaptime>2.50</elaptime>
</supldata>
</mpditem>

Rev #26 01/13/21 D6-82973

Page -39
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CAUTION

1.0 ELEMENT NAME

caution - Caution

1.1 ELEMENT CONTENT

<!ELEMENT caution - - (%text;) -(note) +(effect) >

The caution element is used to identify a “CAUTION.” According to the

ATA Specification 2200 Warnings, Cautions, and Notes shall be applied as follows:

These adjuncts to the text shall be used to highlight or emphasize important points
when necessary.
• Warnings call attention to use of materials, processes, methods, procedures, or
limits which must be followed precisely to avoid injury to persons.
• Cautions call attention to methods and procedures which must be followed to
avoid damage to equipment.
• Notes call attention to methods which make the job easier.
• Warnings and cautions shall be located directly above the text to which they
relate and vertically in line with the numerical or alphabetical breakdown of the
steps to which they apply.
• Notes shall follow the text to which they relate and be located directly under and
vertically in line with the text to which they apply.
• Warnings, cautions and notes shall always be on the same page as the text to
which they apply.

All notes shall be in upper and lower case letters and preceded by the word NOTE in
caps and underlined.

Example: NOTE: It is not necessary to relieve pressure.

All cautions shall be printed in capital letters throughout and is preceded with the word
CAUTION in capital letters and underlined.

Example: CAUTION: DO NOT OPERATE CONTROLS.

All warnings shall be printed in capital letters and boldface throughout and is preceded
with the word WARNING in bold capital letters and underlined.

Example: WARNING: SOLUTION IS EXTREMELY FLAMMABLE.

Rev #26 01/13/21 D6-82973

Page -40
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CAUTION

The caution element appears in the context of the %w.c entity. The %w.c entity
appears in the context of the following elements:
ENTITY ELEMENT

(In %w.c) task

topic
subtask

entry

l1item - l7item

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

<!ELEMENT l1item - - (%w.c;, regulatory*, %text;, (list2,
note*)?) -(list1) >
<!ELEMENT l2item - - (%w.c;, regulatory*, %text;, (list3,
note*)?) -(list1) >
<!ELEMENT l3item - - (%w.c;, regulatory*, %text;, (list4,
note*)?) -(list1) >
<!ELEMENT l4item - - (%w.c;, regulatory*, %text;, (list5,
note*)?) -(list1) >
<!ELEMENT l5item - - (%w.c;, regulatory*, %text;, (list6,
note*)?) -(list1) >
<!ELEMENT l6item - - (%w.c;, regulatory*, %text;, (list7,
note*)?) -(list1) >
<!ELEMENT l7item - - (%w.c;, regulatory*, %text;)
-(list1) >

Printed Example:

SGML:
<subtask CHAPNBR="21" SECTNBR="27" SUBJNBR="00" FUNC="860" SEQ="031"
PGBLKNBR="5" ID="D297D7E0781341340E0AFB8831A6A85A">
<effect EFFRG="801899" EFFTEXT="ZAP ALL">
</effect>
<list1>
<l1item>
<caution>
<para>MAKE SURE THAT YOU CLOSE THE FAN CIRCUIT BREAKER WITHIN 5 MINUTES AFTER
YOU OPEN IT. IF YOU LEAVE THE CIRCUIT BREAKER OPEN MORE THAN 5 MINUTES, THE
ELECTRICAL/ELECTRONIC EQUIPMENT CAN BECOME TOO HOT. THIS CAN CAUSE DAMAGE TO
THE ELECTRICAL/ELECTRONIC EQUIPMENT.</para>
</caution>
<para>Open this circuit breaker and install safety tag:</para>
. . .
</l1item>
</subtask>

1.4 BOEING IMPLEMENTATION RULES

a. The published strings “WARNING:”, “CAUTION:” and “NOTE:” are not
contained in the SGML content. They must be generated by the data recipient.

Rev #26 01/13/21 D6-82973

Page -42
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

1.0 ELEMENT NAME

cb - Circuit Breaker

1.1 ELEMENT CONTENT

<!ELEMENT cb - - (#PCDATA) >

The cb element is used to tag the identification code of a circuit breaker, though not its
name or location information. The cb element appears in the context of the following
element:

ELEMENT

para

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -43
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

1.3.1 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Printed Example:

Printed Example:

Rev #26 01/13/21 D6-82973

Page -47
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CH5TSKNO

1.0 ELEMENT NAME

ch5tskno - Chapter 5 Task Number

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT ch5tskno - - (#PCDATA) >

The ch5tskno element identifies all task cards with an MPD task requirement which
are non-Maintenance Manual related, receive a Maintenance Manual chapter 5
AMTOSS number, and are listed in Maintenance Manual chapter 5. The ch5tskno
element appears in the context of the following element.

ELEMENT

mpditem

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -48
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CHGDESC

1.0 ELEMENT NAME

chgdesc - Change Description

1.1 ELEMENT CONTENT

<!ELEMENT chgdesc - - (#PCDATA) >

The chgdesc element gives the reason for a revision within an anchor or element.
Normally each change will also be bounded by a REVST and REVEND tag pair
which will further define the scope of the change. The chgdesc element appears in the
context of the following elements or entity:
ENTITY ELEMENT

taskcard

(In %deleted) taskcard

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: taskcard

Printed Example: chgdesc is not viewable on the printed page but may be available in
the PDF highlights within the frontmatter.

SGML:
<taskcard cardnbr="12-002-01-01" mprog="SYS" etopsind="No" chg="R"
key="T0000026246">
<effect effrg="HNAZZZ" efftext="ZAP ALL">
</effect>
<chgdesc>Changed the data to show the new stabilizer panels.</chgdesc>
<chgdesc>Changed the data to show extra steps to prevent elevator movement.
</chgdesc>
<chgdesc>Added WARNING 12-21-04-840-003</chgdesc>
<mainhead>
<source>MRB</source>
<skill>AIRPL</skill>
<workarea>ELEVATORS</workarea>

Rev #26 01/13/21 D6-82973

Page -49
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CHGDESC

<intdata>
<interval>
<version>1.1</version>
<thrshold>
<thrshtyp>N</thrshtyp>
<multiple>5000</multiple>
<unit>FH</unit>
. . .
</taskcard.

1.4 BOEING APPLICATION RULES

a. The document receiver uses the <chgdesc> element to build the highlights of a
revision.
b. The element <chgdesc> should be populated whenever a change has occurred.
c. Anchors can contain multiple <chgdesc> elements.
d. chgdesc may be supplied for graphics if all sheets are new, deleted or changed.
e. In our new authoring and publishing system there are two kinds of change
descriptions, authored and auto-generated. The auto-generated change descriptions
occur when something within the system changes and the authored change
descriptions occur when the engineer authors content and assigns a change
description to it.
f. The SGML contains both the authored change descriptions and the auto-generated
change descriptions. Highlights in the SGML are placed on the nearest element to
which they apply per the DTD.
g. The PDF contains the authored change descriptions and a limited set of auto-
generated descriptions. Highlights in the PDF are rolled up to the TASKCARD
level.

Rev #26 01/13/21 D6-82973

Page -50
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

COCEFF

1.0 ELEMENT NAME

coceff - Customer-originated Change Effectivity

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT coceff - o EMPTY >

The coceff element contains the data necessary to determine the range of aircraft for
which an anchor or other element is effective. Used to identify data either produced by
the customer (operator) within its own database/system or within the manufacturer’s
“master” database/document. The effectivity can be either given as a computer
interpretable string of aircraft identification numbers (EFFRG) or as a human readable
sentence (EFFTEXT). The coceff element appears in the context of the following
element:

ELEMENT

effect

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT coceff - o EMPTY >
<!ATTLIST coceff
effrg CDATA #IMPLIED
efftext CDATA #IMPLIED
cocnbr CDATA #REQUIRED >

Attribute Name Always Provided Provided When Data

is Available

effrg X

efftext X

cocnbr X

Rev #26 01/13/21 D6-82973

Page -51
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

COCST_COCEND

1.0 ELEMENT NAME

cocst/cocend - Customer-Originated Change Start/Customer-Originated Change End

1.1 ELEMENT CONTENT

<!ELEMENT cocst - O EMPTY >
<!ELEMENT cocend - O EMPTY >

The cocst element identifies that all data following the tag, until the tag COCEND is
reached, is information provided by the customer for whom the data is effective. The
cocend element identifies the end of revised data started by the tag COCST. cocst and
cocend elements appear in the context of the following elements:

ELEMENT

tasckard

NOTE: The revst / revend tags must be used in conjunction with the cocst / cocend
tags to indicate changes occur in the COC data.

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Refer to 1.3.2 for examples of cocst_cocend.

Rev #26 01/13/21 D6-82973

Page -52
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

COCST_COCEND

1.3.2 Element: taskcard

Printed Example:

SGML:
<subtask chapnbr="25" sectnbr="22" subjnbr="00" func="710" seq="004"
pgblknbr="6" id="A95D8E4B1663ACB8AE152E19EA9449A6">
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AY 3BA3BH 3BJ3BN 3BP3BP 3BR3BY 3CA3CH
3CJ3CN 3CP3CP 3CR3CY 3DA3DH 3DJ3ZZ" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<cocst>
<para>Release the recline button, and repeatedly push aft on the upper
portion (headrest) of the seatback.</para>
<cocend>
<list2>
<l2item>
<para>Make sure the seat back does not recline.</para>
</l2item>
</list2>
</l1item>
</list1>
</subtask>

Rev #26 01/13/21 D6-82973

Page -53
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

COLSPEC

1.0 ELEMENT NAME

colspec - Column Specification

1.1 ELEMENT CONTENT

<!ELEMENT colspec - o EMPTY >

The Column Specification (colspec) element is used to specify the intended

presentation of a column. colspec attributes are specified for each column in a table.
The colspec element appears in the context of the following elements:
ELEMENT

tgroup

thead

tfoot

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT colspec - o EMPTY >
<!ATTLIST colspec
colnum NUMBER #IMPLIED
colname NMTOKEN #IMPLIED
align (left|right|center
|justify|char) #IMPLIED
charoff NUTOKEN #IMPLIED
char CDATA #IMPLIED
colwidth CDATA #IMPLIED
rowsep %yesorno; #IMPLIED
colsep %yesorno; #IMPLIED >

Attribute Name Always Provided Provided When Data

is Available

colnum X

colname X

align X

charoff X

char X
colwidth X

colsep X

rowsep X

Rev #26 01/13/21 D6-82973

Page -54
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

COLSPEC

1.2.1 Attribute: colnum

Description: Column Number (colnum) indicates the number of the column as
counted from left to right.

1.2.2 Attribute: colname

Description: Column Name (colname) allows a specific column definition to be
named. This name is then used by the namest and namend attributes to
further define the appearance of the table.

1.2.3 Attribute: align

Description: Alignment (align) indicates the intended “justification” of all the
entries in that element.

1.2.4 Attribute: charoff

Description: Character Off (charoff) - if “align” is equal to “char,” percent of the
current width to the left of the (left edge of) character.

1.2.5 Attribute: char

Description: Character (char) - if “align” is equal to “char,” the value is the single
alignment character on which the first occurrence of this character in
the entry is aligned. If that character does not occur in the entry, the
entry aligns to the right of that character offset.

1.2.6 Attribute: colwidth

Description: Column Width (colwidth) provides the intended width of the column in
terms of column units (reference cols attribute within tgroup element).

1.2.7 Attribute: colsep

Description: Column Separator (colsep) is the logical indicator as to whether visible
separators (i.e., vertical lines inside of the frame) are intended to be
displayed on the right side of a specific column or all columns in a
table. The default for the whole table is given at the table element. The
value given at lower levels supersedes that given at higher levels for
that element and its contained elements only.

Boeing Application Rules:

a. In colspec of tgroup, this will specify if there is a visible separator that will be used
on that column throughout the table.
b. When vertical lines are not to be displayed, colsep is “0”; When vertical lines are
to be displayed, colsep is “1”.

Rev #26 01/13/21 D6-82973

Page -55
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

COLSPEC

NOTE: colsep can be overridden at a lower level; however, only the entry element
level is supported at this time.

1.2.8 Attribute: rowsep

Description: Row Separator (rowsep) is the logical indicator as to whether visible
separators (i.e., horizontal lines inside of the frame) are intended to be
displayed at the bottom of a specific row or all rows in a table. The
default for the whole table is given at the table element. The value
given at lower levels supersedes that given at higher levels for that
element and its contained elements only. Number: “0” = no separators,
“1” = separators.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -56
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

COLSPEC

1.3.1 Element: tgroup

<!ELEMENT tgroup - o (colspec*, spanspec*, thead?,
tfoot?, tbody) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
</effect>
. . .
<title>References</title>
<table frame="NONE">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="320*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>

Rev #26 01/13/21 D6-82973

Page -57
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

COLSPEC

<para>Title</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry>
<para><refext refman="AMM" refloc="28-00-00-010-802">28-00-00-010-802
</refext></para>
</entry>
. . .
</tgroup>
</table>

1.3.2 Element: thead

<!ELEMENT thead - o (colspec*, row+) >

Not used.

1.3.3 Element: tfoot

<!ELEMENT tfoot - o (colspec*, row+) >

Not used.

1.4 BOEING IMPLEMENTATION RULES

a. A <colspec> element is provided for each column of a table.
b. The optional COLNUM attribute is not used.
c. The optional COLNAME attribute can be specified at this level.
d. The optional ALIGN, CHAROFF, CHAR, COLSEP, and ROWSEP attributes are
not used at this level.
e. A value for the optional COLWIDTH attribute is usually provided and is always
expressed as a proportional measure, as in: COLWIDTH="141*". If no value is
provided, the columns are assumed to be of equal width.
f. The COLWIDTH attribute represents a proportion and not a percentage, as the
sum of the colwidth values for the table does not necessarily total 100. In printed
documents published from eMOD, the actual column widths are calculated as a
proportion of the total width of the page, minus the left and right margins.

Rev #26 01/13/21 D6-82973

Page -58
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CON

1.0 ELEMENT NAME

con - Consumable

1.1 ELEMENT CONTENT

<!ELEMENT con - - (connbr, conname) >

The con element identifies a consumable material. The con element appears in the
context of the following element:

ELEMENT

para

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Printed Example:

SGML:
<subtask chapnbr="12" sectnbr="21" subjnbr="04" func="640" seq="001"
pgblknbr="3" id="G56C7F0E95B4F9846B59351986640710">
<effect effrg="701705 731732 771799 941945 981999" efftext="ZAP ALL">
</effect>
<list1>
<l1item>

Rev #26 01/13/21 D6-82973

Page -59
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CON

<para>Put <con>
<connbr>D00015</connbr>
<conname>GREASE</conname>
</con>, in the fittings of the rod end bearing for the PCU and the reaction
link (<refint reftype="TABLE"
refid="O668FC9F5A2172A3032426F779808B6E">Table 301</refint>):</para>
<note>
<para>Only these two bearings at the aft end of each PCU use lubricant. The
bearings at the front of the PCU do not use lubricant. Also, for the PCU rod
end, application of lubricant to only one of the two grease fittings is
necessary.</para>
</note>
<list2>
<l2item>
<para>Add <con>
<connbr>D00015</connbr>
<conname>GREASE</conname>
</con>, until clean <con>
<connbr>D00015</connbr>
<conname>GREASE</conname>
</con>, comes out of the bearings.</para>
</l2item>
. . .
</subtask>

Rev #26 01/13/21 D6-82973

Page -60
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CONNAME

1.0 ELEMENT NAME

conname - Consumable Name

1.1 ELEMENT CONTENT

<!ELEMENT conname - - (#PCDATA) >

The conname element identifies the name or textual description of a consumable

material. The conname element appears in the context of the following element:

ELEMENT

con

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: con

<!ELEMENT con - - (connbr, conname) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -61
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CONNAME

</con>, in the fittings of the rod end bearing for the PCU and the reaction
link (<refint reftype="TABLE"
refid="O668FC9F5A2172A3032426F779808B6E">Table 301</refint>):</para>
<note>
<para>Only these two bearings at the aft end of each PCU use lubricant. The
bearings at the front of the PCU do not use lubricant. Also, for the PCU rod
end, application of lubricant to only one of the two grease fittings is
necessary.</para>
</note>
<list2>
<l2item>
<para>Add <con>
<connbr>D00015</connbr>
<conname>GREASE</conname>
</con>, until clean <con>
<connbr>D00015</connbr>
<conname>GREASE</conname>
</con>, comes out of the bearings.</para>
</l2item>
. . .
</subtask>

Rev #26 01/13/21 D6-82973

Page -62
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CONNBR

1.0 ELEMENT NAME

connbr - Consumable Number

1.1 ELEMENT CONTENT

<!ELEMENT connbr - - (#PCDATA) >

The connbr element identifies the unique code or part number by which a consumable
material is identified. The connbr element appears in the context of the following
element:

ELEMENT

con

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: con

<!ELEMENT con - - (connbr, conname) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -63
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CONNBR

<conname>GREASE</conname>
</con>, in the fittings of the rod end bearing for the PCU and the reaction
link (<refint reftype="TABLE"
refid="O668FC9F5A2172A3032426F779808B6E">Table 301</refint>):</para>
<note>
<para>Only these two bearings at the aft end of each PCU use lubricant. The
bearings at the front of the PCU do not use lubricant. Also, for the PCU rod
end, application of lubricant to only one of the two grease fittings is
necessary.</para>
</note>
<list2>
<l2item>
<para>Add <con>
<connbr>D00015</connbr>
<conname>GREASE</conname>
</con>, until clean <con>
<connbr>D00015</connbr>
<conname>GREASE</conname>
</con>, comes out of the bearings.</para>
</l2item>
. . .
</subtask>

Rev #26 01/13/21 D6-82973

Page -64
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CPYRGHT

1.0 ELEMENT NAME

cpyrght - Copyright

1.1 ELEMENT CONTENT

<!ELEMENT cpyrght - - (year*, holder*, geninfo) >

The cpyrght element is used as a container element to support the need to identify
copyright information. The content model consists of a year element and a holder
element. The cpyrght element appears in the context of the following elements:

ELEMENT

legalntc
fullstmt

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: legalntc

<!ELEMENT legalntc - - (exprtcl | cpyrght | proptary | geninfo)+>

Not used.

1.3.2 Element: fullstmt

<!ELEMENT fullstmt - - (title?, cpyrght?, para+) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -65
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

CPYRGHT

SGML:
<legalntc CHG="N" KEY="T-legalntc" REVDATE="20030210">
<proptary>
<fullstmt>
<title>BOEING PROPRIETARY, CONFIDENTIAL, AND/OR TRADE SECRET</title>
<cpyrght>
<year>1994</year>
<holder>The Boeing Company</holder>
<geninfo>
<para>Unpublished Work - All Rights Reserved</para>
<para>Boeing claims copyright in each page of this document only to the
extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para></geninfo></cpyrght>
<PARA>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, WA 98124.
</para></fullstmt>
<para>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, WA 98124.
</para></fullstmt></proptary>
<geninfo>
<para>Boeing, the Boeing signature, the Boeing symbol, 707, 717, 727, 737,
747, 757, 767, 777, BBJ, DC-8, DC-9, DC-10, MD-10, MD-11, MD-80, MD-88, MD-90
and the red-white-and-blue Boeing livery are all trademarks owned by The
Boeing Company; and no trademark license is granted in connection with this
document unless provided in writing by Boeing.</para></geninfo></legalntc>

Rev #26 01/13/21 D6-82973

Page -66
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

DELETED

1.0 ELEMENT NAME

deleted - Deleted

1.1 ELEMENT CONTENT

<!ELEMENT deleted - o EMPTY >

The deleted element has the reserved-keyword element empty (in the ISO 8879
specification) as its content model. empty contains no embedded content.

When the content of the parent element has been deleted, the data sender will
substitute the deleted element for the content.

The deleted element is used to indicate that the element is to be deleted on

incorporation of this (partial) revision or has been deleted from this issue of a (total)
revision. When an element is to be deleted and coded as DELETED, its content will be
empty; therefore, none of its subordinate elements will be in the revised document
instance. All deleted elements must have a chg=“D” attribute value.
The deleted element appears in the context of the %deleted which appears in the
context of the following element:

ELEMENT

taskcard

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -67
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

DELETED

1.3.1 Element: taskcard

Printed Example:

SGML:
<taskcard cardnbr="20-010-01-01" mprog="SYS" etopsind="No" chg="D"
key="T0000026722">
<deleted>
<chgdesc>Deleted Task</chgdesc>
</taskcard>

1.4 BOEING APPLICATION RULES

a. The <deleted> element is used to represent any deleted anchor element.

Rev #26 01/13/21 D6-82973

Page -68
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EAPPNOTE

1.0 ELEMENT NAME

eappnote - Engine Applicability Note

1.1 ELEMENT CONTENT

<!ELEMENT eappnote - - (%text;) >

The eappnote element is the engine applicability note which accompanies the engine
applicability. The eappnote element appears in the context of the following element.

ELEMENT

enapdata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -69
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EAPPNOTE

1.3.1 Element: enapdata

<!ELEMENT enapdata - - (engappl*, eappnote*) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
</effect>
<mainhead>
. . .
<enapdata>
<engappl>715C1</engappl>
<eappnote>
<para>Not applicable to Engine Series XXX</para>
</eappnote>
</enapdata>
. . .
</taskard>

Rev #26 01/13/21 D6-82973

Page -70
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

1.0 ELEMENT NAME

effect - Effectivity

1.1 ELEMENT CONTENT

<!ELEMENT effect - - ((sbeff | coceff)*) >

The effect element contains the data necessary to determine the range of aircraft,
engines, or components for which an anchor or other element is effective. It can also
contain coc and sb effectivities. All effectivities must be equal to, or subsets of, the
effectivity of the parent element. The effect element must immediately follow the start
tag of the element to which it applies, except when a REVST, COCST or CHGDESC
tag is encountered. In this case, the element immediately follows the REVST, COCST
or CHGDESC. The effrg attribute is given as a computer-interpretable string. The
efftext attribute is the human-readable form and is meant for the display of the
effectivity string and the associated text. The effect element appears in the context of
the following elements:

ELEMENT

taskcard

task

pretopic*

topic

regulatory

regulation

subtask**

grphcref

warning*

caution*
note*

graphic

sheet
*allows effectivity as an inclusion - Inclusions define elements that can be included at any point in the
current element or any element embedded within it.
**allows effectivity as an inclusion as well as a child element

Rev #26 01/13/21 D6-82973

Page -71
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

For example:

Effectivity as an inclusion:
<!ELEMENT pretopic - - (title, (%text; | list1)) +(effect) >

Effectivity as a child as well as an inclusion:

<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect) >

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT effect - - ((sbeff | coceff)*) >
<!ATTLIST effect
effrg CDATA #IMPLIED
efftext CDATA #IMPLIED >

Attribute Name Always Provided Provided When

Data is Available

effrg X
efftext X

1.2.1 Attribute: effrg

Description: Effectivity Range (effrg) provides the range of aircraft in the fleet to
which the text or graphic is applicable. It includes repeating effectivity
codes where the first digits are for the first aircraft and the last digits
are for the last aircraft applicable for the entry.

Boeing Application Rules:

a. The effrg is the Customer Effectivity Code (cec) and is an alpha, numeric, or
combination of both alpha and numeric range (e.g., 001999, 005008, AAAZZZ,
A01A10).

effrg=“001999” <--- effrg is “ALL”

effrg=“001005” <--- effrg is “planes 001-005”
effrg=“001005 008010 012015” <--- effrg is “planes 001-005, 008-010 and
012-015”

b. Chapter effrg will always default to ALL, i.e., effrg=“001999” or

effrg=“AAAZZZ”.

Rev #26 01/13/21 D6-82973

Page -72
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

1.2.2 Attribute: efftext

Description: Effectivity Text (efftext) provides a description of how the effectivity of
the element is to be applied depending on the aircraft status,
configuration, modification embodiment, etc. The efftext attribute is
human readable and is useful in displaying effectivity statements.
However, efftext is not intended for machine extraction or processing.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: taskcard

Example 1:

Printed Example:

...

Rev #26 01/13/21 D6-82973

Page -73
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

SGML:
<taskcard cardnbr="12-002-01-01" mprog="SYS" etopsind="No" chg="N"
key="T0000026246">
<effect effrg="AOAAOZ" efftext="ZAP ALL">
</effect>
. . .
</taskcard>

Example 2:

Printed Example:

...

SGML:
<taskcard cardnbr="21-131-00-01" mprog="SYS" etopsind="No" chg="R"
key="T0000018404">
<revst>
<revend>
<revst>
<effect effrg="197199 701710 751799 967969" efftext="ZAP 708-710, 756-799;
ZAP 197-199, 701-707, 751-755, 967-969 POST SB 777-21A0
038; AIRPLANES WITH CARGO COMPARTMENT OVERHEAT SWITCHES">
</effect>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -74
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

1.3.2 Element: task

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect) >

Example 1:

Page -81
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

1.3.12 Element: graphic

<!ELEMENT graphic - - (effect, seqnum, title?, sheet+) >

NOTE: graphic effectivity is the union of sheet effectivity. graphic is a container

element for sheet.

Printed Example: Graphic effectivity is implied and is not viewable on the printed
page.

SGML:
<graphic chapnbr="12" sectnbr="21" subjnbr="04" func="990" seq="801"
pgblknbr="3" id="BE9721EC9FC48AD398F19713F17D6272">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<seqnum>301</seqnum>
<title>Elevator Power Control Unit (PCU) Servicing</title>
<sheet gnbr="HF0AC3BBC9E59DF9141FC7C478221DA2" sheetnbr="1"
id="MEA0232A25BDDDDEEBEBB37DA9F19337">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
</sheet>
<sheet gnbr="CC4C041FBEE167D0720EB29A67BCF25A" sheetnbr="2"
id="HEDFA2BA7BE6DC2D6B1D6D6E25463AA0">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
</sheet>
</graphic>

Rev #26 01/13/21 D6-82973

Page -82
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

1.3.13 Element: sheet

<!ELEMENT sheet - - (effect, title?, gdesc?) >

Printed Example:

SGML:
<graphic chapnbr="12" sectnbr="21" subjnbr="04" func="990" seq="801"

Rev #26 01/13/21 D6-82973

Page -83
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

pgblknbr="3" id="BE9721EC9FC48AD398F19713F17D6272">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<seqnum>301</seqnum>
<title>Elevator Power Control Unit (PCU) Servicing</title>
<sheet gnbr="HF0AC3BBC9E59DF9141FC7C478221DA2" sheetnbr="1"
id="MEA0232A25BDDDDEEBEBB37DA9F19337">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
</sheet>
<sheet gnbr="CC4C041FBEE167D0720EB29A67BCF25A" sheetnbr="2"
id="HEDFA2BA7BE6DC2D6B1D6D6E25463AA0">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
</sheet>
</graphic>

1.4 BOEING APPLICATION RULES

a. Engine Logo Translation Table for chapter efftext for APU engine chapters.

Model Beginning Ending Chappref/ Engine Definitions

Chapter Chapter Confltr
(engine
prefix)

“ALL” 00 48 ‘’ “ALL” **

“ALL” 49 49 ‘’ “ALL” **

“ALL” 50 69 ‘’ “ALL” **

“P-8” 70 89 ‘F’ “CFM56 ENGINES (CFM56-7)”

737-300/400/500 49 49 A APS2000 ENGINES

737-300/400/500 49 49 B GTCP36-280 ENGINES

737-300/400/500 49 49 D GTCP85-129 SERIES ENGINES

737-300/400/500 70 89 C CFM56 (CFM56-3) ENGINES

“737-600/700/800/ 70 89 ‘F’ “CFM56 ENGINES (CFM56-7)”

900”
“737-7/8/8200/9” 70 89 ‘G’ “LEAP-1B ENGINES”

“747-400” 70 89 ‘D’ “RB211-524 SERIES ENGINES”

“747-400” 70 89 ‘J’ “CF6-80C2 SERIES ENGINES”

“747-400” 70 89 ‘N’ “PW4000 SERIES ENGINES”

“747-8” 70 89 ‘G’ “GEnx SERIES ENGINES”

“757” 70 89 ‘R’ “RB211-535 SERIES ENGINES”

Rev #26 01/13/21 D6-82973

Page -84
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

Model Beginning Ending Chappref/ Engine Definitions

Chapter Chapter Confltr
(engine
prefix)

“757” 70 89 ‘P’ “PW2000 SERIES ENGINES”

“777-200/300” 70 89 ‘G’ “GE90-70/80/90 SERIES ENGINES”

“777-200/300” 70 89 ‘N’ “PW4000 SERIES ENGINES”

“777-200/300” 70 89 ‘R’ “TRENT 800 SERIES ENGINES”

“777-200/300” 70 89 ‘H’ “GE90-100 SERIES ENGINES”

MD11 70 89 ‘N’ “PW4460/4462”

MD11 70 89 ‘G’ “CF6-80C2D1F”

b. Effectivity Inclusions: Inclusions define elements that can be included at any

point in the current element or any element embedded within it.
c. The TC DTD allows effectivity inclusions in the pretopic, subtask, warning, note
and caution elements.
d. When an inclusion is encountered on a list item, that effectivity applies only to
children (sub-lists) of that list item until a new effectivity is encountered. The
effectivity on a list item does not apply to any peer list items.
e. When only the effrg has changed (identified during the publishing process), the
change attribute will be set to CHG="R", the revdate will not change (i.e., the
revdate will not be the current revision date of the manual), and no
<revst><revend> tags will be applied.

Rev #26 01/13/21 D6-82973

Page -85
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

f. <revst><revend> tags can be applied as follows:

(1) <revst><revend> pairs can be applied before the <effect> tag

<seqnum>1</seqnum>
<title>Figure 1. INTERNAL-GENERAL VISUAL: INTERNAL-STABILIZER
TORSION BOX COMPARTMENT<revst> <revend></title>
<sheet GNBR="NF0007323FE18F4FF5A927E03723BA63" SHEETNBR="1"
ID="EE0E5222873781D47FB30F2A6F1B6B9A">
<revst><revend><effect EFFRG="001099 101199 251299 301699 701702
704705 801999" EFFTEXT="ZAP ALL">
</effect>
</sheet>

(2) <revst><revend> tags can be around the <effect> tag:

<seqnum>1</seqnum>
<revst><revend><title>Figure 1. Cabin Pressure Control System Test
</title>
<sheet GNBR="FC8FD621E8C099444679548DD196AFFC" SHEETNBR="1"
ID="NDE7F63180D807CB006300B0120089CD">
<revst><effect EFFRG="001099 101147 701702 704705 801999"
EFFTEXT="ZAP 001-099, 101-147, 701, 702, 704, 705, 801-999">
</effect>
<revend></sheet>
<sheet GNBR="BC761A4F44632D69115C4887EAA0BFD7" SHEETNBR="2"
ID="ABD11271322100464F3EB35DF9599DDB">
<revst><effect EFFRG="001099 101147 701702 704705 801999"
EFFTEXT="ZAP 001-099, 101-147, 701, 702, 704, 705, 801-999">
</effect>
<revend></sheet>

(3) <revst><revend> pairs can be applied after the closing effect tag
(i.e., </effect)

<taskcard CARDNBR="27-062-00-02" MPROG="SYS" ETOPSIND="No" CHG="R"

KEY="T0000027613" REVDATE="20091015">
<effect EFFRG="001099 101199 251299 301699 701702 704705 801999"
EFFTEXT="ZAP 129-199, 251-299, 301-699; ZAP 001-099, 101-128, 701
, 702, 704, 705, 801-999 POST SB 737-27-1253">
</effect>
<revst><revend><chgdesc>Revised</chgdesc>
<chgdesc>Changed from "ZAP 129-199, 251-299, 301-699; ZAP 001-099,
101-128, 701, 702, 801-999 POST SB 737-27-1253" to "ZAP 129-199,
251-299, 301-699; ZAP 001-099, 101-128, 701, 702, 704, 705, 801-999
POST SB 737-27-1253"</chgdesc>
<chgdesc>Revised Phase Code. Update with new utilization parame-
ters.</chgdesc>
<mainhead>

Rev #26 01/13/21 D6-82973

Page -86
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EFFECT

g. The data receiver must determine how and when to display effectivity statements.
In the Boeing PDF, effectivity statements are generally displayed when it differs
from the previous effectivity statement.

Rev #26 01/13/21 D6-82973

Page -87
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EIN

1.0 ELEMENT NAME

ein - Equipment Identification Number

1.1 ELEMENT CONTENT

<!ELEMENT ein - - (#PCDATA) >

The ein element is a functional identification number assigned to the specific usage of
the part. For electric elemental parts, this is the Electrical Equipment Number shown
in the Wiring Diagram Manual. The ein element appears in the context of the
following elements:

ELEMENT

para

title

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -88
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EIN

1.3.1 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Printed Example: Example taken from AMM

SGML:
<subtask CHG="R" REVDATE="20011001" KEY="KEF844CBB7EBE2B420D13164A0D26FA3"
FUNC="720" SEQ="007" SUBJNBR="01" SECTNBR="41" CHAPNBR="30" PGBLKNBR="5">
<effect EFFRG='475487' EFFTEXT="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Do a check for 115 VAC at the Windshield Controller connector, <ein>P1-
4422A</ein> as follows:</para>
. . .

1.3.2 Element: title

<!ELEMENT title - - (#PCDATA | ein | sbnbr | sub
| super)+ >

Not used.

Rev #26 01/13/21 D6-82973

Page -89
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ELAPTIME

1.0 ELEMENT NAME

elaptime - Elapsed Time

1.1 ELEMENT CONTENT

<!ELEMENT elaptime - - (#PCDATA) >

The elaptime element identifies the time it takes to complete the task, excluding open/
close access requirements. The elaptime element appears in the context of the
following element.

ELEMENT

supldata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: supldata

<!ELEMENT supldata - - (manhours, nbrpeopl, elaptime,
tc_manhours?, tc_nbrpeopl?,
tc_elaptime?, taskctgy?, feftctgy*)>

Printed Example: The supldata information does not appear on the printed taskcard.

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
. . .
<supldata>
<manhours>1.00</manhours>
<nbrpeopl>1</nbrpeopl>
<elaptime>1.00</elaptime>
</supldata>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -90
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENAPDATA

1.0 ELEMENT NAME

enapdata - Engine Applicability Data

1.1 ELEMENT CONTENT

<!ELEMENT enapdata - - (engappl*, eappnote*) >

The enapdata element defines the engine applicability and its accompanying note. The
enapdata element appears in the context of the following elements:

ELEMENT

mainhead

cchead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -91
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENAPDATA

1.3.1 Element: mainhead

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
<mainhead>
• • •
<enapdata>
<engappl>715B1</engappl>
</enapdata>
. . .
</mainhead>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -92
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENAPDATA

1.3.2 Element: cchead

<!ELEMENT cchead - - (skill+, workarea+, reltask*, specnote?,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -93
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENGAPPL

1.0 ELEMENT NAME

engappl - Engine Applicability

1.1 ELEMENT CONTENT

<!ELEMENT engappl - - (#PCDATA) >

The engappl element defines the general reference to the applicable engine model. The
engappl element appears in the context of the following element.

ELEMENT

enapdata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: enapdata

<!ELEMENT enapdata - - (engappl*, eappnote*) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
<mainhead>
• • •

Rev #26 01/13/21 D6-82973

Page -94
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENGAPPL

Rev #26 01/13/21 D6-82973

Page -95
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENTRY

1.0 ELEMENT NAME

entry - Entry in a Table

1.1 ELEMENT CONTENT

<!ELEMENT entry - o (regulatory | %text; | %w.c;
| graphic)* >

The entry element is the basic component of a cellular table (table). Each entry
appears in one of the rows of the table. An entry is a logical element that can contain
several lines (presentation is not forced in the SGML text). An entry is also commonly
referred to as a cell. A row in a table is made up of one or more cells (i.e., entries). The
entry element appears in the context of the following element:

ELEMENT

row

1.2 ATTRIBUTE MARKUP RULES

Attribute Name Always Provided Provided When Data

is Available

colname X

namest X
nameend X

spanname X

morerows X

Rev #26 01/13/21 D6-82973

Page -96
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENTRY

Attribute Name Always Provided Provided When Data

is Available

colsep X
rowsep X

rotate X

valign X
align X

charoff X

char X

1.2.1 Attribute: colname

Description: Column Name (colname) allows a specific column definition to be
named. This name is then used by the namest and namend attributes to
further define the appearance of the table.

1.2.2 Attribute: namest

Description: Name Start (namest) defines the number of the column at which an
entry is to begin.

Boeing Application Rules:

a. This is the column number under which an entry starts. It is the far left column of
the cell.
b. The optional NAMEST attribute is specified only when a cell spans one or more
columns.

1.2.3 Attribute: nameend

Description: Name End (nameend) defines the number of the column at which an
entry is to stop.

Boeing Application Rules:

a. This is the column number under which an entry ends. It is the far right column of
the cell.
b. The optional NAMEEND attribute is specified only when a cell spans one or more
columns.

Rev #26 01/13/21 D6-82973

Page -97
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENTRY

1.2.4 Attribute: spanname

Description: Span Name (spanname) allows a specific span definition to be named.
This name may then be used in the entry element to further define the
appearance of the table.

1.2.5 Attribute: morerows

Description: More Rows (morerows) is the number of additional logical rows in a
vertical span.

Boeing Application Rules:

a. The optional MOREROWS attribute is specified only when an entry spans rows.
b. When an entry only spans one row in the table, the morerows attribute may not be
present in the SGML, indicating the morerows is equal “0”. The example below
has morerows=“0”:

821CR Panel Pull-in Hook

c. When an entry spans more than one logical row in the table, morerows is the
number of additional rows in the vertical span. In the example below, columns one
through six have rows with MOREROWS=“0”; that is, they span no additional
vertical rows. The last column in the table body spans three additional rows;
therefore, the attribute value is MOREROWS=“3”.

821 Forward Forward Large With Forward Large

Large Cargo Door Window Cargo Door
Cargo Door Components Components
that can be used
821CR Panel Pull-in Hook With Latch to repair any
821DR Panel Hinge Latch configuration
for this
821ER 821FR Panel Mid-span Latch particular model
Latch

Rev #26 01/13/21 D6-82973

Page -98
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENTRY

1.2.6 Attribute: colsep

Boeing Application Rules:

a. Reference the element colspec for colsep rules.
b. When vertical lines are not used as column separators, set colsep to “0”. When
vertical lines are to be used as column separators, set colsep to “1”.

1.2.7 Attribute: rowsep

Boeing Application Rules:

a. When horizontal lines are not used as row separators, set rowsep to 0. When
horizontal lines are to be used as row separators, set rowsep to 1.

1.2.8 Attribute: rotate

Description: Rotate content is either in the orientation of the table (value is one or
more zeros) or 90 degrees counterclockwise to table orientation (value
is other than zeros).

1.2.9 Attribute: valign

Description: valign is the text vertical positioning within the entries. Declared values
equal top, middle (vertically centered), or bottom. The default is “top.”

1.2.10 Attribute: align

Description: Alignment (align) indicates the intended “justification” of all the
entries in that element.

Boeing Application Rule:

a. The optional ALIGN attribute can be specified at this level. If no value is
provided, the default is assumed to be “left”.

Rev #26 01/13/21 D6-82973

Page -99
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENTRY

1.2.11 Attribute: charoff

Description: Character Off (charoff) for align is char, whose value is the percent of
the current width to the left edge of character. The default is “50”.

1.2.12 Attribute: char

Description: If align equals char (Character), the value is the single alignment
character on which the first occurring character in the entry is aligned.
If that character does not occur in the entry, the entry aligns to the right
of that character offset.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -100
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENTRY

1.3.1 Element: row

<!ELEMENT row - o (entry+) >

Printed Example:

SGML:
<title>References</title>
<table frame="NONE">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="320*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>
<para>Title</para>
</entry>
</row>
</thead>

Rev #26 01/13/21 D6-82973

Page -101
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ENTRY

1.4 BOEING IMPLEMENTATION RULES

a. The optional COLNAME attribute can be specified at this level.
b. The optional NAMEST and NAMEEND attributes are specified only when a cell
spans one or more columns.
c. The optional SPANNAME attribute is not used.
d. The optional MOREROWS attribute is specified only when an entry spans rows.
e. The optional COLSEP and ROWSEP are used at this level.
f. The optional ROTATE attribute is not used.
g. The optional VALIGN attribute can be specified at this level.
h. The optional ALIGN attribute can be specified at this level. If no value is
provided, the default is assumed to be “left”.
i. The optional CHAROFF and CHAR can be specified at this level.

Rev #26 01/13/21 D6-82973

Page -102
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EQU

1.0 ELEMENT NAME

equ - Equation

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT equ - - (#PCDATA) >

The equ element identifies a statement of mathematical or logical expressions. The

equ element appears in the context of the following element:

ELEMENT

para

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -103
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EXPRTCL

1.0 ELEMENT NAME

exprtcl - Export Control

1.1 ELEMENT CONTENT

<!ELEMENT exprtcl - - (para | unlist | numlist | note)+ >

The exprtcl element is used as a container element to support the need to identify
export control information. The content model consists of textual elements to provide
a variety of authoring needs. The exprtcl element appears in the context of the
following element:

ELEMENT

legalntc

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of data followed by an example of the SGML
markup.

Rev #26 01/13/21 D6-82973

Page -104
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EXPRTCL

1.3.1 Element: legalntc

<!ELEMENT legalntc - - (exprtcl | cpyrght | proptary | geninfo)+>

NOTE: The following examples are fabricated. The Export Control statements are
currently under development and are shown here as examples only. In
addition, the control statements may differ depending on the type of export
control that is required.

Printed Example:

SGML:
Example 1: Document with one or more EAR Export Control Classification
Numbers:

<legalntc chg = "n" key = "ab23c7b1" revdate = "20061118">

<exprtcl>
<para> This document has EAR data with Export Control Classification Numbers
(ECCN) of: </para>
<unlist bulltype=BULLET>
<unlitem><para>9E991</para></unlitem>
</unlist>
<para>Export of this technology is controlled under the United States Export
Administration Regulations (EAR) (15 CFR 730-774). An export license may be
required before it is used for development, production or use by foreign
persons from specific countries. The controller of this data has the

Rev #26 01/13/21 D6-82973

Page -105
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EXPRTCL

individual responsibility to abide by all export laws.</para>

</exprtcl>
<proptary>
<fullstmt>
<title>BOEING PROPRIETARY, CONFIDENTIAL, AND/OR TRADE SECRET</title>
<cpyrght>
<year>2006</year>
<holder>The Boeing Company</holder>
<geninfo>
<para>Unpublished Work - All Rights Reserved</para>
<para>Boeing claims copyright in each page of this document only to the
extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para>
</geninfo>
</cpyrght>
<para>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, Washington
98124.</para>
</fullstmt>
<partstmt>
<para> BOEING PROPRIETARY - Copyright © Unpublished Work - See title page
for details.</para>
</partstmt>
</proptary>
<geninfo>
<para>Boeing, the Boeing signature, the Boeing symbol, 707, 717, 727, 737,
747, 757, 767, 777, BBJ, DC-8, DC-9, DC-10, MD-10, MD-11, MD-80, MD-88,
MD-90, and the red-white-and-blue Boeing livery are all trademarks owned by
The Boeing Company; and no trademark license is granted in connection with
this document unless provided in writing by Boeing.</para>
</geninfo>
</legalntc>

Rev #26 01/13/21 D6-82973

Page -106
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

EXPRTCL

Example 2: Document with ITAR classification restrictions

<legalntc>
. . .
<exprtcl>
<para> This document contains technical information, which is controlled by
the United States Government, Department of State, International Traffic and
Arms Regulations (ITAR) (22 CPR 120-130), and requires an export license
prior to sharing with foreign persons. It is the responsibility of the
organization and individual in control of this data to abide by U.S. export
laws.</para>
</exprtcl>
. . .
</legalntc>

1.4 BOEING APPLICATION RULES

a. ECCN9E991 represents non-restricted EAR data.

Rev #26 01/13/21 D6-82973

Page -107
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

FEFTCTGY

1.0 ELEMENT NAME

feftctgy - Maintenance Steering Group-3 Failure Effect Category

1.1 ELEMENT CONTENT

<!ELEMENT feftctgy - - (#PCDATA) >

The feftctgy element categorizes the failure effect by requiring an evaluation of each
functional failure. For systems maintenance program only. The feftctgy element
appears in the context of the following element.

ELEMENT

supldata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: supldata

<!ELEMENT supldata - - (manhours, nbrpeopl, elaptime,
tc_manhours?, tc_nbrpeopl?,
tc_elaptime?, taskctgy?, feftctgy*)>

Printed Example: The mpditem information does not appear on the printed taskcard.

SGML:
<taskcard cardnbr="08-002-00-01" mprog="SYS" etopsind="No" chg="N"
key="T0000017914">
<effect effrg="001999">
</effect>
<mainhead>
<source>GOV</source>
. . .
<mpditem>
<mpdnbr>08-002-00</mpdnbr>
<title>FQIS Densitometers</title>
<taskdesc>
<para>Operationally check DENSITOMETERS of Fuel Quantity Indicating System.
(Check OMS)</para>
</taskdesc>
<supldata>
<manhours>0.50</manhours>

Rev #26 01/13/21 D6-82973

Page -108
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

FEFTCTGY

Rev #26 01/13/21 D6-82973

Page -109
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

FTNOTE

1.0 ELEMENT NAME

ftnote - Footnote

1.1 ELEMENT CONTENT

<!ELEMENT ftnote - - %text; >

The ftnote element is used to identify a footnote to a table entry. The ftnote element
appears in the context of the following element:

ELEMENT

table

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT ftnote - - %text; >
<!ATTLIST ftnote
ftnoteid ID #REQUIRED >

Attribute Name Always Provided Provided When Data

is Available

ftnoteid X

1.2.1 Attribute: ftnoteid

Description: A unique number to allow direct SGML cross-referencing to be
performed from the REFID attribute of the REFINT element.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -110
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

FTNOTE

1.3.1 Element: table

<!ELEMENT table - - ((seqnum?, title?, tgroup, ftnote*)
| graphic+) -(table) >

Printed Example:

SGML:
<para>Do this task: <refext refman="AMM" refloc="20-10-29-420-
801">Lubrication Fitting Installation, AMM TASK 20-10-29-420-801</refext>.
</para>
<table frame="ALL" id="P82516F3E0F53950A5C88F23BE5F55A5">
<seqnum>302</seqnum>
<title>Nose Landing Gear Lower End Components Lubrication</title>
<tgroup cols="5" colsep="1" rowsep="1">
<colspec colname="COL1" colwidth="5*">
<colspec colname="COL2" colwidth="38*">
<colspec colname="COL3" colwidth="14*">
<colspec colname="COL4" colwidth="12*">
<colspec colname="COL5" colwidth="10*">
<thead>
<row>
<entry valign="MIDDLE" align="CENTER">
<para>Item No.</para>
. . .
</tgroup>
<ftnote ftnoteid="CA533F06DE17B8AFEA049FD40783C35A">
<para>Use a manual grease gun, or, a restricted, pressurized grease gun,
whose lubricant flowrate does not exceed 0.65 lb/min (0.3 kg/min), to
minimize the possibility of seal migration or separation, during

Rev #26 01/13/21 D6-82973

Page -111
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

FTNOTE

lubrication.</para>
</ftnote>
<ftnote ftnoteid="M5E6333251A396E59F8DC9246ED21E2F">
<para>Do not over lubricate the gland nut. Use minimum pressure on the hand
pump to apply the grease. Apply the equivalent of 3-5 pumps of a medium size
grease gun. If you over lubricate with too much pressure the scraper ring can
be pushed out of position in the gland nut.</para>
</ftnote>
<ftnote ftnoteid="I0DA444C06737A6997CD2F5287E5A81D">
<para>Some gland nuts do not have lubrication fittings, it is not necessary
to lubricate these gland nuts.</para>
</ftnote>
<ftnote ftnoteid="K77E9344CA3A275EB1163D286E243D9A">
<para>Do not lubricate if the gland nut lubrication fitting has been removed
and the hole plugged.</para>
</ftnote>
</table>

1.4 BOEING APPLICATION RULES

a. Though the DTD allows additional content, <ftnote> will only consist of one or
more <para>, <unlist> or <note>.
b. The footnote markers (*, [], #, numbers, etc.) are not contained in the SGML
content. They must be generated by the data recipient. However, ftnotes within
TRs will include the footnote markers within the para element and therefore these
symbols will not need to be generated by the receiving system.

Rev #26 01/13/21 D6-82973

Page -112
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

FULLSTMT

1.0 ELEMENT NAME

fullstmt - Full Statement

1.1 ELEMENT CONTENT

<!ELEMENT fullstmt - - (title?, cpyrght?, para+) >

The fullstmt element is used as a container for the full proprietary statement. The
content model consists of a year element and a holder element. The fullstmt element
appears in the context of the following element:

ELEMENT

proptary

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: proptary

<!ELEMENT proptary - - (fullstmt, partstmt?) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -113
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

FULLSTMT

<para>Unpublished Work - All Rights Reserved</para>

<para>Boeing claims copyright in each page of this document only to the
extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para></geninfo></cpyrght>
<PARA>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company
, P.O. Box 3707, Seattle, WA 98124.</para></fullstmt></proptary>
. . .
</legalntc>

Rev #26 01/13/21 D6-82973

Page -114
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GCHGDESC

1.0 ELEMENT NAME

gchgdesc - General Change Description

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT gchgdesc - - (#PCDATA) >

The gchgdesc element contains highlights for the entire taskcard deck. The element
gchgdesc appears in the context of the following element.

ELEMENT

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -115
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GDESC

1.0 ELEMENT NAME

gdesc - Graphic Description

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT gdesc - - (unlist | numlist) >

The gdesc element describes how each sheet in a graphic may be followed by a list.
This list will usually provide a key or legend to the associated graphic image. The
gdesc element appears in the context of the following elements.

ELEMENT

sheet

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -116
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GENINFO

1.0 ELEMENT NAME

geninfo - General Information

1.1 ELEMENT CONTENT

<!ELEMENT geninfo - - (para | unlist | numlist | note)+ >

The geninfo element is the general information portion of a copyright statement. The
geninfo element appears in the context of the following elements:

ELEMENT

legalntc

cpyrght

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: legalntc

<!ELEMENT legalntc - - (exprtcl | cpyrght | proptary | geninfo)+>

Printed Example:

SGML:
<legalntc CHG="N" KEY="T-legalntc" REVDATE="20030210">
<proptary>
<fullstmt>
<title>BOEING PROPRIETARY, CONFIDENTIAL, AND/OR TRADE SECRET</title>

Rev #26 01/13/21 D6-82973

Page -117
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GENINFO

<cpyrght>
<year>1994</year>
<holder>The Boeing Company</holder>
<geninfo>
<para>Unpublished Work - All Rights Reserved</para>
<para>Boeing claims copyright in each page of this document only to the
extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para></geninfo></cpyrght>
<para>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, WA 98124.
</para></fullstmt></proptary>
<geninfo>
<para>Boeing, the Boeing signature, the Boeing symbol, 707, 717, 727, 737,
747, 757, 767, 777, BBJ, DC-8, DC-9, DC-10, MD-10, MD-11, MD-80, MD-88, MD-90
and the red-white-and-blue Boeing livery are all trademarks owned by The
Boeing Company; and no trademark license is granted in connection with this
document unless provided in writing by Boeing.</para></geninfo></legalntc>

1.3.2 Element: cpyrght

<!ELEMENT cpyrght - - (year*, holder*, geninfo) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -118
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GENINFO

<para>Boeing claims copyright in each page of this document only to the

extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para></geninfo></cpyrght>
<para>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, WA 98124.
</para></fullstmt></proptary>
<geninfo>
<para>Boeing, the Boeing signature, the Boeing symbol, 707, 717, 727, 737,
747, 757, 767, 777, BBJ, DC-8, DC-9, DC-10, MD-10, MD-11, MD-80, MD-88, MD-90
and the red-white-and-blue Boeing livery are all trademarks owned by The
Boeing Company; and no trademark license is granted in connection with this
document unless provided in writing by Boeing.</para></geninfo></legalntc>

Rev #26 01/13/21 D6-82973

Page -119
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRAPHIC

1.0 ELEMENT NAME

graphic - Graphic

1.1 ELEMENT CONTENT

<!ELEMENT graphic - - (effect, seqnum, title?, sheet+) >

The graphic element acts as the placeholder for a set of sheets. The graphic element
appears in the context of the following elements:

ELEMENT

taskcard

task

table

entry

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT graphic - - (effect, seqnum, title?, sheet+) >
<!ATTLIST graphic
chappref CDATA #IMPLIED
chapnbr NUMBER #IMPLIED
sectnbr NUMBER #IMPLIED
subjnbr NUMBER #IMPLIED
func CDATA #IMPLIED
seq CDATA #IMPLIED
confltr CDATA #IMPLIED
varnbr NUMBER #IMPLIED
alunqi CDATA #IMPLIED
pgblknbr NUMBER #IMPLIED
confnbr NUMBER #IMPLIED
id ID #REQUIRED >

Attribute Name Always Provided May or May Not Be

Present

chappref X
chapnbr X

sectnbr X

subjnbr X

func X

seq X

Rev #26 01/13/21 D6-82973

Page -120
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRAPHIC

Attribute Name Always Provided May or May Not Be

Present

confltr X
varnbr X

alunqi X

pgblknbr X
confnbr X

id X

1.2.1 Attribute: chappref

Description: Chapter Prefix (chappref) is a unique identifier for chapters with
multiple engine types. This identifier is used with the amtoss
numbering scheme as defined in ATA Spec. 2200.

1.2.2 Attribute: chapnbr

Description: Identification number of a chapter. For documents defined by ATA
maintenance specifications this is a 2 digit number (00 up to 99) as
defined in ATA. For other documents this number (or other code) will
be assigned by the data creator. All anchor elements within a chapter
will be identified with the number of its parent chapter.

1.2.3 Attribute: sectnbr

Description: Identification number of a section. For documents defined by ATA
maintenance specifications this is a 2 digit number (00 up to 99) as
defined in ATA. For other documents this number (or other code) will
be assigned by the data creator. All anchor elements within a section
will be identified with the number of its parent section.

1.2.4 Attribute: subjnbr

Description: Identification number of a subject. A 2 digit number (00 up to 99) as
defined in ATA Spec 100. SUBJECT: gives the number associated
with the SUBJECT to which this attribute applies. All others: gives the
number of the parent SUBJECT which contains the element to which
this attribute applies. Also forms the third element of the AMTOSS/
JEMTOSS number where applicable.

Rev #26 01/13/21 D6-82973

Page -121
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRAPHIC

1.2.5 Attribute: func

Description: Identifies the fourth element of a task or subtask (xx-xx-xx-XXX- xxx-
xxx-xxx). Numerical representation of the function corresponding to
the task/subtask. Also, a numerical representation of the function for
which a product or a tool is used.

1.2.6 Attribute: seq

Description: Identifies the fifth element of a task or subtask (xx-xx-xx-xxx- XXX-
xxx-xxx). Numerical representation of the chronological sequence
number of the task or subtask within a subject and function code
combination.

1.2.7 Attribute: confltr

Description: Identifies the first character of a three character element of sixth
position of task or subtask (xx-xx-xx-xxx-xxx-Xxx-xxx). Used when
the accomplishment of a task/subtask requires different procedures or
maintenance resources.

Boeing Application Rules:

a. confltr values will be alpha characters or “0” (zero).

NOTE: confltr is based on the engine configuration of an aircraft. If an airline has

more than one engine configuration for an aircraft, the configuration letter will reflect
the engine type. Reference the Engine Logo Translation Table in the effect element for
valid values.

b. If varnbr is available in the source data but confltr is not, the confltr attribute will
be provided as zero (i.e., confltr=“0”) and varnbr will be provided as a 2-digit
numeric value (e.g., varnbr=“01”). If varnbr is not available in the source data but
confltr is, confltr will be an alpha character (e.g., R, N, or G, ect.) and varnbr will
be 00 (i.e., varnbr=“00”). When both the varnbr and confltr are available in the
source data, varnbr will be provided as a 2-digit numeric value and confltr will be
provided as a 1-digit alpha value. When both the varnbr and confltr are not
available in the source data, their attributes will not be provided in the SGML.
c. In engine chapters and the APU Chapter 49, the confltr attribute is sometimes
referred to as the engine prefix. confltr will contain alpha values in
chapters 49 and 70-89.

1.2.8 Attribute: varnbr

Description: The last two digits of a three character element at the sixth position of a
task or subtask number (xx-xx-xx-xxx-xxx-xXX-xxx). Identifies
variants of a particular sequence number of a task or subtask.

Rev #26 01/13/21 D6-82973

Page -122
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRAPHIC

Boeing Application Rules:

a. If varnbr is available in the source data but confltr is not, the confltr attribute will
be provided as zero (i.e., confltr=“0”) and varnbr will be provided as a 2-digit
numeric value (e.g., varnbr=“01”). If varnbr is not available in the source data but
confltr is, confltr will be an alpha character (e.g., R, N, or G, ect.) and varnbr will
be 00 (i.e., varnbr=“00”). When both the varnbr and confltr are not available in the
source data, their attributes will not be provided in the SGML.

1.2.9 Attribute: alunqi

Description: Identifies the code found in the seventh element of task or subtask (xx-
xx-xx-xxx-xxx-xxx-XXX) when a customer originated change has
been incorporated. Normally, this will not be generated by the
manufacturer and in most cases will be left empty.

1.2.10 Attribute: pgblknbr

Description: Identification number of a pageblock.
• NUMBER : 2-digit number (00 up to 99) as defined in ATA
Spec100 2-1-1 or 2-13-1. This is to allow consistent indexing and
retrieval methods across different systems. The AMM document
instance will always use a number between 00 and 09. A single
digit is not permitted.
• PGBLK : gives the number associated with the PGBLK to which
this attribute applies. All others gives the number of the parent
PGBLK which contains the element to which this attribute applies.
Also forms part of the index number where applicable.

1.2.11 Attribute: confnbr

Description: Identifies a unique configuration of a pageblock. This is NOT the same
as the AMTOSS/JEMTOSS configuration letter.

1.2.12 Attribute: id
Description: Identifying unique number to allow direct SGML cross-referencing to
be performed from the REFID attribute.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Page -128
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRAPHIC

1.4 BOEING IMPLEMENTATION RULES

a. Graphic titles are only provided using the optional <title> of the <graphic>
element. The content may be all upper-case or mixed-case, depending on the
document type and airplane model.
b. It is up to the data recipient to generate the string “Figure” as well as the correct
sequence number for the <graphic>. The <seqnum> element content can be used
for the correct sequence number.
c. In general, all graphics associated with a taskcard are collected and placed at the
end of the taskcard.

Example:
Taskcard xx-xxx-xx-xx
Task A (Removal)
Reference to Figure 1
Reference to Figure 2
Task B (Installation)
Reference to Figure 1
Reference to Figure 2
Task C
Reference to Figure 3
(End of all tasks)
Figure 1
Figure 2
Figure 3
End of Taskcard

d. The figure number associated with the illustration and seqnum are renumbered
within the taskcard; therefore, they may not match the corresponding figure
number found in the AMM.
e. Graphic titles may contain a figure number. This number is auto-generated by the
system and placed in the <title> element (e.g., Figure 601.). The period “.” can be
suppressed by the receiving system, if desired.

Rev #26 01/13/21 D6-82973

Page -129
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRPHCREF

1.0 ELEMENT NAME

grphcref - Graphic Reference

1.1 ELEMENT CONTENT

<!ELEMENT grphcref - - (effect?, #PCDATA) >

This tag identifies the text describing a reference to a graphic. The grphcref element
appears in the context of the following element:

ENTITIES ELEMENT

para

refblock

%g.r task

topic

subtask

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT grphcref - - (effect?, #PCDATA) >
<!ATTLIST grphcref
refid IDREF #IMPLIED
sheetnbr CDATA #IMPLIED
shownow %yesorno; "0"
structid CDATA #IMPLIED >

Attribute Name Always Provided Provided When Data is

Available

refid X

sheetnbr X

shownow X

structid X

Rev #26 01/13/21 D6-82973

Page -130
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRPHCREF

1.2.1 Attribute: refid

Description: grphcref refid identifies the graphic element that is being referenced.

Boeing Application Rules:

a. The value of the REFID attribute on the <grphcref> matches the value of the ID
attribute on a <graphic> or <sheet>.

1.2.2 Attribute: sheetnbr

Description: The sequential (but not necessarily contiguous) number of a sheet
within a graphic. Can be used to link a graphic reference to a particular
sheet or image within the set of sheets in a graphic.

1.2.3 Attribute: shownow

Description: The graphic referenced is intended to be displayed at the point of the
graphic reference element sheet or image within the set of sheets in a
graphic.

1.2.4 Attribute: structid

Description: An identifier by which the graphical structure can be uniquely
referenced.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -131
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRPHCREF

SGML:
<subtask chapnbr="72" sectnbr="21" subjnbr="00" func="210" seq="002"
confltr="H01" pgblknbr="6" id="D8739E9C29809320537546734CDBBCFB">
<effect effrg="901902" efftext="ZAP 901, 902">
</effect>
<list1>
<l1item>
<para>Examine the fan blade metal leading edge nose in Area [N1] (<grphcref
refid="L05D764F2596845E24016ACE384FA382">Figure 602</grphcref>):</para>

1.3.2 Element: refblock

<!ELEMENT refblock - - (#PCDATA | refint | refext | grphcref)*>

Printed Example:

1.3.3 Element: task

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

Similar to refblock, refer to 1.3.2 for examples.

Rev #26 01/13/21 D6-82973

Page -132
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRPHCREF

1.3.4 Element: topic

<!ELEMENT topic - - (effect?, title, %g.r;, %w.c;, note*,
subtask*) >

Not used.

1.3.5 Element: subtask

<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect)

Not used.

Rev #26 01/13/21 D6-82973

Page -133
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRSYMBOL

1.0 ELEMENT NAME

grsymbol - Inline Graphic

1.1 ELEMENT CONTENT

<!ELEMENT grsymbol - O EMPTY >

The grsymbol element is a mechanism to deliver inline graphical symbols. The

grsymbol element appears in the context of the following element:

ELEMENT

regulation

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT grsymbol - O EMPTY >
<!ATTLIST grsymbol
gnbr ENTITY #REQUIRED
reprowid CDATA #IMPLIED
reprohgt CDATA #IMPLIED
reproscl CDATA #IMPLIED >

Attribute Name Always Provided Provided When Data

is Available

gnbr X

reprowid X

reprohgt X

reproscl X

1.2.1 Attribute: gnbr

Description: This is used to identify a sender-assigned identification of a graphic
(sheet).

Rev #26 01/13/21 D6-82973

Page -134
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

GRSYMBOL

1.2.2 Attribute: reprowid

Description: The physical dimension of the width of the image space of an inline
graphic.

1.2.3 Attribute: reprohgt

Description: The physical dimension of the Height of the image space of an inline
graphic.

1.2.4 Attribute: reproscl

Description: Reproduction scaling (yes/no).

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: regulation

<!ELEMENT regulation - - (effect?, grsymbol?, #PCDATA) >

Printed Example:

SGML:
<task CHAPNBR="05" SECTNBR="00" SUBJNBR="00" FUNC="200" SEQ="806"
PGBLKNBR="2" CHG="N" KEY="JF67BC888B5E89FB060B8F427953378F"
REVDATE="20150314">
<effect EFFRG="104105" EFFTEXT="ZAP 104, 105">
</effect>
<title>Scheduled Maintenance Task</title>
<regulatory>
<regulation REGTYPE="CMR" REGVALUE="72-CMR-03"><grsymbol
GNBR="REGULATORY">72-CMR-03</regulation>
</regulatory>
. . .
</task>

Rev #26 01/13/21 D6-82973

Page -135
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

HAZMT

1.0 ELEMENT NAME

hazmt - Hazardous Material

1.1 ELEMENT CONTENT

<!ELEMENT hazmt - - (title, warning) >

The hazmt element provides the hazardous material information. The hazmt element
appears in the context of the following element:

ELEMENT

hazmtlst

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure
<!ELEMENT hazmt - - (title, warning) >
<!ATTLIST hazmt
id ID #REQUIRED >

Attribute Name Always Provided Provided When Data

is Available

id X

1.2.1 Attribute: id
Description: Identifying unique number to allow direct SGML cross-referencing to
be performed from the REFID attribute.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -136
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

HAZMT

1.3.1 Element: hazmtlst

<!ELEMENT hazmtlst - - (title, pretopic*, hazmt+) >

Printed Example:

SGML:
<hazmtlst>
. . .
<hazmt id="J3199FAE10257D40E539EE4ABC6AC519">
<title>HZ1000—REFER TO MSDS </title>
. . .
</hazmt>
</hazmtlst>

Rev #26 01/13/21 D6-82973

Page -137
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

HAZMTLST

1.0 ELEMENT NAME

hazmtlst - Hazardous Material List

1.1 ELEMENT CONTENT

<!ELEMENT hazmtlst - - (title, pretopic*, hazmt+) >

The hazmtlst element provides the hazardous material list information. The hazmtlst
element appears in the context of the following element:

ELEMENT

tcbody

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT hazmtlst - - (title, pretopic*, hazmt+) >
<!ATTLIST hazmtlst
id ID #REQUIRED >

Attribute Name Always Provided Provided When Data

is Available

id X

1.2.1 Attribute: id
Description: Identifying unique number to allow direct SGML cross-referencing to
be performed from the REFID attribute.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -138
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

HAZMTLST

1.3.1 Element: tcbody

<!ELEMENT tcbody - - (tccat?, taskproc?, mpditem*,
pretsmry?, hazmtlst?, (task* | refext*))>

Printed Example:

...

SGML:
<taskcard cardnbr="05-038-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000018891">
<effect effrg="001999">
</effect>
. .
<tcbody>
. . .
<hazmtlst id="D0A23E9DECC9EABCF5F7764A0B207C2C">
<title>Hazardous Material Warnings</title>
<pretopic>
<title>General</title>
<list1>
<l1item>
<para>This section has the HAZMAT
warnings for the 717 Aircraft Maintenance Manual.</para>
. . .

Rev #26 01/13/21 D6-82973

Page -139
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

HAZMTLST

<hazmt id="J3199FAE10257D40E539EE4ABC6AC519">
<title>HZ1000—REFER TO MSDS </title>
<warning>
<para>REFER TO THE APPLICABLE MANUFACTURER'S OR SUPPLIER'S MSDS FOR:</para>
<unlist>
<unlitem>
<para>MORE PRECAUTIONARY DATA</para>
</unlitem>
<unlitem>
<para>APPROVED SAFETY EQUIPMENT</para>
</unlitem>
<unlitem>
<para>EMERGENCY MEDICAL AID.</para>
</unlitem>
</unlist>
<para>TALK WITH THE LOCAL SAFETY DEPARTMENT OR AUTHORITIES FOR THE PROCEDURES
TO DISCARD THIS HAZARDOUS AGENT.</para>
</warning>
</hazmt>
<hazmt id="O5052CEE8BFBDD2660B9B044737F0D82">
<title>HZ1319—CLEANER/LIQUID DETERGENT (DPM 5216)</title>
<warning>
<para>LIQUID DETERGENT CLEANER IS AN AGENT THAT IS AN IRRITANT. MAKE SURE ALL
PERSONS OBEY THE PRECAUTIONS WHEN LIQUID DETERGENT CLEANER IS USED.</para>
<unlist>
<unlitem>
<para>DO NOT USE IN AREAS WHERE THERE IS HIGH HEAT, SPARKS, OR FLAMES.</para>
</unlitem>
<unlitem>
<para>USE IN AN AREA OPEN TO THE AIR.</para>
</unlitem>
<unlitem>
<para>CLOSE THE CONTAINER WHEN NOT USED.</para>
</unlitem>
<unlitem>
<para>DO NOT GET LIQUID DETERGENT CLEANER IN THE EYES, ON THE SKIN, OR ON YOUR
CLOTHES.</para>
</unlitem>
<unlitem>
<para>DO NOT BREATHE THE GAS.</para>
</unlitem>
</unlist>
</warning>
</hazmt>
</hazmtlst>
</tcbody>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -140
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

HOLDER

1.0 ELEMENT NAME

holder - Holder

1.1 ELEMENT CONTENT

<!ELEMENT holder - - (#PCDATA) >

The holder element contains PCDATA to hold any form of information needed to
identify a copyright holder in text. The holder element appears in the context of the
following element:

ELEMENT

cpyrght

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: cpyrght

<!ELEMENT cpyrght - - (year*, holder*, geninfo) >

Printed Example:

SGML:
<legalntc CHG="N" KEY="T-legalntc" REVDATE="20030210">
<proptary>
<fullstmt>
<title>BOEING PROPRIETARY, CONFIDENTIAL, AND/OR TRADE SECRET</title>
<cpyrght>

Rev #26 01/13/21 D6-82973

Page -141
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

HOLDER

<year>1997</year>
<holder>The Boeing Company</holder>
<geninfo>
<para>Unpublished Work - All Rights Reserved</para>
<para>Boeing claims copyright in each page of this document only to the
extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para></geninfo></cpyrght>
<para>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, WA 98124.
</para></fullstmt></proptary>
<geninfo>
<para>Boeing, the Boeing signature, the Boeing symbol, 707, 717, 727, 737,
747, 757, 767, 777, BBJ, DC-8, DC-9, DC-10, MD-10, MD-11, MD-80, MD-88, MD-90
and the red-white-and-blue Boeing livery are all trademarks owned by The
Boeing Company; and no trademark license is granted in connection with this
document unless provided in writing by Boeing.</para></geninfo></legalntc>

Rev #26 01/13/21 D6-82973

Page -142
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

HOTLINK

1.0 ELEMENT NAME

hotlink - Hotlink

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT hotlink - o EMPTY >

The hotlink element, only for use by retrieval engines, is not to be used in interchange
SGML document instances. During data preparation by a retrieval software vendor,
the cross links between references in a document instance must be coded for that
particular software and set of documents. This element allows a target and source to be
encoded in whatever format is necessary for that software. Because it is an inclusion at
the manual level, it can be used to code all implicit as well as explicit references. Its
exact use and positioning is entirely dependent on the requirements of the retrieval
engine’s requirements and so is not defined in this document. The hotlink element
appears in the context of the following element:

ELEMENT

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT hotlink - o EMPTY >
<!ATTLIST hotlink
targetrefidCDATA #IMPLIED
targetid CDATA #IMPLIED >

Rev #26 01/13/21 D6-82973

Page -143
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

INTDATA

1.0 ELEMENT NAME

intdata - Interval Data

1.1 ELEMENT CONTENT

<!ELEMENT intdata - - ((interval+, intnote?) | intnote) >

The intdata element is the interval data and its accompanying note. The intdata
element appears in the context of the following element.

ELEMENT

mainhead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Page -146
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

INTERVAL

1.0 ELEMENT NAME

interval - Interval

1.1 ELEMENT CONTENT

<!ELEMENT interval - - (version, thrshold, repeat?, phase?)>

The interval element is the periodic frequency of a task accomplishment identified in

the MPD. It contains interval data such as version initial threshold, sample interval,
repeat interval and phase. It defines the scheduling frequency of a given task,
including the repeating interval and the sampling value. The interval element appears
in the context of the following element.

1.0 ELEMENT NAME

intnote - Interval Note

1.1 ELEMENT CONTENT

<!ELEMENT intnote - - (%text;) >

The intnote element is the interval note which accompanies the interval data. The
intnote element appears in the context of the following element.

ELEMENT

intdata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Page -152
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ISO_ENTITY

1.0 ENTITY NAMES

ISO - ATA Public Entities:
ISOpub, ISOnum, ISOtech, ISOgrk1-ISOgrk4, ISOlat1

1.1 ENTITY CONTENT

ATA Entities:
• ISOpub: Publishing Entities
• ISOnum: Numeric and Special Graphic
• ISOtech: General Technical Entities
• ISOgrk1: Greek Letter Entities
• ISOgrk2: Monotoniko Greek Entities
• ISOgrk3: Greek Symbol Entities
• ISOgrk4: Alternative Gree Symbol Entities
• ISOlat1: Added Latin Entities

NON-ATA PUBLIC ENTITY SETS THAT ARE USED BY BOEING

<!ENTITY boxv SDATA “[boxv ]”--=vertical line-->
<!ENTITY sime SDATA “[sime ]”--=tilde, overline-->
<!ENTITY curren SDATA “[curren ]”--=currency sign-->
<!ENTITY lang SDATA “[lang ]”--=angle bracket-->
<!ENTITY sfcircle SDATA “[sfcircle]”--=small filled circle-->
<!ENTITY lfcircle SDATA “[lfcircle]”--=large filled circle-->
<!ENTITY laquo SDATA “[laquo ]”--=left angle quot. mark-->
<!ENTITY aacute SDATA “[aacute ]”--=small a w/ acute sign-->
<!ENTITY raquo SDATA “[raquo ]”--=right angle quot. mark-->
<!ENTITY frac14 SDATA “[frac14 ]”--=1/4-->
<!ENTITY frac12 SDATA “[frac12 ]”--=1/2-->
<!ENTITY frac34 SDATA “[frac34 ]”--=3/4-->
<!ENTITY infin SDATA “[infin ]”--=infinity symbol-->
<!ENTITY prop SDATA “[prop ]”--=varies as-->
<!ENTITY dif SDATA “[dif ]”--=differance-->
<!ENTITY bottom SDATA “[bottom ]”--=perpendicular-->
<!ENTITY sub0 SDATA “[sub0 ]”--=subscript zero-->
<!ENTITY sub1 SDATA “[sub1 ]”--=subscript one-->
<!ENTITY sub2 SDATA “[sub2 ]”--=subscript two-->
<!ENTITY sub3 SDATA “[sub3 ]”--=subscript three-->
<!ENTITY sub4 SDATA “[sub4 ]”--=subscrift four-->
<!ENTITY sub5 SDATA “[sub5 ]”--=subscript five-->
<!ENTITY sub6 SDATA “[sub6 ]”--=subscript six-->
<!ENTITY sub7 SDATA “[sub7 ]”--=subscript seven-->
<!ENTITY sub8 SDATA “[sub8 ]”--=subscript eight-->
<!ENTITY sub9 SDATA “[sub9 ]”--=subscript nine-->
<!ENTITY centln SDATA “[centln ]”--=center line-->
<!ENTITY boxul SDATA “[boxul ]”--=box - top left-->
<!ENTITY boxdl SDATA “[boxdl ]”--=box - lower left-->
<!ENTITY boxur SDATA “[boxur ]”--=box - top right-->
<!ENTITY boxdr SDATA “[boxdr ]”--=box - lower right-->
<!ENTITY times SDATA “[times ]”--=multiplication-->

Rev #26 01/13/21 D6-82973

Page -153
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ISO_ENTITY

<!ENTITY Uuml SDATA “[Uuml ]”--=capital U w/ diaresis-->

<!ENTITY agr SDATA “[agr ]”--=lower case alpha-->
<!ENTITY ggr SDATA “[ggr ]”--=lower case gamma-->
<!ENTITY dgr SDATA “[dgr ]”--=lower case delta-->
<!ENTITY egr SDATA “[egr ]”--=lower case epsilon-->
<!ENTITY ccedil SDATA “[ccedil ]”--=lower case c w/ cedilla-->
<!ENTITY thgr SDATA “[thgr ]”--=lower case theta-->
<!ENTITY eacute SDATA “[eacute ]”--=small e,accent acute-->
<!ENTITY lgr SDATA “[lgr ]”--=lower case lambda-->
<!ENTITY sgr SDATA “[sgr ]”--=lower case sigma-->
<!ENTITY divide SDATA “[divide ]”--=divided by-->
<!ENTITY lowbar SDATA “[lowbar ]”--=lowline-->
<!ENTITY PSgr SDATA “[PSgr ]”--=upper case psi-->
<!ENTITY Urcorn SDATA “[Urcorn ]”--=upper rt corner, heavy-->
<!ENTITY ndash SDATA “[ndash ]”--=en dash-->
<!ENTITY Ndash SDATA “[Ndash ]”--=en dash, heavy-->
<!ENTITY verbar SDATA “[verbar ]”--=vertical bar-->

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -154
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LEGALNTC

1.0 ELEMENT NAME

legalntc - Legal Notice

1.1 ELEMENT CONTENT

<!ELEMENT legalntc - - (exprtcl | cpyrght | proptary | geninfo)+>

The legalntc element is a container element to support the need to identify export
control and copyright information. The legalntc element appears in the context of the
following element:

ELEMENT

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT legalntc - - (exprtcl | cpyrght | proptary | geninfo)+>
<!ATTLIST legalntc
%revatt; >

Attribute Name Always Provided Provided When Data

is Available

%revatt X

1.2.1 Attribute: %revatt

Description: %revatt is the group of attributes needed for sending revision
information for incremental updates or a complete re-issue of manual
with revisions. The revision attributes are applied to each anchor.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -155
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LEGALNTC

Printed Example:

SGML:
<tc chg="R" docnbr="D633A109-ZAP" cusname="ZAP Airlines, Inc." cus="ZAP"
oidate="19980605" lang="EN" model="737-600/700/800/900" revdate="20031010"
spl="81205" tsn="21A">
<legalntc CHG="N" KEY="T-legalntc" REVDATE="20030210"><proptary>
<fullstmt>
<title>BOEING PROPRIETARY, CONFIDENTIAL, AND/OR TRADE SECRET</title>
<cpyrght>
<year>1994</year>
<holder>The Boeing Company</holder>
<geninfo>
<para>Unpublished Work - All Rights Reserved</para>
<para>Boeing claims copyright in each page of this document only to the
extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para></geninfo></cpyrght>
<para>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, WA 98124.
</para></fullstmt></proptary>
<geninfo>
<para>Boeing, the Boeing signature, the Boeing symbol, 707, 717, 727, 737,
747, 757, 767, 777, BBJ, DC-8, DC-9, DC-10, MD-10, MD-11, MD-80, MD-88, MD-90
and the red-white-and-blue Boeing livery are all trademarks owned by The
Boeing Company; and no trademark license is granted in connection with this
document unless provided in writing by Boeing.</para></geninfo></legalntc>
. . .
</tc>

Rev #26 01/13/21 D6-82973

Page -156
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LEGALNTC

1.3.2 Element: tr
<!ELEMENT tr - - (legalntc?, trfmatr, (legalntc|taskcard))>

Examples not available at this time

Rev #26 01/13/21 D6-82973

Page -157
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LINSPECT

1.0 ELEMENT NAME

linspect - Level of Inspection

1.1 ELEMENT CONTENT

<!ELEMENT linspect - - (#PCDATA) >

The linspect element identifies the task level of inspection. The linspect element
appears in the context of the following element.

ELEMENT

mpditem

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -158
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LINSPECT

1.3.1 Element: mpditem

<!ELEMENT mpditem - - (mpdnbr, taskloc?, linspect?, title?,
taskdesc?, ch5tskno?, awlimit?,
supldata) >

Printed Example: The mpditem information does not appear on the printed taskcard.

Rev #26 01/13/21 D6-82973

Page -159
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LISTX

1.0 ELEMENT NAME

listX - List of Level X (1 - 7)

1.1 ELEMENT CONTENT

<!ELEMENT list1 - - (l1item+) >
<!ELEMENT list2 - - (l2item+) >
<!ELEMENT list3 - - (l3item+) >
<!ELEMENT list4 - - (l4item+) >
<!ELEMENT list5 - - (l5item+) >
<!ELEMENT list6 - - (l6item+) >
<!ELEMENT list7 - - (l7item+) >

The element listx identifies a set of ordered items of level “x” (lxitem). The level
number refers to the nesting level of the listx within other lists (logical level of
identification). In this case, list1 is the topmost level of a list structure that can go
seven levels deep. The listX element appears in the context of the following elements:

ELEMENT

pretopic

subtask

l1item through l7item

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: pretopic

<!ELEMENT pretopic - - (title, (%text; | list1)) +(effect) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -160
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LISTX

SGML:
<task chapnbr="05" sectnbr="55" subjnbr="25" func="200" seq="801"
pgblknbr="6" id="H42DC148517781F1ED7FDA09FAD4BF9F">
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AY 3BA3BH 3BJ3BN 3BP3BP 3BR3BY 3CA3CH
3CJ3CN 3CP3CP 3CR3CY 3DA3DH 3DJ3ZZ" efftext="ZAP ALL">
</effect>
<title>Wire Bundle Inspection - Left Main Landing Gear</title>
<refblock>(<grphcref
refid="OA3F75E015FE883B61A2D45470C43EAB">Figure 601</grphcref>)
</refblock>
<tfmatr>
<pretopic>
<title>General</title>
<list1>
<l1item>
<para>A General Visual Inspection is a visual check of specified details
associated with assemblies or installations.</para>
. . .
</list1>
</pretopic>

1.3.2 Element: subtask

<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect)

Printed Example:

SGML:
<subtask chapnbr="05" sectnbr="55" subjnbr="25" func="010" seq="001"
pgblknbr="6" id="H4A944408911B7CA7CDE99BCBED8EEDA">
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AY 3BA3BH 3BJ3BN 3BP3BP 3BR3BY 3CA3CH
3CJ3CN 3CP3CP 3CR3CY 3DA3DH 3DJ3ZZ" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Make sure the MLG and Doors are locked open.</para>
</l1item>
</list1>
</subtask>

Rev #26 01/13/21 D6-82973

Page -161
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LISTX

1.3.3 Element: l1item-l7item

Printed Example:

SGML:
<subtask chapnbr="06" sectnbr="00" subjnbr="01" func="916" seq="002"
pgblknbr="6" id="L39D9E4D57642C65C9707949B1F6F0D8">
<effect effrg="001099 301999" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>This inspection is accomplished from the ground and starts at the front
of the airplane, proceeds around the left side of the airplane and ends back
at the front as shown in <grphcref
refid="J1CED53BA8817CBAB6D99C99A7975351">Figure 601</grphcref>.
</para>
<list2>
<l2item>
<para>Check forward fuselage, radome, left and right wing leading edge for
damage. Check radome for security and burned lightning
diverter strips.</para>
</l2item>
<l2item>
<para>Check the pitot tubes, angle of attack sensor and antennas for damage;
drains for leaks.</para>
</l2item>
. . .
</list2>

Rev #26 01/13/21 D6-82973

Page -162
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LISTX

. . .
</l1item>
</list1>

Rev #26 01/13/21 D6-82973

Page -163
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LXITEM

1.0 ELEMENT NAME

lXitem - Item of a List of Level X

1.1 ELEMENT CONTENT

The element lXitem identifies a set of ordered items of level “X” (lXitem). The level
number refers to the nesting level of the listx within other lists (logical level of
identification). The lXitem element appears in the context of the following element:

ELEMENT

listX

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -164
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

LXITEM

1.3.1 Element: listx

Printed Example:

Rev #26 01/13/21 D6-82973

Page -165
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MAINHEAD

1.0 ELEMENT NAME

mainhead - Main Heading

1.1 ELEMENT CONTENT

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

The mainhead element is the task card heading data for all task cards except the
component change or remove/replace task card. The mainhead element appears in the
context of the following element.

ELEMENT

taskcard

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -166
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MAINHEAD

1.3.1 Element: taskcard

Printed Example:

SGML:
<tc chg="R" docnbr="ME717-009-ZAP" cusname="ZAP Airlines" cus="ZAP"
oidate="20021106" lang="EN" model="717" revdate="20021106" spl="88277"
tsn="1">
<title>TASKCARDS</title>
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>
<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
. . .
</mainhead>
. . .
</taskcard>
. . .
</tc>

Rev #26 01/13/21 D6-82973

Page -167
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MANHOURS

1.0 ELEMENT NAME

manhours - Man Hours

1.1 ELEMENT CONTENT

<!ELEMENT manhours - - (#PCDATA) >

The manhours element identifies the estimated time required to accomplish an aircraft
task, excluding open/close access. The manhours element appears in the context of the
following element.

ELEMENT

supldata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: supldata

<!ELEMENT supldata - - (manhours, nbrpeopl, elaptime,
tc_manhours?, tc_nbrpeopl?,
tc_elaptime?, taskctgy?, feftctgy*)>

Printed Example: The mpditem information does not appear on the printed taskcard.

Rev #26 01/13/21 D6-82973

Page -168
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MANHOURS

Rev #26 01/13/21 D6-82973

Page -169
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MNTCYCLE

1.0 ELEMENT NAME

mntcycle - Maintenance Cycle

1.1 ELEMENT CONTENT

<!ELEMENT mntcycle - - (#PCDATA) >

The mntcycle element is the period of time which all checks are accomplished, after
which the maintenance program essentially repeats itself. The mntcycle element
appears in the context of the following element.

ELEMENT

phase

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: phase

<!ELEMENT phase - - (mntcycle, pthrshld, prepeat) >

Printed Example: mntcycle is not viewable on the printed task card

Rev #26 01/13/21 D6-82973

Page -170
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MNTCYCLE

Rev #26 01/13/21 D6-82973

Page -171
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MNTCYCLE

<multiple>5250</multiple>
<unit>DY</unit>
<sample>100</sample>
</thrshold>
<repeat>
<thrshtyp>N</thrshtyp>
<multiple>750</multiple>
<unit>DY</unit>
<sample>100</sample>
</repeat>
</interval>
<intnote>
<para>Initial threshold and repeat is 12000 flight cycles or 2250 days
(whichever comes first) until 28000 flight cycles or 5250 days (whichever
comes first) is reached. From this point on the repeat interval of 4000
flight cycles or 750 days is applicable.</para>
</intnote>
</intdata>

Rev #26 01/13/21 D6-82973

Page -172
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MPDITEM

1.0 ELEMENT NAME

mpditem - MPD Item

1.1 ELEMENT CONTENT

<!ELEMENT mpditem - - (mpdnbr, taskloc?, linspect?, title?,
taskdesc?, ch5tskno?, awlimit?,
supldata) >

The mpditem element identifies the recommended scheduled maintenance MPD task
with its number. This element is an optionally repeating element which includes
mpdnbr, task location, level of inspection, title, task description, chapter 5 task number
and airworthiness limitation. The mpditem element appears in the context of the
following element.

ELEMENT

tcbody

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -173
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MPDITEM

1.3.1 Element: tcbody

<!ELEMENT tcbody - - (tccat?, taskproc?, mpditem*,
pretsmry?, hazmtlst?, (task* | refext*))>

Printed Example: The mpditem information does not appear on the printed task card.

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
. . .
<tcbody>
<taskproc>
<para>Functionally check the Lower Lobe Attendant Rest (LLAR) Back-up
Lighting System Battery Pack for proper capacity (perform time loading
test).</para>
</taskproc>
<mpditem>
<mpdnbr>05-002-00</mpdnbr>
<taskloc>EXTERNAL</taskloc>
<linspect>DETAILED</linspect>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<taskdesc>
<para>Functionaly check the Lower Lobe Attendant Rest (LLAR) Back-up LIghting
System Battery Pack for proper capacity (perform time loading test).</para>
</taskdesc>
<supldata>
. . .
</mpditem>
. . .
</tcbody>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -174
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MPDNBR

1.0 ELEMENT NAME

mpdnbr - MPD Item Number

1.1 ELEMENT CONTENT

<!ELEMENT mpdnbr - - (#PCDATA) >

The mpdnbr element identifies the MPD item number of the task listed. The mpdnbr
element appears in the context of the following element.

ELEMENT

mpditem

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: mpditem

<!ELEMENT mpditem - - (mpdnbr, taskloc?, linspect?, title?,
taskdesc?, ch5tskno?, awlimit?,
supldata) >

Printed Example: The mpditem information does not appear on the printed task card.

Rev #26 01/13/21 D6-82973

Page -175
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MPDNBR

System Battery Pack for proper capacity (perform time loading test).</para>
</taskdesc>
<supldata>
. . .
</mpditem>
. . .
</tcbody>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -176
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MULTIPLE

1.0 ELEMENT NAME

multiple - Multiple

1.1 ELEMENT CONTENT

<!ELEMENT multiple - - (#PCDATA) >

The multiple element is the number of units of a particular interval. The multiple
element appears in the context of the following elements:

ELEMENT

thrshold

repeat

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Elements: thrshold and repeat

<!ELEMENT thrshold - - (thrshtyp, ((multiple, unit, sample)
| optask)) >
<!ELEMENT repeat - - (thrshtyp, multiple, unit, sample) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -177
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

MULTIPLE

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>
<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
<intdata>
<interval>
<version>1.1</version>
<thrshold>
<thrshtyp>N</thrshtyp>
<multiple>100</multiple>
<unit>FC</unit>
<sample>100</sample>
</thrshold>
<repeat>
<thrshtyp>N</thrshtyp>
<multiple>100</multiple>
<unit>FC</unit>
<sample>100</sample>
</repeat>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -178
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NBRPEOPL

1.0 ELEMENT NAME

nbrpeopl - Number of People

1.1 ELEMENT CONTENT

<!ELEMENT nbrpeopl - - (#PCDATA) >

The nbrpeopl element identifies the number of people performing the task on the
airplane. The nbrpeopl element appears in the context of the following element.

ELEMENT

supldata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: supldata

<!ELEMENT supldata - - (manhours, nbrpeopl, elaptime,
tc_manhours?, tc_nbrpeopl?,
tc_elaptime?, taskctgy?, feftctgy*)>

Printed Example: The mpditem information does not appear on the printed taskcard.

Rev #26 01/13/21 D6-82973

Page -179
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

Page -183
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NOTE

1.0 ELEMENT NAME

note - Note

1.1 ELEMENT CONTENT

<!ELEMENT note - - (%text;) -(note) +(effect) >

The note element is used to identify a “note.”According to the ATA Spec. 2200
warnings, cautions, and notes shall be applied as follows:

All notes shall be in upper and lower case letters and preceded by the word NOTE in
caps and underlined.

Example: NOTE: It is not necessary to relieve pressure.

All cautions shall be printed in capital letters throughout and is preceded with the word
CAUTION in capital letters and underlined.

Example: CAUTION: DO NOT OPERATE CONTROLS.

All warnings shall be printed in capital letters and boldface throughout and is preceded
with the word WARNING in bold capital letters and underlined.

Example: WARNING: SOLUTION IS EXTREMELY FLAMMABLE.

Rev #26 01/13/21 D6-82973

Page -184
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NOTE

The note element appears in the context of the following elements:

ENTITY ELEMENT

exprtcl

geninfo

task

topic

subtask
l1item - l6item

(In %text) intnote

apapnote
eappnote

acpanote

taskproc
taskdesc

pretopic

entry

l1item - l7item

ftnote

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -185
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NOTE

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: exprtcl

<!ELEMENT exprtcl - - (para | unlist | numlist | note)+ >

Not used.

1.3.2 Element: geninfo

<!ELEMENT geninfo - - (para | unlist | numlist | note)+ >

Not used.

1.3.3 Element: task

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

Printed Example:

SGML:
<task chapnbr="27" sectnbr="41" subjnbr="00" func="700" seq="808"
pgblknbr="5" id="CB89CBFA59E9AE9CAC34FBE03AC2E958">
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AY 3BA3BH 3BJ3BN 3BP3BP 3BR3BY 3CA3CH
3CJ3CN 3CP3CP 3CR3CY 3DA3DH 3DJ3ZZ" efftext="ZAP ALL">
</effect>
<title>Stabilizer Trim Secondary Brake System Test</title>
<refblock>(<grphcref
refid="K53CD45C4322DF58701EDEFD8FCEEFB0">Figure 505</grphcref>)
</refblock>
<note>
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AS" efftext="ZAP 3AA-3AH, 3AJ-3AN,
3AP, 3AR, 3AS PRE SB 737-27-1210; HORIZONTAL STABILIZER
TRIM ACTUATOR WITH PRIMARY BRAKE ONLY">
</effect>
<para>See <grphcref
refid="FC1CD309F7F31FF5EA1AB179AA00F51E">Figure 506</grphcref>.</para>

Rev #26 01/13/21 D6-82973

Page -186
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NOTE

</note>
. . .
</task>

1.3.4 Element: topic

<!ELEMENT topic - - (effect?, title, %g.r;, %w.c;, note*,
subtask*) >

Printed Example:

SGML:
<topic>
<title>Positive Pressure Relief Valve - System Test</title>
<note>
<para>This test can only be done on one relief valve at a time. Do the test on
the outboard relief valve, then do the test again o
n the inboard relief valve.</para>
</note>
. . .
</topic>

1.3.5 Element: subtask

<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect)

Not used.

Rev #26 01/13/21 D6-82973

Page -187
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NOTE

<!ELEMENT pretopic - - (title, (%text; | list1)) +(effect) >

Not used.

1.3.14 Element: entry

<!ELEMENT entry - o (regulatory | %text; | %w.c;
| graphic)* >

Printed Example:

...

SGML:
<subtask chapnbr="12" sectnbr="21" subjnbr="15" func="420" seq="001"
confltr="0" varnbr="01" pgblknbr="3" id="B961A575EB02559DCC81
09F2E26E43E2">
<effect effrg="HNAZZZ" efftext="ZAP ALL">
</effect>
. . .
<table frame="ALL" id="OAA6C4FC7EDADDD647D0957345119D49">
<seqnum>301</seqnum>
<title><revst>Table 301. <revend>Main Landing Gear Doors and Actuating
Mechanisms Lubrication</title>
. . .
<entry namest="COL1" nameend="COL5" align="LEFT">
<note>
<para>Some items numbers may be skipped.</para>
</note>
</entry>

Rev #26 01/13/21 D6-82973

Page -189
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NOTE

1.3.15 Element: l1item through l7item

Printed Example:

SGML:
<taskcard cardnbr="20-040-01-01" mprog="SYS" etopsind="No" chg="N"
key="T0000026732">
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AY 3BA3BH 3BJ3BN 3BP3BP 3BR3BY 3CA3CH
3CJ3CN 3CP3CP 3CR3CY 3DA3DH 3DJ3ZZ" efftext="ZAP ALL">
</effect>
. . .
<subtask chapnbr="05" sectnbr="55" subjnbr="40" func="220" seq="001"
pgblknbr="6" id="KE9D4C1C6E10F2D64737837C8033EDAF">
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AY 3BA3BH 3BJ3BN 3BP3BP 3BR3BY 3CA3CH
3CJ3CN 3CP3CP 3CR3CY 3DA3DH 3DJ3ZZ" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Do a Functional Test of the electrical bond between the connectors
shown in (<refint reftype="table"
refid="N7C4D7EC12A9110171C85924E7C2B2C6">Table 601</refint>) and
airplane structure.</para>
<note>
<para>The physical location of the connectors is shown in (<grphcref
refid="KB3E84B7A23FB2EC4548990AC6FF8297">Figure 601</grphcref>).</para>
</note>
. . .
</l1item>

Rev #26 01/13/21 D6-82973

Page -190
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NOTE

1.3.16 Element: ftnote

<!ELEMENT warning - - (%text;) -(note) +(effect) >

Not used.

1.4 ELEMENT CONTEXT MARKUP EXAMPLES

a. The published strings “WARNING:,” “CAUTION:” and “NOTE:” are not
contained in the SGML content. They must be generated by the data recipient.

Rev #26 01/13/21 D6-82973

Page -191
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NUMLIST

1.0 ELEMENT NAME

numlist - Numbered List

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT numlist - - (numlitem+) >

The numlist element identifies a set of ordered items of text. Unlike the list structures
elsewhere in the DTD, the data in this list may contain the required numbering if no
automatic numbering is defined by the NUMTYPE attribute. The numlist element
appears in the context of the following elements:

ENTITY ELEMENT

exprtcl
geninfo

gdesc

(In %text) intnote

apapnote

eappnote

acpanote

taskproc

taskdesc

pretopic

warning

caution

note

entry
l1item - l7item

ftnote

Rev #26 01/13/21 D6-82973

Page -192
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NUMLIST

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT numlist - - (numlitem+) >
<!ATTLIST numlist
numtype CDATA #IMPLIED >

1.2.1 Attribute: numtype

Description: An attribute of NUMLIST which indicates the numbering system to be
used (alpha, numeric, other). It also indicates any parentheses, full
stops or underscores that are necessary to indicate level: refer to the
table below. The numbering is done by the receiver of the data. If this
attribute is not present the numbering must be included in the text of
the NUMLITEMs.

Code Description Example

NNP Number: no case; period 1.

AUP Alpha: Upper case; period A.

NNB Number; no case: both right and left parenthesis (1)

ALB Alpha; lower case: both right and left parenthesis (a)

NNS Number; no case; underscore 1

RUP Roman numeral; upper case; period I.

RLP Roman numeral; lower case; period i.

RUR Roman numeral; upper case; right parenthesis I)

RLR Roman numeral; lower case; right parenthesis i)

NNR Number; no case; right parenthesis l)

AUR Alpha; upper case; right parenthesis A)

ALR Alpha; lower case; right parenthesis a)

Rev #26 01/13/21 D6-82973

Page -193
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

NUMLITEM

1.0 ELEMENT NAME

numlitem - Numbered List Item

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT numlitem - - (para+) >

The numlitem element identifies an item of a numlist. The numlitem element appears
in the context of the following element:

ELEMENT

numlist

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -194
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

OPTASK

1.0 ELEMENT NAME

optask - Operational Task

1.1 ELEMENT CONTENT

<!ELEMENT optask - - (#PCDATA) >

The optask element defines the type of non-functional check to be performed. The
optask element appears in the context of the following element.

ELEMENT

thrshold

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: thrshold

<!ELEMENT thrshold - - (thrshtyp, ((multiple, unit, sample)
| optask)) >

Printed Example:

SGML:
<taskcard cardnbr="05-005-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000018889">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>

Rev #26 01/13/21 D6-82973

Page -195
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

OPTASK

<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
<reltask>
<rtaskcd>W</rtaskcd>
<rtasknbr>
<refint refid="T0000018732">05-033-00-29</refint>
</rtasknbr>
</reltask>
<intdata>
<interval>
<version>1.1</version>
<thrshold>
<thrshtyp>M</thrshtyp>
<optask>NAT REQ</optask>
</thrshold>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -196
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PAN

1.0 ELEMENT NAME

pan - Panel

1.1 ELEMENT CONTENT

<!ELEMENT pan - - (#PCDATA) >

The pan element identifies access panel information, i.e., the panel number. The pan
element appears in the context of the following element:

ELEMENT

para

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Page -199
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARA

1.0 ELEMENT NAME

para - Paragraph Block

1.1 ELEMENT CONTENT

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

The para tag identifies a subdivision of text that consists of one or more sentences,
deals with one point or gives the words of one speaker. The para element appears in
the context of the following elements:

ENTITY ELEMENT

fullstmt
partstmt

exprtcl

geninfo

unlitem

numlitem

(In %text) intnote

apapnote

eappnote

acpanote

taskproc

taskdesc

pretopic

warning
caution

note

entry

l1item - l7item

ftnote

Rev #26 01/13/21 D6-82973

Page -200
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARA

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: fullstmt

PARA

1.3.5 Element: unlitem

<!ELEMENT unlitem - - (para+) >

Printed Example:

SGML:
<unlist>
<unlitem>
<para>A 0-500 </para>
</unlitem>

1.3.6 Element: numlitem

<!ELEMENT numlitem - - (para+) >

Not used.

Rev #26 01/13/21 D6-82973

1.3.12 Element: taskdesc

<!ELEMENT taskdesc - - (%text;) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>
. . .
<taskdesc>
<para>Perform a General Visual Inspection</para>
</taskdesc>

Rev #26 01/13/21 D6-82973

Page -208
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARA

1.3.13 Element: pretopic

<!ELEMENT pretopic - - (title, (%text; | list1)) +(effect) >

Refer to sections 1.3.1, 1.3.4-1.3.5, 1.3.7-1.3.12 and 1.3.14-1.3.19 for examples of

para.

1.3.14 Element: warning

<!ELEMENT warning - - (%text;) -(note) +(effect) >

Printed Example:

SGML:
</subtask>
<subtask chapnbr="12" sectnbr="21" subjnbr="04" func="840" seq="002"
pgblknbr="3" id="DA0DA1CBB09A064859A4936161E646F7">
<effect effrg="HNAZZZ" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<warning>
<para>KEEP PERSONS AND EQUIPMENT CLEAR OF THE FLIGHT CONTROL SURFACES, THE
THRUST REVERSERS, AND THE LANDING GEAR. THESE COMPONENTS CAN MOVE SUDDENLY
WHEN YOU SUPPLY HYDRAULIC POWER. THIS CAN CAUSE INJURIES TO PERSONS AND
DAMAGE TO EQUIPMENT.</para>
</warning>
<para>Do this task: <refext refman="AMM" refloc="29-11-00-860-801">Main
Hydraulic System Pressurization, AMM TASK 29-11-00-860-801
</refext>.</para>
</l1item>
</list1>
</subtask>

Rev #26 01/13/21 D6-82973

Page -209
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARA

1.3.15 Element: caution

<!ELEMENT caution - - (%text;) -(note) +(effect) >

Printed Example:

SGML:
<subtask CHAPNBR="12" SECTNBR="21" SUBJNBR="08" FUNC="410" SEQ="001"
PGBLKNBR="3" ID="B8ECFDF7B2D8FB59BFE089E0350B5C4E">
<effect EFFRG="104105 601602 700999" EFFTEXT="ZAP ALL">
</effect>
<list1>
<l1item>
<caution>
<para>MAKE SURE THAT YOU INSTALL THE SKIRT FAIRING ON THE PANEL FROM THE
OUTER SIDE OF THE LEADING EDGE HOLE. IF NOT, DAMAGE TO THE ACCESS PANEL CAN
OCCUR DURING THE EXTENSION OF THE LEADING EDGE SLAT.</para>
</caution>
<para>Install these fixed leading edge panels on the lower surface of the
wing:</para>

1.3.16 Element: note

<!ELEMENT note - - (%text;) -(note) +(effect) >

Printed Example:

SGML:
<subtask chapnbr="05" sectnbr="55" subjnbr="40" func="220" seq="001"
pgblknbr="6" id="KE9D4C1C6E10F2D64737837C8033EDAF">
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AY 3BA3BH 3BJ3BN 3BP3BP 3BR3BY 3CA3CH
3CJ3CN 3CP3CP 3CR3CY 3DA3DH 3DJ3ZZ" efftext="ZAP ALL"></effect>
<list1><l1item>
<para>Do a Functional Test of the electrical bond between the connectors
shown in (<refint reftype="table"
refid="N7C4D7EC12A9110171C85924E7C2B2C6">Table 601</refint>) and
airplane structure.</para>
<note>
<para>The physical location of the connectors is shown in (<grphcref

Rev #26 01/13/21 D6-82973

Page -210
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARA

refid="KB3E84B7A23FB2EC4548990AC6FF8297">Figure 601</grphcref>).</para>
</note>
. . .
</subtask>

Page -213
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARA

minimize the possibility of seal migration or separation, during

Rev #26 01/13/21 D6-82973

Page -214
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARTSTMT

1.0 ELEMENT NAME

partstmt - Partial Statement

1.1 ELEMENT CONTENT

<!ELEMENT partstmt - - (title?, para+) >

The partstmt element is used to identify a partial proprietary statement. The partstmt
element appears in the context of the following element:

ELEMENT

proptary

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of data followed by an example of the SGML
markup.

Rev #26 01/13/21 D6-82973

Page -215
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARTSTMT

1.3.1 Element: proptary

<!ELEMENT proptary - - (fullstmt, partstmt?) >

NOTE: The following is a fabricated example. The Export Control statements are
currently under development and are shown here as examples only. In
addition, the control statements may differ depending on the type of export
control that is required.

Printed Example: (Legal Notice)al Notice)

Printed Example: (PARTSTMT)

Rev #26 01/13/21 D6-82973

Page -216
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PARTSTMT

required before it is used for development, production or use by foreign

persons from specific countries. The controller of this data has the
individual responsibility to abide by all export laws.</para>
</exprtcl>
<proptary>
<fullstmt>
<title>BOEING PROPRIETARY, CONFIDENTIAL, AND/OR TRADE SECRET</title>
<cpyrght>
<year>2006</year>
<holder>The Boeing Company</holder>
<geninfo>
<para>Unpublished Work - All Rights Reserved</para>
<para>Boeing claims copyright in each page of this document only to the
extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para>
</geninfo>
</cpyrght>
<para>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, Washington
98124.</para>
</fullstmt>
<partstmt>
<para> BOEING PROPRIETARY - Copyright © Unpublished Work - See title page
for details.</para>
</partstmt>
</proptary>
<geninfo>
<para>Boeing, the Boeing signature, the Boeing symbol, 707, 717, 727, 737,
747, 757, 767, 777, BBJ, DC-8, DC-9, DC-10, MD-10, MD-11, MD-80, MD-88,
MD-90, and the red-white-and-blue Boeing livery are all trademarks owned by
The Boeing Company; and no trademark license is granted in connection with
this document unless provided in writing by Boeing.</para>
</geninfo>
</legalntc>

1.4 BOEING APPLICATION RULES

a. The text of the PARTSTMT element will be displayed at the bottom of each
printed page of the document and on any screen display.

Rev #26 01/13/21 D6-82973

Page -217
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PHASE

1.0 ELEMENT NAME

phase - Phase Code

1.1 ELEMENT CONTENT

<!ELEMENT phase - - (mntcycle, pthrshld, prepeat) >

The phase element is a task interval and is converted into a phase code in order to
schedule the task into a work package. The phase element appears in the context of the
following element.

ELEMENT

interval

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -218
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

1.4 BOEING IMPLEMENTATION RULES

a. The phase data is provided once per each major “<version>” (i.e., 1.1, 2.1, 3.1,
etc.). phase is not provided in subsequent peer levels (e.g., 1.2, 2.2, 2.3, etc.).
The example shown above demonstrates this rule in which phase is provided for
<version>1.1 and <version>2.1 but not for 1.2 or for 2.2.

Rev #26 01/13/21 D6-82973

Page -221
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PREPEAT

1.0 ELEMENT NAME

prepeat - Phase Repeat

1.1 ELEMENT CONTENT

<!ELEMENT prepeat - - (#PCDATA) >

The prepeat element defines the numeric value for the repeat interval. The prepeat
element appears in the context of the following element.

ELEMENT

phase

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: phase

<!ELEMENT phase - - (mntcycle, pthrshld, prepeat) >

Printed Example: prepeat is not viewable on the printed task card

Rev #26 01/13/21 D6-82973

Page -222
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PREPEAT

Rev #26 01/13/21 D6-82973

Page -223
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PREPEAT

<unit>DY</unit>
<sample>100</sample>
</thrshold>
<repeat>
<thrshtyp>N</thrshtyp>
<multiple>750</multiple>
<unit>DY</unit>
<sample>100</sample>
</repeat>
</interval>
<intnote>
<para>Initial threshold and repeat is 12000 flight cycles or 2250 days
(whichever comes first) until 28000 flight cycles or 5250 days (whichever
comes first) is reached. From this point on the repeat interval of 4000
flight cycles or 750 days is applicable.</para>
</intnote>
</intdata>

Rev #26 01/13/21 D6-82973

Page -224
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PRETOPIC

1.0 ELEMENT NAME

pretopic - Preliminary Topic

1.1 ELEMENT CONTENT

<!ELEMENT pretopic - - (title, (%text; | list1)) +(effect) >

The element pretopic identifies a section of the preliminary task frontmatter data.
These sections are used for such things as summaries of the Tools, Consumables,
Access panels etc. required for, or affected by, the task. The pretopic element appears
in the context of the following elements:

ELEMENT

pretsmry

hazmtlst

tfmatr

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -225
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PRETOPIC

1.3.1 Element: pretsmry

<!ELEMENT pretsmry - - (pretopic+) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
</effect>
. . .
<pretsmry>
<pretopic>
<title>References</title>
<table frame="NONE">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="320*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>

Rev #26 01/13/21 D6-82973

Page -226
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PRETOPIC

<para>Title</para>
. . .
</pretopic>
</pretsmry>

1.3.2 Element: hazmtlst

<!ELEMENT hazmtlst - - (title, pretopic*, hazmt+) >

Not used.

1.3.3 Element: tfmatr

<!ELEMENT tfmatr - - (pretopic+) >

Printed Example:

SGML:
<tfmatr>
<pretopic>
<title>References</title>
<table frame="NONE">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="420*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>
<para>Title</para>
</entry>
</row>
</thead>
. . .
</pretopic>
</tfmatr>

Rev #26 01/13/21 D6-82973

Page -227
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PRETSMRY

1.0 ELEMENT NAME

pretsmry - Pretopic Summary

1.1 ELEMENT CONTENT

<!ELEMENT pretsmry - - (pretopic+) >

The pretsmry element identifies the pretopic(s) that precede the task. The pretopics
from each task within a task card are combined by pretopic type (references,
consumable materials, etc.). The pretsmry element appears in the context of the
following element.

ELEMENT

tcbody

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Page -230
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PROPTARY

1.0 ELEMENT NAME

proptary - Proprietary Statement

1.1 ELEMENT CONTENT

<!ELEMENT proptary - - (fullstmt, partstmt?) >

The proptary element is the content model for the proprietary statement. The proptary
element appears in the context of the following element:

ELEMENT

legalntc

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -231
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PROPTARY

1.3.1 Element: legalntc

<!ELEMENT legalntc - - (exprtcl | cpyrght | proptary | geninfo)+>

Printed Example:

SGML:
<tc chg="R" docnbr="D633A109-ZAP" cusname="ZAP Airlines, Inc." cus="ZAP"
oidate="19980605" lang="EN" model="737-600/700/800/900" revdate="20031010"
spl="81205" tsn="21A">
<legalntc CHG="N" KEY="T-legalntc" REVDATE="20030210">
<proptary>
<fullstmt>
<title>BOEING PROPRIETARY, CONFIDENTIAL, AND/OR TRADE SECRET</title>
<cpyrght>
<year>1994</year>
<holder>The Boeing Company</holder>
<geninfo>
<para>Unpublished Work - All Rights Reserved</para>
<para>Boeing claims copyright in each page of this document only to the
extent that the page contains copyrightable subject matter. Boeing also
claims copyright in this document as a compilation and/or collective work.
</para></geninfo></cpyrght>
<para>This document includes proprietary information owned by The Boeing
Company and/or one or more third parties. Treatment of the document and the
information it contains is governed by contract with Boeing. For more
information, contact The Boeing Company, P.O. Box 3707, Seattle, WA 98124.
</para></fullstmt></proptary>
<geninfo>
<para>Boeing, the Boeing signature, the Boeing symbol, 707, 717, 727, 737,
747, 757, 767, 777, BBJ, DC-8, DC-9, DC-10, MD-10, MD-11, MD-80, MD-88, MD-90
and the red-white-and-blue Boeing livery are all trademarks owned by The
Boeing Company; and no trademark license is granted in connection with this
document unless provided in writing by Boeing.</para></geninfo></legalntc>
. . .
</tc>

Rev #26 01/13/21 D6-82973

Page -232
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PTHRSHLD

1.0 ELEMENT NAME

pthrshld - Periodic Threshold

1.1 ELEMENT CONTENT

<!ELEMENT pthrshld - - (#PCDATA) >

The pthrshld element defines the periodic frequency of a given task. The pthrshld
element appears in the context of the phase element.

ELEMENT

phase

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: phase

<!ELEMENT phase - - (mntcycle, pthrshld, prepeat) >

Printed Example: pthrshld is not viewable on the printed task card

Rev #26 01/13/21 D6-82973

Page -233
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PTHRSHLD

Rev #26 01/13/21 D6-82973

Page -234
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

PTHRSHLD

Rev #26 01/13/21 D6-82973

Page -235
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFBLOCK

1.0 ELEMENT NAME

refblock - Reference Block

1.1 ELEMENT CONTENT

<!ELEMENT refblock - - (#PCDATA | refint | refext | grphcref)*>

The refblock element is structure containing internal and external references to

graphics or text. The refblock element appears in the context of the %g.r entity:

ENTITY ELEMENT

(In %g.r) task

topic
subtask

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: task

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -236
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFBLOCK

1.3.2 Element: topic

<!ELEMENT topic - - (effect?, title, %g.r;, %w.c;, note*,
subtask*) >

Printed Example:

SGML:
<task chapnbr="70" sectnbr="00" subjnbr="03" func="200" seq="801"
pgblknbr="2" id="N040154E00E8437A5E6E6059A4C75743">
<effect effrg="475999" efftext="ZAP ALL">
</effect>
<title>Types of Damage</title>
<topic>
<title>Types of Damage</title>
<refblock>(<grphcref
refid="C0F15F2C183D763ACED52B9526B23B27">Figure 201</grphcref>)
</refblock>
. . .
</task>

1.3.3 Element: subtask

<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect)

Not used.

Rev #26 01/13/21 D6-82973

Page -237
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

1.0 ELEMENT NAME

refext - Reference (External)

1.1 ELEMENT CONTENT

<!ELEMENT refext - - (#PCDATA) >

The refext element identifies an explicit external reference to text or a structure in

another manual. The attributes give the information necessary to allow the system to
resolve the reference. The tag contains the “human-readable” text explaining the
reference. The refext element appears in the context of the following elements:

ENTITY ELEMENT

tcbody

para

reblock

(In %g.r) task

topic

subtask

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT refext - - (#PCDATA) >
<!ATTLIST refext
refman CDATA #IMPLIED
refloc CDATA #IMPLIED
refspl CDATA #IMPLIED
docnbr CDATA #IMPLIED
refmodel CDATA #IMPLIED >

Attribute Name Always Provided Provided When Data is

Available

refman X
refloc X

refspl X

docnbr X
refmodel X

Rev #26 01/13/21 D6-82973

Page -238
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

1.2.1 Attribute: refman

Description: Identifies the manual code of the manual which contains the element
pointed to by the reference (element refext) to which this attribute
applies.

1.2.2 Attribute: refloc

Description: Identifies the location of the reference in another manual as defined by
refman. This attribute equates to the refid of the refint element, but,
because an external reference may not be resolvable by the system, it is
not explicitly defined as an SGML ID.

1.2.3 Attribute: refspl

Description: A Supplier code identifying the provider of the data to which the
reference applies.

1.2.4 Attribute: docnbr

Description: Document Number (docnbr) is assigned by the aircraft manufacturer. It
is a specific document identification number. An example of a Boeing
docnbr is D633W101-ZAP.

1.2.5 Attribute: refmodel

Description: Identifies the engine model manual to which the reference applies.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: tcbody

<!ELEMENT tcbody - - (tccat?, taskproc?, mpditem*,
pretsmry?, hazmtlst?, (task* | refext*))>

Examples not available at this time.

Rev #26 01/13/21 D6-82973

Page -239
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

1.3.2 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

( ) denotes optional use in reference

REFMAN = AFM REFLOC = A

(Aircraft Flight A = section number (1 char)
Manual)

Rev #26 01/13/21 D6-82973

Page -241
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = AMM REFLOC = (X)AA-BB-CC Printed Text:

(Aircraft Maintenance X = chappref (1 char - engine 2. Replace or repair the duct (AMM SUBJECT
Manual) chapters only) 21-23-01).
AA = chapter number (2 char)
ALIAS = MM BB = section number ( 2 char) SGML:
CC = subject number ( 2 char) <PARA>Replace or repair the duct (<REFEXT
OR refman=”AMM” refloc=”21-23-01”>AMM
REFLOC = (X)AA-BB-CC-D(-N) SUBJECT 21-23-01</REFEXT>)
X = chappref (1 char - engine
chapters only) Printed Text:
AA = chapter number ( 2 char) 2. Do a check of the elevator surface freeplay
BB = section number ( 2 char) (AMM PAGEBLOCK 27-02-00/601).
CC = subject number ( 2 char)
D = pgblk number (1 char) SGML:
N = Config number <PARA>Do a check of the elevator surface
OR freeplay (<REFEXT refman=”AMM”
REFLOC = (X)AA-BB-CC-EEE-FFF(- refloc=”27-02-00-6”>AMM PAGEBLOCK 27-
GHH) 02-00/601</REFEXT>).
X = chappref (1 char - engine
chapters only) Printed Text:
AA = chapter number (2 char) (12) Stop the left and right engines. To stop
BB = section number ( 2 char) the engines, do this task: GE: Stop the Engine
CC = subject number ( 2 char) Procedure (Usual Engine Stop), AMM TASK
EEE = function number (3 char) 71-00-00-800-813-G00 or PW: Engine
FFF = Sequence number (3 char) Shutdown Procedure (Normal Engine
G = Confltr number (1 char) Shutdown), AMM TASK 71-00-00-860-809-
HH = Varnbr number (2 char) N00 or G1: Stop the Engine Procedure (Usual
Engine Stop), AMM TASK 71-00-00-800-837-
H00

SGML:
<para>Stop the left and right engines. To stop
the engines, do this task: <refext
REFMAN="AMM" REFLOC="G71-00-00-800-
813-G00">GE: Stop the Engine
Procedure (Usual Engine Stop), AMM
TASK 71-00-00-800-813-G00</refext>
or <refext REFMAN="AMM" REFLOC="N71-
00-00-860-809-N00">PW: Engine
Shutdown Procedure (Normal Engine
Shutdown), AMM TASK 71-00-00-860-
809-N00</refext> or <refext
REFMAN="AMM" REFLOC="H71-00-00-800-
837-H00">G1: Stop the Engine
Procedure (Usual Engine Stop), AMM
TASK 71-00-00-800-837-H00
</refext></para>

Rev #26 01/13/21 D6-82973

Page -242
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = AIPC REFLOC = AA-BB-CC Printed Example:

(Aircraft Illustrated AA = chapter number (2 char) “ 29-11-10 50 275”
Parts Catalog) BB = section number ( 2 char) (ch-sec-sub fig item)
CC = subject number ( 2 char)
ALIAS = IPC SGML:
OR <para><REFEXT refman="AIPC" refloc="29-
REFLOC = AA-BB-CC-DD(D) 11-10-50-275">275</REFEXT></para>
AA = chapter number (2 char) </ENTRY></ROW>
BB = section number ( 2 char)
CC = subject number ( 2 char)
DD(D) = figure number
( 2 or 3 char) could have alpha in
any position

OR
In TOD tables only:
REFLOC = AA-BB-CC-DD(D)
-EEE(E)
AA = chapter number ( 2 char)
BB = section number ( 2 char)
CC = subject number ( 2 char)
DD(D) = figure number
( 2 or 3 char) could have alpha in
any position
EEE(E) = item number
( 3 or 4 char) could have alpha
in any position

In TOD tables only:

AA-BB-CC DD EEE

REFMAN = ATS REFLOC = AAAAAAAA

(Automated Test AAAAAAAA = document
Station (737-767)) number (8 char)
Ex: Document # (e.g. D643T801)

REFMAN = BCLM REFLOC = AA-BB-CC Printed Example:

(Baggage Cargo AA = chapter number (2 char) (2) BCLM 25-53-21
Loading) BB = section number ( 2 char)
CC = subject number ( 2 char) SGML:
<L1ITEM>
<para><REFEXT refman="BCLM" refloc="25-
53-21">BCLM 25-53-21</REFEXT></para></
L1ITEM></LIST1>

REFMAN = BITE REFLOC = AA-BB-CC

(Built in Test AA = chapter number (2 char)
Equipment) BB = section number ( 2 char)
CC = subject number ( 2 char)

Rev #26 01/13/21 D6-82973

Page -243
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = CMM REFLOC = AA-BB-CC(C) Printed Example:

(Component AA = chapter number ( 2 char) If functional test was not normal or you can
Maintenance Manual) BB = section number ( 2 char) not install the downlock pin for the nose land-
CC(C) = subject number ing gear, adjust the lock links for the nose
( 2 or 3 char) landing gear. This procedure is in this manual:
DD(D) = figure number CMM 32-21-02/701.
( 2 or 3 char)
SGML:
<para>If functional test was not normal or you
can not install the downlock pin for the nose
landing gear, adjust the lock links for the nose
landing gear. This procedure is in this manual:
(<refext REFMAN="CMM" REFLOC="32-21-
02/701">CMM 32-21-02/701</refext>).
</para>

REFMAN = CMMI REFLOC = AA-BB-CC

(Component AA = chapter number ( 2 char)
Maintenance BB = section number ( 2 char)
Overhaul Manual CC = subject number ( 2 char)
Index)

REFMAN = CPM REFLOC = (P-)AA-BB-CC Printed Example:

(Corrosion Prevention OR AA-BB-CC(-P) (1) Do the check for microbial growth (CPM
Manual) P = Part 1,2 or 3 20-62-00).
AA = chapter number ( 2 char)
BB = section number ( 2 char) SGML:
CC = subject number ( 2 char) <LIST1>
<L1ITEM>
<para>Do the check for microbial growth
<REFEXT refman="CPM" refloc="20-62-
00">(CPM 20-62-00)
</REFEXT>.</para></L1ITEM>
</LIST1>

REFMAN = DDG REFLOC = AA(-BB)(-CC)

(Dispatch Deviation AA = chapter number (2 char)
Guide) BB = section number ( 2 char)
CC = subject number ( 2 char)

REFMAN = EHD REFLOC = AA-BB-CC

(Engine Ground AA = chapter number (2 char)
Handling Document) BB = section number ( 2 char)
CC = subject number ( 2 char)

Rev #26 01/13/21 D6-82973

Page -244
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = EIPC REFLOC = AA-BB-CC-DDDD

(Engine Illustrated AA = chapter number ( 2 char)
Parts Catalog) BB = section number ( 2 char)
CC = subject number ( 2 char)
DDDD = figure number
(1-4 chars) Figure number
could start or end with an
alpha or numeric

REFMAN = FCTM REFLOC = AA(-BB)(-PP)

(Flight Crew Training AA = chapter number (2 char)
Manual) BB = section number ( 2 char)
PP = page ID (2 char)

Rev #26 01/13/21 D6-82973

Page -245
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = FRMFIM REFLOC = (X)AA-BB Printed Example:

(Fault Reporting X = chappref (1 char - engine FIM 22-00 TASK 804 Alert FCC 1 FAIL -Fault
Manual/Fault Isolation chapters only) Isolation (P/B )
Manual) AA = chapter number (2 char)
BB = section number ( 2 char) SGML:
<row>
OR <entry>
<para><refext REFMAN=”FRMFIM”
REFLOC = (X)AA-BB-CC-EEE-FFF[- REFLOC="22-00-XX-XXX-XXX >FIM 22-
GHH] 00 TASK 804</refext>
X = chappref (1 char - engine </para>
chapters only) </entry>
AA = chapter number (2 char)
BB = section number ( 2 char) Printed Example:
CC = subject number ( 2 char) (l) Examine the engines, the nose cowl and
EEE = function number (3 char) the inlet.
FFF = Sequence number (3 char)
G = Confltr number (1 char) NOTE: If the engine shows signs of a
HH = Varnbr number (2 char) bird/hail strike on the nacelle,
refer to the applicable bird strike
trouble shooting procedures
(FIM 71-00 SUBJECT 00 FAULT
CODE INDEX).

SGML:
<note>
<para>If the engine shows signs of a bird/hail
strike or suspected bird/hail strike on the
nacelle, refer to the applicable bird s
trike trouble shooting procedures (<refext
REFMAN="FRMFIM" REFLOC="J71-00-
00">FIM 7100 SUBJECT 
00</refext> FAULT CODE INDEX).</para>
</note>

Printed Example:
FIM 27-20 PGBLK 2 27-20 TASKS

SGML:
<entry>
<para><refext REFMAN="FRMFIM"
REFLOC="27-20-00-2">FIM 27-
20 PGBLK 2</refext></para>
</entry>
<entry>
<para>27-20 TASKS</para>
</entry>

Rev #26 01/13/21 D6-82973

Page -246
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = ISAR REFLOC = XX-XX-XXXX-XX

(In service Activities XX-XX-XXXX-XX = report
Report) number

REFMAN = ITEL REFLOC = AA-BB-CC

(Illustrated Tool and AA = chapter number (2 char)
Equipment Manual) BB = section number ( 2 char)
CC = subject number ( 2 char)

REFMAN = ITEM REFLOC = AA-BB-CC

(Illustrated Tool and AA = chapter number (2 char)
Equipment Manual) BB = section number ( 2 char)
CC = subject number ( 2 char)

REFMAN = MEL REFLOC = AA(-BB)(-PP)

(Minimum Equipment AA = chapter number (2 char)
List) BB = section number ( 2 char)
PP = procedure number
Note: Boeing Manual (2 char)
is called the MMEL
(Master Minimum
Equipment List)

Rev #26 01/13/21 D6-82973

Page -247
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = MPD 757/767 (systems)

(Maintenance REFLOC = AAA-BB-CC-DD
Planning Document) AAA = engine and chapter
(3 char)
BB = section ( 2 char)
CC = subject ( 2 char)
DD = page block ( 2 char)
unique alpha id

757/767 (structures)
REFLOC = AAAA-BBB-CCC
AAAA= ATA system/
subsystem
BBB = zone # ( 2 char)
CCC = sequence # ( 2 char)
internal or external

757/767 (zonal)
REFLOC = AAA-BB-CC-DD
AAA= ATA system/subsystem
BB = zone # ( 2 char)
CC = sequence # ( 2 char)
DD = ID zone task ( 2 char)

747-400 (systems)
REFLOC = AAAA-BBB-CCC
AAAA = engine and chapter
BBB = section ( 3 char)
CCC = subject ( 3 char)
page block, sequence, task
card only, position ID (engine
/strut position) l.r (left, right)

747-400 (structures)
REFLOC = AAA-BBBB
AAA = structural task & TA #
BBBB = basic sequence (SSI)
tasks w/i SSI, task card
sequence #,
task card only (engine/strut)
l,r, (left, right) applicability

747-400 (zonal)
REFLOC = AAA-BBB-CCC
AAA =zonal task & chapter
BBB =zone
CCC =sequence
task card only (engine/strut
position) l,r (left, right)

Rev #26 01/13/21 D6-82973

Page -248
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = NDT (757/767)

(Non-Destructive Test REFLOC = (P-)AA-BB-CC
Manual) OR AA-BB-CC(-P)
P = Part 1,2 or 3
AA = chapter number ( 2 char)
BB = section number ( 2 char)
CC = subject number ( 2 char)

(707-747)
REFLOC = (P-)AA-BB-CC-DD
OR AA-BB-CC-DD(-P)
P = Part 1,2 or 3
AA = chapter number ( 2 char)
BB = section number ( 2 char)
CC = subject number ( 2 char)
DD = figure number ( 2 char)

REFMAN = OHM REFLOC = AA-BB-CC Printed Example:

(Overhaul Manual) AA = chapter number (2 char) (3) For a more detailed check (weld penetrant
BB = section number ( 2 char) checks, etc.) of the pneumatic ducts, do the
CC = subject number ( 2 char) check in (OHM 36-10-07/).

SGML:
<LIST1>
<L1ITEM>
<para>For a more detailed check (weld
penetrant checks, etc.) of the pneumatic
ducts, do the check in
<REFEXT refman="OHM" refloc="36-10-
07">(OHM 36-10-07)</REFEXT>.
</para></L1ITEM></LIST1>

REFMAN = OM REFLOC = AA(-BB)(-P)

(Operations Manual) AA = chapter number (2 char)
BB = section number ( 2 char)
P = page ID

REFMAN = PPBU REFLOC = AA-BB-CC

(Power Plan Build Up) AA = chapter number (2 char)
BB = section number ( 2 char)
CC = subject number ( 2 char)

REFMAN = RMM REFLOC = AA-BB(B)

(Ramp Maintenance) AA = chapter number (2 char)
BB = section number ( 2 char)
could have 3rd char alpha

Rev #26 01/13/21 D6-82973

Page -249
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = SB Service Bulletin Airplane (727-777)

(Service Bulletin) REFLOC = AA-BBBB
AA = chapter ( 2 char)
BBBB = unique ID (4 char)
Note: Alert Service Bulletin has
character ‘A’ between chapter and
unique ID (AAABBBB)

Component Service Bulletin

REFLOC = TTTTTTTT-AA-BB
TTTTTTTT = Top Component
Part Number (8 char)
AA = chapter ( 2 char)
BB = section (2 char)

REFMAN = SB ATS REFLOC = ATS-DDD

(ATS Service Bulletin) DDD = unique ID (3 char)

REFMAN = SDS REFLOC = AA-BB-CC

(System Description AA = chapter number (2 char)
Section) BB = section number ( 2 char)
CC = subject number ( 2 char)
Note: currently all subjects are 00, but
we are leaving it in the refloc definition
for future expansion.

REFMAN = SIIA REFLOC = AAA

(Structural Item AAA = unique ID (3 char)
Interim Adversory)

REFMAN = SBI Model 707-720, 727

(Service Bulletin REFLOC = D6-AAAA
Index) AAAA = unique ID (4 char)

Model 747
REFLOC = D6-AAAAA
AAAAA = unique ID (5 char)

Model 757, 767

REFLOC = D6AAAAAA
AAAAAA = unique ID (6 char)

Rev #26 01/13/21 D6-82973

Page -250
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = SL For Service Letters the refloc will be the Printed Example 1:
(Service Letters) Service Letter Document number:
SL 737-SL-29-37
REFLOC = MMM-SL-CC-PP(P)-X
MMM=Model SGML Example 1:
SL=Service Letter <row>
CC = chapter (2 char) <entry>
PP(P) = unique ID (2 or 3 chars) <para><refext refman="SL"
X=Alpha refloc="737-SL-29-37"><revst>SL
737-SL-29-37<revend></refext>
</para>
</entry>

Printed Example 2:

SL 737-SL-78-053-A

SGML Example 2:
<row>
<entry>
<para><refext refman="SL"
refloc="21-029">SL 21-029
</refext></para>
</entry>
<entry>

REFMAN = SRM REFLOC = AA-BB-CC Printed Example:

(Structural Repair AA = chapter number (2 char) (6) Install soft 1100-F aluminum rivets in the
Manual) BB = section number ( 2 char) holes drilled in the fairing panels (SRM 51-40-
CC = subject number ( 2 char) 02).

SGML:
<LIST1>
<L1ITEM>
<para>Install soft 1100-F aluminum rivets in
the holes drilled in the fairing panels
(<REFEXT refman="SRM" refloc="51-40-
02">SRM 51-40-02
</REFEXT>) </para></L1ITEM>
</LIST1

The above example may also contain the

word “SUBJECT” before the XX-XX-XX and it
could be two digits (i.e., 51-40) instead of
three.

Rev #26 01/13/21 D6-82973

Page -251
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = SSM REFLOC = AA-BB-CC Printed Example:

(System Schematics AA = chapter number (2 char) For an SDM [1] in column 1 (SSM 23-31-20);
Manual) BB = section number ( 2 char) Make sure that this circuit breaker is open:
CC = subject number ( 2 char)
SGML:
<LIST1>
<L1ITEM>
...
(<REFEXT refman="SSM" refloc="23-31-
20">SSM 23-31-20</REFEXT>); Make sure
that this circuit breaker is open:</para>

REFMAN = SOPM REFLOC = AA-BB-CC Printed Example:

(Standard Overhaul AA = chapter number (2 char) This procedure contains a list of solvents for
Practices Manual) BB = section number ( 2 char) final cleaning of all organic coatings before
CC = subject number ( 2 char) painting as given in BAC5750 (SOPM 20-30-
ALIAS = SOP 03). T

SGML:
<LIST1>
<L1ITEM>
<para>This procedure contains a list of
solvents for final cleaning of all organic
coatings before painting as given in BAC5750
(<REFEXT refman="SOPM" refloc="20-30-
03">SOPM 20-30-03
</REFEXT>). . . .</para></L1ITEM>
</LIST1>

REFMAN = SWPM REFLOC = AA-BB-CC Printed Example:

(Standard Wiring AA = chapter number (2 char) Do a check of the coaxial cables and
Practices Manual) BB = section number ( 2 char) connectors if it is necessary (SWPM 20-50-
CC = subject number ( 2 char) 00).
ALIAS = SWP
Chapter 20 (Standard Wiring Practices) SGML:
<LIST1>
<L1ITEM>
<para>Do a check of the coaxial cables and
connectors if it is necessary (<REFEXT
refman="SWPM" refloc="20-50-00">SWPM
20-50-00</REFEXT>).
</para></L1ITEM></LIST1>

Rev #26 01/13/21 D6-82973

Page -252
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFEXT

Standard Acronym & External Reference Format

Referenced Manual Refloc Value Printed Text/SGML Examples

( ) denotes optional use in reference

REFMAN = WDM REFLOC = AA-BB-CC Printed Example:

(Wiring Diagram AA = chapter number ( 2 char) To continue the fault isolation, move the LRT
Model) BB = section number ( 2 char) to the other end of the faulty wire bundle
CC = subject number ( 2 char (WDM 24-33-31).

SGML:
<L3ITEM>
<para>To continue the fault isolation, move
the LRT to the other end of the faulty wire
bundle (<REFEXT refman="WDM"
refloc="24-33-31">
WDM 24-33-31</REFEXT>).
</para>

Rev #26 01/13/21 D6-82973

Page -253
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFINT

1.0 ELEMENT NAME

refint - Reference (Internal)

1.1 ELEMENT CONTENT

<!ELEMENT refint - - (#PCDATA) >

The refint element identifies an explicit internal reference to text within the same
manual. The attributes give the information necessary to allow the system to resolve
the reference. The tag refint contains the “human readable” text explaining the
reference. The refint element appears in the context of the following elements:

ENTITY ELEMENT

rtasknbr

para

refblock

(In %g.r) task

topic

subtask

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT refint - - (#PCDATA) >
<!ATTLIST refint
reftype CDATA #IMPLIED
refid IDREF #IMPLIED >

Attribute Name Always Provided Provided When Data is

Available

reftype X

refid X

Rev #26 01/13/21 D6-82973

Page -254
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFINT

1.2.1 Attribute: reftype

Description: Reference Type (reftype) identifies the element type for the element
elsewhere in the document instance to which a reference is made.

1.2.2 Attribute: refid

Description: Reference Identification (refid) identifies an object (text or graphics) in
the same manual to which a reference is made.

Boeing Application Rules:

a. refid must match the key of the anchor that is being referenced.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: rtasknbr

<!ELEMENT rtasknbr - - (#PCDATA | refint)+ >

Printed Example:

SGML:
<taskcard cardnbr="05-005-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000018889">
<effect effrg="001999">

Rev #26 01/13/21 D6-82973

Page -255
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFINT

</effect>
<mainhead>
<source>MRB</source>
<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
<reltask>
<rtaskcd>W</rtaskcd>
<rtasknbr>
<refint refid="T0000018732">05-033-00-29</refint>
</rtasknbr>
</reltask>
. . .
</taskcard>

1.3.2 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Printed Example:

SGML:
<taskcard cardnbr="06-002-00-04" mprog="COR" etopsind="No" chg="N"
key="T0000018066">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>
. . .
<subtask chapnbr="52" sectnbr="11" subjnbr="01" func="820" seq="039"
pgblknbr="5" id="B6F6CBF2E81F84E7D1126AE750265DBB">
<effect effrg="475999" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Do the hold-open hook adjustment/test. (<refint reftype="TASK"
refid="KCA9A498A70A29A3AC602F9943B55950">Adjustment of the Passenger Forward
Entrance Door Hold-Open Hook, TASK 52-11-01-820-810</refint>)</para>
</l1item>
</list1>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -256
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFINT

1.3.3 Element: refblock

<!ELEMENT refblock - - (#PCDATA | refint | refext | grphcref)*>

Printed Example:

SGML:
<subtask chapnbr="12" sectnbr="21" subjnbr="09" func="860" seq="016"
pgblknbr="3" id="H65434DAF255C4B248C0DA4138D5272F">
<effect effrg="701705 731732 771799 941945 981999" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Extend the trailing edge flaps to the 30-unit position. To extend them,
do this task: <refext refman="AMM" refloc="27-51-00-860-804">Extend the
Trailing Edge Flaps, AMM TASK 27-51-00-860-804</refext>.
</para>
</l1item>
</list1>
</subtask>
</topic>
<topic>
<title>Outboard Flap Inboard Transmission, Ballscrew and Gimbal Lubrication
</title>
<refblock>(<refint reftype="TABLE"
refid="M12FD0FAB003D3A3620F389342E5F986">Table 308</refint>)</refblock>

Rev #26 01/13/21 D6-82973

Page -257
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REFINT

1.3.4 Element: task

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

Not used.

1.3.5 Element: topic

<!ELEMENT topic - - (effect?, title, %g.r;, %w.c;, note*,
subtask*) >

Not used.

1.4 BOEING IMPLEMENTATION RULES

a. The #PCDATA content of the <refint> contains the resolved display content of the
cross-reference.
b. The REFID attribute is #IMPLIED and will be supplied when data is available.
c. The value of the REFID attribute on the <refint> matches the value of the ID
attribute on the target element.
d. The optional REFTYPE attribute value matches the Generic Identifier of the
element being referenced (e.g., REFTYPE=“task”).
e. A <refint> element is used to reference a hazardous material warning (<hazmt>).

Rev #26 01/13/21 D6-82973

Page -258
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REGULATION

1.0 ELEMENT NAME

regulation - Regulation

1.1 ELEMENT CONTENT

<!ELEMENT regulation - - (effect?, grsymbol?, #PCDATA) >

The regulation element is maintenance data used to fulfill compliance with a

regulatory requirement. Maintenance data that is related to a regulatory requirement
that, when deleted or modified, could lead to noncompliance to a regulatory
requirement.

Note: This element is defined using a mixed content model. A mixed content
model contains element and #PCDATA content. Separator characters such as
spaces, tabs, and newlines are treated as #PCDATA; therefore, separator
characters must not appear before any element defined in the mixed content
model.

<regulation REGTYPE="AWL" REGVALUE="47-AWL-02: CDCCL"><grsymbol

GNBR="REGULATORY">47-AWL-02: CDCCL</regulation>

The regulation element appears in the context of the following elements:

ELEMENT

regulatory

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT regulation - - (effect?, grsymbol?, #PCDATA) >
<!ATTLIST regulation
regtype CDATA #REQUIRED
regsource CDATA IMPLIED
regvalue CDATA #IMPLIED >

Attribute Name Always Provided Provided When Data is

Available

regtype X

regsource X

regvalue X

Rev #26 01/13/21 D6-82973

Page -259
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REGULATION

1.2.1 Attribute: regtype

Description: Identifies the manual code of the manual which contains the element
pointed to by the reference (element refext) to which this attribute
applies.

AD - Airworthiness Directive
AMOC - Alternative Method Of Compliance
AWL - Airworthiness Limitation
CAT III - Instrument Landing System Category III or Autoland Category III
CMR - Certification Maintenance Requirements
ETOPS - Extended Twin-Engine Operations
EWIS - Electrical Wiring Interconnection Systems
LOI - Letter of Investigation
RII - Required Inspection Item
SFAR 88 - Special Federal Aviation Regulation 88
SCI - Special Compliance Item

1.2.2 Attribute: regsource

Description: Identifies the regulatory agency that is controlling the content.

Not Used.

1.2.3 Attribute: regvalue

Description: Identifies multiple regulatory elements in the context where it is used,
which allows the association of applicability information with each
regulatory element.

Boeing Application Rules:

a. When the content of the attributes regtype and regvalue are the same, regvalue will
not be present in the SGML.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -260
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REGULATION

1.3.1 Element: regulatory

<!ELEMENT regulatory - - (effect?, regulation+) >

Printed Example: EXAMPLE TAKEN FROM THE AMM

1.4 BOEING APPLICATION RULES

a. The data from Boeing only contains FAA regulations; therefore, the regsource
attribute will not be populated. However, in the future if regulation data from other
agencies (such as those in Europe, Asia, Australia, etc.) is contained within the
manual the attribute will reflect the acronyms for those agencies.
b. This attribute can be used by airlines to populate additional regulatory information
within their systems.

Rev #26 01/13/21 D6-82973

Page -261
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REGULATORY

1.0 ELEMENT NAME

Regulatory - Regulatory

1.1 ELEMENT CONTENT

<!ELEMENT regulatory - - (effect?, regulation+) >

The regulatory element is a collection of maintenance data regulatory requirements.

The regulatory element appears in the context of the following elements:

ELEMENT

task

subtask

l1item-l7item

entry

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -262
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REGULATORY

1.3.1 Element: task

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

Printed Example: Example taken from the AMM

Rev #26 01/13/21 D6-82973

Page -263
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REGULATORY

1.3.2 Element: subtask

<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect) >

Printed Example: Example taken from the AMM

SGML:
<subtask CHAPNBR="05" SECTNBR="55" SUBJNBR="54" FUNC="200" SEQ="003"
PGBLKNBR="6" CHG="R" KEY="A8F9EB5F11FCACC1616CC54492209AE6"
REVDATE="20150315">
<effect EFFRG="001007 009011 014016 018099 101112 303303 401460 501501
901999" EFFTEXT="ZAP ALL">
</effect>
<regulatory>
<regulation REGTYPE="AWL" REGVALUE="28-AWL-04: CDCCL"><grsymbol
GNBR="REGULATORY">28-AWL-04: CDCCL</regulation>
</regulatory>
<list1>
<l1item>
<para>If any FQIS wire bundle in the unpressurized zone is replaced or the
FQIS wire bundle's shield is repaired, do this task: <refint REFTYPE="task"
REFID="OBD72D0806CA34C1F4CD7A916453887C">FQIS Wiring And Bonding -
Inspection, TASK 05-55-54-200-801</refint>.</para>
<note>
<para>CDCCL - Refer to the task: <refint REFTYPE="task"
REFID="ND46A578B8DC88115B533D0EA972EEEB">Airworthiness Limitation
Precautions, TASK 05-00-00-910-802</refint>, for information on Critical
Design Configuration Control Limitations (CDCCLs).</para>
</note>
<note>
<para>This is applicable to Airworthiness Limitation 28-AWL-04.</para>
</note>
</l1item>
</list1>
</subtask>

Rev #26 01/13/21 D6-82973

Page -264
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REGULATORY

1.3.3 Element: l1item-l7item

Printed Example: Example taken from the AMM

SGML:
<subtask CHAPNBR="05" SECTNBR="55" SUBJNBR="54" FUNC="200" SEQ="004"
PGBLKNBR="6" CHG="N" KEY="D59C78706F9B17717C51D81A1CA560B7"
REVDATE="20150314">
<effect EFFRG="104105 601602 700999" EFFTEXT="ZAP ALL">
</effect>
<list1>
<l1item>
<regulatory>
<regulation REGTYPE="AWL" REGVALUE="28-AWL-04: CDCCL"><grsymbol
GNBR="REGULATORY">28-AWL-04: CDCCL</regulation>
</regulatory>
<para>Do the bond check to measure the joint between the connector backshell
and primary structure with the <ted>
<toolnbr>COM-1550</toolnbr>
<toolname>intrinsically safe approved bonding meter</toolname>
</ted>, for each connector listed in Tables below:</para>
. . .
</l1item>
</list1>
</subtask>

Rev #26 01/13/21 D6-82973

Page -265
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REGULATORY

1.3.4 Element: entry

<!ELEMENT entry - O (regulatory | %text; | %w.c; | graphic)* >

Printed Example:
Example not available at this time

SGML:
Example not available at this time

1.4 BOEING APPLICATION RULES

a. Per airline requirements regarding which regulatory types are displayed in the
PDF, the regulatory tables located in the front matter will match the regulatory
types contained within the body of the manual. For the SGML, the body of the
manual will contain all the regulatory types authored for a particular airline.
However, upon airline request to filter the regulatory data, the regulatory tables in
the front matter of the SGML will not match the data found in the body of the
manual.
b. The regulatory tables in the front matter are SGML CALS tables and are not under
regulatory authority. These tables are provided for informational purposes only to
indicate where to find the regulatory data within the body of the manual. It will be
up to the data receiver to display or not display the regulatory information per their
airlines requirements.

Rev #26 01/13/21 D6-82973

Page -266
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

RELTASK

1.0 ELEMENT NAME

reltask - Related Task

1.1 ELEMENT CONTENT

<!ELEMENT reltask - - (rtaskcd, rtasknbr) >

The reltask element indicates other related task cards that are identified by a related
task card code and card number. The value may be either B (before), A (after),
W (width), R (Precluded by) or P (Precludes). The reltask element appears in the
context of the following elements:

ELEMENT

mainhead

cchead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -267
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

RELTASK

1.3.1 Element: mainhead

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

SGML:
<taskcard cardnbr="05-005-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000018889">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>
<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
<reltask>
<rtaskcd>W</rtaskcd>
<rtasknbr>
<refint refid="T0000018732">05-033-00-29</refint>
</rtasknbr>
</reltask>
. . .
</mainhead>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -268
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

RELTASK

1.3.2 Element: cchead

<!ELEMENT cchead - - (skill+, workarea+, reltask*, specnote?,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

SGML:
<taskcard cardnbr="07-007-00-01" mprog="RAR" chg="N" key="T0000018580">
<effect effrg="001999">
</effect>
<cchead>
<skill>ELEC</skill>
<workarea>LWR FUSELAGE</workarea>
<reltask>
<rtaskcd>B</rtaskcd>
<rtasknbr>
<refint refid="T0000019511">06-006-00-04</refint>
</rtasknbr>
</reltask>
. . .
</cchead>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -269
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REPEAT

1.0 ELEMENT NAME

repeat - Repeat Interval

1.1 ELEMENT CONTENT

<!ELEMENT repeat - - (thrshtyp, multiple, unit, sample) >

The repeat element defines the measure of initial threshold for the repeat cycle. The
repeat element appears in the context of the following element.

ELEMENT

interval

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -270
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REPEAT

1.3.1 Element: interval

<!ELEMENT interval - - (version, thrshold, repeat?, phase?)>

Printed Example:

Rev #26 01/13/21 D6-82973

Page -271
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REVST_REVEND

1.0 ELEMENT NAME

revst/revend - Revision Start/Revision End

1.1 ELEMENT CONTENT

<!ELEMENT revst - o EMPTY >
<!ELEMENT revend - o EMPTY >

The revst element identifies that all data following the tag, until the tag revend is
reached, is revised with information from the manufacturer in this revision of the
document. The revend tag identifies the end of the revised data. The revst and revend
elements are an inclusion and may occur anywhere within the TC but cannot cross
anchors.

ELEMENT

taskcard

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Revised Content Identified by revst/revend

Printed Example:

SGML:
<taskcard cardnbr="20-010-01-01" mprog="SYS" etopsind="No" chg="R"
key="T0000026722">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
. . .
<table frame="ALL" id="F755435E26E8F85F75CF7B46C0057F80">
<seqnum>601</seqnum>
<title>Table 601. </title>
. . .
<entry valign="TOP" align="CENTER">
<para><revst><revend><revst>B<revend></para>

Rev #26 01/13/21 D6-82973

Page -272
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REVST_REVEND

</entry>
<entry valign="TOP" align="LEFT">
<para> AL420 - Spoiler 4 Position, FCC</para>
</entry>
</row>
<row>
<entry valign="TOP" align="CENTER">
</entry>
<entry valign="TOP" align="CENTER">
<para> D42102P</para>
</entry>
<entry valign="TOP" align="CENTER">
<para>601</para>
</entry>
<entry valign="TOP" align="CENTER">
<para><revst><revend><revst>B<revend></para>
</entry>
<entry valign="TOP" align="LEFT">
<para> AL720A Spoiler 4<revst><revend><revst> Position, FCC<revend></para>
</entry>
. . .
</taskcard>

1.3.2 New Content Identified by revst/revend

Printed Example:

SGML:
<revst>
<taskcard cardnbr="32-230-00-02" mprog="SYS" etopsind="No" chg="N"
key="T0000032026">

Rev #26 01/13/21 D6-82973

Page -273
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REVST_REVEND

<effect effrg="001999" efftext="ZAP ALL">

</effect>
<chgdesc>Added Task.</chgdesc>
<chgdesc>Added new task card. Revised task to have separate left and right
task cards. Task 32-230-00-01 is left side task card. Task 32-230-00-02 is
right side task card.</chgdesc>
. . .
</taskcard>
<revend>

1.3.3 Deleted Content Identified by revst/revend

Example 1: Deleted Anchor

Printed Example: deleted content is not viewable on the printed page.

SGML:
<revst><revend><taskcard CARDNBR="33-065-00-01" MPROG="SYS" ETOPSIND="No"
CHG="D" KEY="T0000106537" REVDATE="20210115">
<revst><deleted><chgdesc>Revised</chgdesc>
<chgdesc>Deleted Task. Task Deleted, not an applicable option for the 737 MAX
series airplanes.</chgdesc>
<revend></taskcard>

Example 2: Deleted content:

Printed Example:

SGML:
<entry valign="TOP" align="CENTER">
<para>W1022</para>
</entry>
<entry valign="TOP" align="CENTER">
<para> D42100P</para>
</entry>
<entry valign="TOP" align="CENTER">
<para>601</para>
</entry>
<entry valign="TOP" align="CENTER">
<para><revst><revend><revst>B<revend></para>
</entry>
<entry valign="TOP" align="LEFT">
<para> AL420 - Spoiler 4 Position, FCC</para>
</entry>
</row>

Rev #26 01/13/21 D6-82973

Page -274
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REVST_REVEND

1.3.4 Numbering Change (for Anchor Elements only) Identified by revst/revend

Printed Example - Example taken from the FRMFIM

Added new
subtask

SGML:
<subtask CHAPNBR="23" SECTNBR="27" SUBJNBR="00" FUNC="730" SEQ="028"
PGBLKNBR="2" CHG="R" KEY="N1544B34BCF39ACEF724D4843D03389A"
REVDATE="20100105">
<effect EFFRG="7AA7AH 7AJ7AN 7AP7AP 7AR7AY 7BA7BH 7BJ7BN 7BP7BP 7BR7BY
7CA7ZZ" EFFTEXT="ZAP ALL">
</effect>
<chgdesc>Changed the fault isolation procedure.</chgdesc>
<list1>
<l1item>
<revst><revend><para>Do this ground test on the MAT: 31 AIMS - Right AIMS,
System Test, CPM/Comm (M001) in Right AIMS Module Reset.</para>
<list2>
<l2item>
<para>If VHF-C is selected when the line select key (LSK) adjacent to it is
pushed, then you corrected the fault.</para>
</l2item>
<revst><l2item>
<para>If VHF-C is not selected when the line select key (LSK) adjacent to it
is pushed, then continue.</para>
</l2item>
<revend></list2>
</l1item>
</list1>
</subtask>
<revst><revend><subtask CHAPNBR="23" SECTNBR="27" SUBJNBR="00" FUNC="960"
SEQ="011" PGBLKNBR="2" CHG="N" KEY="AE5A0A52D57AB37C2F74AEAC473F891F"
REVDATE="20100105">
<revst><effect EFFRG="7AA7AH 7AJ7AN 7AP7AP 7AR7AY 7BA7BH 7BJ7BN 7BP7BP 7BR7BY
7CA7ZZ" EFFTEXT="ZAP ALL">
</effect>

Rev #26 01/13/21 D6-82973

Page -275
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REVST_REVEND

<chgdesc>Changed the fault isolation procedure.</chgdesc>

<chgdesc>Added SUBTASK 23-27-00-960-011</chgdesc>
<list1>
<l1item>
<para>Replace the left control display unit.</para>
<para>These are the tasks:</para>
<para><refext REFMAN="AMM" REFLOC="34-61-02-020-801">Control Display Unit
(CDU) Removal, AMM TASK 34-61-02-020-801</refext>,
</para>
<para><refext REFMAN="AMM" REFLOC="34-61-02-420-801">Control Display Unit
(CDU) Installation, AMM TASK 34-61-02-420-801</refext>.</para>
<list2>
<l2item>
<para>If VHF-C is selected when the line select key (LSK) adjacent to it is
pushed, then you corrected the fault.</para>
</l2item>
<l2item>
<para>If VHF-C is not selected when the line select key (LSK) adjacent to it
is pushed, then continue.</para>
</l2item>
</list2>
</l1item>
</list1>
<revend></subtask>
<revst><revend></topic>

Note: Whenever items are renumbered, <revst><revend> tags are inserted to

denote the change in numbering.

1.3.5 Attribute Change Identified by revst/revend

Printed Example - Example taken from the FRMFIM

Rev #26 01/13/21 D6-82973

Page -276
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REVST_REVEND

SGML:
<subtask CHAPPREF="H" CHAPNBR="77" SECTNBR="05" SUBJNBR="15" FUNC="810"
SEQ="044" CONFLTR="H" VARNBR="00" PGBLKNBR="2" CHG="R"
KEY="B29167940A070B5B50EA9ECBAC43C259" REVDATE="20200105">
<effect EFFRG="101143 202999" EFFTEXT="ZAP 101-143, 202-999">
</effect>
<chgdesc>Changed engine prefix from “G” to “H”.</chgdesc>
. . . <l1item>
<para>Do this task: <revst><refext REFMAN="AMM" REFLOC="H71-00-00-700-811-
H01"><revend>Test No. 12A - Low Pressure System (Fan/LPT) Trim Balance (For
SCU P/N S332W401-200), AMM TASK 71-00-00-700-811-H01</refext> or <refext
REFMAN="AMM" REFLOC="H71-00-00-700-821-H02">Test No. 12B - Low Pressure
System (Fan/LPT) Trim Balance (For SCU P/N 241-322-008-022 or 241-322-007-
021, Media P/N 241-322-915-001), AMM TASK 71-00-00-700-821-H02
</refext>.</para>
<list2>

1.4 BOEING IMPLEMENTATION RULES

a. <revst> and <revend> tags are indicators for turning on and off revision bars in the
output products, such as paper or PDF.
b. <revst> and <revend> tags surround revised, added or deleted content.
c. When an entire element has been revised or added, the <revst> and <revend> tags
surround the start and end tags of the element. That is, the <revst> tag precedes the
start tag of the modified element, and the <revend> tag follows the end tag of the
revised element.
d. When multiple contiguous elements (non anchor) have changed, the <revst> tag
precedes start tag of the first changed element, and the <revend> tag follows the
end tag of the last changed element. In other words, a single pair of <revst> and
<revend> tags surrounds a string of contiguous changed elements.
e. When an entire anchor element is revised it is only marked by a CHG=“R”. No
<revst><revend> tags preceed or follow the revised anchor.

Rev #26 01/13/21 D6-82973

Page -277
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REVST_REVEND

f. A new anchor will have a <revst><revend> pair preceeding the start element and a
pair preceeding the end element. Content will have a <revst><revend> around it,
including the graphics at the end of each taskcard.

Example:
...
<revst><revend><taskcard CARDNBR="20-182-00-01" MPROG="SYS" ETOPSIND="No"
CHG="N" KEY="T0000109524" REVDATE="20210115">
<revst><effect EFFRG="001999" EFFTEXT="ZAP ALL">
</effect>
<chgdesc>Added TASKCARD</chgdesc>
<chgdesc>Added Task. Task was added as a result of LHIRF analysis and as
accepted by the 737 MAX Industry Steering Committee meeting, LHIRF session
during the October 2018 and May 2020 WebEx ISC.</chgdesc>
<mainhead>
. . .
</tcbody>
<revend><graphic CHAPNBR="05" SECTNBR="55" SUBJNBR="25" FUNC="990" SEQ="845"
PGBLKNBR="6" ID="B0A83E363C1A5353C8DD9BC7F1BC3668">
<revst><effect EFFRG="001999" EFFTEXT="ZAP ALL">
</effect>
<seqnum>1</seqnum>
<title>Figure 1. Loop Resistance Test of Wire Bundle - Left Engine (MRB 20-
182-00)</title>
<sheet GNBR="HE01598281484B979BA550A7B642D472" SHEETNBR="1" IMGAREA="AP"
ID="J8450DC6A9136B541EB01C3308549C13">
<effect EFFRG="001999" EFFTEXT="ZAP ALL">
</effect>
</sheet>
<revend></graphic>
<revst><revend><graphic CHAPNBR="05" SECTNBR="55" SUBJNBR="25" FUNC="990"
SEQ="846" PGBLKNBR="6" ID="OF8C4570116ECEECF520AC36CBA55A85">
<revst><effect EFFRG="001999" EFFTEXT="ZAP ALL">
</effect>
<seqnum>2</seqnum>
<title>Figure 2. Loop Resistance Test of Wire Bundle - Left Engine (MRB 20-
182-00)</title>
<sheet GNBR="G7814A8C09AD25EBB33C76C03C6B43BD" SHEETNBR="1" IMGAREA="AP"
ID="E6D8FC56CED39FE11215E96A9C1390D5">
<effect EFFRG="001999" EFFTEXT="ZAP ALL">
</effect>
</sheet>
<revend></graphic>
<revst><revend></taskcard>

Rev #26 01/13/21 D6-82973

Page -278
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

REVST_REVEND

g. <revst><revend> tags indicate the start and end of a deletion:

• If there is a deleted anchor, then you will see <revst><revend> pairs before the
deleted anchor. Content will have a <revst><revend> around it.
• If the <deleted> tag is used, the <revst> and <revend> tags surround it and the
<chgdesc>; reference 1.3.3 example 1.
• If the <deleted> tag is not used (non-anchor data), the <revst> is followed
immediately by the <revend> tag; reference 1.3.3 example 2.
• Per ATA rules, the CHG attribute does not propagate upwards or downwards in
the document’s anchor heirarchy when content is changed; however, when a sub-
anchor (i.e., child anchor) is added or deleted, its parent anchor will be marked
as revised (CHG=“R”) and the sub-anchor will be marked as new (CHG=“N”) or
deleted (CHG=“D”).
h. <revst> and <revend> tags never overlap anchors.

Rev #26 01/13/21 D6-82973

Page -279
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ROW

1.0 ELEMENT NAME

row - Row

1.1 ELEMENT CONTENT

<!ELEMENT row - o (entry+) >

The row element is used to define a set of cells (entry elements) that together form a
single logical line or row in the table. A logical line may span more than one physical
line depending on the contents of each cell and the defined size of the cells in the row.
The row element appears in the context of the following elements:

ELEMENT

thead

tfoot

tbody

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT row - o (entry+) >
<!ATTLIST row
rowsep %yesorno; #IMPLIED >

Attribute Name Always Provided May or Not be

Provided

rowsep X

1.2.1 Attribute: rowsep

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -280
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ROW

1.3.1 Element: thead

<!ELEMENT thead - o (colspec*, row+) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
</effect>
. . .
<pretopic>
<title>References</title>
<table frame="NONE">
<tgroup cols="3" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="320*">
<colspec colwidth="100*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>
<para>Title</para>

Rev #26 01/13/21 D6-82973

Page -281
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ROW

</entry>
</row>
</thead>
. . .
</taskcard>

1.3.2 Element: tfoot

<!ELEMENT tfoot - o (colspec*, row+) >

Not used.

1.3.3 Element: tbody

!ELEMENT tbody - o (row+) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
</effect>
. . .
<pretopic>
<title>References</title>
<table frame="NONE">

Rev #26 01/13/21 D6-82973

Page -282
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ROW

<tgroup cols="3" colsep="0" rowsep="0">

<colspec colwidth="180*">
<colspec colwidth="320*">
<colspec colwidth="100*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>
<para>Title</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry>
<para><refext refman="AMM" refloc="28-00-00-010-802">28-00-00-010-802
</refext></para>
</entry>
<entry>
<para>Fuel Tank Access (Main Tanks) (P/B 201)</para>
</entry>
</row>
</tbody>
</tgroup>
</table>
</pretopic>

Rev #26 01/13/21 D6-82973

Page -283
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

RTASKCD

1.0 ELEMENT NAME

rtaskcd - Related Task Code

1.1 ELEMENT CONTENT

<!ELEMENT rtaskcd - - (#PCDATA) >

The rtaskcd element is an alpha code that indicates that the current task should be
performed before, with, or after the related task. The rtaskcd element appears in the
context of the following element.

ELEMENT

reltask

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: reltask

<!ELEMENT reltask - - (rtaskcd, rtasknbr) >

Printed Example:

SGML:
<taskcard cardnbr="05-005-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000018889">
<effect effrg="001999">
</effect>
<mainhead>

Rev #26 01/13/21 D6-82973

Page -284
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

RTASKCD

<source>MRB</source>
<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
<reltask>
<rtaskcd>W</rtaskcd>
<rtasknbr>
<refint refid="T0000018732">05-033-00-29</refint>
</rtasknbr>
</reltask>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -285
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

RTASKNBR

1.0 ELEMENT NAME

rtasknbr - Related Task Card Number

1.1 ELEMENT CONTENT

<!ELEMENT rtasknbr - - (#PCDATA | refint)+ >

The rtasknbr element is the task card number of the related task. The rtasknbr element
appears in the context of the following element.

ELEMENT

reltask

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: reltask

<!ELEMENT reltask - - (rtaskcd, rtasknbr) >

Printed Example:

SGML:
<taskcard cardnbr="05-005-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000018889">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>
<skill>AIRPL</skill>

Rev #26 01/13/21 D6-82973

Page -286
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

RTASKNBR

<workarea>LWR FUSELAGE</workarea>
<reltask>
<rtaskcd>W</rtaskcd>
<rtasknbr>
<refint refid="T0000018732">05-033-00-29</refint>
</rtasknbr>
</reltask>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -287
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SAMPLE

1.0 ELEMENT NAME

sample - Sample

1.1 ELEMENT CONTENT

<!ELEMENT sample - - (#PCDATA) >

The sample element is an airplane fleet sampling interval expressed as a percentage.

The sample element appears in the context of the following elements:

ELEMENT

thrshold

repeat

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: thrshold

<!ELEMENT thrshold - - (thrshtyp, ((multiple, unit, sample)
| optask)) >

Printed Example: (The sample element does not display in the printed Task Card).

Rev #26 01/13/21 D6-82973

Page -288
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SAMPLE

. . .
</taskcard>

1.3.2 Element: repeat

<!ELEMENT repeat - - (thrshtyp, multiple, unit, sample)>

Printed Example: (The sample element does not display in the printed Task Card).

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
. . .
<repeat>
<thrshtyp>N</thrshtyp>
<multiple>100</multiple>
<unit>FC</unit>
<sample>100</sample>
</repeat>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -289
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SBEFF

1.0 ELEMENT NAME

sbeff - Service Bulletin Effectivity

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT sbeff - o EMPTY >

The sbeff element contains the data necessary to determine the range of aircraft/
engines for which an anchor or other element is effective. It is used to further define
the overall effectivity defined in the parent effect element resulting from the
incorporation (or non-incorporation) of Service Bulletins. The effectivity can be either
given as a computer interpretable string of numbers (effrg) and/or as a human-readable
sentence (efftext). The sbeff element appears in the context of the following element:

ELEMENT

effect

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT sbeff - o EMPTY >
<!ATTLIST sbeff
effrg CDATA #IMPLIED
efftext CDATA #IMPLIED
sbnbr CDATA #REQUIRED
sbcond CDATA #REQUIRED
sbrev CDATA #IMPLIED >

Attribute Name Always Provided Provided When Data

is Available

effrg X
efftext X

sbnbr X

sbcond X

sbrev X

Rev #26 01/13/21 D6-82973

Page -290
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SBNBR

1.0 ELEMENT NAME

sbnbr - Service Bulletin Number

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT sbnbr - - (#PCDATA) >

The sbnbr element identifies the number of a Service Bulletin. This number must
include all elements such as the aircraft or engine type and model, the ATA number
and Sequence number necessary to uniquely identify an SB. The sbnbr element
appears in the context of the following elements.

ELEMENT

title

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -291
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SEQNUM

1.0 ELEMENT NAME

seqnum - Sequential Number

1.1 ELEMENT CONTENT

<!ELEMENT seqnum - - (#PCDATA) >

The seqnum element is used to provide the information required to sequentially

number tables and figures. The seqnum element appears in the context of the following
elements:

ELEMENT

table

graphic

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: table

<!ELEMENT table - - ((seqnum?, title?, tgroup, ftnote*)
| graphic+) -(table) >

Printed Example:

SGML:
<subtask chapnbr="12" sectnbr="21" subjnbr="04" func="840" seq="007"
pgblknbr="3" id="K99A4B3DC11765A20EEB3B4040DE61D9">
<effect effrg="701705 731732 771799 941945 981999" efftext="ZAP ALL">
</effect>
<list1>

Rev #26 01/13/21 D6-82973

Page -292
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SEQNUM

<l1item>
<para>On the P61 panel, move the FLT CONTROL HYD POWER - TAIL switches to the
NORM position.</para>
<table frame="ALL" id="O668FC9F5A2172A3032426F779808B6E">
<seqnum>1</seqnum>
<title>Table 1. Elevator PCU Lubrication</title>
<tgroup cols="5" colsep="1" rowsep="1">
<colspec colname="COL1" colwidth="5*">
. . .
</table>

Rev #26 01/13/21 D6-82973

Page -293
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SEQNUM

1.3.2 Element: graphic

<!ELEMENT graphic - - (effect, seqnum, title?, sheet+) >

Printed Example:

SGML:
<graphic chapnbr="12" sectnbr="21" subjnbr="04" func="990" seq="801"
pgblknbr="3" id="BE9721EC9FC48AD398F19713F17D6272">
<effect effrg="701705 731732 771799 941945 981999" efftext="ZAP ALL">
</effect>

Rev #26 01/13/21 D6-82973

Page -294
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SEQNUM

<seqnum>1</seqnum>
<title>Figure 1. Elevator Power Control Unit (PCU) Servicing</title>
<sheet gnbr="HF0AC3BBC9E59DF9141FC7C478221DA2" sheetnbr="1"
id="MEA0232A25BDDDDEEBEBB37DA9F19337">
<effect effrg="701705 731732 771799 941945 981999" efftext="ZAP ALL">
</effect>
</sheet>
<sheet gnbr="CC4C041FBEE167D0720EB29A67BCF25A" sheetnbr="2"
id="HEDFA2BA7BE6DC2D6B1D6D6E25463AA0">
<effect effrg="701705 731732 771799 941945 981999" efftext="ZAP ALL">
</effect>
</sheet>
</graphic>

Rev #26 01/13/21 D6-82973

Page -295
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SKILL

1.0 ELEMENT NAME

skill - Skill

1.1 ELEMENT CONTENT

<!ELEMENT skill - - (#PCDATA) >

The skill element indicates the skill type required to perform a given task. The skill
element appears in the context of the following elements:

ELEMENT

mainhead

cchead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: mainhead

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

Page -298
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SHEET

1.0 ELEMENT NAME

sheet - Sheet

1.1 ELEMENT CONTENT

<!ELEMENT sheet - - (effect, title?, gdesc?) >

The sheet element provides the actual link between the text-based document instance
and a single graphic image “file”. The sheet element appears in the context of the
following element:

ELEMENT

graphic

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT sheet - - (effect, title?, gdesc?) >
<!ATTLIST sheet
gnbr ENTITY #REQUIRED
sheetnbr CDATA #IMPLIED
imgarea (AP|BP|CP|DL|EL|FP|GP|HL|IL) #IMPLIED
id ID #REQUIRED >

Attribute Name Always Provided Provided When Data

is Available

gnbr X

sheetnbr X

imgarea X
id X

Rev #26 01/13/21 D6-82973

Page -299
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SHEET

1.2.1 Attribute: gnbr

Description: Graphic Number (gnbr) is the sender-assigned identification of a
graphic. In the DTD and the document instance, this is an attribute with
a value of ENTITY= that corresponds to the Graphic Image File Name.

1.2.2 Attribute: sheetnbr

Description: Sheet Number is the sequential (but not necessarily contiguous)
number of a sheet within a graphic. It can be used to link a graphic
reference to a particular sheet or image within the set of sheets in a
graphic.

Boeing Application Rules:

a. If there are multiple sheets, the first sheetnbr will begin with 1.
b. If there is only one sheet, it will be numbered 1 in the SGML output.
c. The sheet number is applied to the sheetnbr attribute of the sheet tag.

1.2.3 Attribute: imgarea

Description: This attribute is used to define the size of an image so it may be
rendered by the receiver of the file.

Image Page Size Page Size Orientation Image Area (maximum)

Area Description Limits
Code (inches) Millimeters Inches

AP Full 8.5 x 11 / A4 Portrait 171.45 x 209.55 6.75 x 8.25

BP Half 8.5 x 11 / A4 Portrait 171.45 x 97.79 6.75 x 3.85

CP Quarter 8.5 x 11 / A4 Portrait 171.45 x 44.45 6.75 x 1.75

DL Full 11 x 8.5 / A4 Landscape 109.55 x 171.45 8.25 x 6.75

EL “True” Landscape 11 x 8.5 / A4 Landscape 228.6 x 152.40 9.0 x 6.0

FP Full, small book 5.5 x 8.5 / A5 Portrait 117 x 155 4.61 x 6.1

GP Half, small book 5.5 x 8.5 / A5 Portrait 117 x 66 4.61 x 2.6

HL Foldout 16 x 11 / A3 Landscape 361.95 x 209.55 14.25 x 8.25

source - Source

1.1 ELEMENT CONTENT

<!ELEMENT source - - (#PCDATA) >

The source element is the source of the task card task in order of rank, the highest
being CMR (Certification Maintenance Requirement), the next highest being MRB
(Maintenance Review Board), the last being MPD (Maintenance Planning Data). The
value can also be blank. The element source appears in the context of the following
element.

ELEMENT

mainhead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -304
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SOURCE

1.3.1 Element: mainhead

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

...

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>
. . .
</mainhead>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -305
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SPANSPEC

1.0 ELEMENT NAME

spanspec - Span Specification

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT spanspec - o EMPTY >

The spanspec element is a placeholder element for attributes to specify the intended
presentation of a row. The spanspec element appears in the context of the following
element:

ELEMENT

tgroup

1.2 ATTRIBUTE MARKUP RULES

<!ELEMENT spanspec - o EMPTY >
<!ATTLIST spanspec
namest NMTOKEN #REQUIRED
nameend NMTOKEN #REQUIRED
spanname NMTOKEN #IMPLIED
align (left|right|center
|justify|char) 'center'
charoff NUTOKEN #IMPLIED
char CDATA #IMPLIED
colsep %yesorno; #IMPLIED
rowsep %yesorno; #IMPLIED >

Attribute Name Always Provided Provided When Data

is Available

namest X

nameend X
spanname X

align X

charoff X
char X

colsep X

rowsep X

Rev #26 01/13/21 D6-82973

Page -306
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SPECNOTE

1.0 ELEMENT NAME

specnote - Special Note

1.1 ELEMENT CONTENT

<!ELEMENT specnote - - (%text;) >

The specnote element is a special note. This note is to provide information associated
with the task that is important enough for users to veiw before any other notes. The
specnote element appears in the context of the following element.

ELEMENT

mainhead
cchead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

STD

1.0 ELEMENT NAME

std - Standard Tool and Equipment Description

1.1 ELEMENT CONTENT

<!ELEMENT std - - (stdnbr, stdname) >

The standard tool and equipment description (std) element identifies data associated
with tools and equipment not listed in the Illustrated Tools and Equipment Manual.
The std element appears in the context of the following element:

ELEMENT

para

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Printed Example:

SGML:
<taskcard cardnbr="20-650-00-01" mprog="SYS" etopsind="No" chg="R"
key="T0000025611">
<effect effrg="001999" efftext="ZAP ALL">
. . .
<subtask chapnbr="20" sectnbr="60" subjnbr="02" func="100" seq="001"
pgblknbr="2" id="N9EC9C473CDD556742505C994F813E00">

Rev #26 01/13/21 D6-82973

Page -310
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

STD

<effect effrg="001999" efftext="ZAP ALL">

</effect>
<list1>
<l1item>
<para>Do these steps to clean the wire bundles and the area around them:
</para>
<note>
<para>This procedure cleans the wire bundles and the area around where
significant dust accumulates to reduce the amount of combusible material.
</para>
</note>
<list2>
<l2item>
<para>Remove loose contamination by hand.</para>
</l2item>
<l2item>
<para>Use a <std>
<stdnbr><revst>STD-183<revend></stdnbr>
<stdname><revst><revend><revst>vacuum cleaner<revend></stdname>
</std> to remove accumulations of dust.</para>
</l2item>
<l2item>
<para>Use a <std>
<stdnbr><revst>STD-123<revend></stdnbr>
<stdname><revst><revend><revst>soft bristle brush<revend></stdname>
</std> to loosen accumulations of dust that remain and vacuum the area
again.</para>
</l2item>
</list2>
</l1item>
</list1>
</subtask>

Rev #26 01/13/21 D6-82973

Page -311
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

STDNAME

1.0 ELEMENT NAME

stdname - Standard Tool and Equipment Name

1.1 ELEMENT CONTENT

<!ELEMENT stdname - - (#PCDATA) >

The stdname element identifies the name or textual description of a standard tool or
equipment. The stdname element appears in the context of the following elements.

ELEMENT

std

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: std

<!ELEMENT std - - (stdnbr, stdname) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -312
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

STDNAME

<para>Do these steps to clean the wire bundles and the area around them:</
para>
<note>
<para>This procedure cleans the wire bundles and the area around where
significant dust accumulates to reduce the amount of combusible material.</
para>
</note>
<list2>
<l2item>
<para>Remove loose contamination by hand.</para>
</l2item>
<l2item>
<para>Use a <std>
<stdnbr><revst>STD-183<revend></stdnbr>
<stdname><revst><revend><revst>vacuum cleaner<revend></stdname>
</std> to remove accumulations of dust.</para>
</l2item>
<l2item>
<para>Use a <std>
<stdnbr><revst>STD-123<revend></stdnbr>
<stdname><revst><revend><revst>soft bristle brush<revend></stdname>
</std> to loosen accumulations of dust that remain and vacuum the area
again.</para>
</l2item>
</list2>
</l1item>
</list1>
</subtask>

Rev #26 01/13/21 D6-82973

Page -313
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

STDNBR

1.0 ELEMENT NAME

stdnbr - Standard Tool and Equipment Number

1.1 ELEMENT CONTENT

<!ELEMENT stdnbr - - (#PCDATA) >

The stdnbr element identifies the unique code or part number by which a standard tool
or equipment can be identified. The stdnbr element appears in the context of the
following elements.

ELEMENT

std

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: std

<!ELEMENT std - - (stdnbr, stdname) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -314
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

STDNBR

<l1item>
<para>Do these steps to clean the wire bundles and the area around them:</
para>
<note>
<para>This procedure cleans the wire bundles and the area around where
significant dust accumulates to reduce the amount of combusible material.</
para>
</note>
<list2>
<l2item>
<para>Remove loose contamination by hand.</para>
</l2item>
<l2item>
<para>Use a <std>
<stdnbr><revst>STD-183<revend></stdnbr>
<stdname><revst><revend><revst>vacuum cleaner<revend></stdname>
</std> to remove accumulations of dust.</para>
</l2item>
<l2item>
<para>Use a <std>
<stdnbr><revst>STD-123<revend></stdnbr>
<stdname><revst><revend><revst>soft bristle brush<revend></stdname>
</std> to loosen accumulations of dust that remain and vacuum the area
again.</para>
</l2item>
</list2>
</l1item>
</list1>
</subtask>

Rev #26 01/13/21 D6-82973

Page -315
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SUB

1.0 ELEMENT NAME

sub - subscript

1.1 ELEMENT CONTENT

<!ELEMENT sub - - (#PCDATA) >

Subscript is used to identify a number, symbol or letter next to or slightly below

another character. The sub element appears in the context of the following elements:

ELEMENT

para

title

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Printed Example:

SGML:
<subtask chapnbr="26" sectnbr="22" subjnbr="00" func="860" seq="020"
pgblknbr="5" id="P98C7370FF491335CDBE8BCAC1735B10">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Turn the APU fire handle in the CW<revst> (Clockwise)<revend>
direction.</para>
<list2>

Rev #26 01/13/21 D6-82973

Page -316
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SUB

<l2item>
<para>Make sure the BOTTLE DISCHARGE light on the test box comes on.</para>
</l2item>
<l2item>
<para>Write down the voltage shown on the multimeter as
(<revst><revend><revst>V<sub>1</sub><revend>).</para>
</l2item>
<l2item>
<para>Set the switch on the test box to ON.</para>
</l2item>
<l2item>
<para>Write down the voltage shown on the multimeter as
(<revst><revend><revst>V<sub>2</sub><revend>).</para>
</l2item>
</list2>
</l1item>
</list1>
</subtask>

1.3.2 Element: title

<!ELEMENT title - - (#PCDATA | ein | sbnbr | sub | super)+ >

Note: Examples below have been fabricated

Printed Example:

HZ1125 - NITROGEN/LIQUID H20 (DPM 154-1)

SGML:
<title>HZ1125—NITROGEN/LIQUID H<sub>2</sub>0 (DPM 154-1)</title>

Rev #26 01/13/21 D6-82973

Page -317
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SUBTASK

1.0 ELEMENT NAME

subtask - Subtask

1.1 ELEMENT CONTENT

<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect) >

The subtask element identifies a subtask (AMTOSS subdivision of a task that contains
one or more steps of procedural data). A subtask tag only covers one variant of a
subtask (e.g., subtask 29-11-53-432-006-A01 and subtask 29-11-53-432-007 are
separately marked with two different subtask tags). The first sub-elements (grphcref,
ref, warning, caution, note) apply to the whole subtask and only that subtask. The
subtask element appears in the context of the following element:

ELEMENT

topic

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT subtask - - (effect, %g.r;, regulatory*, %w.c;,
note*, list1) +(effect) >
<!ATTLIST subtask
chappref CDATA #IMPLIED
chapnbr NUMBER #REQUIRED
sectnbr NUMBER #REQUIRED
subjnbr NUMBER #REQUIRED
func CDATA #REQUIRED
seq CDATA #REQUIRED
confltr CDATA #IMPLIED
varnbr NUMBER #IMPLIED
alunqi CDATA #IMPLIED
pgblknbr NUMBER #IMPLIED
confnbr NUMBER #IMPLIED
id ID #IMPLIED >

Attribute Name Always Provided Provided When Data

is Available
chappref X

chapnbr X

sectnbr X
subjnbr X

func X

Rev #26 01/13/21 D6-82973

Page -318
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SUBTASK

Attribute Name Always Provided Provided When Data

is Available

seq X
confltr X

varnbr X

alunqi X
pgblknbr X

confnbr X

id X

1.2.1 Attribute: chappref

Description: Chapter Prefix (chappref) is a unique identifier for chapters with
multiple engine types. This identifier is used with the amtoss
numbering scheme as defined in ATA Spec. 2200.

Boeing Application Rules:

a. chappref is an implied attribute, however it will be supplied in the eMOD data
when data is available.

1.2.2 Attribute: chapnbr

Description: Chapter Number (chapnbr) is the identification number of a chapter.
chapnbr is a two-digit number (00 up to 99) as defined in the
ATA Spec. 2200 (XX-xx-xx-xxx-xxx-xxx-xxx).

1.2.3 Attribute: sectnbr

Description: Section Number (sectnbr) is the identification number of a section.
sectnbr is a two-digit number (00 to 99) as defined in the
ATA Spec. 2200 (xx-XX-xx-xxx-xxx-xxx-xxx).

1.2.4 Attribute: subjnbr

Description: Subject Number (subjnbr) is the identification number of a subject.
subjnbr is a two-digit number (00 to 99), as defined in the
ATA Spec. 2200 (xx-xx-XX-xxx-xxx-xxx-xxx).

Rev #26 01/13/21 D6-82973

Page -319
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SUBTASK

1.2.5 Attribute: func

Description: Function Code (func) identifies the first element of a subtask. The first
two digits of the func is the numerical representation of the function
corresponding to the task/subtask. func is defined in the ATA Spec.
2200 as ranging from 00-99. The third digit is for the manufacturer’s
use.

Boeing Application Rules:

a. When func is not available the attribute will default to “999”.

1.2.6 Attribute: seq

1.1 ELEMENT CONTENT

<!ELEMENT super - - (#PCDATA) >

Superscript is used to identify a number, symbol or letter next to and slightly above
another character. The super element appears in the context of the following elements:

ELEMENT

para

title

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

NOTE: Examples below have been fabricated.

Printed Example:

SGML:
<subtask chg="R" revdate="20030901" key="JB6FAD115DE7D195FBE3775BEE3A4244"
func="720" seq="002" subjnbr="01" sectnbr="34" chapnbr="21" pgblknbr="5">
<effect effrg="475999" efftext="ZAP ALL">
</effect>
<chgdesc>Changed the data for clarity and consistency.</chgdesc>
. . .
<l2item>
<para>Turn the V6 valve in the counterclockwise direction to get
15.000 in/H<revst><sub>2</sub><revend>O (0.038 kg/cm

Rev #26 01/13/21 D6-82973

Page -323
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SUPER

<revst><super>2</super><revend>) ± 2.000 in/H<revst><sub>2

</sub><revend>O (0.005 kg/cm<revst><super>2</super><revend>) on gage
GA3.</para>
. . .
</subtask>

1.3.2 Element: title

<!ELEMENT title - - (#PCDATA | ein | sbnbr | sub | super)+ >

Similar to para; refer to 1.3.1 for example.

Rev #26 01/13/21 D6-82973

Page -324
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SUPLDATA

1.0 ELEMENT NAME

supldata - Supplemental MPD Data

1.1 ELEMENT CONTENT

<!ELEMENT supldata - - (manhours, nbrpeopl, elaptime,
tc_manhours?, tc_nbrpeopl?,
tc_elaptime?, taskctgy?, feftctgy*)>

The supldata element identifies data derived from the MPD. The supldata element
appears in the context of the following element.

ELEMENT

mpditem

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: mpditem

<!ELEMENT mpditem - - (mpdnbr, taskloc?, linspect?, title?,
taskdesc?, ch5tskno?, awlimit?,
supldata) >

Printed Example: The mpditem information does not appear on the printed taskcard.

Rev #26 01/13/21 D6-82973

Page -325
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

SUPLDATA

Rev #26 01/13/21 D6-82973

Page -326
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TABLE

1.0 ELEMENT NAME

table - Table

1.1 ELEMENT CONTENT

<!ELEMENT table - - ((seqnum?, title?, tgroup, ftnote*)
| graphic+) -(table) >

The table element identifies a structured table composed of entries. The table used in
the DTD is a subset (with the exception of the ENTRY contents) of the CALS Table
model. The table element appears in the context of the entity %text. The elements of
the %text entity appears in the context of the following elements:

ENTITY ELEMENT

(In %text) intnote

apapnote

eappnote

acpanote

taskproc

taskdesc

pretopic

warning

caution

note

entry

l1item through l7item

ftnote

Rev #26 01/13/21 D6-82973

Page -327
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TABLE

1.2 ATTRIBUTE MARKUP RULES

Attribute Name Always Provided Provided When Data is

Available

frame X

colsep X

rowsep X

orient X

pgwide X

id X

1.2.1 Attribute: frame

Description: Frame describes position of border side rules, as well as the required
top and bottom rules. Default=“all”.

1.2.2 Attribute: colsep

Rev #26 01/13/21 D6-82973

Page -328
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TABLE

1.2.3 Attribute: rowsep

1.2.4 Attribute: orient

Description: Orientation (orient) gives a logical indication of the intended
orientation of the table (i.e. in portrait (port) or landscape (land)
format).

1.2.5 Attribute: pgwide

Description: If the value of pgwide is other than zeros, the table runs across the page.
If only zeros, the table runs across just the width (galley) of the current
column of the page (regardless of orient). If the value is only zeros, it
has no meaning for orient=land.

1.2.6 Attribute: id
Description: Identifying unique number to allow direct SGML cross-referencing to
be performed from the refid attribute.

Page -330
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TABLE

1.3.7 Element: pretopic

<!ELEMENT pretopic - - (title, (%text; | list1)) +(effect) >

Printed Example: Example 1 - Reference Table

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
. . .
<pretopic>
<title>References</title>
<table frame="NONE">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="320*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>
<para>Title</para>
</entry>
</row>
</thead>
<tbody>
<row>

Rev #26 01/13/21 D6-82973

Page -331
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TABLE

Printed Example: Example 2 - Tools/Equipment Table with Effectivity for multiple

model/series

SGML:
<table FRAME="NONE">
<tgroup COLS="3" COLSEP="0" ROWSEP="0">
<colspec COLNAME="COL1" COLWIDTH="180*"><colspec COLNAME="COL2"
COLWIDTH="20*"><colspec COLNAME="COL3" COLWIDTH="400*"><thead>
<row ROWSEP="1">
<entry>
<para>Reference</para>
</entry>
<entry NAMEST="COL2" NAMEEND="COL3">
<para>Description</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry MOREROWS="1">
<para>COM-6457</para>
</entry>
<entry NAMEST="COL2" NAMEEND="COL3">
<para>Meter - Insulation (Range: 1-1,000 VDC or equivalent, select meter per
test requirements)</para>
</entry>
</row>
<row>
<effect EFFRG="001002 210212 222222 226226 230231 241241 501502 508999"
EFFTEXT="ZAP ALL; 757-200, -300">

Rev #26 01/13/21 D6-82973

Page -332
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TABLE

<seqnum>1</seqnum>
<title>Table 1. Elevator PCU Lubrication</title>
<tgroup cols="5" colsep="1" rowsep="1">
<colspec colname="COL1" colwidth="5*">
<colspec colname="COL2" colwidth="38*">
<colspec colname="COL3" colwidth="14*">
<colspec colname="COL4" colwidth="12*">
<colspec colname="COL5" colwidth="10*">
<thead>
<row>
. . .
</table>
</l1item>
</list1>
</subtask>

1.3.13 Element: ftnote

<!ELEMENT ftnote - - (%text;) >

Not used.

1.4 BOEING IMPLEMENTATION RULES

a. eMOD document instances support the ATA 2200 implementation of the CALS
table model and is also based on the OASIS table exchange model. OASIS
Exchange is a subset of the full CALS table model that has been designed by the
OASIS vendor consortium to provide maximum compatibility between multiple
systems.
b. The following attributes are not supported:
TABSTYLE
PGWIDE
COLSEP
c. The optional ORIENT attribute is not currently used. All eMOD tables have the
same orientation as their surrounding text.
d. The optional FRAME attribute is supplied when data is available.
e. The optional ID attribute is specified on some, but not all tables. “Pretopic” tables
which contain consumable, cross-reference, tool, part, zone or access-panel
information and appear at the beginning of some maintenance procedures do not
have ID values.
NOTE: Given the presence of cross references to tables it is important to reproduce
the original table sequence numbers when rendering the SGML instance.
These table cross references call out the original table sequence number, for
example:
. . . Refer to (<refint reftype=”table”
refid="E000070728">Table 2/51-10-04, GENERAL</refint>). . .
f. Table number and seqnum are renumbered in taskcards; therefore, they may not

Rev #26 01/13/21 D6-82973

Page -338
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TABLE

match the corresponding table found in the AMM.

g. Table titles may contain a table number. This number is auto-generated by the
system and placed in the <title> element (e.g., Table 11.). The period “.” can be
suppressed by the receiving system, if desired.
h. For Tools/Equipment table containing effectivity for multiple model series see
section 1.3.7, Example 2 and 4. To replicate the Boeing PDF display only the data
after the semi-colon in the EFFTEXT attribute.
i. For Tools/Equipment table containing effectivity for single model/series, see
section 1.3.7, Example 3. The PDF will not display the effectivity; however, the
effectivity is provided in the <effect> element. It is up to the data receiver to
determine display rules based on their business requirements.

Rev #26 01/13/21 D6-82973

Page -339
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASK

1.0 ELEMENT NAME

task - Task

1.1 ELEMENT CONTENT

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

The task element identifies a task (prime AMTOSS division). A task tag only covers
one configuration of a task, e.g., task 29-11-53-400-802 and task 29-11-53-400-803
may be two configurations of tasks that perform the same action. They are separately
identified with two different task tags. The task element appears in the context of the
following element:

ELEMENT

tcbody

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >
<!ATTLIST task
chappref CDATA #IMPLIED
chapnbr NUMBER #REQUIRED
sectnbr NUMBER #REQUIRED
subjnbr NUMBER #REQUIRED
func CDATA #REQUIRED
seq CDATA #REQUIRED
confltr CDATA #IMPLIED
varnbr NUMBER #IMPLIED
alunqi CDATA #IMPLIED
pgblknbr NUMBER #IMPLIED
confnbr NUMBER #IMPLIED
id ID #IMPLIED >

Attribute Name Always Provided Provided When Data

is Available

chappref X
chapnbr X

sectnbr X

subjnbr X
func X

seq X

Rev #26 01/13/21 D6-82973

Page -340
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASK

Attribute Name Always Provided Provided When Data

is Available

confltr X
varnbr X

alunqi X

pgblknbr X
confnbr X

id X

1.2.1 Attribute: chappref

Description: Chapter Prefix (chappref) is a unique identifier for chapters with
multiple engine types. This identifier is used with the amtoss
numbering scheme as defined in ATA Spec. 2200.

Boeing Application Rules:

a. chappref is an implied attribute, however it will be supplied when data is available.

1.2.2 Attribute: chapnbr

Description: Chapter Number (chapnbr) is the identification number of a chapter.
chapnbr is a two-digit number (00 up to 99) as defined in
ATA Spec. 2200 (XX-xx-xx-xxx-xxx-xxx-xxx).

1.2.3 Attribute: sectnbr

Description: Section Number (sectnbr) is the identification number of a section.
sectnbr is a two-digit number (00 to 99) as defined in the
ATA Spec. 2200 (xx-XX-xx-xxx-xxx-xxx-xxx).

1.2.4 Attribute: subjnbr

Description: Subject Number (subjnbr) is the identification number of a subject.
subjnbr is a two-digit number (00 to 99) as defined in the
ATA Spec. 2200 (xx-xx-XX-xxx-xxx-xxx-xxx).

1.2.5 Attribute: func

Description: Function Code (func) identifies the fourth element of a task
(xx-xx-xx-XXX-xxx-xxx-xxx). The first two digits of the func is the
numerical representation of the function corresponding to the task. func
is defined in the ATA Spec. 2200 (ranging from 00-99). The third digit
is for the use of the manufacturer. Boeing enters the pageblock number
in the third position.

Rev #26 01/13/21 D6-82973

Page -341
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASK

1.2.6 Attribute: seq

Description: Sequence Number (seq) is the sequential issue number within a chapter
(xx-xx-xx-xxx-XXX-xxx-xxx).

1.2.7 Attribute: confltr

Description: Configuration Letter (confltr) identifies the first character of the three-
character element in the sixth position of a task
(xx-xx-xx-xxx-xxx-Xxx-xxx).
Boeing Application Rules:
a. confltr values will be alpha characters or “0” (zero).

NOTE: confltr is based on the engine configuration of an aircraft. If an airline has

more than one engine configuration for an aircraft, the configuration letter will reflect
the engine type. Reference the Engine Logo Translation Table in the effect element for
valid values.

1.2.8 Attribute: varnbr

Description: Variant Number (varnbr) identifies the last two digits of a three
character element of the sixth position of a task. Identifies variants of a
particular sequence number of a task or subtask (xx-xx-xx-xxx-xxx-
xXX-xxx).

Boeing Application Rules:

Rev #26 01/13/21 D6-82973

Page -342
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASK

1.2.9 Attribute: alunqi

Description: Airline Unique Identification (alunqi) identifies the code found in the
seventh element of task when a customer originated change has been
incorporated (xx-xx-xx-xxx-xxx-xxx-XXX). This number is reserved
for airline use.

Boeing Application Rules:

a. Boeing does not apply the alunqi attribute.

1.2.10 Attribute: pgblknbr

Description: Pageblock Number (pgblknbr) identifies the pageblock.

1.2.11 Attribute: confnbr

Description: Configuration Number (confnbr) identifies the unique configuration of
a pageblock.

1.2.12 Attribute: id
Description: Identifying unique number to allow direct SGML cross-referencing to
be performed from the REFID attribute.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: tcbody

<!ELEMENT tcbody - - (tccat?, taskproc?, mpditem*,
pretsmry?, hazmtlst?, (task* | refext*))>

Printed Example:

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">

Rev #26 01/13/21 D6-82973

Page -343
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASK

. . .
<tcbody>
<taskproc>
<para>Functionaly check the Lower Lobe Attendant Rest (LLAR) Back-up LIghting
System Battery Pack for proper capacity (perform time loading test).</para>
</taskproc>
<task chapnbr="05" sectnbr="00" subjnbr="01" func="800" seq="801"
pgblknbr="6" id="C479BB14E26BAED29CD99745897CDE86">
<effect effrg="475999" efftext="ZAP" ALL">
</effect>
<title>Recording and Control of the Lives of Parts</title>
<topic>
<title>The following equipment is used to record and control the lives of
parts.</title>
<subtask chapnbr="05" sectnbr="00" subjnbr="01" func="861" seq="001"
pgblknbr="6" id="H262849C00A66846CC5DBB81F2C4CBC7">
<effect effrg="475999" efftext="ZAP" ALL">
</effect>
<list1>
<l1item>
<para>Standard Equipment</para>
<list2>
<l2item>
<para>Vibro-engraving tool.</para>
</l2item>
</list2>
</l1item>
</list1>
</subtask>
. . .
</task>
. . .
</tcbody>
</taskcard>

Rev #26 01/13/21 D6-82973

Page -344
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKCARD

1.0 ELEMENT NAME

taskcard - Task Card

1.1 ELEMENT CONTENT

The taskcard element is an individual task card in the Task Card Manual. The element
taskcard appears in the context of the following element.

ELEMENT

1.2 ATTRIBUTE MARKUP RULES

Attribute Name Always Provided Provided When Data

Is Present

cardnbr X

mprog X

etopsind X

%revatt X

1.2.1 Attribute: cardnbr

Description: Card Number (cardnbr) is the source of the unique task card number
that is assigned to each task card.

Boeing Application Rules:

a. The cardnbr value may be up to 18 character positions.

Rev #26 01/13/21 D6-82973

Page -345
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKCARD

1.2.2 Attribute: mprog

Description: The Maintenance Program (mprog) attribute supplies the value for the
type of maintenance program the task card is addressing. e.g., SYS,
STR, COR, ZON, LUB, FAT, SVI, RAR, CSY.

Boeing Application Rule:

a. mprog values are as follows:
SYS - SYSTEM
STR - STRUCTURES
COR - CORROSION
ZON - ZONAL
LUB - LUBRICATION
FAT - FATIGUE
SVI - SYSTEM VISUAL INSPECTION
RAR - REMOVE AND REPLACE
CSY - CUSTOMIZED SYSTEM TASK CARD

1.2.3 Attribute: etopsind

Description: Indicates whether the task is required for ETOPS certified airplanes.

1.2.4 Attribute: %revatt

Description: Revision attributes (%revatt) is a grouping of attributes that are needed
to send revision information for incremental updates or revisions to a
complete reissue of a manual. The revision attributes are applied to
each anchor.

Boeing Application Rules:

a. %revatt is a required attribute.
b. Reference %revatt attribute for application rules.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -346
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKCARD

Printed Example:

...

SGML:
<tc chg="R" docnbr="ME717-009-ZAP" cusname="ZAP Airlines" cus="ZAP"
oidate="20021106" lang="EN" model="717" revdate="20021106" spl="88277"
tsn="1">
<title>Task Card Deck</title>
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256" revdate="20021106">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>
<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
. . .
</taskcard>
. . .
</tc>

Rev #26 01/13/21 D6-82973

Page -347
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKCTGY

1.0 ELEMENT NAME

taskctgy - Maintenance Steering Group-3 Task Category Code

1.1 ELEMENT CONTENT

<!ELEMENT taskctgy - - (#PCDATA) >

The taskctgy element is for systems maintenance programs only. The taskctgy element
appears in the context of the following element.

ELEMENT

supldata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: supldata

<!ELEMENT supldata - - (manhours, nbrpeopl, elaptime,
tc_manhours?, tc_nbrpeopl?,
tc_elaptime?, taskctgy?, feftctgy*)>

Printed Example: The mpditem information does not appear on the printed taskcard.

Rev #26 01/13/21 D6-82973

Page -348
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKCTGY

Rev #26 01/13/21 D6-82973

Page -349
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKDESC

1.0 ELEMENT NAME

taskdesc - Task Description

1.1 ELEMENT CONTENT

<!ELEMENT taskdesc - - (%text;) >

The taskdesc element identifies the MPD task description. The taskdesc element
appears in the context of the following element.

ELEMENT

mpditem

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -350
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKDESC

1.3.1 Element: mpditem

<!ELEMENT mpditem - - (mpdnbr, taskloc?, linspect?, title?,
taskdesc?, ch5tskno?, awlimit?,
supldata) >

Printed Example: The mpditem information does not appear on the printed taskcard.

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
. . .
<mpditem>
<mpdnbr>05-002-00</mpdnbr>
<taskloc>EXTERNAL</taskloc>
<linspect>DETAILED</linspect>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<taskdesc>
<para>Functionally check the Lower Lobe Attendant Rest (LLAR) Back-up
Lighting System Battery Pack for proper capacity (perform time loading
test).</para>
</taskdesc>
. . .
</mdpitem>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -351
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKLOC

1.0 ELEMENT NAME

taskloc - Task Location

1.1 ELEMENT CONTENT

<!ELEMENT taskloc - - (#PCDATA) >

The taskloc element identifies whether the task is internal or external. The taskloc
element appears in the context of the following element.

ELEMENT

mpditem

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -352
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKLOC

1.3.1 Element: mpditem

<!ELEMENT mpditem - - (mpdnbr, taskloc?, linspect?, title?,
taskdesc?, ch5tskno?, awlimit?,
supldata) >

Printed Example: The mpditem information does not appear on the printed taskcard.

Rev #26 01/13/21 D6-82973

Page -353
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKPROC

1.0 ELEMENT NAME

taskproc - Task Procedure

1.1 ELEMENT CONTENT

<!ELEMENT taskproc - - (%text;) >

The taskproc element identifies the task card text. The taskproc element appears in the
context of the following element.

ELEMENT

tcbody

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -354
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKPROC

1.3.1 Element: tcbody

<!ELEMENT tcbody - - (tccat?, taskproc?, mpditem*,
pretsmry?, hazmtlst?, (task* | refext*))>

Printed Example:

Rev #26 01/13/21 D6-82973

Page -355
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKTYPE

1.0 ELEMENT NAME

tasktype - Task Type

1.1 ELEMENT CONTENT

<!ELEMENT tasktype - - (#PCDATA) >

The tasktype element identifies the type of task performed. The tasktype element
appears in the context of the following elements:

ELEMENT

mainhead

cchead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -356
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKTYPE

1.3.1 Element: mainhead

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
<mainhead>
. . .
<tasktype>DETAILED</tasktype>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
. . .
</mainhead>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -357
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TASKTYPE

1.3.2 Element: cchead

<!ELEMENT cchead - - (skill+, workarea+, reltask*, specnote?,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -358
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TBODY

1.0 ELEMENT NAME

tbody - Table Body

1.1 ELEMENT CONTENT

<!ELEMENT tbody - o (row+) >

The tbody element identifies the body of the information in a table group. The tbody
element appears in the context of the following element:

ELEMENT

tgroup

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT tbody - o (row+) >
<!ATTLIST thead
valign (top|middle|bottom) "top" >

Attribute Name Always Provided Provided When Data

is Available

valign X

1.2.1 Attribute: valign

Description: valign is the text vertical positioning within the entries. Declared
value=top, middle (vertically centered), or bottom. Default=top.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -359
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TBODY

1.3.1 Element: tgroup

<!ELEMENT tgroup - o (colspec*, spanspec*, thead?,
tfoot?, tbody) >

Printed Example:

SGML:
<pretopic>
<title>References</title>
<table frame="NONE">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="320*">
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>
<para>Title</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry>
<para><refext refman="AMM" refloc="28-00-00-010-802">28-00-00-010-802
</refext></para>
</entry>
<entry>
<para>Fuel Tank Access (Main Tanks) (P/B 201)</para>
. . .
</tbody>
. . .
</tgroup>
<table>

Rev #26 01/13/21 D6-82973

Page -360
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

1.0 ELEMENT NAME

tc - Task Card

1.1 ELEMENT CONTENT

The task card (tc) element identifies the manual type. The tc attributes identify the
manual’s configuration, e.g., aircraft: vendor, model, customer, document number,
etc. The beginning and the end of the manual is tagged with the tc element; therefore,
all other elements of the Task Card Manual will be contained within the tc start and
end tags.

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT tc - - ((title, gchgdesc*, legalntc?, taskcard+)| tr+)
+(revst | revend | cocst | cocend | hotlink) >
<!ATTLIST tc
model CDATA #REQUIRED
revdate NUMBER #REQUIRED
docnbr CDATA #IMPLIED
cus CDATA #IMPLIED
cusname CDATA #IMPLIED
lang CDATA #REQUIRED
spl CDATA #REQUIRED
oidate CDATA #REQUIRED
tsn CDATA #REQUIRED
chg (N|R|U) #REQUIRED >

Attribute Name Always Provided May or May Not be

Present
model X

revdate X

docnbr X

cus X

cusname X

Description: A sequential control number identifying each transmission of data
whether it is the initial submittal or follow-on revision data. The
number is associated with the revision date of the Service Bulletin or
manual.

1.2.10 Attribute: chg

Description: Change Reason (chg) identifies the manual’s revision status. The chg
attribute at the tc element level does not propagate down through the
document instance. The following chg values are allowed:
N = New, R = Revised, U = Unchanged.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -363
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

Printed Example: tc is the entire taskcard file. Refer to the TC PDF for Printed
Examples.

SGML:
<tc chg="R" docnbr="ME717-009-ZAP" cusname="ZAP Airlines" cus="ZAP"
oidate="20021106" lang="EN" model="717" revdate="20021106" spl="88277"
tsn="1">
<title>Task Card Deck</title>
. . .
</tc>

Boeing Application Rule:

a. The tc title is hardcoded.

Rev #26 01/13/21 D6-82973

Page -364
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TC_ELAPTIME

1.0 ELEMENT NAME

tc_elaptime - Task Card Elapsed Time

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT tc_elaptime- - (#PCDATA) >

The tc_elaptime element identifies the time, determined by a given airplane customer,
it takes to complete the task, excluding open/close access requirements. The
tc_elaptime element appears in the context of the following element.

ELEMENT

supldata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -365
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TC_MANHOURS

1.0 ELEMENT NAME

tc_manhours - Task Card Man Hours

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT tc_manhours- - (#PCDATA) >

The tc_manhours element identifies the estimated time, determined by a given

airplane customer, required to accomplish an aircraft task, excluding open/close
access. The tc_manhours element appears in the context of the following element.

ELEMENT

supldata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -366
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TC_NBRPEOPL

1.0 ELEMENT NAME

tc_nbrpeopl - Task Card Number of People

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT tc_nbrpeopl- - (#PCDATA) >

The tc_nbrpeopl element identifies the number of people, determined by a given

airplane customer, performing the task on the airplane. The tc_nbrpeopl element
appears in the context of the following element.

ELEMENT

supldata

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -367
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TCBODY

1.0 ELEMENT NAME

tcbody - Task Card Body

1.1 ELEMENT CONTENT

<!ELEMENT tcbody - - (tccat?, taskproc?, mpditem*,
pretsmry?, hazmtlst?, (task* | refext*))>

The tcbody element defines the task card body. The tcbody element appears in the
context of the following element.

ELEMENT

taskcard

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -368
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TCBODY

1.3.1 Element: taskcard

Printed Example:

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
. . .
<tcbody>
<taskproc>
<para>Functionally check the Lower Lobe Attendant Rest (LLAR) Back-up
Lighting System Battery Pack for proper capacity (perform time loading
test).</para>
</taskproc>
<mpditem>
<mpdnbr>05-002-00</mpdnbr>
. . .
</tcbody>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -369
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TCCAT

1.0 ELEMENT NAME

tccat - Task Card Category

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT tccat - - (#PCDATA) >

The tccat element shows the type of category of a particular taskcard. There are three
different category types such as: System, Zonal, and Structures. The tccat element
appears in the context of the following element.

ELEMENT

tcbody

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

Rev #26 01/13/21 D6-82973

Page -370
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TED

1.0 ELEMENT NAME

ted - Special Tool and Equipment Description

1.1 ELEMENT CONTENT

<!ELEMENT ted - - (toolnbr, toolname) >

The ted element identifies data associated with tools and equipment listed in the
Illustrated Tools and Equipment Manual. The ted element appears in the context of the
following element
.
ELEMENT

para

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: para

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Printed Example:

SGML:
<taskcard cardnbr="12-002-01-01" mprog="SYS" etopsind="No" chg="R"
key="T0000026246">
<effect effrg="001999" efftext="ZAP ALL">
. . .
<subtask chapnbr="12" sectnbr="21" subjnbr="04" func="840" seq="003"
pgblknbr="3" id="K6D87F7E338114A8253585952D2EDADC">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<list1>

Rev #26 01/13/21 D6-82973

Page -371
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TED

<l1item>
<para>Do one of these two procedures to move the elevators fully up and to
install the <ted>
<toolnbr><revst>SPL-1712<revend></toolnbr>
<toolname><revst><revend><revst>rudder and elevator power control unit
lock<revend></toolname>
</ted>:</para>
<list2>
<l2item>
<para>Procedure 1 - Move the elevator manually:</para>
<list3>
<l3item>
<para>On the P61 panel, move the FLT CONTROL HYD VALVE POWER - TAIL switches
to the SHUT OFF position.</para>
</l3item>
. . .
</subtask>

Rev #26 01/13/21 D6-82973

Page -372
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TFMATR

1.0 ELEMENT NAME

tfmatr - Task Front Matter

1.1 ELEMENT CONTENT

<!ELEMENT tfmatr - - (pretopic+) >

The tfmatr element identifies a set of data found at the beginning of a task that is
applicable to the complete task. The tfmatr element appears in the context of the
following element.

ELEMENT

task

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: task

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
</effect>
. . .
<task chapnbr="57" sectnbr="00" subjnbr="01" func="000" seq="801"
pgblknbr="4" id="G3AD7D1A50A99756CD8ECFADF8D12799">
<effect effrg="475999" efftext="ZAP ALL">

Rev #26 01/13/21 D6-82973

Page -373
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TFMATR

</effect>
<title>Removal of the Wing Fuel Tank Access Door Seal</title>
<tfmatr>
<pretopic>
<title>References</title>
<table frame="NONE">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="420*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
. . .
</tfmatr>
. . .
</task>

Rev #26 01/13/21 D6-82973

Page -374
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TFOOT

1.0 ELEMENT NAME

tfoot - Table Footer

Not used.

1.1 ELEMENT CONTENT

<!ELEMENT (tfoot) - O (colspec*,row+) >

The tfoot element identifies the footer information in a table, displayed after the tbody
and also at the bottom of any tbody rows before a physical break. The tfoot element
appears in the context of the following element:

ELEMENT

tgroup

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT (thead|tfoot)- O (colspec*,row+) >
<!ATTLIST (tfoot|tbody)
valign (top|middle|bottom) "top" >

Attribute Name Always Provided Provided When Data

is Available

valign X

1.2.1 Attribute: valign

Description: valign is the text vertical positioning within the entries. Declared
value=top, middle, or bottom. Default=top.

Rev #26 01/13/21 D6-82973

Page -375
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TGROUP

1.0 ELEMENT NAME

tgroup - Table Group

1.1 ELEMENT CONTENT

<!ELEMENT tgroup - o (colspec*, spanspec*, thead?,
tfoot?, tbody) >

The tgroup element identifies a grouping of elements that form a single logical table
within a table element. The tgroup element appears in the context of the following
element:

ELEMENT

table

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT tgroup - o (colspec*, spanspec*, thead?,
tfoot?, tbody) >
<!ATTLIST tgroup
cols NUMBER #REQUIRED
colsep %yesorno; #IMPLIED
rowsep %yesorno; #IMPLIED
align (left|right|center
|justify|char) "left"
charoff NUTOKEN "50"
char CDATA "" >

Attribute Name Always Provided Provided When Data

is Available
cols X

colsep X

rowsep X

align X

charoff X

char X

Rev #26 01/13/21 D6-82973

Page -376
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TGROUP

1.2.1 Attribute: cols

Description: Columns (cols) is the number of columns in the table.

1.2.2 Attribute: colsep

1.2.3 Attribute: rowsep

1.2.4 Attribute: align

Description: Alignment (align) indicates the intended “justification” of all the
entries in that element.

1.2.5 Attribute: charoff

Description: Character Off (charoff) - if align is equal to “char”, the value is the
percent of the current width to the left (left edge) of the character.

1.2.6 Attribute: char

Description: Character (char) - if align is equal to “char”, the value is the single
alignment character on which the first occurring character in the entry
is aligned. If that character does not occur in the entry, the entry aligns
to the right of that character offset.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -377
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TGROUP

1.3.1 Element: table

<!ELEMENT table - - ((seqnum?, title?, tgroup, ftnote*)
| graphic+) -(table) >

Printed Example:

SGML:
<table frame="NONE">
<tgroup cols="3" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="320*">
<colspec colwidth="100*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>
<para>Title</para>
</entry>
</row>
</thead>
. . .
</tgroup>
. . .
</table>

Rev #26 01/13/21 D6-82973

Page -378
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TGROUP

1.4 BOEING IMPLEMENTATION RULES

a. The optional ROWSEP and COLSEP attributes can be specified at this level.
b. The optional CHAROFF and CHAR attributes are not used at this level.

Rev #26 01/13/21 D6-82973

Page -379
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

THEAD

1.0 ELEMENT NAME

thead - Table Header

1.1 ELEMENT CONTENT

!ELEMENT thead - o (colspec*, row+) >

The thead element identifies the header information (i.e., column titles) in a table. The
thead element appears in the context of the following element:

ELEMENT

tgroup

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT thead - o (colspec*, row+) >
<!ATTLIST thead
valign (top|middle|bottom) "bottom" >

Attribute Name Always Provided Provided When Data

is Available

valign X

1.2.1 Attribute: valign

Description: valign is text vertical positioning within the entries. Declared Value=
top, middle (vertically centered), or bottom. Default="top".

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -380
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

THEAD

1.3.1 Element: tgroup

<!ELEMENT tgroup - O (colspec*, spanspec*, thead?,
tfoot?, tbody) >

Printed Example:

SGML:
<table frame="NONE">
<tgroup cols="2" colsep="0" rowsep="0">
<colspec colwidth="180*">
<colspec colwidth="320*">
<thead>
<row rowsep="1">
<entry>
<para>Reference</para>
</entry>
<entry>
<para>Title</para>
</entry>
</row>
</thead>
. . .
</tgroup>
. . .
</table>

Rev #26 01/13/21 D6-82973

Page -381
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

THRSHOLD

1.0 ELEMENT NAME

thrshold - Threshold Interval

1.1 ELEMENT CONTENT

<!ELEMENT thrshold - - (thrshtyp, ((multiple, unit, sample)
| optask)) >

The thrshold element defines the periodic frequency of a given task. The thrshold
element appears in the context of the following element.

ELEMENT

interval

1.2 ATTRIBUTE MARKUP RULES

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Elements: thrshold

<!ELEMENT thrshold - - (thrshtyp, ((multiple, unit, sample)
| optask)) >

NOTE: Not all of the thrshold information appears on the printed taskcard.

Rev #26 01/13/21 D6-82973

Page -385
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

THRSHTYP

Printed Example:

Rev #26 01/13/21 D6-82973

Page -386
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

THRSHTYP

SGML:
<taskcard cardnbr="20-010-01-01" mprog="SYS" etopsind="No" chg="N"
key="T0000026722">
<effect effrg="3AA3AH 3AJ3AN 3AP3AP 3AR3AY 3BA3BH 3BJ3BN 3BP3BP 3BR3BY 3CA3CH
3CJ3CN 3CP3CP 3CR3CY 3DA3DH 3DJ3ZZ" efftext="ZAP ALL">
</effect>
<mainhead>
<source>MRB</source>
<skill>AVION</skill>
<workarea>LEFT WING</workarea>
<intdata>
<interval>
<version>1.1</version>
<thrshold>
<thrshtyp>N</thrshtyp>
<multiple>15000</multiple>
<unit>FH</unit>
<sample>100</sample>
</thrshold>
. . .
</taskcard>

1.3.2 Elements: repeat

<!ELEMENT repeat - - (thrshtyp, multiple, unit, sample) >

NOTE: Not all of the repeat information appears on the printed taskcard.

Printed Example:

Rev #26 01/13/21 D6-82973

Page -387
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

THRSHTYP

<source>MRB</source>
<skill>AVION</skill>
<workarea>LEFT WING</workarea>
<intdata>
<interval>
<version>1.1</version>
<thrshold>
<thrshtyp>N</thrshtyp>
<multiple>15000</multiple>
<unit>FH</unit>
<sample>100</sample>
</thrshold>
<repeat>
<thrshtyp>N</thrshtyp>
<multiple>15000</multiple>
<unit>FH</unit>
<sample>100</sample>
</repeat>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -388
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

1.0 ELEMENT NAME

title - Title

1.1 ELEMENT CONTENT

<!ELEMENT title - - (#PCDATA | ein | sbnbr | sub
| super)+ >

The title element identifies #pcdata (and any specific special data elements) that
summarize the content of an element. The title element appears in the context of the
following elements:

ELEMENT

tc
fullstmt

partstmt

mainhead

cchead

mpditem

hazmtlst

hazmt
task

pretopic

topic
table

graphic

sheet

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -389
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

Printed Example: Reference the task card manual for examples of title.

SGML:
<tc chg="R" docnbr="ME717-009-ZAP" cusname="ZAP Airlines" cus="ZAP"
oidate="20021106" lang="EN" model="717" revdate="20021106" spl="88277"
tsn="1">
<title>Task Card Deck</title>
. . .
</tc>

1.3.2 Element: fullstmt

<!ELEMENT fullstmt - - (title?, cpyrght?, para+) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -390
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

1.3.3 Element: partstmt

<!ELEMENT partstmt - - (title?, para+) >

Not used.

1.3.4 Element: mainhead

<!ELEMENT mainhead - - (source, skill+, workarea+,
reltask*, specnote?, intdata,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -391
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

<thrshtyp>N</thrshtyp>
<multiple>100</multiple>
<unit>FC</unit>
<sample>100</sample>
</repeat>
</interval>
<intnote>
<para>blah</para>
</intnote>
</intdata>
<tasktype>DETAILED</tasktype>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<apapdata>
<apapplic>200</apapplic>
</apapdata>
<enapdata>
<engappl>715B1</engappl>
</enapdata>
<zone>100</zone>
<acdata>
<acpan>110AL</acpan>
</acdata>
</mainhead>
. . .
</taskcard>

1.3.5 Element: cchead

<!ELEMENT cchead - - (skill+, workarea+, reltask*, specnote?,
tasktype, title, apapdata, enapdata,
zone+, acdata?) >

Rev #26 01/13/21 D6-82973

Page -392
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

Printed Example:

Rev #26 01/13/21 D6-82973

Page -393
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

1.3.6 Element: mpditem

<!ELEMENT mpditem - - (mpdnbr, taskloc?, linspect?, title?,
taskdesc?, ch5tskno?, awlimit?,
supldata) >

Printed Example: The mpditem information does not appear on the printed taskcard.

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
. . .
<mpditem>
<mpdnbr>05-002-00</mpdnbr>
<taskloc>EXTERNAL</taskloc>
<linspect>DETAILED</linspect>
<title>Lower Lobe Attendant Rest (LLAR) Back-up Lighting System</title>
<taskdesc>
<para>Functionaly check the Lower Lobe Attendant Rest (LLAR) Back-up LIghting
System Battery Pack for proper capacity (perform time loading test).</para>
</taskdesc>
<supldata>
<manhours>1.00</manhours>
<nbrpeopl>1</nbrpeopl>
<elaptime>1.00</elaptime>
</supldata>
</mpditem>
. . .
</taskcard>

<para>SEG</para>
<para>LTR</para>
</entry>
<entry valign="TOP" align="LEFT">
<para>PART NUMBER</para>
</entry>
<entry valign="TOP" align="LEFT">
<para>CABLE DIA. IN INCHES (MM) *CONSTR</para>
</entry>
<entry valign="TOP" align="LEFT">
<para>LENGTH IN</para>
<para>INCHES</para>
<para>(MM)</para>
</entry>
<entry valign="TOP" align="LEFT">
<para>TOL. IN</para>
<para>INCHES</para>
<para>(MM)</para>
</entry>
<entry valign="TOP" align="LEFT">
<para>FITTINGS</para>
</entry>
</row>
</thead>
<tbody>
<row>
<entry namest="COL1" nameend="COL7" valign="TOP" align="CENTER">
<para>NOSE GEAR SHIFT - PED. STEERING OFF</para>
</entry>
</row>
<row>
<entry valign="TOP" align="LEFT">
<para>116</para>
</entry>
<entry valign="TOP" align="LEFT">
<para>A</para>
</entry>
<entry valign="TOP" align="LEFT">
<para>S4913802BS03100</para>
</entry>
<entry valign="TOP" align="LEFT">
<para>3/32 </para>
<para>(2.4)</para>
<para>7X7</para>
</entry>
<entry valign="TOP" align="LEFT">
<para> 31</para>
<para>(788)</para>
</entry>
<entry valign="TOP" align="LEFT">

Rev #26 01/13/21 D6-82973

Page -400
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

Rev #26 01/13/21 D6-82973

Page -401
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

1.3.13 Element: graphic

<!ELEMENT graphic - - (effect, seqnum, title?, sheet+) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-22-01" mprog="STR" etopsind="Yes" chg="N"
key="T0000019623">
<effect effrg="001999">
</effect>
. . .
<graphic chapnbr="57" sectnbr="00" subjnbr="01" func="990" seq="801"
pgblknbr="4" id="FF5369B9B30EA56B946B8B070DC74BC3">
<effect effrg="475999" efftext="ZAP ALL">

Rev #26 01/13/21 D6-82973

Page -402
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TITLE

</effect>
<title>WING FUEL TANK ACCESS DOOR SEAL - REMOVAL/INSTALLATION</title>
<sheet gnbr="HFD7B8C75B32FE59D31D636EB2CD" sheetnbr="1"
id="AC1700E814B4CC1B91D384D87503C7D5">
<effect effrg="475999" efftext="ZAP ALL">
</effect>
<seqnum>401</seqnum>
</sheet>
</graphic>
. . .
</taskcard>

1.3.14 Element: sheet

<!ELEMENT sheet - - (effect, title?, gdesc?) >

Note: Titles are not contained with in the sheet element. For an example of title see
the graphic element.

1.4 BOEING IMPLEMENTATION RULES

a. Sheets do not have titles. In the published document, sheets inherit the title of the
parent <graphic> element.
b. Table and graphic titles may contain a number. This number is auto-generated by
the system and placed in the <title> element (e.g., Table 11. or Figure 601.). The
period “.” can be suppressed by the receiving system, if desired.

Rev #26 01/13/21 D6-82973

Page -403
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TOOLNAME

1.0 ELEMENT NAME

toolname - Tool Name

1.1 ELEMENT CONTENT

<!ELEMENT toolname - - (#PCDATA) >

The toolname element tags the standard description of a special tool or equipment
listed in the Illustrated Tools and Equipment Manual. The toolname element appears
in the context of the following element.

ELEMENT

ted

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: ted

<!ELEMENT ted - - (toolnbr, toolname) >

Printed Example:

SGML:
<taskcard cardnbr="12-002-01-01" mprog="SYS" etopsind="No" chg="R"
key="T0000026246">
<effect effrg="001999" efftext="ZAP ALL">
. . .
<subtask chapnbr="12" sectnbr="21" subjnbr="04" func="840" seq="003"
pgblknbr="3" id="K6D87F7E338114A8253585952D2EDADC">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Do one of these two procedures to move the elevators fully up and to
install the <ted>

Rev #26 01/13/21 D6-82973

Page -404
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TOOLNAME

<toolnbr><revst>SPL-1712<revend></toolnbr>
<toolname>rudder and elevator power control unit lock</toolname>
</ted>:</para>
<list2>
<l2item>
<para>Procedure 1 - Move the elevator manually:</para>
<list3>
<l3item>
<para>On the P61 panel, move the FLT CONTROL HYD VALVE POWER - TAIL switches
to the SHUT OFF position.</para>
</l3item>
. . .
</subtask>

Rev #26 01/13/21 D6-82973

Page -405
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TOOLNBR

1.0 ELEMENT NAME

toolnbr - Tool Number

1.1 ELEMENT CONTENT

<!ELEMENT toolnbr - - (#PCDATA) >

The toolnbr element tags the identification number of a special tool or equipment
listed in the Illustrated Tools and Equipment Manual. The toolnbr element appears in
the context of the following element.

ELEMENT

ted

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: ted

<!ELEMENT ted - - (toolnbr, toolname) >

Printed Example:

SGML:
<taskcard cardnbr="12-002-01-01" mprog="SYS" etopsind="No" chg="R"
key="T0000026246">
<effect effrg="001999" efftext="ZAP ALL">
. . .
<subtask chapnbr="12" sectnbr="21" subjnbr="04" func="840" seq="003"
pgblknbr="3" id="K6D87F7E338114A8253585952D2EDADC">
<effect effrg="001999" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Do one of these two procedures to move the elevators fully up and to
install the <ted>

Rev #26 01/13/21 D6-82973

Page -406
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TOOLNBR

Rev #26 01/13/21 D6-82973

Page -407
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TOPIC

1.0 ELEMENT NAME

topic - Topic

1.1 ELEMENT CONTENT

<!ELEMENT topic - - (effect?, title, %g.r;, %w.c;, note*,
subtask*) >

The topic element identifies a topic (ATA major subdivision of a task that contains one
or more subtasks). NOTE: because of the mixing of “old” ATA and “new” AMTOSS
numbering systems, topics will normally continue the labeling of pretopic elements.
For example, if a task contains five pretopics (A-E), the first topic will be labeled F.
The topic element appears in the context of the following element.

ELEMENT

task

Topics are generic headings within tasks to provide groupings of subtasks such as
“Prepare for Removal,” “Prepare for Inspection,” or “Restore Airplane to Normal.”
Less complex procedures without headings and a single topic use “Procedure.”

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -408
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TOPIC

1.3.1 Element: task

<!ELEMENT task - - (effect, title, %g.r;, regulatory*,
%w.c;, note*, tfmatr?, topic*, graphic*) >

Printed Example:

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256">
<effect effrg="001999">
</effect>
. . .
<task chapnbr="05" sectnbr="00" subjnbr="01" func="800" seq="801"
pgblknbr="6" id="C479BB14E26BAED29CD99745897CDE86">
<effect effrg="475999" efftext="ZAP ALL">
</effect>
<title>Recording and Control of the Lives of Parts</title>
<topic>
<title>The following equipment is used to record and control the lives of
parts.</title>
<subtask chapnbr="05" sectnbr="00" subjnbr="01" func="861" seq="001"
pgblknbr="6" id="H262849C00A66846CC5DBB81F2C4CBC7">
<effect effrg="475999" efftext="ZAP ALL">
</effect>
<list1>
<l1item>
<para>Standard Equipment</para>
<list2>
<l2item>
<para>Vibro-engraving tool.</para>
</l2item>
</list2>
</l1item>
</list1>
. . .
</topic>
. . .
</task>
. . .
</taskcard>

Rev #26 01/13/21 D6-82973

Page -409
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

1.0 ELEMENT NAME

tr - Temporary Revision

1.1 ELEMENT CONTENT

<!ELEMENT tr - - (legalntc?, trfmatr, (legalntc|taskcard))>

The tr element is one or more contiguous “Anchor” elements of the DTD, preceded by
some supporting and descriptive data, sent independently of the complete
superstructure of the DTD. TR is used to support partial revisions to a Document
instance made independently of the normal revision cycle. The TR element is provided
to maintain the correspondence between the electronic and paper versions of the
“book”. The major difference between the incremental and Temporary revisions is that
the TRs must not update the database. All incremental revisions (and subsequent TRs)
are made against the previous incremental revision, not the TR. The tr element is
allowed in the context of the following element:

ELEMENT

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Printed Example:
Examples not available at this time.

SGML:
Examples not available at this time.

1.4 BOEING APPLICATION RULES

Currently, each TC Boeing Temporary Revision can consists of an entire taskcard
content.

Rev #26 01/13/21 D6-82973

Page -410
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

TRFMATR

1.0 ELEMENT NAME

trfmatr - Temporary Revision Front Matter

Note used.

1.1 ELEMENT CONTENT

<!ELEMENT trfmatr - - (title, trreason, (%text;)?) >

The trfmatr element identifies data found at the beginning of a tr and which supplies
the data normally found on the paper tr Cover Sheet or letter. The trfmatr element
appears in the context of the following element:

ELEMENT

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT trfmatr - - (title, trreason, (%text;)?) >
<!ATTLIST trfmatr
trnbr CDATA #REQUIRED
trdel CDATA #IMPLIED
trrepl CDATA #IMPLIED
issdate NUMBER #REQUIRED >

Attribute Name Always Provided Provided When Data is

Available

trnbr X
trdel X

trrepl X

issdate X

1.2.1 Attribute: trnbr

Description: Temporary Revision Number - The chapter number and customized
sequence number within the chapter used to uniquely identify a TR.

1.2.2 Attribute: trdel

1.1 ELEMENT CONTENT

<!ELEMENT unit - - (#PCDATA) >

The unit element is a unit of time for an interval. The unit element appears in the
context of the following elements:

ELEMENT

thrshold

repeat

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of data followed by an example of the SGML
markup.

Rev #26 01/13/21 D6-82973

Page -417
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNIT

1.3.1 Elements: thrshold

<!ELEMENT thrshold - - (thrshtyp, ((multiple, unit, sample)
| optask)) >

NOTE: Not all of the thrshold information is on the printed taskcard.

Printed Example:

Rev #26 01/13/21 D6-82973

Page -418
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNIT

1.3.2 Elements: repeat

<!ELEMENT repeat - - (thrshtyp, multiple, unit, sample) >

NOTE: Not all of the thrshold information is on the printed taskcard.

Printed Example:

SGML:
<taskcard cardnbr="05-002-00-01" mprog="COR" etopsind="No" chg="N"
key="T0000019256"><effect effrg="001999">
</effect><mainhead>
<source>MRB</source>
<skill>AIRPL</skill>
<workarea>LWR FUSELAGE</workarea>
<intdata>
<interval>
<version>1.1</version>
<thrshold>
<thrshtyp>N</thrshtyp>
<multiple>100</multiple>
<unit>FC</unit>
<sample>100</sample>
</thrshold>
<repeat>
<thrshtyp>N</thrshtyp>
<multiple>100</multiple>
<unit>FC</unit>
<sample>100</sample>
</repeat>

Rev #26 01/13/21 D6-82973

Page -419
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNLIST

1.0 ELEMENT NAME

unlist - Unnumbered List

1.1 ELEMENT CONTENT

<!ELEMENT unlist - - (unlitem+) >

The unlist element identifies a set of non-ordered items of text. The unlist element
appears in the context of the following elements:

ENTITY ELEMENT

exprtcl

geninfo

gdesc

(In %text) intnote

apapnote
eappnote

acpanote

taskproc

taskdesc
pretopic

warning

caution

note

entry

l1item through 17item

ftnote

Rev #26 01/13/21 D6-82973

Page -420
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNLIST

Boeing Application Rule:

a. Unnumbered Lists will be tagged with <PARA> tags.

1.2 ATTRIBUTE MARKUP RULES

TC DTD Structure:
<!ELEMENT unlist - - (unlitem+) >
<!ATTLIST unlist
bulltype CDATA #IMPLIED >

Attribute Name Always Provided Provided When

Data is Available

bulltype X

1.2.1 Attribute: bulltype

Description: Bullet Type (bulltype) is an attribute of the un-numbered list which
indicates the type of dingbat (symbol) to be used to ‘bullet’ the list
items. The default value allows the receiving system to assign the
dingbat.

Possible Description
Value

ASTERISK The ASCII character “*”

BULLET Round bullet, filled (default if attribute not provided)

DELTA A triangular greek character

DIAMOND A rhombus-shaped figure usually oriented with the

long diagonal vertical

MDASH A long dash (the width of the capital letter M)

NDASH A long dash (the width of the capital letter N)

NONE No bullet

SQUARE A rectangular character with four equal length sides

SYSTEM A system specific character

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

Rev #26 01/13/21 D6-82973

Page -421
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNLIST

1.3.1 Element: exprtcl

<!ELEMENT exprtcl - - (para | unlist | numlist | note)+ >

<!ELEMENT warning - - (%text;) -(note) +(effect) >

Printed Example:

SGML:
<warning>
<para>REFER TO THE APPLICABLE MANUFACTURER'S OR SUPPLIER'S MSDS FOR:</para>
<unlist>
<unlitem>
<para>MORE PRECAUTIONARY DATA</para>
</unlitem>
<unlitem>
<para>APPROVED SAFETY EQUIPMENT</para>
</unlitem>
. . .
</unlist>
</warning>

Rev #26 01/13/21 D6-82973

Page -424
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNLIST

1.3.12 Element: caution

<!ELEMENT caution - - (%text;) -(note) +(effect) >

Similar to unlist within warning, refer to section 1.3.11 for examples.

1.3.13 Element: note

<!ELEMENT note - - (%text;) -(note) +(effect) >

Similar to unlist within warning, refer to section 1.3.11 for examples.

1.3.14 Element: entry

<!ELEMENT entry - o (regulatory | %text; | %w.c;
| graphic)* >

Not used.

Rev #26 01/13/21 D6-82973

Page -425
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNLIST

1.3.15 Element: l1item-l7item

Printed Example:

SGML:
<l4item>
<para>The letter is from A to Z, but does not include I. The letter symbols
are as follows:</para>
<unlist>
<unlitem>
<para>A 0-500 </para>
</unlitem>
<unlitem>
<para>B 501-1000</para>
</unlitem>
. . .

Rev #26 01/13/21 D6-82973

Page -426
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNLIST

</unlist>

1.3.16 Element: ftnote

<!ELEMENT ftnote - - (%text;) >

Not used.

1.4 BOEING APPLICATION RULES

a. If bulltype is not supplied, Boeing will default to round-filled bullets.

Rev #26 01/13/21 D6-82973

Page -427
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNLITEM

1.0 ELEMENT NAME

unlitem - Unnumbered List Item

1.1 ELEMENT CONTENT

<!ELEMENT unlitem - - (para+) >

The unlitem element identifies an item of an unlist. The unlitem element appears in the
context of the following element:

ELEMENT

unlist

Boeing Application Rule:

a. Unnumbered List Items will be tagged with <PARA> tags.

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: unlist

<!ELEMENT unlist - - (unlitem+) >

Printed Example:

SGML:
<warning>
<para>REFER TO THE APPLICABLE MANUFACTURER'S OR SUPPLIER'S MSDS FOR:</para>
<unlist>
<unlitem>

Rev #26 01/13/21 D6-82973

Page -428
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

UNLITEM

<para>MORE PRECAUTIONARY DATA</para>

</unlitem>
<unlitem>
<para>APPROVED SAFETY EQUIPMENT</para>
</unlitem>
<unlitem>
<para>EMERGENCY MEDICAL AID</para>
</unlitem>
</unlist>
</warning>

Rev #26 01/13/21 D6-82973

Page -429
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

VERSION

1.0 ELEMENT NAME

version - Version

1.1 ELEMENT CONTENT

<!ELEMENT version - - (#PCDATA) >

The version element is a number which represents the task interval. The version
element appears in the context of the following element.

ELEMENT

interval

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP RULES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: interval

<!ELEMENT interval - - (version, thrshold, repeat?, phase?)>

Printed Example:

SGML:
<taskcard cardnbr="12-002-01-01" mprog="SYS" etopsind="No" chg="N"
key="T0000026246">
<effect effrg="001999">
</effect>
<mainhead>
<source>MRB</source>

Rev #26 01/13/21 D6-82973

Page -430
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

VERSION

<skill>AIRPL</skill>
<workarea>ELEVATORS</workarea>
<intdata>
<interval>
<version>1.1</version>
<thrshold>
<thrshtyp>N</thrshtyp>
<multiple>5000</multiple>
<unit>FH</unit>
<sample>100</sample>
</thrshold>
. . .
</interval>

Rev #26 01/13/21 D6-82973

Page -431
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

WARNING

1.0 ELEMENT NAME

warning - Warning

1.1 ELEMENT CONTENT

<!ELEMENT warning - - (%text;) -(note) +(effect) >

The warning element is used to identify a hazardous situation. According to the

ATA Spec. 2200 warnings, cautions, and notes shall be applied as follows:

All notes shall be in upper and lower case letters and preceded by the word NOTE in
caps and underlined.

Example: NOTE: It is not necessary to relieve pressure.

All cautions shall be printed in capital letters throughout and is preceded with the word
CAUTION in capital letters and underlined.

Example: CAUTION: DO NOT OPERATE CONTROLS.

All warnings shall be printed in capital letters and boldface throughout and is preceded
with the word WARNING in bold capital letters and underlined.

Example: WARNING: SOLUTION IS EXTREMELY FLAMMABLE.

Rev #26 01/13/21 D6-82973

Page -432
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

WARNING

The warning element appears in the context of the following element:

ENTITY ELEMENT

hazmt

(In %w.c.) task

topic
subtask

entry

l1item-l7item

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: hazmt

<!ELEMENT hazmt - - (title, warning) >

Printed Example:

SGML:
<hazmt id="J3199FAE10257D40E539EE4ABC6AC519">
<title>HZ1000—REFER TO MSDS </title>
<warning>
<para>REFER TO THE APPLICABLE MANUFACTURER'S OR SUPPLIER'S MSDS FOR:</para>
<unlist>
<unlitem>
<para>MORE PRECAUTIONARY DATA</para>
</unlitem>

Rev #26 01/13/21 D6-82973

Page -433
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

a. The published strings “WARNING:”, “CAUTION:” and “NOTE:” are not
contained in the SGML content. They must be generated by the data recipient.

Rev #26 01/13/21 D6-82973

Page -436
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

WORKAREA

1.0 ELEMENT NAME

workarea - Workarea

1.1 ELEMENT CONTENT

<!ELEMENT workarea - - (#PCDATA)>

The workarea element indicates the general area of the airplane where the task is to be
performed. The workarea element appears in the context of the following elements:

ELEMENT

mainhead

cchead

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

year - Year

1.1 ELEMENT CONTENT

<!ELEMENT year - - (#PCDATA) >

The year element contains PCDATA to hold any form of date needed to include a
copyright year format in text. The year element appears in the context of the following
element:

ELEMENT

cpyright

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

1.3 ELEMENT CONTEXT MARKUP EXAMPLES

The context markup rules include example(s) of known textual structures in the TC.
Each example begins with a sample of the printed data followed by an example of the
SGML markup, if available.

1.3.1 Element: cpyrght

<!ELEMENT cpyrght - - (year*, holder*, geninfo) >

Printed Example:

Rev #26 01/13/21 D6-82973

Page -440
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

YEAR

<title>BOEING PROPRIETARY, CONFIDENTIAL, AND/OR TRADE SECRET</title>

Rev #26 01/13/21 D6-82973

Page -441
BOEING PROPRIETARY - Boeing Background Technology
TC SGML Technical Guide

ZONE

1.0 ELEMENT NAME

zone - Zone Number

1.1 ELEMENT CONTENT

<!ELEMENT zone - - (#PCDATA) >

The zone element identifies a zone number of the aircraft as defined in ATA Spec.
2200. The zone element appears in the context of the following elements:

ELEMENT

mainhead

cchead

para

1.2 ATTRIBUTE MARKUP RULES

This element has no attributes.

<!ELEMENT para - - (#PCDATA | cb | con | ein | equ
| grphcref | ncon | pan | refext
| refint | std | sub | super
| ted | txtgrphc | zone)+ >

Not used.

Rev #26 01/13/21 D6-82973

Page -445
BOEING PROPRIETARY - Boeing Background Technology

List of ISO Standards PDF
80% (5)
List of ISO Standards PDF
20 pages
Aw Volumeshare 7 (Aw4.7) : Installation Manual
No ratings yet
Aw Volumeshare 7 (Aw4.7) : Installation Manual
418 pages
MIL-STD-40051 Tech Manual Preparation
No ratings yet
MIL-STD-40051 Tech Manual Preparation
359 pages
Asset Disposal Form
100% (2)
Asset Disposal Form
2 pages
4061-t64x SM
No ratings yet
4061-t64x SM
422 pages
Table of Contents: Lexmark™ T640, T642, and T644 4061-xx0
No ratings yet
Table of Contents: Lexmark™ T640, T642, and T644 4061-xx0
422 pages
RoboShopLite Manuel Rev.01
No ratings yet
RoboShopLite Manuel Rev.01
68 pages
LexmarkT T63x 4060-XXX Factory Repair Service Manual T630 T632 T634
No ratings yet
LexmarkT T63x 4060-XXX Factory Repair Service Manual T630 T632 T634
345 pages
STK 9310 Diagnostics User Guide
100% (1)
STK 9310 Diagnostics User Guide
206 pages
Dell 3335dn Service Manual
No ratings yet
Dell 3335dn Service Manual
306 pages
Addendum
No ratings yet
Addendum
43 pages
Hspice Command Ref
No ratings yet
Hspice Command Ref
406 pages
DOC1387081 - r2 - AW47 - SM (2021 - 03 - 15 11 - 20 - 35 UTC)
No ratings yet
DOC1387081 - r2 - AW47 - SM (2021 - 03 - 15 11 - 20 - 35 UTC)
284 pages
GibbsCAM Macro Reference
No ratings yet
GibbsCAM Macro Reference
87 pages
DOC1387081 r7 AW47 SM
100% (3)
DOC1387081 r7 AW47 SM
328 pages
Service Manual HiPath 1150
No ratings yet
Service Manual HiPath 1150
251 pages
NX Nastran 12: Siemens Siemens Siemens
No ratings yet
NX Nastran 12: Siemens Siemens Siemens
2,800 pages
C5G - R1C - Roboshop Program 2.0.0
No ratings yet
C5G - R1C - Roboshop Program 2.0.0
82 pages
Manual Book RTC Editor
No ratings yet
Manual Book RTC Editor
384 pages
Siemens 3113 PDF
No ratings yet
Siemens 3113 PDF
359 pages
Service Manual
No ratings yet
Service Manual
206 pages
Modelsim User Guaide.
No ratings yet
Modelsim User Guaide.
703 pages
GE Fanuc Open Ladder Editing
100% (1)
GE Fanuc Open Ladder Editing
329 pages
Valcon Easywriter Ver1.0E Manual: Warning
No ratings yet
Valcon Easywriter Ver1.0E Manual: Warning
24 pages
Parameter Guide
No ratings yet
Parameter Guide
584 pages
DELL 5210n, 5310n Parts List, Service Manual
No ratings yet
DELL 5210n, 5310n Parts List, Service Manual
430 pages
Pathloss 4.0 Manual
67% (3)
Pathloss 4.0 Manual
457 pages
Lexmark T630, Lexmark T632, Lexmark T634 Service Manual
No ratings yet
Lexmark T630, Lexmark T632, Lexmark T634 Service Manual
345 pages
ATV900 Programming Manual en NHA80757 03
No ratings yet
ATV900 Programming Manual en NHA80757 03
722 pages
Version B.04
No ratings yet
Version B.04
166 pages
Online Help 1221200074591662857
No ratings yet
Online Help 1221200074591662857
123 pages
Military Handbook MIL-HDBK-1222
100% (3)
Military Handbook MIL-HDBK-1222
180 pages
Mil STD 40051
No ratings yet
Mil STD 40051
61 pages
T-Spice 13 User Guide-Contents: 1 Getting Started 10
No ratings yet
T-Spice 13 User Guide-Contents: 1 Getting Started 10
569 pages
Xerox Docucentre Sc2020: User Guide
No ratings yet
Xerox Docucentre Sc2020: User Guide
322 pages
MWD Log Quality & Standards
100% (1)
MWD Log Quality & Standards
168 pages
Ge Fanuc Open Ladder Editing PDF Free
No ratings yet
Ge Fanuc Open Ladder Editing PDF Free
329 pages
1756 pm004 - en P
No ratings yet
1756 pm004 - en P
90 pages
IBM Infoprint 1532, 1552, 1572 (4536, 4537, 4538) Parts List, Service Manual
No ratings yet
IBM Infoprint 1532, 1552, 1572 (4536, 4537, 4538) Parts List, Service Manual
396 pages
Fileaid Batch Reference
No ratings yet
Fileaid Batch Reference
176 pages
WebTechnology Study Materials
100% (2)
WebTechnology Study Materials
143 pages
Fa Batch
100% (1)
Fa Batch
190 pages
Modelsim User
No ratings yet
Modelsim User
685 pages
ModelSim Users Manual v10.1c PDF
No ratings yet
ModelSim Users Manual v10.1c PDF
733 pages
LEXMARK T640 T642 T644 (4061-xx0) SM
No ratings yet
LEXMARK T640 T642 T644 (4061-xx0) SM
395 pages
Cadence Design With RTL Compiler Physical PDF
No ratings yet
Cadence Design With RTL Compiler Physical PDF
108 pages
MWD Log Quality & Standards - BHI - 1996 PDF
No ratings yet
MWD Log Quality & Standards - BHI - 1996 PDF
168 pages
Karnataka Board 1st PUC Maths Previous Year Paper 2018
No ratings yet
Karnataka Board 1st PUC Maths Previous Year Paper 2018
2 pages
Lexmark C534n 5022-xxx Service Manual
No ratings yet
Lexmark C534n 5022-xxx Service Manual
314 pages
Modelsim User
No ratings yet
Modelsim User
687 pages
Web Publishing and Browsing (WDP)
100% (1)
Web Publishing and Browsing (WDP)
13 pages
Ameh2126 PDF
No ratings yet
Ameh2126 PDF
258 pages
Web Technology and Commerce Unit-2 by Arun Pratap Singh
No ratings yet
Web Technology and Commerce Unit-2 by Arun Pratap Singh
65 pages
Introduction Manual
No ratings yet
Introduction Manual
26 pages
Document - Repository and Search Engine For Alumni of College
67% (3)
Document - Repository and Search Engine For Alumni of College
110 pages
Line Maintenence Manual - Vol III - Issue 01 Rev02 - 15.10.2013
No ratings yet
Line Maintenence Manual - Vol III - Issue 01 Rev02 - 15.10.2013
113 pages
SNew Engine23060422070
No ratings yet
SNew Engine23060422070
23 pages
Z-003 - Technical Information Flow Requirements Ed2, May1998
No ratings yet
Z-003 - Technical Information Flow Requirements Ed2, May1998
19 pages
Engineering Instruction: Air India Express Limited
No ratings yet
Engineering Instruction: Air India Express Limited
26 pages
CAR - CAMO Issue 1 Dated 31 July 2024
No ratings yet
CAR - CAMO Issue 1 Dated 31 July 2024
105 pages
Ei 17 080 A322 - Rev.d
No ratings yet
Ei 17 080 A322 - Rev.d
47 pages
Norma - UL 565-1998
No ratings yet
Norma - UL 565-1998
22 pages
Distributed Database System
No ratings yet
Distributed Database System
6 pages
Engineering Instruction: Page 1 / 4 06:19 RUP 21.jun.2023
No ratings yet
Engineering Instruction: Page 1 / 4 06:19 RUP 21.jun.2023
23 pages
High Comfort
No ratings yet
High Comfort
134 pages
Engineering Instruction: Air India Express Limited
No ratings yet
Engineering Instruction: Air India Express Limited
19 pages
Introduction To Cisco Unified Communication Manager Interfaces
No ratings yet
Introduction To Cisco Unified Communication Manager Interfaces
76 pages
FLT Attn Seat 2157
No ratings yet
FLT Attn Seat 2157
131 pages
Crypto App Project REPORT
No ratings yet
Crypto App Project REPORT
13 pages
Engineering Instruction: RUP 10:24 23.jun.2022 Page 1/3
No ratings yet
Engineering Instruction: RUP 10:24 23.jun.2022 Page 1/3
12 pages
CSC 304 - M1 - Students
No ratings yet
CSC 304 - M1 - Students
20 pages
A320 Family ALS Part 4 Variation 9.1
0% (1)
A320 Family ALS Part 4 Variation 9.1
4 pages
XML Chap8 Sebesta Web2
No ratings yet
XML Chap8 Sebesta Web2
52 pages
It For Managers: An Assignment On What Are Data Warehousing, Meta Data, Data Mining, and The Uses
0% (1)
It For Managers: An Assignment On What Are Data Warehousing, Meta Data, Data Mining, and The Uses
13 pages
Wam
No ratings yet
Wam
155 pages
Imc451 5
100% (1)
Imc451 5
37 pages
Engineering Instruction: Air India Express Limited
No ratings yet
Engineering Instruction: Air India Express Limited
41 pages
Ei 07 116 A322 - Rev.o
No ratings yet
Ei 07 116 A322 - Rev.o
41 pages
Engineering Instruction: Page 1 / 5 09:24 UGK 24.jul.2023
No ratings yet
Engineering Instruction: Page 1 / 5 09:24 UGK 24.jul.2023
22 pages
Engineering Instruction: AIRCRAFT REGISTRATION (To Be Filled by Certifying Staff) : Workorder No
No ratings yet
Engineering Instruction: AIRCRAFT REGISTRATION (To Be Filled by Certifying Staff) : Workorder No
10 pages
Unit 5 HTML An Introduction: Structure
No ratings yet
Unit 5 HTML An Introduction: Structure
44 pages
Engineering Instruction: Air India Express Limited
No ratings yet
Engineering Instruction: Air India Express Limited
25 pages
Engineering Instruction: Page 1 / 3 05:48 UGK 27.jul.2023
No ratings yet
Engineering Instruction: Page 1 / 3 05:48 UGK 27.jul.2023
6 pages
Engineering Instruction: Air India Express Limited
No ratings yet
Engineering Instruction: Air India Express Limited
8 pages
Unit-1 Web and Internet Technology
No ratings yet
Unit-1 Web and Internet Technology
21 pages
Jatr 30 CHK 001 03
No ratings yet
Jatr 30 CHK 001 03
15 pages
Mil-Dtl - 87158 Battle Repair
No ratings yet
Mil-Dtl - 87158 Battle Repair
22 pages
Engineering Instruction: Aix Connect PVT LTD
No ratings yet
Engineering Instruction: Aix Connect PVT LTD
12 pages
(18BCS049) Online Website For Yoga and Gym
No ratings yet
(18BCS049) Online Website For Yoga and Gym
65 pages
Online Aptitude Test Management System Project Report
No ratings yet
Online Aptitude Test Management System Project Report
32 pages
Engineering Instruction: Air India Express Limited
No ratings yet
Engineering Instruction: Air India Express Limited
6 pages
Sun Certified System Administrator Examination For Solaris 9 Study Guide Exam 310-011
No ratings yet
Sun Certified System Administrator Examination For Solaris 9 Study Guide Exam 310-011
845 pages
Engineering Instruction: Air India Express Limited
No ratings yet
Engineering Instruction: Air India Express Limited
10 pages
Rsplnew
No ratings yet
Rsplnew
4 pages
Welcome To Webville: Getting To Know html5
No ratings yet
Welcome To Webville: Getting To Know html5
10 pages
Engineering Instruction: Air India Express Limited
No ratings yet
Engineering Instruction: Air India Express Limited
10 pages
Aircraft Reliability Programme - R&D - Maintworld
No ratings yet
Aircraft Reliability Programme - R&D - Maintworld
15 pages
Book 1
No ratings yet
Book 1
11 pages
Engineering Instruction: RUP 06:01 26.apr.2022 Page 1/4
No ratings yet
Engineering Instruction: RUP 06:01 26.apr.2022 Page 1/4
8 pages
Introduction To XML: A Universal Data Format
No ratings yet
Introduction To XML: A Universal Data Format
41 pages
FWD Cargo Aft Partition FR 35
No ratings yet
FWD Cargo Aft Partition FR 35
1 page
1 MARKUP LANGUAGES Web Standards The History of Ma - 241025 - 141647
No ratings yet
1 MARKUP LANGUAGES Web Standards The History of Ma - 241025 - 141647
17 pages
Suitability Music X ML
No ratings yet
Suitability Music X ML
8 pages
HTML Versions Timeline
No ratings yet
HTML Versions Timeline
1 page
HyTime-Hypermedia-Time Document Structuring Language
No ratings yet
HyTime-Hypermedia-Time Document Structuring Language
17 pages
In Adobe Framemaker 7.2: XML Tips and Techniques
No ratings yet
In Adobe Framemaker 7.2: XML Tips and Techniques
25 pages
Gray Hat Hacking the Ethical Hacker's
From Everand
Gray Hat Hacking the Ethical Hacker's
Çağatay Şanlı
5/5 (1)
Plain JavaScript: Learning the Front-End
From Everand
Plain JavaScript: Learning the Front-End
Roger Beans-Rivet
No ratings yet
The New 3D Layout for Oil & Gas Offshore Projects: How to ensure success
From Everand
The New 3D Layout for Oil & Gas Offshore Projects: How to ensure success
Jacques Daubian
4.5/5 (3)
Time-dependent Behaviour and Design of Composite Steel-concrete Structures
From Everand
Time-dependent Behaviour and Design of Composite Steel-concrete Structures
Massimiliano Bocciarelli
No ratings yet
ChatGPT for Business: Strategies for Success
From Everand
ChatGPT for Business: Strategies for Success
Matthew C. Smith
1/5 (1)
A Guide to Injection Moulding Technique
From Everand
A Guide to Injection Moulding Technique
Dinbandhu Singh
5/5 (2)
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
From Everand
Advanced Multiplayer Game Development with Ureal Engine 5: A Comprehensive Guide to C++ Scripting
Vladimir Kiselev
No ratings yet
Cybersecurity for Executives: A Guide to Protecting Your Business
From Everand
Cybersecurity for Executives: A Guide to Protecting Your Business
Matthew C. Smith
No ratings yet
High Performance Chevy Small-Block Cylinder Heads
From Everand
High Performance Chevy Small-Block Cylinder Heads
Graham Hansen
No ratings yet
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
From Everand
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
Matthew C. Smith
No ratings yet
Content Creation Revolution with chatGPT
From Everand
Content Creation Revolution with chatGPT
Maria Cowen
No ratings yet
Autodesk Fusion 360: A Tutorial Approach
From Everand
Autodesk Fusion 360: A Tutorial Approach
Prof. Sham Tickoo
No ratings yet
Autodesk Fusion 360 PCB Black Book (V 2.0.18719)
From Everand
Autodesk Fusion 360 PCB Black Book (V 2.0.18719)
Gaurav Verma
No ratings yet
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet