Diff for UBL FAQ
Tue, 2014-05-20 20:47 by gkholman | Tue, 2014-05-20 20:50 by gkholman | ||
---|---|---|---|
< previous diff | next diff > | ||
Changes to Body | |||
Line 1 | Line 1 | ||
- | <p>
| ||
- | <!--[if gte mso 9]><xml>
| ||
- | <w:WordDocument>
| ||
- | <w:View>Normal</w:View>
| ||
- | <w:Zoom>0</w:Zoom>
| ||
- | <w:PunctuationKerning/>
| ||
- | <w:ValidateAgainstSchemas/>
| ||
- | <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
| ||
- | <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
| ||
- | <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
| ||
- | <w:Compatibility>
| ||
- | <w:BreakWrappedTables/>
| ||
- | <w:SnapToGridInCell/>
| ||
- | <w:WrapTextWithPunct/>
| ||
- | <w:UseAsianBreakRules/>
| ||
- | <w:DontGrowAutofit/>
| ||
- | </w:Compatibility>
| ||
- | <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
| ||
- | </w:WordDocument>
| ||
- | </xml><![endif]--><span>1. What is UBL?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>2.</span><span><span> </span></span><span>Where did UBL come from?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>3.</span><span><span> </span></span><span>Where does UBL stand at this point?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>4.</span><span><span> </span></span><span>How can I get the UBL 2.1 package, and what's in it?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>5.</span><span><span> </span></span><span>Where can I discuss UBL with other users?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>6.</span><span><span> </span></span><span>Who owns UBL?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>7.</span><span><span> </span></span><span>How much will it cost to use UBL</span><span>?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>8.</span><span><span> </span></span><span>Can UBL be customized to meet specific business
| ||
- | requirements</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>9.</span><span><span> </span></span><span>Has UBL been successful in real-world implementations</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>10.</span><span><span> </span></span><span>Can I use UBL in other contexts?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>11.</span><span><span> </span></span><span>Is the UBL effort still open to participation?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>12.</span><span><span> </span></span><span>How does UBL facilitate international trade?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>13.</span><span><span> </span></span><span>Can I use UBL in a Single Window environment?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>14.</span><span><span> </span></span><span>Is UBL a ‘real’ global standard for electronic
| ||
- | business?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>15.</span><span><span> </span></span><span>What is the relationship of UBL to ebXML?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>16.</span><span><span> </span></span><span>What is the relationship of UBL to ebXML Core
| ||
- | Components?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>17.</span><span><span> </span></span><span>What is the relationship of UBL to UN/CEFACT?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc2">
| ||
- | <span>18.</span><span><span> </span></span><span>How does UBL support the European electronic invoicing
| ||
- | Directive?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc3">
| ||
- | <span>18.1.</span><span><span> </span></span><span>Will UBL be the standard European invoice format?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc3">
| ||
- | <span>18.2.</span><span><span> </span></span><span>Isn’t this yet another standard?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc3">
| ||
- | <span>18.3.</span><span><span> </span></span><span>What will a standard European electronic invoice look
| ||
- | like?</span>
| ||
- | </p>
| ||
- | <p class="MsoToc3">
| ||
- | <span>18.4.</span><span><span> </span></span><span>Should I delay my electronic invoicing programme until
| ||
- | we see what the European semantic standard is?</span>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- |
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136260" title="_Toc262136260"></a><span><span>1.<span style="font: 7pt 'Times New Roman'"> </span></span></span>What
| ||
- | is UBL?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | UBL, the Universal Business Language, is the product of an
| ||
- | international effort to define a royalty-free library of standard electronic
| ||
- | XML business documents such as purchase orders and invoices. Developed in an
| ||
- | open and accountable OASIS Technical Committee with participation from a
| ||
- | variety of industry data standards organizations, UBL is designed to plug
| ||
- | directly into existing business, legal, auditing, and records management
| ||
- | practices, eliminating the re-keying of data in existing fax- and paper-based
| ||
- | supply chains and providing an entry point into electronic business for small
| ||
- | and medium-sized businesses.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136261" title="_Toc262136261"></a><span><span>2.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Where
| ||
- | did UBL come from?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | The UBL initiative originated in efforts beginning in
| ||
- | mid-1999 to create a set of standard XML "office documents" within
| ||
- | OASIS. The work of the OASIS OfficeDoc TC under the leadership of Murray
| ||
- | Altheim of Sun Microsystems was set aside when OASIS and UN/CEFACT began
| ||
- | collaboration on ebXML in December 1999. Interest in the creation of a standard
| ||
- | XML syntax for basic commercial documents revived again in May 2000 with the
| ||
- | decision in ebXML to omit a standard XML "payload" syntax from the
| ||
- | initial set of ebXML deliverables. The working group that came to be known as
| ||
- | UBL began in April 2001 as a discussion group sponsored by CommerceNet and was
| ||
- | established as an OASIS Technical Committee in November 2001.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136262" title="_Toc262136262"></a><span><span>3.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Where
| ||
- | does UBL stand at this point?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | UBL 1.0 was released as an OASIS Standard on 8 November 2004
| ||
- | following three years of open development and public review. UBL 2.0, which
| ||
- | expanded the scope of UBL to include the commercial collaborations of
| ||
- | international trade, was approved in November 2006.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The current version, UBL 2.1, extends the functionality of
| ||
- | UBL 2.0 to include support for collaborative planning, forecasting, and
| ||
- | replenishment; vendor managed inventory; utility billing; tendering; and
| ||
- | intermodal freight management, was approved as an OASIS Standard in November
| ||
- | 2013.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | UBL 2.1 is fully backward compatible with UBL 2.0. It is the
| ||
- | intention of the UBL Technical Committee to stabilize on the UBL 2 for the
| ||
- | foreseeable future so that subsequent releases of UBL will not affect the
| ||
- | validity of any UBL 2.0 (and later) documents.<span>
| ||
- | </span>This means future releases will focus on further extensions to the
| ||
- | functionality and will not require changes to existing UBL implementations.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136263" title="_Toc262136263"></a><span><span>4.<span style="font: 7pt 'Times New Roman'"> </span></span></span>How
| ||
- | can I get the UBL 2.1 package, and what's in it?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | UBL 2.1 can be downloaded as a single zip archive from
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | <a href="http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.zip">http://docs.oasis-open.org/ubl/os-UBL-2.1/UBL-2.1.zip</a>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The UBL 2.1 release package contains an overview of identified
| ||
- | Business Processes:
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpFirst">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Tendering
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Catalogue
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Quotation
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Ordering
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Fulfilment
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Billing
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Freight Billing
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Utility Billing
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Payment Notification
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Report State of Accounts
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Collaborative Planning, Forecasting, and
| ||
- | Replenishment
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Vendor Managed Inventory
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>International Freight Management
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Freight Status Reporting
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Certification of Origin of Goods
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpLast">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Intermodal Freight Management
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | And XML Schemas for the documents used in these processes:
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpFirst">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Application Response
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Attached Document
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Awarded Notification
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Bill of Lading
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Call for Tenders
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Catalogue
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Catalogue Deletion
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Catalogue Item Specification Update
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Catalogue Pricing Update
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Catalogue Request
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Certificate of Origin
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Contract Award Notice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Contract Notice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Credit Note
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Debit Note
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Despatch Advice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Document Status
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Document Status Request
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Exception Criteria
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Exception Notification
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Forecast
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Forecast Revision
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Forwarding Instructions
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Freight Invoice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Fulfilment Cancellation
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Goods Item Itinerary
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Guarantee Certificate
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Instruction for Returns
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Inventory Report
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Invoice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Item Information Request
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Order
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Order Cancellation
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Order Change
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Order Response
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Order Response Simple
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Packing List
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Prior Information Notice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Product Activity
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Quotation
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Receipt Advice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Reminder
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Remittance Advice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Request for Quotation
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Retail Event
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Self Billed Credit Note
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Self Billed Invoice
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Statement
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Stock Availability Report
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Tender
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Tender Receipt
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Tenderer Qualification
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Tenderer Qualification Response
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Trade Item Location Profile
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Transport Execution Plan
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Transport Execution Plan Request
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Transport Progress Status
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Transport Progress Status Request
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Transport Service Description
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Transport Service Description Request
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Transportation Status
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Transportation Status Request
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Unawarded Notification
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Utility Statement
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpLast">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Waybill
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136264" title="_Toc262136264"></a><span><span>5.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Where
| ||
- | can I discuss UBL with other users?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | For questions regarding UBL a publicly subscribable OASIS
| ||
- | ubl-dev list provides a free forum for questions regarding UBL. The ubl-dev
| ||
- | archive is located at:
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | <a href="http://lists.oasis-open.org/archives/ubl-dev/">http://lists.oasis-open.org/archives/ubl-dev/</a>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Subscriptions to ubl-dev can be made through the OASIS list
| ||
- | manager at:
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | <a href="http://www.oasis-open.org/mlmanage/index.php">http://www.oasis-open.org/mlmanage/index.php</a>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | For more general discussions and exchanges of ideas there is
| ||
- | a web site and wiki for the UBL user community at <a href="/">ubl.xml.org</a>.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136265" title="_Toc262136265"></a><span><span>6.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Who
| ||
- | owns UBL?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | UBL is owned by OASIS, a nonprofit organization dedicated to
| ||
- | the open development of public XML standards. UBL is maintained by an OASIS
| ||
- | Technical Committee made up of XML and business experts.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136266" title="_Toc262136266"></a><span><span>7.<span style="font: 7pt 'Times New Roman'"> </span></span></span>How
| ||
- | much will it cost to use UBL?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | The simple answer is that UBL is royalty-free. It can be
| ||
- | used without charge by anyone.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | More precisely, the UBL TC operates in the OASIS
| ||
- | Intellectual Property Rights (IPR) mode known as "Royalty Free on Limited
| ||
- | Terms," which "requires all Obligated Parties to license their
| ||
- | Essential Claims using the RF licensing elements described in Sections 10.2.1
| ||
- | and 10.2.3" of the OASIS IPR Policy, a copy of which can be found at:
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | <a href="http://www.oasis-open.org/who/intellectualproperty.php">http://www.oasis-open.org/who/intellectualproperty.php</a>
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136267" title="_Toc262136267"></a><span><span>8.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Can
| ||
- | UBL be customized to meet specific business requirements?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | In many small-business environments, standard forms can
| ||
- | satisfy business requirements well enough to be used without modification. The
| ||
- | existence of standard paper forms such as the UN Layout Key proves this. In
| ||
- | these environments, UBL can work right out of the box.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Customization is an activity undertaken by implementers of
| ||
- | UBL to apply additional business rules and information requirements to
| ||
- | documents conforming to the standard UBL schema. UBL does not attempt a
| ||
- | complete solution to this problem but instead takes an extremely pragmatic
| ||
- | approach that should allow satisfactory solutions in the great majority of
| ||
- | real-world cases.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | For example, each UBL schema contains an optional extension
| ||
- | area in which trading partners may, by agreement, include any data not already
| ||
- | covered by the very extensive predefined UBL data structure. Maintaining this
| ||
- | extension area and coordinating its use is, of course, the responsibility of
| ||
- | the trading partners. But this simple strategy allows nearly unlimited
| ||
- | flexibility in individual trading relationships without requiring modification
| ||
- | of the standard UBL schemas.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Implementers of UBL typically use customization techniques
| ||
- | to apply extensions, restrictions and other business rules to their documents.
| ||
- | To assist in developing these, the UBL Guidelines for Customization are
| ||
- | available at:
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | <a href="http://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf">http://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf</a>
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136268" title="_Toc262136268"></a><span><span>9.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Has
| ||
- | UBL been successful in real-world implementations?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | Since UBL is publicly available and royalty-free, it is
| ||
- | impossible to track implementations with any accuracy.<span> </span>However, over the past 10 years a number of
| ||
- | UBL user communities have made themselves known to the UBL Technical
| ||
- | Committee.<span> </span>Some of these are listed
| ||
- | below.<span> </span>Many of these stakeholder
| ||
- | communities have also contributed to the ongoing development of UBL.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | From this we can confidently state that UBL has seen
| ||
- | significant large-scale, real-world adoption in public procurement programmes<span>, initially in Europe and now in other
| ||
- | regions across the public and private sector.<span>
| ||
- | </span></span><span> </span>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The first example of this was from Denmark.<span> </span>Since February 2005, use of the UBL Invoice
| ||
- | standard has been mandated by law for all public-sector business in Denmark. Several
| ||
- | million UBL invoices are currently exchanged in Denmark every month. The Danish
| ||
- | Ministry of Finance estimates savings to the government of 100 million euros
| ||
- | annually from use of this one document type. The introduction of their
| ||
- | wider-ranging <a href="http://www.oioubl.info/classes/en/index.html">OIOUBL
| ||
- | initiative</a> in 2010 affected almost all 440,000 businesses in Denmark and
| ||
- | established Denmark as a world leader in electronic invoicing best practice.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | In 2008, the PEPPOL (Pan European eProcurement Online)
| ||
- | initiative scaled UBL adoption across 11 countries: Austria, Denmark, Finland,
| ||
- | France, Germany, Greece, Italy, Norway, Portugal, Sweden, and the United
| ||
- | Kingdom. <span> </span><span>In March 2014 the OpenPEPPOL association, set up to ensure long term
| ||
- | sustainability of PEPPOL had one hundred member organisations from the public
| ||
- | and private sector, from 18 European countries, including Russia and USA.<span> </span>In April 2014, the UK National Health
| ||
- | Service, the world's largest publicly funded health service and the world’s 5th
| ||
- | largest employer, announced that PEPPOL standards (including UBL) would be the
| ||
- | basis of its new eProcurement strategy.</span>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Government adoption in this way has a stimulating effect on
| ||
- | adoption in other communities because government procurement touches on both
| ||
- | commercial and policy issues.<span> </span>In most
| ||
- | economies it is the largest procurement activity.<span> </span>This means standards introduced for public
| ||
- | procurement have traction that encourages adoption by other parts of the
| ||
- | economy.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The current implementations of UBL known to the UBL
| ||
- | Technical Committee are listed below…
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Public Procurement initiatives:
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpFirst">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.peppol.eu/">PEPPOL</a>
| ||
- | (Pan-European)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.oioubl.info/classes/da/index.html">OIOUBL</a> (Denmark)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.difi.no/artikkel/2012/11/papirfakturaens-tid-er-forbi">EHF</a>
| ||
- | (Norway)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.sfti.se/specifikationer/svefaktura">Svefaktura</a> (Sweden)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.icepro.is/Pages/NewsInfo.aspx?id=83">E-Invoicing</a> (Iceland)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://ec.europa.eu/dgs/informatics/supplier_portal/index_en.htm">ePrior</a>
| ||
- | (European Commission)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.efatura.gov.tr/anasayfa.html"><span>E-Fatura</span></a><span> (Turkey)</span>
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://orientacion.sunat.gob.pe/index.php?option=com_content&view=article&id=849&Itemid=155"><span>Factura Electronica</span></a><span> (Peru)</span>
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.e-invoice-gateway.net/knowledgebase/countryrelated/compare?country1=332&country2=332"><span>E-Invoicing</span></a><span> (Croatia)</span>
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpLast">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="https://www.gov.uk/government/publications/nhs-e-procurement-strategy"><span>National Health Service</span></a><span> (UK)</span>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Trading Communities:
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraph">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Textile, Clothing and Footwear (<a href="http://ebiz-tcf.eu/">eBiz-TCF</a>)
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Service Providers:
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpFirst">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>eInvoicing (<a href="http://tradeshift.com/">Tradeshift</a>,
| ||
- | <a href="http://www.fundtech.com/products/cash-management/accountis-eipp/?redirect_source=accountis.com">Accountis</a>,
| ||
- | <a href="https://www.b2brouter.net/">B2BRouter</a>, <a href="http://www.simplerinvoicing.org/"><span>SimplerInvoicing</span></a><span>) </span>
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Logistics Services (<a href="http://www.freightgate.com/">Freightgate</a>, <a href="http://www.electra.se/">Electra</a>)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>ePurchasing (<a href="http://www.ozedi.com.au/">Ozedi</a>)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Online Retailing (<a href="http://www.wehkamp.nl/">Wehkamp</a>)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpLast">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Interoperability Services (<a href="http://www.eespa.eu/content/interoperability">European eInvoice Service
| ||
- | Providers Association</a>)
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Freight Logistics and Transport initiatives:
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpFirst">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.efreightproject.eu/">eFreight</a>
| ||
- | (European Commission, DG MOVE)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.hk-dttn.com/home/english/home.html">DTTN</a> (Port of Hong
| ||
- | Kong)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="https://www.certoforigin.com/tnlcoo/pfk/PfkMainServlet?pContents=/coo/CooWalkinUrl.jsp&pPortalId=COO">CertOfOrigin</a>
| ||
- | (CrimsonLogic, Singapore)
| ||
- | </p>
| ||
- | <p style="margin-left: 57.25pt; text-indent: -0.25in" class="ListParagraphCxSpLast">
| ||
- | <span style="font-family: 'Courier New'"><span>o<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span><a href="http://www.its.dot.gov/efm/">Electronic
| ||
- | Freight Management</a> (US Dept of Transport)
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136269" title="_Toc262136269"></a><span><span>10.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Can I use
| ||
- | UBL in other contexts?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | Yes. Many communities have successfully built their own XML
| ||
- | schema using UBL as a starting point. Some of these have subsequently been
| ||
- | submitted to the UBL Technical Committee as candidates for inclusion in the
| ||
- | official UBL standard.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Others have used the UBL’s Naming and Design Rules to create
| ||
- | completely new messages in domains such as healthcare, education and customs.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136270" title="_Toc262136270"></a><span><span>11.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Is the UBL
| ||
- | effort still open to participation?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | Yes! Anyone interested in the further development of UBL
| ||
- | should join OASIS and sign up for the UBL TC. OASIS memberships are available
| ||
- | at the following URL:
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | <a href="http://www.oasis-open.org/join/">http://www.oasis-open.org/join/</a>
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136271" title="_Toc262136271"></a><span><span>12.<span style="font: 7pt 'Times New Roman'"> </span></span></span>How does
| ||
- | UBL facilitate international trade?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | <span>One of the challenges
| ||
- | with </span>international trade in the digital era<span> is trust. When businesses seek to develop or
| ||
- | improve their international supply chains their primary consideration is trust
| ||
- | in the complete trade system. Trust in the security, reliability and
| ||
- | authenticity of the processes and partners they are dealing with.<span> </span>Fundamental to establishing this trust are
| ||
- | standards.<span> </span>Using standards creates
| ||
- | certainty… and certainty enables trust.</span>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | UBL's contribution to ensuring trust in international trade
| ||
- | lies in the definition of a standard set of XML documents that provide the
| ||
- | world with standards for the electronic versions of traditional business
| ||
- | documents designed in a way that recognizes established commercial and legal
| ||
- | practices.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Exchanging standard UBL documents ensures that the
| ||
- | structures and semantics of the information being exchanged is consistent and
| ||
- | interoperable with trading partners.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><span><span>13.<span style="font: 7pt 'Times New Roman'"> </span></span></span><span> </span><a name="_Toc262136272" title="_Toc262136272"></a>Can I use UBL in a
| ||
- | Single Window environment?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | The regulatory Single Window concept has been implemented in
| ||
- | many developing countries around the world as a major platform for
| ||
- | collaboration and information exchange among different government agencies
| ||
- | involved in international trade. Recognized as effective trade facilitation
| ||
- | measures in the recent Bali Ministerial Declaration and WTO Trade Facilitation
| ||
- | Agreement, regulatory Single Window systems are increasingly being adopted by
| ||
- | developed and developing countries.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | However, international trade transactions require a number
| ||
- | of different business processes (not just regulatory) that need to be
| ||
- | coordinated.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | European projects such as PEPPOL and e-Freight have
| ||
- | demonstrated that UBL is a suitable standard for implementing the commercial,
| ||
- | transport and freight logistic documents required by processes that complement
| ||
- | regulatory Single Windows.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136273" title="_Toc262136273"></a><span><span>14.<span style="font: 7pt 'Times New Roman'"> </span></span></span>Is UBL a
| ||
- | ‘real’ global standard for electronic business?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | Perhaps the clearest summary of what makes standards
| ||
- | effective comes from a recent article published by the American National
| ||
- | Standards Institute (ANSI).
| ||
- | </p>
| ||
- | <p style="margin: 0in 46.45pt 0.0001pt 0.5in; text-align: justify" class="MsoNormal">
| ||
- | <em><span> </span>“When
| ||
- | it comes to international standardization, good practices are measured against
| ||
- | the World Trade Organization (WTO) Technical Barriers to Trade (TBT) Agreement
| ||
- | Committee Decision<a name="_ftnref1" href="#_ftn1" title="_ftnref1"><span class="MsoFootnoteReference"><span style="font-family: Cambria"><span><span class="MsoFootnoteReference"><strong><span style="font-size: 12pt; font-family: Cambria">[1]</span></strong></span></span></span></span></a>,
| ||
- | which states that the global relevance of a standard is determined by how it
| ||
- | was developed, not where. More specifically, the Decision states that the
| ||
- | development of international standards must rely upon a number of principles,
| ||
- | including openness, impartiality, consensus, transparency, and coherence, among
| ||
- | others.</em>
| ||
- | </p>
| ||
- | <p style="margin: 0in 46.45pt 0.0001pt 0.5in; text-align: justify" class="MsoNormal">
| ||
- | <em>In other words, the global relevance of a
| ||
- | standard cannot and should not be measured by which organization developed it.
| ||
- | The degree to which a standard is used in the global marketplace is, in ANSI’s
| ||
- | view, the best measure of an international standard.”<a name="_ftnref2" href="#_ftn2" title="_ftnref2"><span class="MsoFootnoteReference"><span style="font-family: Cambria"><span><span class="MsoFootnoteReference"><strong><span style="font-size: 12pt; font-family: Cambria">[2]</span></strong></span></span></span></span></a></em>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Using this description we believe UBL qualifies as an
| ||
- | international standard in compliance with the World Trade Organization (WTO)
| ||
- | Technical Barriers to Trade (TBT) Agreement Committee Decision<em>.</em>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The strength of UBL (as with any standard) is that:
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpFirst">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>it is an open global standard (from a recognized
| ||
- | standards consortium)
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>it exists (the technology works)
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpMiddle">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>it is stable (it has good governance)
| ||
- | </p>
| ||
- | <p style="text-indent: -0.25in" class="ListParagraphCxSpLast">
| ||
- | <span style="font-family: Symbol"><span>·<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>it is proven to meet business requirements (it
| ||
- | has market adoption).<span> </span>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | UBL has been developed within OASIS (a global standards
| ||
- | development consortia) and OASIS has recently submitted UBL 2.1 to the ISO-IEC
| ||
- | Joint Technical Committee 1 (Information Technology) for publication as an ISO
| ||
- | standard.<span> </span>This will ensure that UBL is
| ||
- | both recognized in public sector policies and will also provide additional
| ||
- | layers of governance for the long-term sustainability of UBL.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | In this way UBL is following a typical evolutionary path for
| ||
- | effective global standards.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136274" title="_Toc262136274"></a><span><span>15.<span style="font: 7pt 'Times New Roman'"> </span></span></span>What is
| ||
- | the relationship of UBL to ebXML?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | The impetus to begin the UBL TC came from the desire of a
| ||
- | number of ebXML participants to define a standard XML payload format for ebXML
| ||
- | — that is, an XML counterpart to traditional EDI standards such as ANSI X12 and
| ||
- | UN/EDIFACT. The ebXML suite of specifications, many of them now standardized as
| ||
- | ISO 15000, provides a complete, next-generation XML-based infrastructure that
| ||
- | enables EDI functionality over the free Internet.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | UBL provides a standard data format for the messages to be
| ||
- | exchanged in such an infrastructure. However, UBL is designed to be
| ||
- | "agnostic" with respect to the infrastructure, and UBL messages can
| ||
- | be used in a very wide range of functional contexts, from complex
| ||
- | service-oriented architectures and cloud services to the simple exchange of
| ||
- | documents via email.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136275" title="_Toc262136275"></a><span><span>16.<span style="font: 7pt 'Times New Roman'"> </span></span></span>What is
| ||
- | the relationship of UBL to ebXML Core Components?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | UBL was the first published data format specification
| ||
- | produced in full conformance with UN/CEFACT's ebXML Core Components Technical Specification
| ||
- | (CCTS) Version 2.01 - ISO TS15000-5:2005.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The UBL library consists of ebXML CCTS Business Information
| ||
- | Entities (BIEs). UBL XML schemas are defined through the application of UBL
| ||
- | Naming and Design Rules (NDRs) to an underlying data model mapped to the Core
| ||
- | Component types.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | For more information please see the UBL Committee Note on “<span>UBL Conformance to ebXML CCTS” at:</span>
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | <a href="http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/cn01/UBL-conformance-to-CCTS-v1.0-cn01.html">http://docs.oasis-open.org/ubl/UBL-conformance-to-CCTS/v1.0/cn01/UBL-conformance-to-CCTS-v1.0-cn01.html</a>
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136276" title="_Toc262136276"></a><span><span>17.<span style="font: 7pt 'Times New Roman'"> </span></span></span>What is
| ||
- | the relationship of UBL to UN/CEFACT?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | The UBL Technical Committee is concerned about the
| ||
- | perception of being in competition with UN/CEFACT for the development of XML
| ||
- | standards.<span> </span>This is a misrepresentation
| ||
- | of the true situation.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | UN/CEFACT is the subcommittee of the UN Economic Commission
| ||
- | for Europe responsible to provide technology neutral recommendations and
| ||
- | standards for electronic business for international trade facilitation.<span> </span>The foundation of UN/CEFACT is maintenance of
| ||
- | the UN/EDIFACT EDI standard.<span> </span>As an
| ||
- | intergovernmental body UN/CEFACT has a strong influence in public sector policy
| ||
- | decisions and this sets UN/CEFACT apart from dedicated standards making bodies.
| ||
- | Unfortunately, there is a belief (sometimes expressed by members of UN/CEFACT)
| ||
- | that UN/CEFACT is the exclusive organization for creating standards for
| ||
- | electronic business and that as part of the United Nations, UN/CEFACT holds a
| ||
- | superior position to other standards making bodies.<span> </span>It follows from this belief that any other
| ||
- | electronic business standards development activities (for example, UBL) are in
| ||
- | competition with UN/CEFACT’s work and should stop.<span> </span>We do not believe this to be true or
| ||
- | necessary.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | <span>In an environment
| ||
- | where there is very little true standardization, UBL is the nearest the world
| ||
- | has to a comprehensive set of open standards for XML documents used in the
| ||
- | international supply chain.<span> </span>And </span>the
| ||
- | increasing use of UBL has created a requirement to have ongoing support for
| ||
- | current and future stakeholder communities.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The Memorandum of Understanding on eBusiness makes a clear
| ||
- | statement on the role of the various standards bodies:
| ||
- | </p>
| ||
- | <p style="margin-left: 0.5in; text-align: justify" class="MsoNormal">
| ||
- | “<em>A.1 In the case of UN/EDIFACT messages or
| ||
- | other messages using its functionality, syntax and/or directories, UN/CEFACT is
| ||
- | responsible for the development and maintenance of these messages and the
| ||
- | associated implementation guidelines.</em>
| ||
- | </p>
| ||
- | <p style="margin-left: 0.5in; text-align: justify" class="MsoNormal">
| ||
- | <em>A.2 Since the standardization of syntaxes
| ||
- | for electronic business is broader than UN/EDIFACT, it is recognized that ISO
| ||
- | and IEC are the more appropriate organizations for the development and
| ||
- | maintenance of standardized syntaxes for electronic business</em>.”
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | UBL has been developed within OASIS (a global standards
| ||
- | development consortia) and OASIS has recently submitted UBL 2.1 to the ISO-IEC
| ||
- | Joint Technical Committee 1 (Information Technology) for publication as an ISO
| ||
- | standard.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | It is also worth noting that there is no set of standards equivalent
| ||
- | to UBL from UN/CEFACT. However<span>, there
| ||
- | is some duplication by UN/CEFACT of few UBL standard documents.<span> </span></span>In all cases the UN/CEFACT projects to
| ||
- | develop these duplicate standards were launched after the publication of
| ||
- | standards from UBL. Furthermore, apart from some specific agricultural industry
| ||
- | messages there is little evidence of any real-world implementations using
| ||
- | official UN/CEFACT XML standards.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The situation with UN/CEFACT XML today is that while
| ||
- | governments and commercial organizations do not (and will not) criticize the
| ||
- | work of UN/CEFACT, most do not use UN/CEFACT’s XML standards. Instead they seek
| ||
- | effective solutions such as UBL, or create their own.<span> </span>This has been the case in Europe since the
| ||
- | responsible public sector agencies in Northern Europe joined forces to
| ||
- | implement UBL standards in 2006.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | Overall, it is difficult to see the benefits to users in
| ||
- | UN/CEFACT publishing standards that compete with the UBL standards currently
| ||
- | implemented and operational across many communities.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | To this end, both OASIS and members of the UBL Technical
| ||
- | Committee are continuing to work with UN/CEFACT management to establish
| ||
- | strategies that will benefit all stakeholders involved in international trade.
| ||
- | </p>
| ||
- | <h2 style="margin-left: 0.25in; text-indent: -0.25in"><a name="_Toc262136277" title="_Toc262136277"></a><span><span>18.<span style="font: 7pt 'Times New Roman'"> </span></span></span>How does
| ||
- | UBL support the European electronic invoicing Directive?</h2>
| ||
- | <p class="MsoNormal">
| ||
- | The European Directive on electronic invoicing in public
| ||
- | procurement is a law enacted by the European parliament obliging public
| ||
- | authorities in all EU member states to receive electronic invoices. One
| ||
- | aspect of this law is that a common European standard for the semantic data
| ||
- | model of the core elements of an electronic invoice (the ‘European standard on
| ||
- | electronic invoicing’) will be developed over the next few years. When
| ||
- | this is published, public sector contracting authorities will be obliged to
| ||
- | receive and process electronic invoices formatted using a listed set of syntaxes
| ||
- | that comply with the European semantic standard.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- | The work of the CEN BII Workshop will be a key foundation for
| ||
- | the European standard for electronic invoicing and we expect UBL will be one of
| ||
- | the syntaxes identified.
| ||
- | </p>
| ||
- | <h3 style="margin-left: 0.55in; text-indent: -0.3in"><a name="_Toc262136278" title="_Toc262136278"></a><span><span>18.1.<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Will UBL be the standard European invoice
| ||
- | format?</h3>
| ||
- | <p style="margin-left: 0.25in" class="MsoNormal">
| ||
- | Yes (and no). There will not be a standard format or
| ||
- | syntax for European invoices.<span> </span>The
| ||
- | European standard on electronic invoicing will not dictate what syntax or
| ||
- | format is to be used, only the semantics of the required information.
| ||
- | </p>
| ||
- | <p style="margin-left: 0.25in" class="MsoNormal">
| ||
- | However, the semantic model of the CEN BII Post-award
| ||
- | Profile will be a key foundation of the European semantics and as the
| ||
- | combination of BII semantics and UBL format/syntax has been widely adopted in
| ||
- | Europe, the expectation is that the established BII user community will be
| ||
- | supported by the standard.
| ||
- | </p>
| ||
- | <p style="margin-left: 0.25in" class="MsoNormal">
| ||
- | While there will not be a European standard for
| ||
- | invoice syntax, we expect that market forces will determine that UBL syntax is
| ||
- | the most effective implementation of the European standard on electronic
| ||
- | invoicing.
| ||
- | </p>
| ||
- | <h3 style="margin-left: 0.55in; text-indent: -0.3in"><a name="_Toc262136279" title="_Toc262136279"></a><span><span>18.2.<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Isn’t this yet another standard?</h3>
| ||
- | <p style="margin-left: 0.25in" class="MsoNormal">
| ||
- | No, fortunately this work is already well established
| ||
- | and the formal standardization can be seen as the next stage on the natural
| ||
- | evolution of standards. The obligation is for invoices to contain core
| ||
- | information elements. Defining what is required as core information is not
| ||
- | a new piece of work. These requirements will be based on existing
| ||
- | standardization activities by groups such as the CEN BII Workshop and the
| ||
- | semantic data model used in the BII Profiles for post-award processes.
| ||
- | </p>
| ||
- | <h3 style="margin-left: 0.55in; text-indent: -0.3in"><a name="_Toc262136280" title="_Toc262136280"></a><span><span>18.3.<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>What will a standard European electronic invoice
| ||
- | look like?</h3>
| ||
- | <p style="margin-left: 0.25in" class="MsoNormal">
| ||
- | We expect that various subsets of the UBL Invoice
| ||
- | will be compliant to the new standard. Valid subsets will contain the
| ||
- | core elements of information (the semantics) defined by the European standard
| ||
- | on electronic invoicing.
| ||
- | </p>
| ||
- | <h3 style="margin-left: 0.55in; text-indent: -0.3in"><a name="_Toc262136281" title="_Toc262136281"></a><span><span>18.4.<span style="font: 7pt 'Times New Roman'">
| ||
- | </span></span></span>Should I delay my electronic invoicing programme
| ||
- | until we see what the European semantic standard is?</h3>
| ||
- | <p style="margin-left: 0.25in" class="MsoNormal">
| ||
- | Not at all. This is unnecessary and counter to the
| ||
- | intention of the Directive. The work of the CEN BII Workshop will be a key
| ||
- | foundation on which to develop the European standard for electronic invoicing
| ||
- | and UBL will be one of the syntaxes identified. Therefore, the current CEN BII
| ||
- | Post-award Profile offers a suitable placeholder for the eventual European
| ||
- | standard and so can be implemented with some confidence that this will comply
| ||
- | with the Directive.
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- |
| ||
- | </p>
| ||
- | <p class="MsoNormal">
| ||
- |
| ||
- | </p>
| ||
- | <div>
| ||
- | <br />
| ||
- | <hr />
| ||
- | <div id="ftn1">
| ||
- | <p class="MsoFootnoteText">
| ||
- | <a name="_ftn1" href="#_ftnref1" title="_ftn1"><span class="MsoFootnoteReference"><span style="font-family: Cambria"><span><span class="MsoFootnoteReference"><span style="font-size: 12pt; font-family: Cambria">[1]</span></span></span></span></span></a>
| ||
- | <span style="font-size: 10pt">G/TBT/ 1/REV. 10. “Decision of the Committee on
| ||
- | Principles for the Development of International Standards, Guides and
| ||
- | Recommendations with Relation to Articles 2, 5 and Annex 3 of the Agreement”</span>
| ||
- | </p>
| ||
- | </div>
| ||
- | <div id="ftn2">
| ||
- | <p class="MsoFootnoteText">
| ||
- | <a name="_ftn2" href="#_ftnref2" title="_ftn2"><span class="MsoFootnoteReference"><span style="font-family: Cambria"><span><span class="MsoFootnoteReference"><span style="font-size: 12pt; font-family: Cambria">[2]</span></span></span></span></span></a>
| ||
- | <span style="font-size: 10pt">ANSI Supports
| ||
- | Continued Dialogue on Standards for EU-U.S. Transatlantic Trade and Investment
| ||
- | Partnership<strong>, </strong></span><span style="font-size: 10pt">New York
| ||
- | October 11, 2013 (</span><a href="http://ansi.org/news_publications/news_story.aspx?menuid=7&articleid=3754"><span style="font-size: 10pt">http://ansi.org/news_publications/news_story.aspx?menuid=7&articleid=3754</span></a><span style="font-size: 10pt">)</span>
| ||
- | </p>
| ||
- | </div>
| ||
- | </div>
| ||
- | <!--[if gte mso 9]><xml>
| ||
- | <w:LatentStyles DefLockedState="false" LatentStyleCount="156">
| ||
- | </w:LatentStyles>
| ||
- | </xml><![endif]--><!--[if gte mso 10]>
| ||
- | <style>
| ||
- | /* Style Definitions */
| ||
- | table.MsoNormalTable
| ||
- | {mso-style-name:"Table Normal";
| ||
- | mso-tstyle-rowband-size:0;
| ||
- | mso-tstyle-colband-size:0;
| ||
- | mso-style-noshow:yes;
| ||
- | mso-style-parent:"";
| ||
- | mso-padding-alt:0in 5.4pt 0in 5.4pt;
| ||
- | mso-para-margin:0in;
| ||
- | mso-para-margin-bottom:.0001pt;
| ||
- | mso-pagination:widow-orphan;
| ||
- | font-size:10.0pt;
| ||
- | font-family:"Times New Roman";
| ||
- | mso-ansi-language:#0400;
| ||
- | mso-fareast-language:#0400;
| ||
- | mso-bidi-language:#0400;}
| ||
- | </style>
| ||
- | <![endif]-->
| ||
Revision of Tue, 2014-05-20 20:50: