OECL Format Description

Open EDA Component
Library Format
Version 1.0
© 2013 National Instruments Corporation

Important Information
Warranty
The media on which you receive National Instruments software are warranted not to fail to execute programming instructions, due to defects in materials and workmanship, for a
period of 90 days from date of shipment, as evidenced by receipts or other documentation. National Instruments will, at its option, repair or replace software media that do not
execute programming instructions if National Instruments receives notice of such defects during the warranty period. National Instruments does not warrant that the operation of
the software shall be uninterrupted or error free.
A Return Material Authorization (RMA) number must be obtained from the factory and clearly marked on the outside of the package before any equipment will be accepted for
warranty work. National Instruments will pay the shipping costs of returning to the owner parts which are covered by warranty.
National Instruments believes that the information in this document is accurate. The document has been carefully reviewed for technical accuracy. In the event that technical or
typographical errors exist, National Instruments reserves the right to make changes to subsequent editions of this document without prior notice to holders of this edition. The
reader should consult National Instruments if errors are suspected. In no event shall National Instruments be liable for any damages arising out of or related to this document or the
information contained in it.
EXCEPT AS SPECIFIED HEREIN, NATIONAL INSTRUMENTS MAKES NO WARRANTIES, EXPRESS OR IMPLIED, AND SPECIFICALLY DISCLAIMS ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. CUSTOMER’S RIGHT TO RECOVER DAMAGES CAUSED BY FAULT OR NEGLIGENCE ON THE PART OF NATIONAL INSTRUMENTS SHALL BE LIMITED TO THE AMOUNT THERETOFORE PAID
BY THE CUSTOMER. NATIONAL INSTRUMENTS WILL NOT BE LIABLE FOR DAMAGES RESULTING FROM LOSS OF DATA, PROFITS, USE OF PRODUCTS, OR INCIDENTAL OR CONSEQUENTIAL DAMAGES, EVEN IF
ADVISED OF THE POSSIBILITY THEREOF. This limitation of the liability of National Instruments will apply regardless of the form of action, whether in contract or tort, including
negligence. Any action against National Instruments must be brought within one year after the cause of action accrues. National Instruments shall not be liable for any delay in
performance due to causes beyond its reasonable control. The warranty provided herein does not cover damages, defects, malfunctions, or service failures caused by owner’s
failure to follow the National Instruments installation, operation, or maintenance instructions; owner’s modification of the product; owner’s abuse, misuse, or negligent acts; and
power failure or surges, fire, flood, accident, actions of third parties, or other events outside reasonable control.
Copyright
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an
information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.
National Instruments respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws.
Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in
accordance with the terms of any applicable license or other legal restriction.
Trademarks
National Instruments, NI, ni.com, and LabVIEW are trademarks of National Instruments Corporation. Refer to the Terms of Use section on ni.com/legal for more information
about National Instruments trademarks.
Electronics Workbench, Multisim and Ultiboard are trademarks of National Instruments.
Parents
For patents covering National Instruments products, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your CD, or ni.com/patents.
Some portions of this product are protected under United States Patent No. 6,560,572.
WARNING REGARDING USE OF NATIONAL INSTRUMENTS PRODUCTS

(1) NATIONAL INSTRUMENTS PRODUCTS ARE NOT DESIGNED WITH COMPONENTS AND TESTING FOR A LEVEL OF RELIABILITY SUITABLE FOR USE IN
OR IN CONNECTION WITH SURGICAL IMPLANTS OR AS CRITICAL COMPONENTS IN ANY LIFE SUPPORT SYSTEMS WHOSE FAILURE TO PERFORM CAN
REASONABLY BE EXPECTED TO CAUSE SIGNIFICANT INJURY TO A HUMAN.
(2) IN ANY APPLICATION, INCLUDING THE ABOVE, RELIABILITY OF OPERATION OF THE SOFTWARE PRODUCTS CAN BE IMPAIRED BY ADVERSE
FACTORS, INCLUDING BUT NOT LIMITED TO FLUCTUATIONS IN ELECTRICAL POWER SUPPLY, COMPUTER HARDWARE MALFUNCTIONS, COMPUTER
OPERATING SYSTEM SOFTWARE FITNESS, FITNESS OF COMPILERS AND DEVELOPMENT SOFTWARE USED TO DEVELOP AN APPLICATION,
INSTALLATION ERRORS, SOFTWARE AND HARDWARE COMPATIBILITY PROBLEMS, MALFUNCTIONS OR FAILURES OF ELECTRONIC MONITORING OR
CONTROL DEVICES, TRANSIENT FAILURES OF ELECTRONIC SYSTEMS (HARDWARE AND/OR SOFTWARE), UNANTICIPATED USES OR MISUSES, OR
ERRORS ON THE PART OF THE USER OR APPLICATIONS DESIGNER (ADVERSE FACTORS SUCH AS THESE ARE HEREAFTER COLLECTIVELY TERMED
“SYSTEM FAILURES”). ANY APPLICATION WHERE A SYSTEM FAILURE WOULD CREATE A RISK OF HARM TO PROPERTY OR PERSONS (INCLUDING THE
RISK OF BODILY INJURY AND DEATH) SHOULD NOT BE RELIANT SOLELY UPON ONE FORM OF ELECTRONIC SYSTEM DUE TO THE RISK OF SYSTEM
FAILURE. TO AVOID DAMAGE, INJURY, OR DEATH, THE USER OR APPLICATION DESIGNER MUST TAKE REASONABLY PRUDENT STEPS TO PROTECT
AGAINST SYSTEM FAILURES, INCLUDING BUT NOT LIMITED TO BACK-UP OR SHUT DOWN MECHANISMS. BECAUSE EACH END-USER SYSTEM IS
CUSTOMIZED AND DIFFERS FROM NATIONAL INSTRUMENTS' TESTING PLATFORMS AND BECAUSE A USER OR APPLICATION DESIGNER MAY USE
NATIONAL INSTRUMENTS PRODUCTS IN COMBINATION WITH OTHER PRODUCTS IN A MANNER NOT EVALUATED OR CONTEMPLATED BY NATIONAL
INSTRUMENTS, THE USER OR APPLICATION DESIGNER IS ULTIMATELY RESPONSIBLE FOR VERIFYING AND VALIDATING THE SUITABILITY OF
NATIONAL INSTRUMENTS PRODUCTS WHENEVER NATIONAL INSTRUMENTS PRODUCTS ARE INCORPORATED IN A SYSTEM OR APPLICATION,
INCLUDING, WITHOUT LIMITATION, THE APPROPRIATE DESIGN, PROCESS AND SAFETY LEVEL OF SUCH SYSTEM OR APPLICATION.
Contents
Chapter 1 Introduction
About Open EDA Component Library ...................................................................................................................... 1-1
OECL Media Type, File Name Extension ................................................................................................................. 1-1
OECL namespace ........................................................................................................................................ 1-1
Notation ..................................................................................................................................................................... 1-1
Terminology .............................................................................................................................................................. 1-2
Chapter 2 Basic Datatypes

Definitions ................................................................................................................................................................. 2-1
Attribute Types .......................................................................................................................................................... 2-1
The notEmptyString attribute ...................................................................................................................... 2-2
The identifierType attribute ........................................................................................................................ 2-2
The identifierRefType attribute ................................................................................................................... 2-2
The dateTimeRefType attribute .................................................................................................................. 2-2
The positiveDecimalType attribute ............................................................................................................. 2-3
The oeclVersionNumberType attribute ....................................................................................................... 2-3
The symbolMimeType attribute .................................................................................................................. 2-3
The symbolPinShapeType attribute ............................................................................................................ 2-3
The symbolPinLengthType attribute ........................................................................................................... 2-3
The placeholderType attribute .................................................................................................................... 2-3
The modelMimeType attribute .................................................................................................................... 2-4
The modelFormatType attribute .................................................................................................................. 2-4
The connectionNameType attribute ............................................................................................................ 2-4
The prefixStringType attribute .................................................................................................................... 2-4
The pinIdType attribute ............................................................................................................................... 2-4
The symbolStyleType attribute ................................................................................................................... 2-5
The symbolStyleListType attribute ............................................................................................................. 2-5
The statusType attribute .............................................................................................................................. 2-5
The availabilityType attribute ..................................................................................................................... 2-5
The quantityAvailableType attribute........................................................................................................... 2-6
The currencyType attribute ......................................................................................................................... 2-6
The propertyKeyType attribute ................................................................................................................... 2-6
The propertyNameType attribute ................................................................................................................ 2-6
The measurementValueType attribute ........................................................................................................ 2-6
The layerType attribute ............................................................................................................................... 2-7
The markingLayerType attribute................................................................................................................. 2-7
Element Types ........................................................................................................................................................... 2-7
The Properties element ................................................................................................................................ 2-7
The BooleanProperty element ..................................................................................................................... 2-8
© 2013 National Instruments Corporation iii Open EDA Component Library Format
Contents
The CurrencyProperty element ................................................................................................................... 2-8

The DateTimeProperty element .................................................................................................................. 2-9
The DoubleProperty element ...................................................................................................................... 2-9
The IntegerProperty element ..................................................................................................................... 2-10
The MeasurementProperty element........................................................................................................... 2-10
The TextProperty element ......................................................................................................................... 2-11
The URLProperty element ........................................................................................................................ 2-12
The Localization Element ......................................................................................................................... 2-12
Chapter 3 Document Structure

Defining an OECL Document ................................................................................................................................... 3-1
Overview ..................................................................................................................................................... 3-1
The root ComponentLibrary element ........................................................................................................................ 3-1
Chapter 4 Graphic symbols for schematics

The SymbolBlueprintDictionary element .................................................................................................................. 4-1
The SymbolBlueprint element ................................................................................................................................... 4-1
The svg element......................................................................................................................................................... 4-2
SVG for EDA symbols ................................................................................................................................ 4-2
Pin graphics ................................................................................................................................................. 4-6
Placeholder text ......................................................................................................................................................... 4-8
Best practices ............................................................................................................................................................. 4-8
Example 1: resistor .................................................................................................................................................... 4-8
Example 2: operational amplifier .............................................................................................................................. 4-9
Chapter 5 Simulation Models for SPICE Simulation

The SimulationModelBlueprintDictionary Element .................................................................................................. 5-1
The SimulationModelBlueprint element ................................................................................................................... 5-1
The Instance element ................................................................................................................................................. 5-2
The Definition element .............................................................................................................................................. 5-3
Instance microsyntax ................................................................................................................................................. 5-3
The Port element ......................................................................................................................................... 5-4
The Variable element .................................................................................................................................. 5-4
Example 1 .................................................................................................................................................................. 5-4
Chapter 6 Manufacturer Packages for Mapping to Standard Packages

The ManufacturerPackageDictionary element .......................................................................................................... 6-1
The ManufacturerPackage element ........................................................................................................................... 6-1
The LandMap element ............................................................................................................................................... 6-2
Example: DIP-ABC ................................................................................................................................................... 6-2
Chapter 7 Packages for Printed Circuit Board Layout

The PackageBlueprintDictionary element ................................................................................................................. 7-1
Open EDA Component Library Format iv © 2013 National Instruments Corporation

Contents
The PackageBlueprint element .................................................................................................................................. 7-1

The Package element ................................................................................................................................................. 7-2
The SilkScreen element ............................................................................................................................................. 7-3
The AssemblyDrawing element ................................................................................................................................ 7-3
The SolderMask element ........................................................................................................................................... 7-4
The SolderPaste element ........................................................................................................................................... 7-4
The Marking element ................................................................................................................................................ 7-5
The Pin element ......................................................................................................................................................... 7-6
The Hole element ...................................................................................................................................................... 7-7
The Slot Element ....................................................................................................................................................... 7-8
Permitted elements .................................................................................................................................................... 7-9
Example: DIP-6 ......................................................................................................................................................... 7-9
Example: SOIC-8 .................................................................................................................................................... 7-11
Chapter 8 Category Information for Component Organization

The ComponentCategoryDictionary element ............................................................................................................ 8-1
Component Category Dictionary Identifiers ............................................................................................... 8-1
The Category element................................................................................................................................................ 8-2
The LocalizedName element ..................................................................................................................................... 8-2
The BlueprintRef element ......................................................................................................................................... 8-3
The CategoryDictionaryRef element ......................................................................................................................... 8-4
Example ..................................................................................................................................................................... 8-4
Chapter 9 Components for Representing Orderable Items

The ComponentBlueprintDictionary element ............................................................................................................ 9-1
The ComponentBlueprint element ............................................................................................................................. 9-2
The Connections element .......................................................................................................................................... 9-3
The Connection element ............................................................................................................................................ 9-3
The Sections element ................................................................................................................................................. 9-4
The Section element .................................................................................................................................................. 9-4
The ConnInstance element ........................................................................................................................................ 9-5
The SymbolConfigurations element .......................................................................................................................... 9-6
The SymbolConfiguration element ........................................................................................................................... 9-7
The Symbol element .................................................................................................................................................. 9-7
The PinMap element.................................................................................................................................................. 9-8
The SimulationModelConfigurations element........................................................................................................... 9-9
The SimulationModelConfiguration element .......................................................................................................... 9-10
The SimulationModel element ................................................................................................................................ 9-10
The ModelPortMap element .................................................................................................................................... 9-11
The OrderablePackageConfigurations element ....................................................................................................... 9-12
The OrderablePackageConfiguration element ......................................................................................................... 9-12
The PadMap element ............................................................................................................................................... 9-13
Example 1: resistor .................................................................................................................................................. 9-14
© 2013 National Instruments Corporation v Open EDA Component Library Format

Contents
Example 2: electrolytic capacitor ............................................................................................................................ 9-15

Example 3: electrolytic capacitor #2 ....................................................................................................................... 9-15
Example 4: quad 2-input positive NAND gates ...................................................................................................... 9-16
Chapter 10 Status Information for Component Obsolescence

The StatusDictionary element ................................................................................................................................. 10-1
The Status element .................................................................................................................................................. 10-1
The Replacement element ....................................................................................................................................... 10-2
Chapter 11 Order Information for Connections to Suppliers/Distributors

The OrderingInfoDictionary element ...................................................................................................................... 11-1
The OrderingInfo element ....................................................................................................................................... 11-1
The Price Element ................................................................................................................................................... 11-2
Example ................................................................................................................................................................... 11-3
Chapter 12 Standard Property Keys

Short Description ..................................................................................................................................................... 12-1
Example .................................................................................................................................................... 12-1
Description .............................................................................................................................................................. 12-1
Example .................................................................................................................................................... 12-1
Datasheet ................................................................................................................................................................. 12-1
Example .................................................................................................................................................... 12-1
Chapter 13 References
Open EDA Component Library Format vi © 2013 National Instruments Corporation

About Open EDA Component Library

This specification defines the features and syntax for the Open EDA Component Library (OECL).
OECL is an XML language for describing libraries for electronic design automation (EDA). Libraries include graphic
symbols, simulation models, packages, land patterns, and components for the purpose of schematic capture, simulation, and
printed circuit board layout. Components in this format can be imported into tools that support OECL.
OECL Media Type, File Name Extension

The media type (formerly known as MIME type) for OECL is “application/oecl+xml”.
OECL files have the extension “.oecl” (all lower case) on all platforms.
OECL namespace
The following is the OECL 1.0 namespace:
http://www.oecl.org/2012/oecl
Notation
This document uses special fonts and coloring to identify XML syntax.
© 2013 National Instruments Corporation 1-1 Open EDA Component Library Format
Item Examples
Element ComponentLibrary
Attribute name id, description
Attribute value ANSI, true
Schema type xsd:string, identifier
Character data, CDATA <![CDATA[.model diodeexample
+ IS=5e-6
]]>
Other <, >, =""
Terminology
This section is non-normative.
This format uses attributes to define relationships between different objects. Where these attributes are intended to be
displayed to the user, the attribute name generally has the suffix Name. Where these attributes are not intended to be
displayed to the user, the attribute generally has the suffix Id.
Open EDA Component Library Format 1-2 © 2013 National Instruments Corporation
OECL uses types defined in several standards. This specification uses the namespace prefixes in the following table to
identify these types. Types may be used without namespace prefixes in OECL documents.
Datatypes Definition Prefix
W3C XML datatypes http://www.w3.org/TR/2008/REC-xml-20081126/ xml:

(Extensible Markup Language (XML) 1.0 (Fifth
Edition))
W3C XML schema datatypes http://www.w3.org/2000/10/XMLSchema (XML xsd:

Schema Part 2)
W3C SVG datatypes http://www.w3.org/TR/2011/REC-SVG11-20110816/ None
W3C XML Linking Language http://www.w3.org/TR/xlink11 (XML Linking xlink:

datatypes Language (XLink) Version 1.1)
IPC-2581A http://webstds.ipc.org/2581 (Generic Requirements for ipc:

Printed Board Assembly Products Manufacturing
Description Data and Transfer Methodology)
OECL uses custom types defined in this specification. Custom types have no prefix.
Definitions
Property elements
One of the element types that define properties for a ComponentBlueprint. Specifically: BooleanProperty,
CurrencyProperty, DateTimeProperty, DoubleProperty, IntegerProperty, MeasurementProperty,
TextProperty, or URLProperty.
Core property attributes

Core property attributes are attributes that can be specified on all property elements. The core property attributes are key and
name. Property elements must have a key and/or name attribute.
The key attribute assigns cross-implementation meaning to the property according to the name of the key (see Standard
Property Keys). The value of the key attribute is not intended to be displayed. The key attribute type is propertyKeyType.
The name attribute is a display name for the property. The name attribute type is propertyNameType.
Attribute Types
The following section defines additional attribute basic types (SimpleTypes) for use in the OECL format.
The notEmptyString attribute

The notEmptyString type must contain at least one non-whitespace character. Whitespace characters are space, tab, line
feed, and carriage return, and are identified by the \s XML Schema regular expression multi-character escape.
The identifierType attribute

The identifierType type is a universally unique identifier for an element. Identifier types always have a paired
xsd:dateTime attribute. The combination of these two items should be universally unique. The identifierType type is
derived from notEmptyString.
Constructing identifier attributes

identifierType instances should be univerally unique, although there is no registration process. To ensure uniqueness,
identifierType instances should be written in reverse domain name notation.
The reverse domain name notation should include a company/organization name, a category for the identifier, and a unique
name for the item. Items that comply with a published standard, such as should include the standard body, a category for the
identifier, and the unique name for the item.
Recommended categories for the identifiers are:
Element Suggested category
SymbolBlueprint symb
ModelBlueprint modl
ManufacturerPackage mpkg
PackageBlueprint pkg
ComponentBlueprint comp
OrderablePackageConfiguration ordpkg
Examples of identifiers written using reverse domain name notation are:

com.domainname.symb.op-amp
com.companyname.comp.ABC123
org.ipc.pkg.BGA127P2X3-6
The identifierRefType attribute

The identifierRefType type is a reference to an identifierType attribute defined within the OECL document. The
identifierRefType type is derived from identifierType.
The dateTimeRefType attribute

The dateTimeRefType type is a reference to an xsd:dateTime attribute defined within the OECL document. The
dateTimeRefType type is derived from xsd:dateTime.
The positiveDecimalType attribute

The positiveDecimalType type defines a positive number. The positiveDecimalType type is derived from
xsd:double by setting the value of xsd:minInclusive to 0.
The oeclVersionNumberType attribute

The oeclVersionNumberType type defines the format version of the document. The oeclVersionNumberType type is
the single enumerated value 1.0.
The symbolMimeType attribute

The symbolMimeType type identifies the format of the symbol information that follows. The symbolMimeType type is the
single enumerated value image/oecl.schsymbol+xml.
The symbolPinShapeType attribute

The symbolPinShapeType type identifies the functional purpose of the pin. The symbolPinShapeType type is the set of
enumerated values in the following table.
Enumerated value Usage Example (non-normative)
passive The pin is a passive pin.
inverting The pin is an inverting pin.
clock The pin is a clock pin.
inverting-clock The pin is an inverting clock pin.
active-low The pin is an active low pin.
active-high The pin is an active high pin.
active-low-clock The pin is an active low clock pin.
nonlogic The pin is not a logical pin.
custom The shape is none of the other values. Not applicable

SVG elements describe the shape of the
pin.
The symbolPinLengthType attribute

The symbolPinLengthType type identifies the length of the pin (without inspecting the drawing elements). The
symbolPinLengthType type is one of the following: 0, 10, 20, 30, 40.
The placeholderType attribute

The placeholderType type identifies the text that is substituted when a SymbolBlueprint is associated with a
ComponentBlueprint. The placeholderType type is the set of enumerated values in the following table.
Enumerated value Usage
symbolPin The functional name of the pin.
packagePad The name of the associated pad on the package.
refDes The reference designator.
properties The displayed list of component properties.
The modelMimeType attribute

The modelMimeType type identifies the format of the simulation model information that follows. The value
modelMimeType type is the single enumerated value application/oecl.spice+xml.
The modelFormatType attribute

The modelFormatType type identifies compatible simulators for the simulation model. To determine compatible simulators,
the value must be split on spaces. The resulting tokens identify compatible simulators for the model. Keywords are case-
sensitive, and must not be specified more than once per attribute. A keyword beginning with a dash (-) explicitly identifies
incompatible simulators for the model.
Splits on spaces indicate the “split a string on spaces algorithm” defined by HTML 5 (see 2.5.7 Space-separated tokens).
Keywords are implementation defined. Ignores unknown keywords.
Simulator Identifiers
Keywords in the modelFormatType type should be globally unique, although there is no registration process. In order to
ensure uniqueness, keywords should be written in reverse domain notation. Examples of reverse domain name notation are:
com.domainname.simulator
com.companyname
The connectionNameType attribute

The connectionNameType type identifies a name for a connection. The connectionNameType type must contain 1 to 8
characters from the set: a-z, A-Z, 0-9, +, -, *, ~.
The prefixStringType attribute

The prefixStringType type identifies the class designation letter portion of a reference designator, for example, as
defined by IEC 81346. The prefixStringType is derived from notEmptyString.
The pinIdType attribute

The pinIdType type identifies the SVG element that names a symbol pin. The pinIdType is derived from
notEmptyString.
The symbolStyleType attribute

The symbolStyleType type identifies standards that a symbol satisfies. The symbolStyleType type is the set of
enumerated values in the following table.
IEEE_Std_315 Complies with IEEE Std 315.
IEC_60617 Complies with IEC 60617.
The symbolStyleListType attribute

The symbolStyleListType type identifies standards that a symbol satisfied as a space-separated list. The
symbolStyleListType type is derived from xsd:list by setting the value of xsd:itemType to symbolStyleType.
The statusType attribute

The statusType type identifies the availability of a component. The statusType type is the set of enumerated values in
the following table.
available The component is in production and available.
obsolete The component is obsolete.
unknown Status information is unknown.
other Status information is known, but not available or

obsolete.
The availabilityType attribute

The availabilityType type identifies the availability of a component blueprint from a supplier/distributor. The
availabilityType type is the set of enumerated values in the following table.
inStock The component is in stock.
notStocked The component is not stocked.
backOrder The component is on back order.
RFQ Availability requires a request for quote.
unknown Availability information is unknown.
other Availability information is known, but not inStock,

notStocked, backOrder, or RFQ.
The quantityAvailableType attribute

The quantityAvailableType type identifies the number of components in stock from a particular supplier/distributor. The
quantityAvailableType type is the union of xsd:nonNegativeInteger and the enumerated value unknown.
The currencyType attribute

The currencyType type identifies a currency using the ISO 4217 3-character currency code. The currencyType type must
contain 3 characters as defined by ISO 4217.
The following paragraph is non-normative.
OECL does not define specific three-character currency codes so that currencies can be added/removed from ISO 4217
without changing this specification. Applications should be designed to permit future addition of currency codes.
The propertyKeyType attribute

The propertyKeyType type identifies a property, where the meaning of the property is defined elsewhere. If the value is not
recognized by the application, the application should handle the element as through the name attribute was specified. The
propertyKeyType type is derived from notEmptyString.
The propertyNameType attribute

The propertyNameType type identifies a property, where the meaning of the property is defined by the attribute’s content.
The propertyNameType type is derived from notEmptyString.
The measurementValueType attribute

The measurementValueType type identifies a numeric value with optional SI unit prefix. The measurementValueType
type is derived from xsd:string by setting the value of xsd:pattern to [-+]?[0-9]*\.?[0-9]+([eE][-+]?[0-
9]+)?([YZEPTGMkhdcmuμnpfazy]|da)?.
The micro sign is the Unicode character U+00B5. In circumstances in which Unicode characters are not allowed, the micro
prefix can be represented using the letter u.
The layerType attribute

The layerType type identifies the layer for a shape. The layerType type is the set of enumerated values in the following
table.
all The shape is the same on all layers.
top The shape is for the top layer of the PCB.
inner The shape is for inner layers (not top or bottom) of the PCB.
bottom The shape is for the bottom layer of the PCB.
The markingLayerType attribute

The markingLayerType type identifies the target layer for a shape. The markingLayerType type is the set of enumerated
values in the following table.
top The shape is for the top layer of the PCB.
bottom The shape is for the bottom layer of the PCB.
Element Types
The Properties element
Properties
Contexts in which this element can be used:
As an element in the ComponentBlueprint element
Content model:
Zero or more property elements
Attributes:
None
Defines properties for ComponentBlueprint instances.
The BooleanProperty element

BooleanProperty
As an element in the Properties element
Content model:
Zero or more Localization elements
Attributes:
core property attributes

value
Defines a Boolean property.
Attribute Attribute Type Description Required
value xsd:boolean The Boolean value Yes
The CurrencyProperty element

CurrencyProperty
Content model:
Attributes:

value
currency
Defines a currency property.
value xsd:decimal The currency value Yes
currency currencyType The currency using the ISO 4217 Yes

alphabetic code (3-character)
The DateTimeProperty element

DateTimeProperty
Content model:
Attributes:

value
Defines a date-time property.
value xsd:dateTime The date-time value Yes
The DoubleProperty element

DoubleProperty
Content model:
Attributes:

value
Defines a numeric property.
value xsd:double The double value Yes
The IntegerProperty element

IntegerProperty
Content model:
Attributes:

value
Defines an integer property.
value xsd:integer The integer value Yes
The MeasurementProperty element

MeasurementProperty
Content model:
Attributes:

value
unit
Defines a measurable quantity property. Measurable quantities have values and units.
value measurementValueType The numeric value with optional SI Yes

unit prefix.
unit xsd:string The unit name or symbol. Yes
The TextProperty element

TextProperty
Content model:
Text content
Attributes:

value
xml:lang
Defines a text property. Text properties may have a value attribute or text content, but not both. The value attribute and
text content are equivalent.
xml:lang xml:language The language of the value. The initial No

value is implementation defined.
value xsd:string The text value or content. Yes
The URLProperty element

URLProperty
Content model:
Attributes:

value
Defines a URL/hyperlink property.
value xsd:string The URL value. Yes
The Localization Element

Localization
As an element in one of the property elements
Content model:
Empty or text content
Attributes:
xml:lang
name
value
Defines a translated name or value for the parent element. Sibling elements must have unique values for xml:lang. Text
content is permitted if the parent element is a TextProperty, otherwise, the content model is empty.
xml:lang Language identifier as defined by The language of the translated value. Yes
IETF BCP 47.
name notEmptyString Optional translated name for the No

property. Omit the attribute if the
name is not translated.
value xsd:string Optional translated value for the No

property. Omit the attribute if the
value is not translated or if the parent
element is a TextProperty and the
Localization element contains text
content. A translated value is only
permitted for the TextProperty and
URLProperty elements.
Chapter 3 Document Structure
Defining an OECL Document

Overview
An OECL document consists of up to 8 dictionary elements contained within a ComponentLibrary element.
An OECL document can range from an empty fragment (that is, no content inside of the ComponentLibrary element), to
individual dictionaries, to complex interdependent dictionaries.
An OECL document is a stand-alone, self-contained file or resource.
The root ComponentLibrary element

ComponentLibrary
Content model:
The following elements may appear in any order

Zero or one SymbolBlueprintDictionary
Zero or one SimulationModelBlueprintDictionary
Zero or one ManufacturerPackageDictionary
Zero or one PackageBlueprintDictionary
Zero or one ComponentCategoryDictionary
Zero or one ComponentBlueprintDictionary
Zero or one StatusDictionary
Zero or one OrderingInfoDictionary
Attributes:
version
The ComponentLibrary element represents the root of an OECL document.
Attribute Name Attribute Type Description Required
version oeclVersionNumberType Indicates the OECL language version Yes

to which this document conforms. This
attribute is fixed to the value of 1.0.
The SymbolBlueprintDictionary element

SymbolBlueprintDictionary
As an element in the ComponentLibrary element
Content model:
Zero or more SymbolBlueprint elements
Attributes:
None
Defines reusable graphic symbols for schematic capture. Each reusable graphic symbol is described by a SymbolBlueprint
element.
The SymbolBlueprint element

SymbolBlueprint
As an element in the SymbolBlueprintDictionary element
Content model:
One svg element
Attributes:
id
mimetype
description
revisionDate
Each graphic symbol is composed of two types of information: connection points (pins) for schematic capture wiring and
primitive graphic elements for drawing the symbol.
Attribute Name Attribute Type Description Required
id identifier Unique identifier for the graphic Yes

symbol.
mimetype symbolMimeType Identifies the format of the sub-element Yes

symbol information. This attribute is
fixed to the value
image/oecl.schsymbol+xml.
description xsd:string Description of the symbol graphic for No

identifying the meaning of the graphic
symbol. The initial value is a zero-
length string.
revisionDate xsd:dateTime Date of this revision. Yes
The svg element

Although the symbol is described using SVG, OECL uses a restricted sub-set of elements and attributes that is appropriate for
electronics schematics.
A graphic symbol for schematic capture contains graphical elements (for the purpose of drawing) and connection elements
(for the purpose of wiring). Connection elements are handled through extensions to the SVG format.
SVG for EDA symbols

SVG for EDA symbols consist of the following SVG 1.1 modules. For each module, the permissible attributes/elements in
each module are given following the module name. Additional restrictions that apply to coordinate values, presentation
attribute values, and the transform attribute are described in Additional restrictions.
In addition, SVG for EDA symbols defines additional attributes for the purpose of describing pins and substitution text. The
following sections define these attributes.
Structure
Core attribute module
Collection name Attributes in Collection
Core.attrib id
Structure module
Element Attributes Content Model
defs Core.attrib, transform (Structure.class | Shape.class |

View.class | Text.class)*
g Core.attrib, transform, Paint.attrib, (Structure.class | Shape.class |

OeclConn.attrib View.class | Text.class)*
svg Core.attrib, x, y, width, height, (Structure.class | Shape.class |

viewBox, version Image.class | Text.class)*
use Core.attrib, Paint.attrib, Empty

XLink.attrib, OeclConnType.attrib,
transform, x, y, width, height
Painting module
Basic paint attribute module
Paint.attrib fill, stroke, stroke-width, opacity
Property inheritance is not supported.

Basic graphics attribute module
Graphics.attrib visibility
Property inheritance is not supported.
Hyperlinking
XLink attribute module
XLink.attrib xlink:href
Shapes
Shapes module
circle Core.attrib, Paint.attrib, Animation.class

Graphics.attrib, OeclConnPoint.attrib,
cx, cy, r, transform
ellipse Core.attrib, Paint.attrib, Animation.class

Graphics.attrib, cx, cy, rx, ry,
transform
line Core.attrib, Paint.attrib, Animation.class

Graphics.attrib, x1, y1, x2, y2,
transform
path Core.attrib, Paint.attrib, Animation.class

Graphics.attrib, d, transformd
polygon Core.attrib, Paint.attrib, Animation.class

Graphics.attrib, points, transform
polyline Core.attrib, Paint.attrib, Animation.class

Graphics.attrib, points, transform
rect Core.attrib, Paint.attrib, Animation.class

Graphics.attrib, x, y, width, height,
rx, ry, transform
Text
Basic text module
text Core.attrib, Paint.attrib, #PCDATA

Graphics.attrib, Font.attrib,
TextContent.attrib, OeclLabel.attrib,
transform, x, y
x and y attributes must be a single-coordinate or not specified.
Basic text attribute set
Font.attrib font-family, font-size, font-

style, font-weight
TextContent.attrib text-anchor
font-family attribute
A single <family-name> is permitted.
Value: <family-name>
font-size attribute
Font sizes must be specified in px. The px unit is not required.
Value: <absolute-size>
font-style attribute
The following subset of values is permitted.
Value: normal | italic
Implementations should interpret other values as normal.

font-weight
The following subset of values is permitted.
Value: normal | bold
Implementations should interpret other values as normal.
Additional restrictions
SVG for EDA symbols must satisfy the below additional restrictions.
All coordinate values must be unit-less.
The inherit attribute value is not allowed for presentation attributes.
The transform attribute permits only combinations of the following transforms:

 Rotate in 90 degree increments
 Scaling
 Translation
OECL Extension Module

OECL Attribute Set
OeclConn.attrib oecl:pinId
OeclConnPoint.attrib oecl:connPoint
OeclLabel.attrib oecl:placeholder
OeclConnType.attrib oecl:pin, oecl:pinLength
Attribute Attribute Type Description
oecl:pinId pinIdType Identifier for the symbol pin. This ID is used as a reference from
a ComponentBlueprint.
oecl:connPoint xsd:boolean Identifies the location of the connection point for wiring.
Required on a circle element that defines the location of the
connection point. Not allowed in other contexts.
oecl:placeholder placeholderType Text elements with this attribute define placeholder text items
that are substituted with values from a ComponentBlueprint
when placed on a schematic.
oecl:pin symbolPinShapeType Enumerated shape of the pin. Required on use elements that
define a pin. Not allowed in other contexts.
oecl:pinLength symbolPinLengthType Enumerated length of the pin. Required on use elements that
define a pin. Not allowed in other contexts.
Pin graphics
Symbols contain pins which form the connection points to the symbol and display information about the connection point.
Pins have standard types, and these standard types are instantiated by the graphic. Functionally, instances of a pin contain:
 an identifier for the pin, for reference by component blueprints, and
 a reference to the standard pin type and default shape, and
 placeholder text elements that are substituted when the symbol is referenced by a component blueprint.
Instances of a pin are described by a g (group) with the oecl:pinId attribute element that contains the identifier for the pin.
g elements with the oecl:pinId attribute must define an instance of a pin.
g elements that define a pin instance contain three sub-elements:

 one use element that identifies the shape of the pin.
 one text element that identifies substitution text for the symbol pin name from a referencing component blueprint.
 one text element that identified substitution text for the package pad from a referencing component blueprint.
The substitution text elements may be omitted.
The use element for pin graphics

The use element with the oecl:pin attribute defines the graphic for the pin. The element references a graphic contained in
the defs section that provides a default graphic for the pin. This information is normally useful for viewing the graphic in a
standard SVG viewer.
The use element must contain the oecl:pin attribute. The oecl:pin attribute describes the functional purpose of the pin.
The x and y attributes of the use element must be located on a grid of 10 in the initial viewport coordinate system. See
Drawing pin graphics for additional information.
Implementations typically use the oecl:pin attribute to identify the functional purpose of the pin. Implementations typically
ignore the graphic objects referenced by the xlink:href attribute.
The text element for pin graphics

The text element with the oecl:placeholder element defines placeholder text elements used when a symbol blueprint is
referenced by a component blueprint. Each pin defines two placeholder text elements, one for the connection name (see the
PinMap element) and one for the package pad name (see the PadMap element).
Implementations replace the content of the text element with the appropriate name from the referencing component
blueprint. The appropriate name is determined by the oecl:placeholder attribute, and described by the following table.
symbolPin The functional name of the pin.
packagePad The name of the associated pad on the package.
Drawing pin graphics

Connection points for wiring must be drawn on a grid of 10. That is, 10 is defined as the implementation-specific minimum
Manhattan distance between pins.
Pin length must be 0, 10, 20, 30, or 40. The connection point for schematic wiring for all pins is at (0,0). For pins with a
primary line segment, the line segment ends at (0,0). The pin starts at (0,0), (10,0), (20,0), (30,0), or (40,0), depending on the
length of the pin. Enumerated values for the oecl:pinLength attribute define possible pin lengths. The length of the
referenced graphic must equal the length of the oecl:pinLength attribute.
Enumerated values for the oecl:pin attribute define possible pin types.
The passive pin graphics can have lengths of 0, 10, 20 or 40. Other pin graphics can have lengths of 10, 20, 30, or 40.
The custom oecl:pin type can be drawn either as specified by the SVG drawing objects or as the passive oecl:pin
type.
The following paragraph is non-normative
Implementations typically use the oecl:pin attribute to identify the functional purpose of the pin. Implementations typically
ignore the graphic objects referenced by the xlink:href attribute. For readability, implementations should name the
referenced id to match the standard pin type and length, separated by a dash. For example, the id of the passive pin type
with length 10 should be passive-10 and the xlink:href should be #passive-10.
Placeholder text
Symbols may contain placeholder text elements whose value is replaced with information from the referencing component
blueprint, for example the component name, or information from the schematic, for example the reference designator.
text elements with the oecl:placeholder attribute identify placeholder text, as described by the following table.
refDes The reference designator.
properties The displayed list of component properties.
Implementations may ignore text elements with the oecl:placeholder attribute.
The following paragraph is non-normative
Implementations typically ignore the text elements with the oecl:placeholder attribute. These elements are typically used
for displaying the graphic symbol with no connection to a schematic.
Best practices
This section is non-normative
Implementations typically have implementation-specific styles for drawing components for colors and font that provide a
consistent look for the application. Symbols should typically omit this style information and allow the implementation to
provide implementation-specific default styles.
Shapes should usually omit the fill and stroke attributes (except the value none) so that implementations may use their
default color information.
Text should usually omit the font attributes (Font.attrib) so that implementations may use their default font information.
Many implementations require all pins to originate from the boundary of a box enclosing the symbol contents. For best
results across multiple applications, pins should be on a bounding box enclosing the symbol.
The following graphic illustrates this concept. The pins (green), end on the boundary of the drawing objects (red). The pins
labeled VS- and VS+ have additional drawing objects to connect the pin to triangle.
Example 1: resistor
The following XML fragment defines the symbol blueprint for the IEC 60617 resistor (S00555).
<SymbolBlueprint id="com.example.symb.resistor" mimetype="image/oecl.schsymbol+xml"
description="IEC 60617 S00555 Resistor, general symbol" revisionDate="2012-07-17T21:32:52">
<svg xmlns:svg="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:oecl="http://www.oecl.org/2012/oecl"
xmlns="http://www.w3.org/2000/svg">

<defs>
<g id="passive-10">
<line x1="10" y1="0" x2="0" y2="0"/>

<circle cx="0" cy="0" r="1" oecl:connPoint="true"/>
</g>
</defs>

<g oecl:pinId="1">
<use transform="translate(-50,0)" xlink:href="#passive-10" oecl:pin="passive"
oecl:pinLength="10"/>

<text transform="translate(-50,-10)" text-anchor="end"
oecl:placeholder="symbolPin">a</text>
<text transform="translate(-50,20)" text-anchor="end"
oecl:placeholder="packagePad">1</text>
</g>
<g oecl:pinId="2">
<use transform="translate(50,0) rotate(180)" xlink:href="#passive-10"
oecl:pin="passive" oecl:pinLength="10"/>

<text transform="translate(45,-10)" oecl:placeholder="symbolPin">b</text>
<text transform="translate(45,20)" oecl:placeholder="packagePad">2</text>
</g>

<rect x="-40" y="-10" width="80" height="20" fill="none"/>
<text x="0" y="20" oecl:placeholder="refDes" text-anchor="middle">R1</text>
<text x="0" y="30" oecl:placeholder="properties" text-anchor="middle">1k</text>
</svg>
</SymbolBlueprint>
Graphically, this XML fragment draws as shown below.
Example 2: operational amplifier

<svg xmlns:svg="http://www.w3.org/2000/svg"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:oecl="http://www.oecl.org/2012/oecl"
xmlns="http://www.w3.org/2000/svg">

<defs>
<g id="passive-10">
<line x1="0" y1="0" x2="10" y2="0"/>


<circle cx="0" cy="0" r="1" oecl:connPoint="true"/>
</g>
</defs>

<g oecl:pinId="IN+">
<use transform="translate(-40,-20)" xlink:href="#passive-10" oecl:pin="passive"
<text transform="translate(-50,-30)" text-anchor="end"
oecl:placeholder="symbolPin">IN+</text>
</g>
<g oecl:pinId="IN-">
<use transform="translate(-40,20)" xlink:href="#passive-10" oecl:pin="passive"
<text transform="translate(-50,10)" text-anchor="end"
oecl:placeholder="symbolPin">IN-</text>
</g>
<g oecl:pinId="OUT">
<use transform="translate(40,0) rotate(180)" xlink:href="#passive-10"
<text transform="translate(45,-10)" oecl:placeholder="symbolPin">OUT</text>
</g>
<g oecl:pinId="VS-">
<use transform="translate(0,40) rotate(-90)" xlink:href="#passive-10"
<text transform="translate(-25,40)" oecl:placeholder="symbolPin">VS-</text>
</g>
<g oecl:pinId="VS+">
<use transform="translate(0,-40) rotate(90)" xlink:href="#passive-10"
<text transform="translate(-25,-35)" oecl:placeholder="symbolPin">VS+</text>
</g>

<path d="M -30 -30 L 30 0 L -30 30 z"/>
<line x1="0" y1="15" x2="0" y2="30"/>
<line x1="0" y1="-15" x2="0" y2="-30"/>
</svg>
Chapter 5 Simulation Models for SPICE
Simulation
The SimulationModelBlueprintDictionary Element

SimulationModelBlueprintDictionary
Content model:
Zero or more SimulationModelBlueprint elements
Attributes:
None
Defines reusable models for simulation. Each reusable simulation model is described by a SimulationModelBlueprint
element.
The SimulationModelBlueprint element

SimulationModelBlueprint
As an element in the SimulationModelBlueprintDictionary element
Content model:
One or more Instance elements followed by one or more Definition elements
Attributes:
id
name
manufacturer
author
mimetype
description
copyright
revisionDate
There are two parts to the model blueprint, (1) instance information and (2) model text, represented by the Instance and
Model elements, respectively. The instance information is used to instantiate the model (make the model specific to a
particular component), whereas the model text is common (shared) between instances of the model.
id identifierType Unique identifier for the simulation Yes

model.
name notEmptyString Descriptive name of the model. For Yes

SPICE models, this is the name of the
.subckt or .model.
manufacturer notEmptyString The name of the manufacturer for No

models that describe the behavior from
a particular manufacturer. The initial
value is a zero-length string.
author xsd:string Name of the model publisher. The No

initial value is a zero-length string.
mimetype modelMimeType Identifies the format of the sub-element Yes

model information.
description xsd::string Description information for the model. No
copyright xsd:string Model copyright information. The No

initial value is a zero-length string.
The Instance element

Instance
As an element in the SimulationModelBlueprint element
Content model:
Instance text in a CDATA section
Attributes:
simulators
Describes how to instantiate the simulation model (that is, map ports).
simulators modelFormatType Identifies compatible simulators for the No

model. The missing or empty attribute
indicates unknown information. Listed
values must be unique for all
Instance elements of the same
SimulationModelBlueprint.
The Definition element

Definition
As an element in the SimulationModelBlueprint element
Content model:
Model text or encrypted model text in a CDATA section
Attributes:
simulators
Shared information for a simulation model. The name of the SPICE .subckt or .model must match the value of the
SimulationModelBlueprint’s name attribute.
simulators modelFormatType Identifies compatible simulators for the No

model. The missing or empty attribute
indicates unknown information. Listed
values must be unique for all
Definition elements of the same
Instance microsyntax
The CDATA section for the Instance element describes how to instantiate the SPICE model.
The syntax is an XML-like markup language where all characters, including white space, is significant. The syntax does not
have a root element. The CDATA section for the Instance element may contain the following elements in any order:
 text content block
 Port element
 Variable element
The Port element

Port
As an element in the Instance CDATA section element
Content model:
One text content block. The text content block contains only the name of the terminal
Attributes:
behavior
Defines the name of a port (terminal).
behavior xsd:string Simulator-specific information that No

describes the electrical behavior of the
port. The initial value is a zero-length
string.
The Variable element

Variable
As an element in the Instance CDATA section element
Content model:
The string REFDES or the string MODEL
Attributes:
None
Identifies replacement text for the reference designator of the instantiated model or the name of the instantiated model.
Example 1
The following XML fragment defines the model blueprint for a 1 kΩ resistor.
<SimulationModelBlueprint id="BBC45068-2D72-4385-8E1C-A77D7E695F13" name="myres"
manufacturer="Generic" mimetype=" application/oecl.spice+xml" revisionDate="2012-07-
17T21:32:52">
<Instance><![CDATA[x<Variable>REFDES</Variable> <Port>T0</Port> <Port>T1</Port>
<Variable>MODEL</Variable>]]></Instance>
<Definition><![CDATA[.subckt myres 1 2
R1 1 2 1k
.ends]]></Definition>
</SimulationModelBlueprint>
Chapter 6 Manufacturer Packages for
Mapping to Standard Packages
The ManufacturerPackageDictionary element

ManufacturerPackageDictionary
Content model:
Zero or more ManufacturerPackage elements
Attributes:
None
Provides definitions of manufacturer-specific packages names/pin numbering and mapping of the package to reusable
standard packages. Each manufacturer-specific package is described by a ManufactuerPackage element.
The ManufacturerPackage element

ManufacturerPackage
As an element in the ManufacturerPackageDictionary element
Content model:
One or more LandMap elements
Attributes:
id
name
manufacturer
packageBlueprintRef
packageBlueprintdateTime
revisionDate
Defines the manufacturer-specific name for a package and mapping to the standard package.
id identifierType Unique identifier for the Yes

manufacturer's package.
name notEmptyString Manufacturer name of the package. Yes
manufacturer notEmptyString Manufacturer name. The initial value No

is a zero-length string.
packageBluepr identifierRefType Unique identifier for the associated Yes

intRef package.
packageBluepr xsd:dateTime The dateTime of the referenced No

intDateTime PackageBlueprint. If omitted,
matches the most recent
PackageBlueprint.
The LandMap element

LandMap
As an element in the ManufacturerPackage element
Content model:
Empty
Attributes:
padName
landName
Defines how pad names on the manufacturer package map to land names on the standard package.
padName notEmptyString Manufacturer name of the Yes

pad/electrical connection point.
landName notEmptyString The name of the land on the Yes

referenced package blueprint.
Example: DIP-ABC
The following XML fragment defines a manufacturer package.
<ManufacturerPackage id="com.example.mpkg.DIP-ABC" name="DIP-ABC" manufacturer="Generic
Manufacturer" packageBlueprintRef="com.example.pkg.DIP-8" revisionDate="2012-07-17T21:32:52">
<LandMap padName="A" landName="1"/>
<LandMap padName="B" landName="2"/>

</ManufacturerPackage>
Chapter 7 Packages for Printed Circuit
Board Layout
The PackageBlueprintDictionary element

PackageBlueprintDictionary
Content model:
Zero or more PackageBlueprint elements
Attributes:
None
Defines reusable packages (footprints, land-patterns) for components. Each reusable package is described by a
PackageBlueprint element. For example, surface mount land patterns generally should comply with IPC-7351 Generic
Requirements for Surface Mount Design and Land Pattern Standard.
The PackageBlueprint element

PackageBlueprint
As an element in the PackageBlueprintDictionary element
Content model:
One Package element
Attributes:
id
name
revisionDate
units
Defines a package (which includes the land pattern).
id identifierType Unique identifier for the package. Yes
name notEmptyString A unique name for the package. Yes

Typically, this name follows the IPC-
7351 series of part and land pattern
descriptions.
units ipc:unitsType An enumerated string that must be one Yes

of the following:
MILLIMETER | MICRON | INCH.
The Package element

Package
As an element in the PackageBlueprint element
Content model:
One Outline element (defined as ipc:OutlineType)

Zero or one SilkScreen element
Zero or one AssemblyDrawing element
Zero or one SolderMask element
Zero or one SolderPaste element
Zero or more Pin elements
Attributes:
name
type
pinOne
height
Defines a package (which includes the land pattern). The package elements are based on a modified version of IPC-2581A.
Elements that are identical to elements defined in IPC-2581A are not listed in this specification.
The value of the name attribute is often the same as the value of the name attribute of the parent element.
name ipc:qualifiedNameType See IPC-2581A. Yes
type ipc:PackageTypeType See IPC-2581A. Yes
pinOne xsd:string See IPC-2581A. No
height xsd:double See IPC-2581A. No
The SilkScreen element

SilkScreen
As an element in the Package element
Content model:
Zero or more Outline elements (defined as ipc:OutlineType)

Zero or more Marking elements
Attributes:
None
The SilkScreen element is based on the ipc:SilkScreenType from IPC-2581A.
The AssemblyDrawing element

AssemblyDrawing
Content model:
Zero or one Outline elements (defined as ipc:OutlineType)

Attributes:
None
The AssemblyDrawing element is based on the ipc:AssemblyDrawingType from IPC-2581A.
The SolderMask element

SolderMask
Content model:

Attributes:
None
The SolderMask element reuses the same embedded elements and attributes as defined for the SilkScreen element. If
omitted, all lands on the package have solder mask that matches the shape of the land.
The SolderPaste element

SolderPaste
Content model:

Attributes:
None
The SolderPaste element reuses the same embedded elements and attributes as defined for the SilkScreen element. If
omitted, all lands on the package have solder paste that matches the shape of the land.
The Marking element

Marking
As an element in the SilkScreen, AssemblyDrawing, SolderMask, or SolderPaste elements
Content model:
Zero or one Xform elements (defined as ipc:XformType)

One Location element (defined as ipc:LocationType)
Zero or more Feature elements (ABSTRACT type defined in IPC-2581A)
Attributes:
markingUsage
layer
The Marking element is based on the ipc:markingType from IPC-2581A with the addition of the layer attribute.
markingUsage ipc:markingUsageType See IPC-2581A. Yes
layer markingLayerType Defines the layer for the marking. The No

initial value is top.
The Pin element

Pin
Content model:
Zero or one Xform elements (defined as ipc:XformType)

One Location element (defined as ipc:LocationType)
One or three StandardShape elements (ABSTRACT type defined in IPC-2581A). See below for additional attributes
on the StandardShape element
Zero or one Hole or Slot elements
Attributes:
number
name
type
electricalType
mountType
The Pin element is based on the ipc:PinType from IPC-2581A. The Pin element defines the pad stack and contains either
one StandardShape substitution group child element or three StandardShape substitution group child elements.
For through-hole pins (type is THRU or BLIND), if the Pin element contains one StandardShape substitution group child
element, the pad is the same on all layers. If the Pin element contains three StandardShape substitution group child elements,
each StandardShape substitution group child element must contain a unique oecl:pinLayer attribute (type
oecl:layerType), and the pad shape is as specified on the layer.
For through-hole pins (type is THRU or BLIND), one Hole or Slot element is required and the element defines the shape of
the formed hole for the pin.
For surface mount pads (type is SURFACE), the Hole or Slot element is not allowed.
number ipc:qualifiedNameType See IPC-2581A. Yes
name ipc:qualifiedNameType See IPC-2581A. No
type ipc:cadPinType See IPC-2581A. Yes
electricalTyp ipc:pinElectricalType See IPC-2581A. No

e
mountType ipc:pinMountType See IPC-2581A. No
The Hole element

Hole
As an element in the Pin element
Content model:
Empty
Attributes:
name
diameter
platingStatus
plusTol
minusTol
The Hole element is based on the ipc:HoleType from IPC-2581A. The Hole element defines a circular drill hole
associated with a through-hole pin.
The x and y attributes offset the hole relative to the Pin and are typically 0.
diameter ipc:nonNegativeDoubleType See IPC-2581A. Yes
platingStatus ipc:platingStatusType See IPC-2581A. Yes
plusTol ipc:nonNegativeDoubleType See IPC-2581A. Yes
minusTol ipc:nonNegativeDoubleType See IPC-2581A. Yes
x xsd:double See IPC-2581A. Yes
y xsd:double See IPC-2581A. Yes
The Slot Element

Slot
As an element in the Pin element
Content model:
One or more ipc:Arc, ipc:Line, ipc:Outline and/or ipc:Polyline elements
Attributes:
name
platingStatus
plusTol
minusTol
The Slot element is based on the ipc:SlotType from IPC-2581A. The Slot element defines an arbitrarily shaped drill
hole associated with a through-hole pin.
The positions of the child elements are relative to the Pin.
platingStatus ipc:platingStatusType See IPC-2581A. Yes
plusTol ipc:nonNegativeDoubleType See IPC-2581A. Yes
minusTol ipc:nonNegativeDoubleType See IPC-2581A. Yes
Permitted elements
The content model of the PackageBlueprint element contains one Package element. All child elements defined by IPC-
2581A for the Package element are permitted, except the following:
LineDescRef
StandardPrimitiveRef
UserPrimitiveRef
Example: DIP-6
The following XML fragment defines a package blueprint the DIP-6 package.
<PackageBlueprint id="DIP762W46P254L876Q6B" name="DIP-6" revisionDate="2012-07-17T21:32:52"
units="MILLIMETER">
<Package name="DIP-6" type="CERAMIC_DIP">
<Outline>
<LineDesc lineEnd="ROUND" lineWidth="0.001"/>
<Polygon>
<PolyBegin x="-4.635" y="4.945"/>
<PolyStepSegment x="-4.635" y="-4.945"/>
<PolyStepSegment x="4.635" y="-4.945"/>
<PolyStepSegment x="4.635" y="4.945"/>
<PolyStepSegment x="-4.635" y="4.945"/>
</Polygon>
</Outline>
<SilkScreen>
<Outline>
<Polygon>
<PolyBegin x="-2.9" y="4.4"/>
</Polygon>
</Outline>
<Marking markingUsage="PIN_ONE">
<Location x="-1.88" y="3.4"/>
<Circle diameter="1.0"/>
</Marking>
</SilkScreen>
<AssemblyDrawing>
<Outline>
<Polygon>
<PolyBegin x="-3.21" y="4.38"/>
</Polygon>
</Outline>
<Location x="-2.2" y="3.37"/>
<Donut shape="ROUND" outerDiameter="1.0" innerDiameter="0.8"/>
</Marking>
</AssemblyDrawing>
<Pin number="1" type="THRU" electricalType="ELECTRICAL" mountType="THROUGH_HOLE_PIN">
<Location x="-3.81" y="2.54"/>
<RectCenter width="1.15" height="1.15"/>
<Hole name="1" diameter="0.5" platingStatus="PLATED" plusTol="0.005"
minusTol="0.005" x="0" y="0"/>
</Pin>
<Location x="-3.81" y="0"/>
minusTol="0.005" x="0" y="0"/>
</Pin>
<Location x="-3.81" y="-2.54"/>
minusTol="0.005" x="0" y="0"/>
</Pin>
<Location x="3.81" y="-2.54"/>
minusTol="0.005" x="0" y="0"/>
</Pin>
<Location x="3.81" y="0"/>
minusTol="0.005" x="0" y="0"/>
</Pin>
<Location x="3.81" y="2.54"/>
minusTol="0.005" x="0" y="0"/>
</Pin>
</Package>
</PackageBlueprint>
Example: SOIC-8
The following XML fragment defines a package blueprint the SOIC-8 package.
<PackageBlueprint id="SOIC127P600-8N" name="SOIC-8" revisionDate="2012-07-17T21:32:52"
units="MILLIMETER">
<Package name="SOIC-8" type="SOIC">
<Outline>
<Polygon>
<PolyBegin x="-3.75" y="2.75"/>
</Polygon>
</Outline>
<SilkScreen>
<Outline>
<Polygon>
<PolyBegin x="-1.5" y="2.45"/>
</Polygon>
</Outline>
<Location x="0" y="0"/>
<Contour>
<Polygon>
<PolyBegin x="-1.5" y="2.45"/>
</Polygon>
</Contour>
</Marking>
</SilkScreen>
<AssemblyDrawing>
<Outline>
<Polygon>
<PolyBegin x="-1.95" y="2.45"/>
</Polygon>
</Outline>
<Location x="-0.95" y="1.45"/>
<Donut shape="ROUND" outerDiameter="1.0" innerDiameter="0.8"/>

</Marking>
</AssemblyDrawing>
<Pin number="1" type="SURFACE" electricalType="ELECTRICAL"
mountType="SURFACE_MOUNT_PAD">
<Location x="-2.65" y="1.905"/>
</Pin>
<Location x="-2.65" y="0.635"/>
</Pin>
<Location x="-2.65" y="-0.635"/>
</Pin>
<Location x="-2.65" y="-1.905"/>
</Pin>
<Location x="2.65" y="-1.905"/>
</Pin>
<Location x="2.65" y="-0.635"/>
</Pin>
<Location x="2.65" y="0.635"/>
</Pin>
<Location x="2.65" y="1.905"/>
</Pin>
</Package>
</PackageBlueprint>
Chapter 8 Category Information for
Component Organization
The ComponentCategoryDictionary element

ComponentCategoryDictionary
Content model:
Zero or more Category elements
Attributes:
dictionaryId
revisionDate
Defines a hierarchical structure for components. Components may exist in multiple categories, and applications may display
the results merged. Tree nodes are described by nested Category elements that identify which components exist in the node.
Components not referenced by any Category element should appear uncategorized.
dictionaryId notEmptyString A unique identifier for the category Yes

tree.
Component Category Dictionary Identifiers

dictionaryId instances should be globally unique, although there is no registration process. In order to ensure uniqueness,
dictionaryId instances should be written in reverse domain name notation. Examples of reverse domain name notation
are:
com.domainname.analogcomponents
com.companyname
The Category element

Category
As an element in the ComponentCategoryDictionary element or as an element in the Category element
Content model:
Zero or more LocalizedName elements followed by zero or more BlueprintRef elements followed by zero or more
Category elements, followed by zero or more CategoryDictionaryRef elements
Attributes:
name
Defines an item (node) in the component category hierarchy. The name attribute provides a default name for the component
category.
name notEmptyString A name for the family using US Yes

ASCII characters, as defined by IETF
RFC 3986. Name must be unique
within the context.
Names containing characters not in the US ASCII character set can be specified by specifying a LocalizedName with an
empty xml:lang attribute.
The LocalizedName element

LocalizedName
As an element in the Category element
Content model:
Empty
Attributes:
xml:lang
name
Defines a translated name for the parent category.
xml:lang Language identifier as defined by The language for the localized name, Yes
IETF BCP 47 or an empty string.
name notEmptyString The localized name for the category. Yes

Name must be unique within the
context (sibling categories with the
same name language identifier).
The BlueprintRef element

BlueprintRef
Content model:
Empty
Attributes:
blueprintRef
blueprintDateTime
Defines a reference to a component that exists at the particular node in the category.
blueprintRef identifierRefType The unique identifier for the Yes

component.
blueprintDate xsd:dateTime The dateTime of the referenced No

Time Blueprint. If omitted, matches the
most recent Blueprint.
The CategoryDictionaryRef element

CategoryDictionaryRef
Content model:
Empty
Attributes:
dictionaryId
Defines a reference to a component that exists at the particular node in the category.
dictionaryId notEmptyString The unique identifier for the Yes

component category dictionary (see
the dictionaryId attribute of the
CategoryDictionary element).
Example
The following XML fragment defines a component category dictionary.
<ComponentCategoryDictionary dictionaryId="com.mycompany" revisionDate="2012-07-17T21:32:52">
<Category name="Generic Manufacturer">
<LocalizedName xml:lang="de" name="Generika-Hersteller"/>
<Category name="Digital">
<BlueprintRef blueprintRef="com.mycompany.comp.123"/>
</Category>
<Category name="Analog">
</Category>
<Category name="Educational">
<LocalizedName xml:lang="de" name="Bildung"/>

</Category>
<CategoryDictionaryRef dictionaryId="com.companyinc.in-dev-components"/>
</Category>
<Category name="Components Inc">
<BlueprintRef blueprintRef="com.mycompany.comp.ABC"/>
</Category>
</ComponentCategoryDictionary>
Chapter 9 Components for Representing
Orderable Items
The ComponentBlueprintDictionary element

ComponentBlueprintDictionary
Content model:
Zero or more ComponentBlueprint elements
Attributes:
None
Defines component blueprints as combinations of graphic symbols, simulation models and packages that when combined,
represent an electronic component.
The ComponentBlueprint element

ComponentBlueprint
As an element in the ComponentBlueprintDictionary element
Content model:
The following elements in any order

One Connections element
Zero or one Sections elements
One SymbolConfigurations element
Zero or one SimulationModelConfigurations elements
Zero or one OrderablePackageConfigurations elements
Zero or one Properties elements
Attributes:
id
name
revisionDate
The component blueprint is the main definition of a component. Component blueprint definitions in the component blueprint
dictionary are not self-contained. Rather, component blueprints reference the other dictionaries in this or possibly other
libraries. The primary role of the component blueprint is to tie these pieces together.
The component blueprint defines the connections on the component blueprint in the Connections and Sections sub-
elements. Additionally, the component blueprint references items in other dictionaries (symbol, model and package) through
the SymbolConfigurations, SimulationModelConfigurations and PackageConfigurations sub-elements, and
defines the mapping between connections in the component and the pins, pads, ports, etc. in the mapped item.
The simplest ComponentBlueprint contains a list of connections (the Connections element) and an associated graphic
symbol (the SymbolConfigurations element).
id identifierType Unique identifier for the component. Yes
name notEmptyString Name of the component. Yes
The Connections element

Connections
Content model:
One or more Connection elements
Attributes:
None
Defines the complete set of connections on the component. Each electrically independent connection to the component has a
unique Connection element. For example, repeated ground connections only have one Connection element if the ground
connections are internally connected. The connection list must include non-electrical connections exposed by a referenced
simulation model in order to connect to the connection from a symbol.
The Connection element

Connection
As an element in the Connection element
Content model:
Empty
Attributes:
connName
Defines the reference name for a connection on the component.
connName connectionNameType Identifier for the connection. This Yes

name is used as a reference within the
component definition.
The Sections element

Sections
Content model:
One or more Section elements
Attributes:
None
The Sections element groups connections and defines groups of connections that are functionally identical. Section order is
not important, however, implementations should display connections in the same order as they occur in the
ComponentLibrary.
Sections on the component group related pins. Sections define swappable units on a component. For example, a component
with two AND gates would have two sections, one for each gate. The Sections element may be omitted for components
with a single section.
The Section element

Section
As an element in the Sections element
Content model:
One or more ConnInstance elements
Attributes:
name
sectionSwapGroup
Defines a grouping of connections by section.
name notEmptyString The section name is the name for No

mapping with graphic symbols,
simulation models, and for display.
Typically this is A, B, C, etc, or a
functional description of the section.
The name must be unique for a
particular ComponentBlueprint.
Required for components with multiple
sections. May be omitted or empty
value for single section components.
sectionSwapGroup xsd:string Sections with the name No

sectionSwapGroup value are
functionally equivalent. An empty
sectionSwapGroup does not match
other empty sectionSwapGroup
instances.
The ConnInstance element

ConnInstance
As an element in the Section element
Content model:
Empty
Attributes:
connName
connSwapGroup
Identifies the connection as belonging to the ancestor section. Connections can belong to multiple sections (shared/common
pins).
connName connectionNameType The name of the connection from the Yes

list in the Connections element.
connSwapGroup xsd:string Connections with the same No

connSwapGroup value are
functionally equivalent within the
same section.
Identical connSwapGroup items
identify functionally identical
connections. A missing or empty
connSwapGroup only matches
identically named connections in other
sections.
If sectionSwapGroup is set for the
containing Section, for the
connections to be swappable all
ConnectionInstance elements
must have connSwapGroup specified
and common names between Section
elements, or identical connection
names.
The SymbolConfigurations element

SymbolConfigurations
Content model:
One or more SymbolConfiguration elements
Attributes:
None
Defines a set of graphical symbols for a ComponentBlueprint.
The SymbolConfiguration element

SymbolConfiguration
As an element in the SymbolConfigurations element
Content model:
One or more Symbol elements
Attributes:
style
refdesPrefix
References and maps a particular graphical symbol for the ComponentBlueprint.
style symbolStyleListType The standards this graphical Yes

representation complies with.
refdesPrefix prefixStringType The character prefix for the RefDes, Yes

for example, IEC 81346 – Structuring
principle and reference designators.
The Symbol element

Symbol
As an element in the SymbolConfiguration element
Content model:
One or more PinMap elements
Attributes:
symbolRef
symbolDateTime
sectionName
Defines a reference to the the graphical symbol for a particular section on the component blueprint, and the mapping between
connections and pins on the symbol.
symbolRef identifierRefType The unique identifier of the graphical Yes

symbol, referenced from the
SymbolBlueprintDictionary.
symbolDateTime xsd:dateTime The dateTime of the referenced No

SymbolBlueprint. If omitted,
SymbolBlueprint.
sectionName xsd:string Identifies which section this symbol No

represents.
The value is the name of the section or
missing/empty to indicate the graphic
representation of all sections.
The PinMap element

PinMap
As an element in the Symbol element
Content model:
Empty
Attributes:
connName
symbolPinId
displayName
Defines how connections on the component map to pin graphics on the symbol.
connName connectionNameType The name of the connection Yes

represented.
symbolPinId notEmptyString The ID of the pin in the Yes

SymbolBlueprint.
displayName notEmptyString The display name for the connection. No

This replaces the text on the
SymbolBlueprint. If missing/empty,
the connName attribute is used for the
display name.
Common practice shows inverted connections with lines above the characters. Overlines are drawn using the Unicode
combining overline character (U+0305). Numeric superscript and subscript are similarly drawn using the Unicode superscript
and subscript characters.
The SimulationModelConfigurations element

SimulationModelConfigurations
Content model:
Zero or more SimulationModelConfiguration elements
Attributes:
None
Defines a set of simuation models for a ComponentBlueprint.
The SimulationModelConfiguration element

SimulationModelConfiguration
As an element in the SimulationModelConfigurations element
Content model:
One or more SimulationModel elements
Attributes:
None
Defines a referemce to a particular simulation model for the component. The simulation model configuration is a complete
set of simulation models for all sections on a component.
The SimulationModel element

SimulationModel
As an element in the SimulationModelConfiguration element
Content model:
One or more ModelPortMap elements
Attributes:
modelRef
modelDateTime
sectionName
Defines the simulation model for a particular section on the component, or for all sections on the component. The distinction
is determined by the value of the sectionName attribute.
modelRef identifierRefType The unique identifier of the simulation model, Yes

referenced from the
SimulationModelBlueprintDictionary.
modelDateTime xsd:dateTime The dateTime of the referenced No

SimulationModelBlueprint. If omitted,
sectionName xsd:string Identifies which section this model represents. No

The value is the name of the section or
missing/empty to indicate the model
representation of all sections.
The ModelPortMap element

ModelPortMap
As an element in the SimulationModel element
Content model:
Empty
Attributes:
connName
portName
Defines how connections on the component map to ports on the simulation model.

represented. The connection must
belong to the section that this model
represents.
portName notEmptyString The name of the port on the referenced Yes

simulation model being represented.
The OrderablePackageConfigurations element

OrderablePackageConfigurations
Content model:
One or more OrderablePackageConfiguration elements
Attributes:
None
Defines a set of packages for a ComponentBlueprint.
The OrderablePackageConfiguration element

OrderablePackageConfiguration
As an element in the OrderablePackageConfigurations element
Content model:
Zero or more PadMap elements
Attributes:
id
partNumber
manufacturer
manufacturerPackageRef
manufacturerPackageDateTime
Defines a particular orderable package for the component blueprint. Components are often available in multiple packages
with nearly identical functionality, and the package configuration defines a particular orderable component.
id identifierType Unique identifier for the orderable Yes

package.
partNumber notEmptyString The part number to use to order the Yes

component with the particular package.
The combination of the partNumber
and manufacturer must be unique
for the component blueprint.
manufacturer notEmptyString The manufacturer for the component. Yes

The combination of the partNumber
and manufacturer must be unique
for the component blueprint.
manufacturerPackageRef identifierRefType The unique identifier of the package, Yes

referenced from the
ManufacturerPackageDictionary.
manufacturerPackageDateTime xsd:dateTime The dateTime of the referenced No

ManufacturerPackage. If omitted,
ManufacturerPackage.
The PadMap element

PadMap
As an element in the OrderablePackageConfiguration element
Content model:
Empty
Attributes:
connName
padName
Defines how connections on the component map to pads on the package.

represented. Connections can be
repeated when they map to multiple
distinct pads on the manufacturer
package.
padName notEmptyString The name of the pad on the referenced Yes

manufacturer package being
represented. Pad names must be
unique in the mapping.
Example 1: resistor
The following XML fragment defines the component blueprint for a resistor.
<ComponentBlueprint id="com.example.comp.ABC123" name="ABC123">
<Connections>
<Connection connName="1"/>
</Connections>
<Sections>
<Section>
<ConnInstance connName="1" connSwapGroup="1"/>
<ConnInstance connName="2" connSwapGroup="1"/>
</Section>
</Sections>
<SymbolConfigurations>
<SymbolConfiguration style="IEEE_Std_315 IEC_60617" refdesPrefix="R">
<Symbol symbolRef="com.example.symb.res"/>
<PinMap connName="1" symbolPinId="1" displayName="1"/>
</Symbol>
</SymbolConfiguration>
</SymbolConfigurations>
<SimulationModelConfigurations>
<SimulationModelConfiguration>
<SimulationModel modelRef="com.example.modl.res">
<ModelPortMap connName="1" portName="1"/>
</SimulationModel>
</SimulationModelConfiguration>
</SimulationModelConfigurations>
<OrderablePackageConfigurations>
<OrderablePackageConfiguration partNumber="ABC123-1" manufacturer="Components Inc"
manufacturerPackageRef="com.example.mpkg.pkg1">
<PadMap connName="1" padName="A"/>
<PadMap connName="2" padName="B"/>
</OrderablePackageConfiguration>
<OrderablePackageConfiguration partNumber="ABC123-2" manufacturer="Components Inc"
manufacturerPackageRef="com.example.mpkg.pkg2">

</OrderablePackageConfigurations>
</ComponentBlueprint>
Example 2: electrolytic capacitor

The following XML fragment defines the component blueprint for an electrolytic capacitor.
<ComponentBlueprint id="com.example.comp.CBA123" name="CBA123">
<Connections>
</Connections>
<SymbolConfiguration style="IEEE_Std_315" refdesPrefix="C">
<Symbol symbolRef="com.example.symb.cap">
</Symbol>
<SymbolConfiguration style="IEC_60617" refdesPrefix="C">
<Symbol symbolRef="com.example.symb.cap">
<PinMap connName="1" symbolPinId="A" displayName="1"/>
<PinMap connName="2" symbolPinId="B" displayName="2"/>
</Symbol>
<SimulationModel modelRef="com.example.modl.CBA123">
</SimulationModel>
<OrderablePackageConfiguration partNumber="CBA123-1" manufacturer="Components Inc"
manufacturerPackageRef="com.example.mpkg.CBA123-1">
Example 3: electrolytic capacitor #2

The following XML fragment defines the component blueprint for an electrolytic capacitor. This definition is equivalent to
Example 2.
<ComponentBlueprint id="com.example.comp.cap" name="Electrolytic Capacitor">
<Connections>
</Connections>
<Sections>
<Section name="0">
<ConnInstance connName="1" connGroup="1"/>
<ConnInstance connName="2" connGroup="2"/>
</Section>
</Sections>
<SymbolConfiguration style="IEEE_Std_315 IEC_60617" refdesPrefix="C">
<Symbol symbolRef="com.example.symb.generic-cap">
</Symbol>
<SimulationModel modelRef="com.example.modl.generic-cap">
</SimulationModel>
<OrderablePackageConfiguration partNumber="CBA123-1" manufacturer="Components Inc"
manufacturerPackageRef="com.example.mpkg.CBA123-1">
Example 4: quad 2-input positive NAND gates

The following XML fragment defines the component blueprint for the 7400N quad 2-input positive NAND gates. On the
second symbol configuration, some pins are not visible and require hidden connections.
<ComponentBlueprint id="com.example.comp.7400N" name="7400N">
<Connections>
<Connection connName="1A"/>
<Connection connName="1B"/>
<Connection connName="1Y"/>
<Connection connName="VCC"/>
<Connection connName="GND"/>
</Connections>
<Sections>
<Section name="1" sectionSwapGroup="1">
<ConnInstance connName="1A" connSwapGroup="1"/>
<ConnInstance connName="1B" connSwapGroup="1"/>
<ConnInstance connName="1Y" connSwapGroup="2"/>
<ConnInstance connName="VCC"/>
<ConnInstance connName="GND"/>
</Section>
</Section>
</Section>
</Section>
</Sections>
<SymbolConfiguration style="IEEE_Std_315 IEC_60617" refdesPrefix="U">
<Symbol symbolRef="com.example.symb.nand-quad">
<PinMap connName="1A" symbolPinId="1" displayName="A"/>
<PinMap connName="1B" symbolPinId="2" displayName="B"/>
<PinMap connName="1Y" symbolPinId="3" displayName="Y"/>
<PinMap connName="VCC" symbolPinId="13" displayName="VCC"/>
<PinMap connName="GND" symbolPinId="14" displayName="GND"/>
</Symbol>
<SymbolConfiguration style="IEEE_Std_315 IEC_60617" refdesPrefix="U">
<Symbol symbolRef="com.example.symb.nand" sectionName="1">
<PinMap connName="1A" symbolPinId="1" displayName="1A"/>
<PinMap connName="1B" symbolPinId="2" displayName="1B"/>

<PinMap connName="1Y" symbolPinId="3" displayName="1C"/>
</Symbol>
</Symbol>
</Symbol>
</Symbol>
<SimulationModel modelRef="com.example.modl.nand-quad">
<ModelPortMap connName="1A" portName="1"/>
<ModelPortMap connName="1B" portName="2"/>
<ModelPortMap connName="1Y" portName="3"/>
<ModelPortMap connName="VCC" portName="13"/>
<ModelPortMap connName="GND" portName="14"/>
</SimulationModel>
<OrderablePackageConfiguration partNumber="SN5400N" manufacturer="Comp Manuf Inc"
manufacturerPackageRef="com.example.ordpkg.SN4500N">
<PadMap connName="1A" padName="1"/>
<PadMap connName="1B" padName="2"/>
<PadMap connName="1Y" padName="3"/>
<PadMap connName="GND" padName="7"/>

<PadMap connName="VCC" padName="14"/>
<OrderablePackageConfiguration partNumber="SNJ5400W" manufacturer="Comp Manuf Inc"
manufacturerPackageRef="com.example.ordpkg.SNJ4500W">
<OrderablePackageConfiguration partNumber="FJH131" manufacturer="Part Manuf Inc"
manufacturerPackageRef="com.example.ordpkg.FJH131">

Chapter 10 Status Information for
Component Obsolescence
The StatusDictionary element

StatusDictionary
Content model:
Zero or more Status elements
Attributes:
None
Defines obsolescence (availability) information for components.
The Status element

Status
As an element in the StatusDictionary element
Content model:
Zero or more Replacement elements
Attributes:
ref
status
comment
The Status element describes the default availability/obsolescence of a ComponentBlueprint or a specific

availability/obsolescence of particular PackageConfiguration. Additionally, the Status may define replacement
ComponentBlueprint/PackageConfiguration items. The Status element references the
ComponentBlueprint/OrderablePackageConfiguration by ID.
ComponentBlueprint and OrderablePackageConfiguration instances without status information are defined to be

available without restriction.
Chapter 10 Status Information for Component Obsolescence
ref identifierRefType Reference to the unique identifier for Yes

the ComponentBlueprint or
PackageConfiguration.
status statusType Defines the default status for all part Yes
numbers in the component blueprint.
comment xsd:string Implementations may use this field to No

indicate the source of the status
information.
Defines status information for a particular part number from a manufacturer. This element describes the manufacturer's
definition of status/availability, as opposed to the availability from a particular supplier/distributor.
The Replacement element

Replacement
As an element in the Status element
Content model:
Empty
Attributes:
ref
Defines a replacement for an obsolete part.
ref identifierRefType Reference to the unique identifier for Yes

the ComponentBlueprint or
PackageConfiguration of the
replacement.
Chapter 11 Order Information for
Connections to Suppliers/Distributors
The OrderingInfoDictionary element

OrderingInfoDictionary
Content model:
Zero or more OrderingInfo elements
Attributes:
None
Defines information about orderable components, for example from 3rd party distributors. This information can be included in
the OECL, but often exists in 3rd party repositories. The order information is linked to the orderable component by a unique
identifier.
The OrderingInfo element

OrderingInfo
As an element in the OrderingInfoDictionary element
Content model:
Zero or more Price elements
Attributes:
supplierSku
supplierName
supplierUrl
availability
quantityAvailable
orderablePackageRef
Defines purchase information about a particular component. The OrderInfo element is associated with the particular
component through the orderablePackageRef attribute, allowing for multiple OrderInfo elements for the same
component.
supplierSku xsd:string The supplier's SKU for the component. Yes
supplierName xsd:string The name of the supplier Yes
supplierUrl xsd:anyURL Supplier specific URL for the No

component.
availability availabilityType Availability of the component from the No

supplier. Omitted attribute is equivalent
to unknown
quantityAvailable quantityAvailableType The quantity that the supplier has No

available. Omitted attribute is
equivalent to unknown.
orderablePackageRef identifierRefType Reference to the unique identifier for Yes

the
OrderablePackageConfiguration.
The Price Element

Price
As an element in the OrderingInfo element
Content model:
Empty
Attributes:
minimumQuantity
price
currency
Defines pricing for ordering. Prices are grouped into ranges.
minimumQuantity positiveDecimalType The minimum number of items for Yes

this unit price.
unitPrice xsd:decimal The price per unit. Yes
currency currencyType The currency using the ISO 4217 Yes

alphabetic code (three-character),
Example
The following example defines ordering information from two separate suppliers/distributors or the same component
(manufacturer part number).
<OrderingInfo supplierSku="ABC-123" supplierName="Part Distributor Inc"
supplierUrl="http://www.example.com/ABC-123" availability="inStock" quantityAvailable="1000"
orderablePackageRef="com.example.ordpkg.ABC-123">
<Price minimumQuantity="1" unitPrice="2.00" currency="USD"/>
</OrderingInfo>
<OrderingInfo supplierSku="123-456-789" supplierName="Local Parts Inc"
supplierUrl="http://www.example.org/123-456-789" availability="unknown"
quantityAvailable="unknown" orderablePackageRef="org.example.ordpkg.123-456-789">
</OrderingInfo>
Chapter 12 Standard Property Keys
The OECL Format allows extensions by defining standard property keys. Standard property keys allow applications to assign
meaning to the property and perform application-specific processing on the property.
Consumers of OECL documents should use these standard property keys when processing the document.
Short Description
property element type TextProperty
key short_description
Short description of a ComponentBlueprint with 160 or fewer characters.
Example
<TextProperty key="short_description" name="Description" value="The value describes the
component blueprint in fewer than 160 characters."/>
Description
property element type TextProperty
key description
Description of a ComponentBlueprint.
Example
<TextProperty key="description" name="Description" value="The value describes the component
blueprint. The description text could be very long."/>
Datasheet
property element type URLProperty
key datasheet
Link to the datasheet for the ComponentBlueprint. The link is directly to the datasheet, not a landing page with further
links.
Example
<URLProperty key="datasheet" name="Datasheet" value="http://www.example.com/datasheet.pdf"/>
Chapter 13 References
IEEE Std 315
IEEE. Graphical Symbols for Electrical and Electronics Diagrams (Including Reference Designation Letters). 1975.
IETF BCP 47
IETF (Internet Engineering Task Force). BCP 47, consisting of RFC 4646: Tags for Identifying Languages, and
RFC 4647: Matching of Language Tags, A. Phillips, M. Davis. 2006. (See http://tools.ietf.org/html/bcp47.)
IETF RFC 3986
IETF (Internet Engineering Task Force). RFC 3986: Uniform Resource Identifier (URI): Generic Syntax. Berners-
Lee, T., Fielding, R., and Masinter, L, editors. Internet Engineering Task Force. 2005. (See
http://www.ietf.org/rfc/rfc3986.txt.)
IPC-2581A
IPC. Generic Requirements for Printed Board Assembly Products Manufacturing Description Date and Transfer
Methodology. 2012. (See http://www.ipc-2581.com for the latest version.)
IPC-7351
IPC. IPC-7351 Generic Requirements for Surface Mount Design and Land Pattern Standard. 2005. (See
http://www.ipc.org/TOC/IPC-7351.pdf.)
ISO 4217
ISO (International Organization for Standardization). ISO 4217:2008. Codes for the representation of currencies
and funds, as, from time to time, amended, replaced by a new edition or expanded by the addition of new parts.
[Geneva]: International Organization for Standardization. (See http://www.iso.org for the latest version.)
IEC 60617
IEC (International Electrotechnical Comission). IEC 60617 – Graphical Symbols for Diagrams.
IEC 81346
ISO (International Organization for Standardization). IEC 81346-1:2009. Industrial systems, installations and
equipment and industrial products - Structuring principles and reference designations – Part 1: Basic rules. (See
http://www.iso.org for the latest version.)
HTML5
W3C (World Wide Web Consortium). HTML5 A vocabulary and associated APIs for HTML and XHTML. W3C
Working Draft 25 October 2012. (See http://www.w3.org/TR/2012/WD-html5-20121025/)
SVG
W3C (World Wide Web Consortium). Scalable Vector Grapics (SVG) 1.1 (Second Edition). W3C Recommendation
16 August 2011. (See http://www.w3.org/TR/2011/REC-SVG11-20110816/)

OECL Format Description

Uploaded by

Copyright:

Available Formats

OECL Format Description

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OECL Format Description

Uploaded by

Copyright:

Available Formats

Open EDA Component

© 2013 National Instruments Corporation

WARNING REGARDING USE OF NATIONAL INSTRUMENTS PRODUCTS

Chapter 2 Basic Datatypes

The CurrencyProperty element ................................................................................................................... 2-8

Chapter 3 Document Structure

Chapter 4 Graphic symbols for schematics

Chapter 5 Simulation Models for SPICE Simulation

Chapter 6 Manufacturer Packages for Mapping to Standard Packages

Chapter 7 Packages for Printed Circuit Board Layout

Open EDA Component Library Format iv © 2013 National Instruments Corporation

The PackageBlueprint element .................................................................................................................................. 7-1

Chapter 8 Category Information for Component Organization

Chapter 9 Components for Representing Orderable Items

© 2013 National Instruments Corporation v Open EDA Component Library Format

Example 2: electrolytic capacitor ............................................................................................................................ 9-15

Chapter 10 Status Information for Component Obsolescence

Chapter 11 Order Information for Connections to Suppliers/Distributors

Chapter 12 Standard Property Keys

Open EDA Component Library Format vi © 2013 National Instruments Corporation

About Open EDA Component Library

OECL Media Type, File Name Extension

Attribute name id, description

Attribute value ANSI, true

Schema type xsd:string, identifier

Character data, CDATA <![CDATA[.model diodeexample

Other <, >, =""

Datatypes Definition Prefix

W3C XML datatypes http://www.w3.org/TR/2008/REC-xml-20081126/ xml:

W3C XML schema datatypes http://www.w3.org/2000/10/XMLSchema (XML xsd:

W3C SVG datatypes http://www.w3.org/TR/2011/REC-SVG11-20110816/ None

W3C XML Linking Language http://www.w3.org/TR/xlink11 (XML Linking xlink:

IPC-2581A http://webstds.ipc.org/2581 (Generic Requirements for ipc:

Core property attributes

The notEmptyString attribute

The identifierType attribute

Constructing identifier attributes

Recommended categories for the identifiers are:

Element Suggested category

Examples of identifiers written using reverse domain name notation are:

The identifierRefType attribute

The dateTimeRefType attribute

The positiveDecimalType attribute

The oeclVersionNumberType attribute

The symbolMimeType attribute

The symbolPinShapeType attribute

Enumerated value Usage Example (non-normative)

passive The pin is a passive pin.

inverting The pin is an inverting pin.

clock The pin is a clock pin.

inverting-clock The pin is an inverting clock pin.

active-low The pin is an active low pin.

active-high The pin is an active high pin.

active-low-clock The pin is an active low clock pin.

nonlogic The pin is not a logical pin.

custom The shape is none of the other values. Not applicable

The symbolPinLengthType attribute

The placeholderType attribute

Enumerated value Usage

symbolPin The functional name of the pin.