This note is related to Universal Business Language Version 2.1. OASIS Standard. http://docs.oasis-open.org/ubl/UBL-2.1.html.
This document was last revised or approved by the UBL TC on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/ubl/.
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page at http://www.oasis-open.org/committees/ubl/ipr.php.
See Appendix A, Release Notes for more information regarding this release package.
When referencing this note the following citation format should be used:
[UBL-2.1-ASN.1] UBL 2.1 Abstract Syntax Notation 1 (ASN.1) Alternative Representation Version 1.0. 23 October 2013. OASIS Committee Note 02. http://docs.oasis-open.org/ubl/UBL-2.1-ASN.1/v1.0/cn02/UBL-2.1-ASN.1-v1.0-cn02.html.
Copyright © OASIS Open 2013. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the “OASIS IPR Policy”). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.
This document and the information contained herein is provided on an “AS IS” basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS AND ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS’ procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.
The name “OASIS” is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/policies-guidelines/trademark.php for guidance.
The OASIS Universal Business Language (UBL) defines a generic XML interchange format for business documents that can be restricted or extended to meet the requirements of particular industries. Specifically, UBL provides the following:
A suite of structured business objects and their associated semantics expressed as reusable data components and common business documents.
A library of XML schemas for reusable data components such as “Address”, “Item”, and “Payment”—the common data elements of everyday business documents.
A set of XML schemas for common business documents such as “Order”, “Despatch Advice”, and “Invoice” that are constructed from the UBL library components and can be used in generic procurement and transportation contexts.
This Committee Note provides an alternative non-normative representation of the UBL XML schemas for use in systems supporting Abstract Syntax Notation 1 (ASN.1), ISO/IEC 8825-1.
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY and OPTIONAL, when they appear in this document, are to be interpreted as described in [RFC2119].
UBL 2.1 continues the practice, adopted at the beginning of the UBL effort, of creating its normative XML specifications using W3C Schema (XSD) syntax. Alternative representations of the same content are generated directly from the XSD and are intended to implement the same document instance constraints.
Alternative representations of the same content are technically non-normative.
The UBL ASN.1 specification provides an alternative schema definition for UBL documents in accordance with ITU-T X.680-X.693 [ASN.1]. The UBL ASN.1 specification defines the same UBL documents as the UBL XSD schemas that constitute the normative definitions of valid UBL documents. The UBL ASN.1 XML specification enables ASN.1 tools to be used for UBL transfers, and in conjunction with the ASN.1 Packed Encoding Rules, it provides a specification for an efficient binary encoding of UBL messages.
The ASN.1 modules were created using a tool from OSS Nokalva that conforms to ITU-T Recommendation X.694 | ISO/IEC 8825-5 for converting XSD Schema to ASN.1.
This software-generated summary documentation file describes the contents of the ASN.1 schemas for UBL 2.1 in a human-readable format in HTML:
The following ASN.1 schemas are for the UBL 2.1 document models:
The following schemas are not addressed directly for validation of a UBL document but are referenced from the document schemas in support of their requirements:
Online and downloadable versions of this release are available from the locations specified at the top of this document.
Release of this package to the public marks the beginning of its first public review of Committee Note 02. The UBL Technical Committee actively solicits input from the user community regarding this release. See Status at the beginning of this document for procedures to be used in submitting comments to the Committee. Note that in accordance with OASIS policies regarding intellectual property, the UBL TC cannot accept input from persons outside the UBL TC (including OASIS members) unless it is submitted via the comment list.
This OASIS Committee Note is published as a zip archive in the http://docs.oasis-open.org/ubl/UBL-2.1-ASN.1/v1.0/cn02/ directory. Unzipping this archive creates a directory tree containing a master DocBook XML file (UBL-2.1-ASN.1-v1.0-cn02.xml), a generated hypertext version of this file (UBL-2.1-ASN.1-v1.0-cn02.html), a generated PDF version of this file (UBL-2.1-ASN.1-v1.0-cn02.pdf), and a number of subdirectories. The files in these subdirectories contain the various components of this release. A description of each subdirectory is given below. Note that while the UBL-2.1-ASN.1-v1.0-cn02.xml file is the “original” of this specification, it may not be viewable in all currently available web browsers.
ASN.1 UBL 2.1 schemas
DocBook documentation support files
Note that the files and directories in this package are named such that the contents of this package can be overlaid on top of the unzipped UBL 2.1 package contents without overwriting any files.
UBL is a volunteer project of the international business community. Inquiries regarding UBL may be posted to the public ubl-dev list, archives for which are located at
Subscriptions to ubl-dev can be made through the OASIS list manager at
OASIS provides an official community gathering place and information resource for UBL at
The following persons contributed to the work of the committee during the preparation of this work product.
|Oriol Bausa Peris, Individual|
|Kenneth Bengtsson, Alfa1lab|
|Peter Borresen, Document Engineering Services Limited|
|Jon Bosak, Individual|
|Kees Duvekot, RFS Holland Holding B.V.|
|G. Ken Holman, Crane Softwrights Ltd.|
|Tim McGrath, Document Engineering Services Limited|
|Andrew Schoka, Individual|
|Paul Thorpe, OSS Nokalva|
Copyright © OASIS Open 2013. All rights reserved.
|23 October 2013|