IEC PAS 61182-12:2014

Generic requirements for printed board assembly products manufacturing description data and transfer methodology

IEC PAS 61182-2:2014(E) specifies the XML schema that represents the intelligent data file format used to describe printed board and printed board assembly products with details sufficient for tooling, manufacturing, assembly, and inspection requirements. This format may be used for transmitting information between a printed board designer and a manufacturing or assembly facility. The data is most useful when the manufacturing cycle includes computer-aided processes and numerical control machines.

General Information

• Status: Withdrawn
• Publication Date: 21-Aug-2014
• Withdrawal Date: 28-Oct-2021
• ICS: 31.180 - Printed circuits and boards
• Technical Committee: TC 91 - Electronics assembly technology
• Current Stage: WPUB - Publication withdrawn
• Start Date: 29-Oct-2021
• Completion Date: 29-Oct-2021

Standards Content (Sample)

IEC PAS 61182-12 ®
Edition 1.0 2014-08
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
colour
inside
Generic requirements for printed board assembly products manufacturing
description data and transfer methodology

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Central Office Tel.: [phone]
3, rue de Varembé Fax: [phone]
CH-1211 Geneva 20 [e-mail]
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing more than 30 000 terms and
Technical Specifications, Technical Reports and other definitions in English and French, with equivalent terms in 14
documents. Available for PC, Mac OS, Android Tablets and additional languages. Also known as the International
iPad. Electrotechnical Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a More than 55 000 electrotechnical terminology entries in
variety of criteria (reference number, text, technical English and French extracted from the Terms and Definitions
committee,…). It also gives information on projects, replaced clause of IEC publications issued since 2002. Some entries
and withdrawn publications. have been collected from earlier publications of IEC TC 37,

77, 86 and CISPR.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: [e-mail].
IEC PAS 61182-12 ®
Edition 1.0 2014-08
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
colour
inside
Generic requirements for printed board assembly products manufacturing

description data and transfer methodology

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XH
ICS 31.180 ISBN 978-2-8322-1804-4

– i – IEC PAS 61182-12:2014 © IEC 2014
TABLE OF CONTENTS
1 SCOPE . 1
1.1 Focus and intent. 1
1.2 Notation . 1
2 APPLICABLE DOCUMENTS . 2
2.1 Documentation conventions . 2
3 REQUIREMENTS . 5
3.1 Rules concerning the use of XML and XML Schema . 7
3.1.1 File readability and uniformity . 7
3.1.2 File markers . 7
3.1.3 File extension . 7
3.1.4 File remarks . 7
3.1.5 Character set definition . 7
3.2 Data organization and identification rules . 7
3.2.1 Naming elements within a 258X File. 8
3.2.2 The Use of XML elements and types . 8
3.2.3 Attribute base types (governing templates). 8
3.2.4 Coordinate system and transformation rules . 10
3.3 Transformation characteristics (Xform) . 11
3.3.1 The x and y Offset attributes . 12
3.3.2 The rotation attribute . 12
3.3.3 The mirror attribute . 13
3.3.4 The scale attribute . 13
3.3.5 The x and y Location attributes . 13
3.4 Substitution groups . 14
3.4.1 ColorGroup . 16
3.4.2 Feature . 16
3.4.3 Fiducial . 16
3.4.4 FirmwareGroup . 17
3.4.5 FontDef . 18
3.4.6 LineDescGroup . 18
3.4.7 FillDescGroup . 19
3.4.8 PolyStep . 19
3.4.9 Simple . 20
3.4.10 StandardPrimitive. 20
3.4.11 StandardShape . 22
3.4.12 UserPrimitive . 22
3.4.13 UserShape . 23
4 CONTENT . 24
4.1 Content: FunctionMode . 25
4.1.1 USERDEF mode . 26
4.1.2 DESIGN mode . 26

4.1.3 FABRICATION mode . 27
4.1.4 ASSEMBLY mode . 27
4.1.5 TEST mode . 27
4.2 Function levels . 27
4.2.1 USERDEF Mode Level 1 . 28
4.2.2 Design Levels . 29
4.2.3 Fabrication Levels . 31
4.2.4 Assembly Levels . 33
4.2.5 Test Levels . 35
4.3 Content: StepRef . 37
4.4 Content: LayerRef . 38
4.5 Content: BomRef . 38
4.6 Content: AvlRef . 39
4.7 Content: DictionaryStandard . 39
4.7.1 StandardPrimitive: Butterfly . 40
4.7.2 StandardPrimitive: Circle . 42
4.7.3 StandardPrimitive: Contour . 43
4.7.4 StandardPrimitive: Diamond . 46
4.7.5 StandardPrimitive: Donut . 47
4.7.6 StandardPrimitive: Ellipse . 49
4.7.7 StandardPrimitive: Hexagon . 50
4.7.8 StandardPrimitive: Moire . 52
4.7.9 StandardPrimitive: Octagon . 53
4.7.10 StandardPrimitive: Oval . 54
4.7.11 StandardPrimitive: RectCenter . 56
4.7.12 StandardPrimitive: RectCham . 58
4.7.13 StandardPrimitive: RectCorner . 60
4.7.14 StandardPrimitive: RectRound . 62
4.7.15 StandardPrimitive: Thermal . 64
4.7.16 StandardPrimitive: Triangle . 66
4.8 Content: DictionaryUser . 68
4.8.1 UserPrimitive, Simple . 69
4.8.2 UserPrimitive: Text . 75
4.8.3 UserPrimitive: UserSpecial . 78
4.9 Content: DictionaryFont . 79
4.9.1 FontDefEmbedded . 80
4.9.2 FontDefExternal . 81
4.9.3 FontDef: Glyph . 81
4.9.4 FontDef: Glyph combination . 82
4.10 Content: DictionaryLineDesc . 82
4.10.1 LineDesc. 84
4.10.2 LineDescRef . 85
4.11 Content: DictionaryFillDesc . 86
4.11.1 FillDesc . 87

– iii – IEC PAS 61182-12:2014 © IEC 2014
4.11.2 FillDescRef . 89
4.12 Content: DictionaryColor . 90
4.12.1 Color . 91
4.12.2 ColorRef . 91
4.13 Content: DictionaryFirmware . 92
4.13.1 CachedFirmware . 93
4.13.2 FirmwareRef . 93
5 LOGISTIC HEADER . 94
5.1 LogisticHeader . 94
5.2 Role . 95
5.3 Enterprise . 96
5.4 Person . 98
6 HISTORY RECORD . 100
6.1 HistoryRecord . 100
6.2 FileRevision . 101
6.3 SoftwarePackage . 102
6.4 ChangeRec . 103
7 BOM (Material List) . 104
7.1 BOM Header . 106
7.2 BomItem . 106
7.2.1 BomDes . 108
7.2.2 Characteristics . 114
8 ELECTRONIC COMPUTER AIDED DESIGN (ECAD) . 118
8.1 CadHeader . 118
8.1.1 Spec . 119
8.1.2 Property . 133
8.1.3 ChangeRec . 134
8.2 CadData . 135
8.2.1 Layer . 137
8.2.2 Stackup . 143
8.2.3 Step . 151
8.2.4 DfxMeasurementList . 204
9 APPROVED VENDOR LIST (AVL) . 207
9.1 AvlHeader . 208
9.2 AvlItem . 209
9.2.1 AvlVmpn . 209
10 GLOSSARY . 212
10.1 Process Flow Descriptions . 212
10.2 Terms and Definitions . 212
10.3 Enumerated strings of 2581 . 213
11 REFERENCE INFORMATION. 214
11.1 IPC . 214
11.2 American National Standards Institute . 214

11.3 Department of Defense . 215
11.4 Electronic Industries Association . 215
11.5 International Organization for Standards (ISO) . 215
Appendix A IPC-7351 Naming Convention for Land Patterns . 216
Appendix B Panel Instance File . 220
Appendix C Potential Reference Designator Assignment for Non Electrical Items . 225

– v – IEC PAS 61182-12:2014 © IEC 2014
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
GENERIC REQUIREMENTS FOR PRINTED BOARD ASSEMBLY PRODUCTS
MANUFACTURING DESCRIPTION DATA AND TRANSFER METHODOLOGY

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
A PAS is a technical specification not fulfilling the requirements for a standard, but made
available to the public.
IEC PAS 61182-12, submitted by IPC has been processed by IEC technical committee 91:
Electronics assembly technology. It is based on IPC-2581B. It is published as a double-logo
PAS. The structure and editorial rules used in this PAS reflect the practice of the organization
which submitted it.
The text of this PAS is based on the This PAS was approved for
following document: publication by the P-members of the
committee concerned as indicated in
the following document
Draft PAS Report on voting
91/1182/PAS 91/1192/RVD
Following publication of this PAS, the technical committee or subcommittee concerned may
transform it into an International Standard.

This PAS shall remain valid for an initial maximum period of 3 years starting from the
publication date. The validity may be extended for a single period up to a maximum of 3 years,
at the end of which it shall be published as another type of normative document, or shall be
withdrawn.
IMPORTANT – The “colour inside” logo on the cover page of this publication indicates

that it contains colours which are considered to be useful for the correct understanding
of its contents. Users should therefore print this publication using a colour printer.

– vii – IEC PAS 61182-12:2014 © IEC 2014

Generic Requirements for Printed Board Assembly Products
Manufacturing Description Data and Transfer Methodology

1 SCOPE
This standard specifies the XML schema that represents the intelligent data file format used to describe
printed board and printed board assembly products with details sufficient for tooling, manufacturing,
assembly, and inspection requirements. This format may be used for transmitting information between a
printed board designer and a manufacturing or assembly facility. The data is most useful when the
manufacturing cycle includes computer-aided processes and numerical control machines.
The data can be defined in either English or International System of Units (SI) units. The format is a
convergence of the IPC-2511 “GenCAM” and the Valor Computerized Systems “ODB-X” format structure.
1.1 Focus and intent
The generic format requirements are provided in a series of standards focused on printed board
manufacturing, assembly, and inspection testing. This standard series consists of a generic standard (IPC-
2581) that contains all the general requirements. There are seven sectional standards that are focused on the
XML details necessary to accumulate information in the single file, that addresses the needs of the
manufacturing disciplines producing a particular product.
The sectional standards (IPC-2582 through 2588) paraphrase the important requirements and provide
suggested usage and examples for the topic covered by the sectional standard.
1.2 Notation
Although the data would be contained in a single file, the file can have different purposes as described in
Section 4. The XML schema used for this standard follows the notations set forth by the W3C and is as
follows:
element – Element appears exactly one time
element? – Element may appear 0 or 1 times
element* – Element may appear 0 or more times
element+ – Element may appear 1 or more times
Any IPC-258X file is composed of a high level element (IPC-2581) that contains up to six sub-elements:
Content – information about the contents of the 258X file
LogisticHeader – information pertaining to the order and supply data
HistoryRec – change information of the file
Bom – Bill of Materials (Material List) information
Ecad – Computer Aided Design (engineering) information
Avl – Approved Vendors List information

– 2 – IEC PAS 61182-12:2014 © IEC 2014
2 APPLICABLE DOCUMENTS
The following documents contain requirements which, when referenced, constitutes provisions of IPC-2581.
At the time of publication, the editions indicated were valid. All documents are subject to revision and parties
entering into agreements based on this standard are encouraged to investigate the possibility of applying the
most recent editions of the documents indicated below.
The revision of the document in effect at the time of solicitation shall take precedence.
IPC-T-50 Terms and Definitions for Interconnecting and Packaging Electronic Circuits

IPC-2501 Definition for Web-Based Exchange of XML Data

IPC-2524 PWB Fabrication Data Quality Rating System

IPC-2511 Generic Requirements for Implementation of Product Manufacturing Description Data and Transfer
XML Schema Methodology
IPC-2571 Generic Requirements for Electronics Manufacturing Supply Chain Communication - Product Data
eXchange (PDX)
IPC-2576 Sectional Requirements for Electronics Manufacturing Supply Chain Communication of As-Built
Product Data - Product Data eXchange

IPC-2577 Sectional Requirements for Supply Chain Communication of Manufacturing Quality Assessment -
Product Data eXchange (PDX)
IPC-2578 Sectional Requirements for Supply Chain Communication of Bill of Material and Product Design
Configuration Data - Product Data eXchange

IPC-7351 Generic Requirements for Surface Mount Design and Land Patterns

2.1 Documentation conventions
The XML file format standard and the XML Schema definition language standard, as defined the by World
Wide Web Consortium (W3C), have been adopted by IPC for use in the IPC-2500 series of standards.
In addition to the text based schema notation, this document provides graphical representation of the
structure of the file format. The XML diagrams are designed to effectively illustrate the structure and
cardinality of elements and attributes that make up any IPC-258X file. The notation in the graphics does not
provide a complete visualization of the schema definition for the file format, but it does provide a good top
down overview. Should there be any conflict between the graphical notation and the schema notation, the
authoritative definition is the schema notation.
Table 1 provides an overview of the graphical notation used in the document.

Table 1 Graphical Notation Overview
This diagram depicts an element named AnElement
that is of type TypeB. There is one attribute, named
anAttribute, that is of type double. The attribute is
required.
Example:

Note that all attribute values must be enclosed in quotes, regardless of type.
This diagram depicts an element named
AnotherElement that is of type TypeA with two
attributes. The attribute anAttribute is required. The
second attribute, anOptionalAttribute, is optional.
Both attributes are of type string.

Examples:


The ElementType OneToManyOrElements is the
parent of an unordered list of one or more instances
of the elements AnElement and AnotherElement.
The type TypeA occurs only once while TypeB can
occur many times.
The arrow indicates a substitution of the element
named AnOrParentElement. The substitution
declares that one and only one occurrence is
allowed. The AnOrParentElement can have one of
AnElement or AnotherElement as a child element.

– 4 – IEC PAS 61182-12:2014 © IEC 2014
The optional indication for the three element children
shows that none may be present or many versions
of all three are possible.
This diagram depicts an element, AParentElement,
of type AParentElementType. This element has one
attribute, attributeOfParent, which is optional. The
lines indicate that occurrences of AnElement and
AnotherElement appear in the order with AnElement
indicated as required while AnotherElement is
optional. Both elements have a required attribute;
however, if AnotherElement is instantiated,
anOptionalAttribute is also possible.

This diagram depicts a type, AParentElementType,
that contains a sequence starting with one of
AThirdElement or AFourth element followed by 1-n
AnElement and an optional final AnotherElement.
The AParentElement also has an optional attribute.

3 REQUIREMENTS
The XML schema contained in this document describes the structure of a generic computer-aided
manufacturing 258X exchange format. The document specifies data elements specifically designed to
establish the information exchange related to the data needed by printed board manufacturing, and assembly
including inspection of those products.
The XML schema defines the configuration of mandatory and optional elements, as well as mandatory and
optional attributes. The Top Level (TopElement) of the schema contains six major elements. The schema
notation specifies that the 6 top-level elements are required to appear in the order shown in Figure 1. The
order of appearance in the file is significant. For instance, the appearance of graphics on a layer is dependent
on the order of appearance in the file. The order is also important because elements often reference
information that is defined elsewhere in the file in order to eliminate redundancy within the file. The file is
structured to allow all references to be resolved in one pass.
An implementation of the XML schema must be able to facilitate the reading and/or writing of all
characteristics defined within the requirements stated in the Mode function of this standard. Some tools may
have only read capability; some may have only write capability. Some tools may have both read/write
capability. All schema defined in the standard as mandatory (1-1, 1-n occurrences) shall be executed as
appropriate. Tool providers shall identify their capability by Mode Level (USERDEF 1, Design 1, 2 or 3,
Fabrication 1, 2, or 3 etc.) plus 2581R; 2581W; or 2581RW.
Each element has a specific function or task. Accordingly, the information interchange for a specific purpose
is possible only if that element is populated. The ability to select those characteristics that are appropriate for
a given task makes the schema a robust methodology for defining only those areas and characteristics that
are necessary to produce a given product. Figure 1 shows the potential children elements of the Top Element
(IPC-2581).
– 6 – IEC PAS 61182-12:2014 © IEC 2014

Attribute / Attribute / Description Occur-
Element Name Element Type rence
IPC-2581 IPC-2581Type
The generic name of the file used to describe Design, Fabrication, Assembly, 1-1
and Test information in accordance with the IPC-2581 standard.
revision string
The status of the IPC-2581 file content. 1-1
Content ContentType The Content element defines the function of the file, and references the
1-1
major sections of the product description (i.e., Step, Layer, Bom and Avl). In
addition, there are six dictionaries indicated in Content that would contain
the pre-described information needed for the file details.
LogisticHeader LogisticHeaderType The LogisticHeader describes information pertaining to ordering and
1-1
delivery, by identifying individuals and locations responsible for these
functions.
HistoryRecord HistoryRecordType The HistoryRecord element provides a sequential change number for
1-1
the IPC-2581 file. The number is changed every time the controlled version
of the IPC-2581 file is modified. Also identified are the change approval
conditions.
Bom BomType
The Bill of Materials for the board is a list of all the different components to 0-n
be used for the assembly of the board, arranged by their OEM Design
Number (ODN) and the materials used to fabricate the printed board.
Ecad EcadType
The Ecad section describes the Computer Aided Design data of the job,
1-1
including all the graphical description of the layers, component location,
panel design, etc.
Avl AvlType
The AVL element contains the list of matching manufacturer’s part numbers
0-1
(MPNs) and vendor information of a certain component parts. Approved
vendors of printed board materials may also be included.
Figure 1 IPC-258X Children Element

3.1 Rules concerning the use of XML and XML Schema
The rules required to define syntax and semantics of the 258X file format notation have been simplified by the
adoption of the W3C standards for XML Schema and XML file formats. These two standards are well
specified by the W3C. The popularity of these standards has lead to the development of many commercial
and open source software tools and libraries that conform to the W3C standards.
A 258X file begins with the notation of the revision of the generic standard and the latest revision letter
followed by the software revision of the released XML schema. i.e., tag and
ends with the tag. The content between these tags must match the .xsd definition of the 258X
schema as defined by the IPC-2581 through IPC-2588 XML. The latest software release is found at:
http://webstds.ipc.org/standards.htm#x2580.
3.1.1 File readability and uniformity
A valid 258X file must conform to the W3C Canonical XML format. The format is defined by the
http://www.w3.org/TR/xml-c14n specification. Software tools exist that will take malformed XML and
automatically generate Canonical XML.
3.1.2 File markers
An optional checksum can be appended following the tag. The checksum is an MD5 message digest
algorithm (see Internet RFC 1321: http://www.ietf.org/rfc/rfc1321.txt) that is base64 encoded. The checksum
starts with the “<” character of the <258X> tag and ending with the “>” character of the closing tag.
The checksum follows immediately after the “>” character of the closing tag.
The digest provides a 128-bit checksum of the 258X file contents. The MD5 signature must be base64
encoded (see IETF RFC 1421 for the base64 algorithm) to convert the MD5 signature to a US-ASCII, base64
string. An end of line character will indicate the end of the base64 encoded MD5 signature.
3.1.3 File extension
The file extension for a 258X file is .xml.
3.1.4 File remarks
The 258X format permits file remarks using the standard XML commenting notation. They are only to be used
to support debugging software. A parser may ignore and discard remarks when reading a 258X file. File
remarks are never to be used to represent design or manufacturing information.
3.1.5 Character set definition
The XML standard uses the Unicode character set. This character set covers the characters used in hundreds
of written languages. The XML standard allows several of the Unicode encoding formats to be used in an
XML file. IPC-2581 through IPC-2588 requires the use of the UTF-8 character encoding of the Unicode
character set. Although comments and user assigned names may be in any language of choice, all qualified
names or enumerated string names shall be in English only.
3.2 Data organization and identification rules
The 258X standards use a namespace mechanism for XML instance files that is similar to the XML
namespace mechanism that was created for managing XML meta-data namespaces. The instance file
namespace mechanism prevents collisions between the names used by the different products within a single
file. This partitioning of namespaces is necessary because any of the 258X files may contain information
describing an arbitrary collection of products. (Boards, assemblies, or panels that are products allowed in an
IPC-258X file.) For example, a file could contain descriptions for building multiple electronic assemblies that
are manufactured on separate panels. This mechanism also prepares the way for a distributed database of
258X design data in which the data can be trusted to be universally unambiguous.

– 8 – IEC PAS 61182-12:2014 © IEC 2014
3.2.1 Naming elements within a 258X File
The capability of Unique namespaces was created to allow a panel to be defined in the single 258X file that
contains multiple unique boards. Since two boards may reuse the same identifier, e.g., “U1”, “R1”, it must be
possible to separate names in the file into namespaces. The 258X namespace implementation borrows the
notation used by XML namespaces and makes the 258X standard format consistent with conventional XML
usage.
There are two types of names used to name top-level objects (element instances) in a 258X file. The first type
of name is a qualifiedName type. This type includes a prefix in the name that corresponds to a
namespace within the 258X file. The prefix and the globally unique identity of the Namespace are declared in
the Namespace element. The second type of name is a shortName type. This type is required to be unique
within the 258X file. The syntax restrictions on short names and qualified names assure that all names will be
unique as top-level names within 258X file.
3.2.2 The Use of XML elements and types
A comprehensive overview of XML Schema can be found in the W3C XML Schema Primer. This section
briefly describes the decisions that were made in the development of the 258X schema. Reviewing the Primer
is recommended prior to reading this section.
The XML Schema defines a namespace mechanism that can be used when defining element names. The
W3C also provides a set of general purpose element and attribute types, such as xsd:string, xsd:double, and
xsd:datetime. The 258X format uses these standard types, however the documentation of the 258X standard
has been defined without the use of a namespace prefix for element names within a 258X file.
Each of the schema elements has a prefix, “xsd:”, which is associated with the XML Schema namespace
through the declaration, xmlns:xsd=”http://www.w3.org/2000/08/XMLSchema”, that appears in the schema
element. The prefix xsd: is used by convention to denote the XML Schema namespace, although any prefix
can be used. The same prefix, and hence the same association, also appears on the names of built-in simple
types, e.g. xsd:string. The purpose of the association is to identify the elements and simple types as
belonging to the vocabulary of the XML Schema language rather than the vocabulary of the schema author.
In XML Schema, there is a basic difference between complex types that allow elements in their content and
may carry attributes, and simple types that cannot have element content and
...