0% found this document useful (0 votes)
85 views32 pages

Easy Access Rules XML Export Documentation 1.0.0

Uploaded by

Lalit Kshh
Copyright
© © All Rights Reserved
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)
85 views32 pages

Easy Access Rules XML Export Documentation 1.0.0

Uploaded by

Lalit Kshh
Copyright
© © All Rights Reserved
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

Easy Access Rules XML Export Documentation

Release version 1.0.0


Revision date of the document 2022-06-24

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 1 of 32
European Union
50668 Cologne, Germany
List of revisions
Release version Revision date of the document Comments
1.0.0 2022-06-24

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 2 of 32
European Union
50668 Cologne, Germany
Contents
1 Introduction ............................................................................................................................................................. 5

1.1 About this document ...............................................................................................................................................5

1.2 Audience ..................................................................................................................................................................5

1.3 Overview ..................................................................................................................................................................5

1.4 Feedback and comments .........................................................................................................................................5

2 About the information architecture.......................................................................................................................... 5

3 How can exported Easy Access Rules be used? ......................................................................................................... 6

3.1 Introduction .............................................................................................................................................................6

3.2 Overall structure of the XML file..............................................................................................................................8

3.3 Opening with Word ...............................................................................................................................................12

3.4 XML processing ......................................................................................................................................................12

4 Resources ............................................................................................................................................................... 14

4.1 Wikipedia references .............................................................................................................................................14

4.2 XML namespaces ...................................................................................................................................................14

4.3 XML schemas .........................................................................................................................................................15

4.4 Open XML SDK .......................................................................................................................................................15

5 Technical schema documentation .......................................................................................................................... 17

5.1 Overview ................................................................................................................................................................17

5.2 Attribute topic-metadata — business description of the metadata .....................................................................17


5.2.1 Multiple values ..................................................................................................................................................17
5.2.2 Attribute topic-metadata / @ERulesId ..............................................................................................................17
5.2.3 Attribute topic-metadata / @Domain ...............................................................................................................18
5.2.4 Attribute topic-metadata / @ActivityType ........................................................................................................18
5.2.5 Attribute topic-metadata / @AircraftCategory .................................................................................................20
5.2.6 Attribute topic-metadata / @AircraftUse .........................................................................................................20
5.2.7 Attribute topic-metadata / @AmendedBy ........................................................................................................21
5.2.8 Attribute topic-metadata / @ApplicabilityDate ................................................................................................21
5.2.9 Attribute topic-metadata / @EntryIntoForceDate ............................................................................................21
5.2.10 Attribute topic-metadata / @EquivalentForeignRegulation .........................................................................22
5.2.11 Attribute topic-metadata / @ICAOReference ...............................................................................................23

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 3 of 32
European Union
50668 Cologne, Germany
5.2.12 Attribute topic-metadata / @Keywords .......................................................................................................23
5.2.13 Attribute topic-metadata / @RegistryState ..................................................................................................26
5.2.14 Attribute topic-metadata / @RegulatedEntity .............................................................................................26
5.2.15 Attribute topic-metadata / @RegulatorySource...........................................................................................27
5.2.16 Attribute topic-metadata / @RegulatorySubject ..........................................................................................28
5.2.17 Attribute topic-metadata / @TechnicalSubjectMatter .................................................................................28
5.2.18 Attribute topic-metadata / @TypeOfContent ..............................................................................................29
5.2.19 Attribute topic-metadata / @ParentIR .........................................................................................................30
5.2.20 Attribute topic-metadata / @EASACategory ................................................................................................31
5.2.21 Attribute document-metadata / @guid ........................................................................................................32
5.2.22 Attribute document-metadata / @pub-time ................................................................................................32
5.2.23 Attribute document-metadata / @map-url ..................................................................................................32
5.2.24 Attribute document-metadata / @pub-template-url ...................................................................................32
5.2.25 Attribute document-metadata / @xslt-url ...................................................................................................32
5.2.26 Attribute document-metadata / @source-title ............................................................................................32

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 4 of 32
European Union
50668 Cologne, Germany
1 Introduction
1.1 About this document
The EASA eRules is a platform for storing and sharing of rules. It is the single, easy-access, online database for all
aviation rules applicable to European airspace users. One of the eRules’ outputs are Easy Access Rules, which
were shared, so far, in two formats – in pdfs and as online publications. These two formats already considerably
increased stakeholders’ work efficiency and reduced the need of locally consolidated documents.
As part of this project, European Aviation Safety Agency (EASA) offers to its stakeholders Easy Access Rules in
the Extensible Markup Language (XML) format. This format allows for machine-to-machine integration and can
easily be processed and automated by users, as well as incorporated into local applications, search databases,
etc.
The document describes the XML publishing format of EASA Easy Access Rules, including the XML schemas used.

1.2 Audience
The document is mostly aimed at technical personnel that need to further process the EASA Easy Access Rules
(the content and metadata) in the XML format.

1.3 Overview
The document is divided into four main parts

• About the information architecture (Chapter 2)


• How to use the content, what are the possibilities (Chapter 3)
• A catalogue of links to schema resources and supplemental documentation (Chapter 4)
• The actual XML schema documentation for the EASA namespace (Chapter 5)

1.4 Feedback and comments


Please send your feedback and comments on this document by using the Easy Access Rules area on the contact
us form.

2 About the information architecture


2.1 Overall information architecture
In eRules and in the exported XML file(s) of Easy Access Rules, the content is separated into smaller components
called topics. A topic can be:

• an EU implementing rule (IR);

• an EU delegated rule (DR);

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 5 of 32
European Union
50668 Cologne, Germany
• an EASA acceptable means of compliance (AMC);
• EASA guidance material (GM); and
• EASA certification specification (CS).
In the release 1.0.0 of the eRules XML Export specification, a topic’s content is considered an opaque data
structure. This means that in this release, the specification does not define the internal structure of the topic.
Nevertheless, an implementation may choose to use the various OOXML formatting tags available inside the
topics content to identify data and extract it.

Each topic has an associated set of metadata providing more information about the topic, such as the applicable
aviation domain, applicability date, etc. In the exported XML file, the metadata is represented as XML attributes.
For a description of the metadata associated with a topic, see Chapter 5.2.

The topics are assembled in a tree-like structure, which represents the conceptual relationships between
different types of topics.

Thus, the topics representing IRs, DRs and CSs may appear as superior nodes on a level of the tree while topics
containing AMCs and GMs will appear as subordinate nodes to the respective IRs, DRs and CSs. Please note that
the combination of superior and subordinate nodes can vary, e.g. an AMC can be a superior node to a
subordinate GM to AMC. The semantic of such an arrangement is the same that can be recognised from the PDF
and/or online format of the Easy Access Rules publications, available on the EASA website.

This structure is represented in the extracted XML file as a hierarchy of XML elements, as described in the
Chapter 3. The attribute ParentIR (see 5.2.19) provides an additional link between a GM or AMC topic and its
parent IR, DR or CS topic.

3 How can exported Easy Access Rules be used?


3.1 Introduction
The international standard Office Open XML format ECMA-376/ISO/IEC 29500 was selected as the XML standard
for the export of the Easy Access Rules.

When using the Open Packaging Conventions (OPC) form of said standard, specified in Part 2 of the ISO/IEC
29500 documentation, the content is extracted as a single XML file that embeds all text, graphics, images,
formulas or other objects; in this case, it also includes the special Easy Access Rules XML content, including its
metadata.

This format was selected because it provides the following benefits:

• it is a well-documented, non-proprietary, international ISO XML standard;

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 6 of 32
European Union
50668 Cologne, Germany
• it is very stable, with a well-ordered maintenance process;
• it is an XML standard that can be:
o machine-processed by any standard XML parser providing objects and application
programming interfaces (APIs),
o transformed using extensible style sheet language transformation (XSLT), and
o edited by any standard XML or plain text editors;

• it allows the content to be opened directly with Microsoft Word (2013 or later version);
• it provides zero-loss processing: any piece of the original content is preserved;

• it is flexible enough to host and embed all extra EASA metadata and other enriching types of
content, as described in this document; and
• there are freely available tools for its format, for example the Open XML SDK 2.5.

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 7 of 32
European Union
50668 Cologne, Germany
3.2 Overall structure of the XML file
A file packaged in Open Packaging Conventions (OPC) format consists of many individual packages, as shown
below:

These packages contain style information, external links, images, etc. Of primary interest are the following two
parts:

• <pkg:part pkg:name="/word/[Link]"

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 8 of 32
European Union
50668 Cologne, Germany
This part contains the body text of the published Easy Access Rules:

Document

Frontmatter

IR 1

AMC to IR 1

GM to IR 1

IR 2

Backmatter

• <er:document xmlns:er=”[Link]
It is the package part that contains the specific EASA XML elements, associated with the above
namespace and described in the Schema Definition file [Link].

In this example, it is contained in the package part <pkg:part


pkg:name="/customXml/[Link]", but the item number varies from document to document:

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 9 of 32
European Union
50668 Cologne, Germany
A topic’s content in the /word/[Link] part is embedded in an <w:sdt> element. The enclosed
<w:sdtPr> element contains an element <w:id> whose attribute w:val contains the key value which can
be used to locate, in the file, the metadata corresponding to that topic. Thus, the corresponding metadata can
be retrieved from the <er:topic> element having the sdt-id attribute with the same value as the w:val
attribute identified above.

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 10 of 32
European Union
50668 Cologne, Germany
Please note that the value of the sdt-id attribute is only valid as an internal pointer within the same XML file
and is not guaranteed to remain the same in different versions of the same XML file. Therefore, it cannot be
used as an unique identifier for a topic across several XML files. For such purpose, please use the attribute
ERulesId see Attribute topic-metadata / @ERulesId

Through this mechanism, all the EASA specific metadata are directly linked to the relevant content and are
available to be extracted.

In addition to the <er:topic> element, the set of EASA specific XML elements include the <er:heading>
element. This element has only a descriptive role. It can be used as a marker for locating inside the

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 11 of 32
European Union
50668 Cologne, Germany
<er:document> tree where certain text (usually high level chapter’s titles) is positioned in relation with
neighbouring topics.

The binary content, for example images used in the document, is included as base64-encoded content, as shown
below. The pkg:part elements containing binary content are referenced in the rest of the file in accordance
with the OOXML specification

3.3 Opening with Word


The exported XML file can also be opened directly with Microsoft Word, allowing all normal Word functions to
be performed on the content:

3.4 XML processing


In addition to being opened with Word, as shown above, the exported XML file can be validated, parsed, and
processed using any standard XML parsers (providing APIs) and/or editors.

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 12 of 32
European Union
50668 Cologne, Germany
This supports many advanced scenarios, such as:

• adding the content to search databases, making full use of the EASA metadata;
• integrating the content into other systems and applications;
• extracting content and metadata;
• transforming content (XSLT) to any other text-based format; and
• extracting individual topics, with the full set of EASA metadata (see shortened example below):

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 13 of 32
European Union
50668 Cologne, Germany
4 Resources
This section provides links to relevant resources, including XML schemas, etc.

4.1 Wikipedia references


• Open Packaging Conventions
[Link]

• Office Open XML


[Link]

4.2 XML namespaces


• EASA namespace [Link]
• Word (Office Open XML) namespaces, including but not limited to:
o [Link]
o [Link]
o [Link]
o urn:schemas-microsoft-com:office:office
o [Link]
o [Link]
o urn:schemas-microsoft-com:vml
o [Link]
o [Link]
o urn:schemas-microsoft-com:office:word
o [Link]
o [Link]
o [Link]
o [Link]
o [Link]
o [Link]
o [Link]

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 14 of 32
European Union
50668 Cologne, Germany
o [Link]
o [Link]

4.3 XML schemas


If needed, the full Office Open XML schemas for Word are available for free download from here:
[Link]

The XML schema definition corresponding to the namespace:


[Link]
is included in the file EASA-eRules-XML-Export-Schema-1.0.0 accompanying this document.
4.4 Open XML SDK
Open XML Software Development Kit (SDK) documentation:
[Link]
Open XML SDK on GitHub:
[Link]
It is recommended to download the free Open XML SDK from this location:
[Link]
In addition to various other useful tools, the SDK contains the complete ISO/IEC 29500-1 official standard
documentation accessible from the Open XML SDK 2.5 Productivity tool ([Link]
XML-SDK/releases/tag/v2.5), as illustrated below:

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 15 of 32
European Union
50668 Cologne, Germany
[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 16 of 32
European Union
50668 Cologne, Germany
5 Technical schema documentation
5.1 Overview
The technical schema documentation is available on the XML website.

5.2 Attribute topic-metadata — business description of the metadata


5.2.1 Multiple values
Some attributes/metadata fields can have multiple separate values. For example:
AircraftCategory = ‘Complex motor-powered aircraft (CMPA); Non-complex motor-powered aircraft (non-
CMPA)’

In this case, a semicolon ‘;’ is used to separate the values.

5.2.2 Attribute topic-metadata / @ERulesId

Description A unique identifier attribute for every topic in the exported XML file, which allows the
unique identification of a topic across all the exported XML files from EASA.

The ERulesId value is unchanged:

• from publication to publication, everywhere the topic is reused; and


• from version to version, throughout the entire life cycle of the topic.

Example:

• ERulesId="ERULES-1891294191-107"

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 17 of 32
European Union
50668 Cologne, Germany
5.2.3 Attribute topic-metadata / @Domain

Description The civil aviation domains as per Regulation EU) 2018/1139 (the EASA ‘New Basic
Regulation’), Regulation (EU) No 628/2013 (the ‘Standardisation Inspections
Regulation’).

Examples (non-inclusive list):

• Air Operations (Air OPS),


• Continuing Airworthiness (CAW),

• Aircrew,

• Basic Regulation (BR),


• Balloons,

• Air Traffic Management (ATM / Air Navigation Services (ANS),


• Third-Country Operators (TCO),

• Aerodromes (ADR).

5.2.4 Attribute topic-metadata / @ActivityType

Description Technical description of the type of activity performed by specific domain.

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• licensing,

• maintenance,
• training,
• examination,

• CAW management,
• airworthiness review certificate (ARC),

• aircraft maintenance programme (AMP),

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 18 of 32
European Union
50668 Cologne, Germany
• assessment,
• aircraft CAW monitoring (ACAM),
• oversight,
• aerodrome data,
• safety management system (SMS),

• notification of differences to ICAO,


• Aeronautical Information Services (AIS),

• Air Traffic Control (ATC) services,

• Air Traffic Services (ATS),


• Meteorological Services (MET),
• Aerodrome Flight Information Services (AFIS),
• Flight Information Services (FIS),
• aerodrome maintenance,
• aerodrome safety management,
• authority management system,

• medical,
• training,

• certification,
• Apron Management Services (AMS),
• aerodrome operations,
• aerodrome design,

• manufacturing.

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 19 of 32
European Union
50668 Cologne, Germany
5.2.5 Attribute topic-metadata / @AircraftCategory

Description Identification of the applicable requirements by specific category of aircraft.

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• complex motor-powered aircraft (CMPA),


• non-complex motor-powered aircraft (non-CMPA),

• ELA 1,
• ELA 2,
• sailplanes,
• balloons,
• large aeroplanes,
• large rotorcraft,
• small aeroplanes,

• small rotorcraft,
• very light rotorcraft (VLR),

• light sport aeroplanes (LSA),


• very light aeroplanes (VLA).

5.2.6 Attribute topic-metadata / @AircraftUse

Description Identification of the applicable requirements by specific use of aircraft.

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• used by licensed air carriers (LACs);

• used for commercial operations other than by a LAC, or by a commercial


approved training organisation (ATO);

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 20 of 32
European Union
50668 Cologne, Germany
• used by private operators or for ‘limited operations’;
• used by commercial air transport (CAT).

5.2.7 Attribute topic-metadata / @AmendedBy

Description The number of the issue/amendment.

Examples (non-inclusive):

• CS Issue 1,
• CS Issue 2,
• CS Issue 3,
• Amendment 1,
• Amendment 2.

5.2.8 Attribute topic-metadata / @ApplicabilityDate

Description Regardless of the legal wording, this date is considered as the last possible date of the
transition period (the end of the transition period).

Examples (non-inclusive list):

• 18 May, 2021,
• 25 April, 2018.

5.2.9 Attribute topic-metadata / @EntryIntoForceDate

Description The date of entry-into-force as indicated in the officially published regulatory material.
It represents the date as of which a legally binding act begins to have legal force.

Examples (non-inclusive list):


• 18 May, 2021,

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 21 of 32
European Union
50668 Cologne, Germany
• 25 April, 2018.

5.2.10 Attribute topic-metadata / @EquivalentForeignRegulation

Description It is important for the aircraft design community to be able to refer to applicable
equivalent foreign design standards.

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• Advisory Circular (AC) 20-153B,


• Federal Aviation Administration (FAA) (Federal Aviation Regulation) FAR-
25,
• FAA Part-121.

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 22 of 32
European Union
50668 Cologne, Germany
5.2.11 Attribute topic-metadata / @ICAOReference

Description Identification of the ICAO Standards and Recommended Practices (SARPs).

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• Annex 2,
• Annex 3,

• Annex 4,
• Annex 10, Volume I,
• Annex 10, Volume II,
• Annex 10, Volume III,
• Annex 10, Volume IV,
• Annex 10, Volume V,
• Annex 11,

• Annex 14, Volume I,


• Annex 14, Volume II,

• Annex 15,
• Annex 19, Chapter 3,
• Annex 19, Chapter 4.

5.2.12 Attribute topic-metadata / @Keywords

Description Additional metadata category.

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• limitation,

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 23 of 32
European Union
50668 Cologne, Germany
• qualification,
• training,
• audit,
• subcontract,
• record,

• operational suitability data (OSD),


• management personnel,

• application,

• airworthiness directive (AD),


• airworthiness limitations section (ALS),
• air operator certificate (AOC),
• aircraft flight manual (AFM),
• transfer,
• independent inspection,
• occurrence reporting,

• permit to fly,
• line,

• base,
• experience,
• pilot-owner maintenance,
• endorsement,

• conversion,
• examination credit,

• type training,

• type examination,
• exposition,

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 24 of 32
European Union
50668 Cologne, Germany
• on-the-job training (OJT),
• training needs analysis (TNA),
• authorisation,
• maintenance organisation manual (MOM),
• basic training,

• differences training,
• task training,

• small organisation,

• contract,
• minimum inspection programme,
• component,
• work order,
• reliability programme,
• pre-flight,
• minimum equipment list (MEL),

• maintenance data,
• escalation,

• reliability programmes,
• critical task,
• non-destructive inspection (NDI),
• bilateral agreement,

• fabrication,
• components,

• assessment,

• examination,
• non-destructive testing (NDT),

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 25 of 32
European Union
50668 Cologne, Germany
• exception,
• used,
• import/export.

5.2.13 Attribute topic-metadata / @RegistryState

Description Identification of the applicable requirements by aircraft State of registry.

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• EU-registered,
• Non-EU-registered.

5.2.14 Attribute topic-metadata / @RegulatedEntity

Description The main legal person or entity to whom the requirements are addressed: aviation
industry or competent authority stakeholders.

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• competent authority,
• EASA,
• aircraft operator,
• aircraft maintenance license (AML) holder,
• approved maintenance organisation (AMO),
• certifying staff,

• maintenance training organisation,

• aircraft owner,

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 26 of 32
European Union
50668 Cologne, Germany
• continuing-airworthiness management organisation (CAMO),
• pilot-in-command (PIC),
• Member State (MS),
• type certificate (TC) holder,
• restricted type certificate (RTC) holder,

• supplemental type certificate (STC) holder,


• design approval holder (DAH),

• European Technical Standard Order (ETSO) authorisation holder,

• production approval holder,


• alternative procedure to design organisation approval (AP-DOA) holder,
• production organisation without production organisation approval (POA).

5.2.15 Attribute topic-metadata / @RegulatorySource

Description Identification of the regulatory document introducing the topic or the last amendment
thereto (‘initial or further issues’ or ‘amendments’).

Examples (non-inclusive list):

• ED Decision 2015/029/R,
• Regulation (EU) No 1321/2014,
• Regulation (EU) 2015/1536,
• Regulation (EU) 2015/1088,
• Regulation (EU) 2015/1536,
• ED Decision 2016/011/R,
• ED Decision 2017/016/R,

• ED Decision 2019/009/R,
• ED Decision 2019/024/R,

• Regulation (EU) 2018/1142,

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 27 of 32
European Union
50668 Cologne, Germany
• Regulation (EU) 2019/1383,
• Regulation (EU) 2020/270.

5.2.16 Attribute topic-metadata / @RegulatorySubject

Description Reference to the relevant regulatory material (cover regulation, annex=part). It refers to
the structure of the regulatory material as published on the Official Journal (OJ) of the
European Union or on the EASA website.

Examples (non-inclusive list):

• cover regulation,
• Part-M,
• Part-145,
• Part-T,
• Part-66,
• Part-147,

• Part-CAMO,

• Part-CAO,
• Part-ML,
• [Link],
• [Link],
• [Link],
• CS-HPT-DSN,

• CS-ADR-DSN.

5.2.17 Attribute topic-metadata / @TechnicalSubjectMatter

Description Standard breakdown number of the technical system.

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 28 of 32
European Union
50668 Cologne, Germany
Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• ATA chapter,

• general,
• runways,

• runway end safety area,


• taxiways,

• aprons,
• isolated aircraft parking positions,
• de-icing/anti-icing facilities,
• obstacle limitation surfaces/requirements,
• indicators and signalling devices,

• markings,
• lights,

• signs,
• markers,

• obstacles,
• restricted-use areas,
• electrical systems,
• operational services, equipment, and installation.

5.2.18 Attribute topic-metadata / @TypeOfContent

Description Identification of the type of regulatory material

Examples (non-inclusive list):

• IR (Implementing rule),

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 29 of 32
European Union
50668 Cologne, Germany
• DR (Delegated rule),
• AMC to IR (Acceptable means of compliance to implementing rule),
• GM to AMC (Guidance material to acceptable means of compliance),
• CS (Certification specification).

5.2.19 Attribute topic-metadata / @ParentIR

Description Identification of the ‘parent-child’ relationship between a superior and subordinate topic
in a nested structure. Typically, the IR/CS are ‘parent’ topics, and the related AMC/GM are
‘child’ topics. That relationship, however, can happen between different types of content.

This attribute holds the title of the ‘parent’ IR/CS topic of the AMC/GM ‘child’ topics. For
example, for each AMC/GM in a consolidated publication, it will hold a value if the
following condition is met:

• the topic has a direct topic parent in the nested structure one level up in
the table of contents (ToC) hierarchy.

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 30 of 32
European Union
50668 Cologne, Germany
5.2.20 Attribute topic-metadata / @EASACategory

Description A list containing the runways intended for the operation of aircraft using visual approach
procedures or instrument approach procedures, as well as the type of the runway’s
surface.

Note: As of this release, this attribute may contain empty or not up-to-date values.

Examples (non-inclusive list):

• non-instrument approach runway,


• non-precision approach runway,
• precision approach runway Category I,
• precision approach runway Category II,

• precision approach runway Category III,


• take-off runway,
• unpaved runway.

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 31 of 32
European Union
50668 Cologne, Germany
5.2.21 Attribute document-metadata / @guid

Description The is a globally unique identifier for exactly this published version of Easy Access Rules.

• Example: 9bbcb121-8886-4a13-986f-4a47ad7ee7bb

5.2.22 Attribute document-metadata / @pub-time

Description Exact publishing time of the XML file.

• Example: 2022-03-09T[Link]Z

5.2.23 Attribute document-metadata / @map-url

Description For EASA internal use only.

5.2.24 Attribute document-metadata / @pub-template-url

Description For EASA internal use only.

5.2.25 Attribute document-metadata / @xslt-url

Description For EASA internal use only.

5.2.26 Attribute document-metadata / @source-title

Description Title of the publication (the XML file).

• Example: Annex II (Part-BOP) — BALLOON AIR OPERATIONS

[Link].00301-007
Postal address: Postfach 10 12 53
50452 Cologne, Germany
An agency of the Visiting address: Konrad-Adenauer-Ufer 3 Page 32 of 32
European Union
50668 Cologne, Germany

You might also like