“Universal Business Language”的意思、由来-开放百科全书

UBL is owned by OASIS and is currently available to all, with no royalty fees. The UBL library of business documents is a well-developed markup language with validators, authoring software, parsers and generators.^[3] UBL version 2.0 was approved as an OASIS Standard in October 2006. Version 2.1 was approved as an OASIS Standard in November 2013 and an ISO Standard (ISO/IEC 19845:2015) in December 2015. Version 2.2 was approved as an OASIS Standard in July 2018. Version 2.1 is fully backward compatible with version 2.0, but it adds 34 new document schemas, bringing the total of business document types defined by UBL to 65. Version 2.2 is fully backward compatible with version 2.1, and it adds another 16 document types for a total of 81.

UBL is described in an extensive overview in the article "[https://www.xml.com/articles/2017/01/01/what-is-ubl/ What is UBL?]" describing customizing and extending UBL, the governance of UBL, how UBL is modeled, and thoughts regarding deploying UBL.

UBL traces its origins back to the EDI standards and other derived XML standards.^[4]^[5]

Downloads

Current

UBL 2.2 - http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.html (Published 09 July 2018)

UBL 2.1 as ISO/IEC 19845:2015 - http://standards.iso.org/ittf/PubliclyAvailableStandards/

Historical

UBL 2.1 (ISO/IEC 19845:2015) and UBL 2.2

OASIS UBL Technical Committee and ISO/IEC 19845 Maintenance Agency

The OASIS Universal Business Language (UBL) Technical Committee^[6] is responsible for the creation and maintenance of the OASIS Standard and has been designated the maintenance agency for ISO/IEC 19845. The maintenance governance procedures^[7] describe how committee and non-committee members contribute to the development of the specification.

Business processes described and supported in UBL

Business process support originating with UBL 1.0 (2004)

Business process support added in UBL 2.0 (2006)

Catalogue, Quotation, Payment, Statement, Transport Services, Certificate of Origin

Business process support added in UBL 2.1 (2013)

eTendering, Vendor Managed Inventory, Intermodal Freight Management, Utility Billing,and Collaborative Planning, Forecasting, Replenishment and e-Invoice / e-Archive and e-Ledger in Turkey

Business process support proposed to be added for UBL 2.2

Standard document types defined by UBL

Document types originally defined in UBL 1.0 (2004)

Order, Order Response, Order Response Simple, Order Change, Order Cancellation, Despatch Advice [Advance Ship Notice], Receipt Advice, Invoice

Document types added in UBL 2.0 (2006)

Added document types for sourcing: Catalogue, Catalogue Deletion, Catalogue Item Specification Update, Catalogue Pricing Update, Catalogue Request, Quotation, Request for Quotation

Added document types for fulfillment: Bill of Lading, Certificate of Origin, Forwarding Instructions, Packing List, Transportation Status, Waybill

Added document types for billing: Credit Note, Debit Note, Freight Invoice, Reminder, Self Billed Credit Note, Self Billed Invoice

Document types added in UBL 2.1 (2013)

Added document types for eTendering: Awarded Notification, Call for Tenders, Contract Award Notice, Contract Notice, Guarantee Certificate, Tender, Tender Receipt, Tenderer Qualification, Tenderer Qualification Response, Unawarded Notification

Added document types for Collaborative planning, forecasting, and replenishment: Exception Criteria, Exception Notification, Forecast, Forecast Revision, Item Information Request, Prior Information Notice, Trade Item Location Profile

Added document types for Vendor Managed Inventory: Instruction for Returns, Inventory Report, Product Activity, Retail Event, Stock Availability Report

Added document types for Intermodal Freight Management: Goods Item Itinerary, Transport Execution Plan, Transport Execution Plan Request, Transport Progress Status, Transport Progress Status Request, Transport Service Description, Transport Service Description Request, Transportation Status, Transportation Status Request

Added supplementary document types: Document Status, Document Status Request

Document types proposed for UBL 2.2 - http://docs.oasis-open.org/ubl/UBL-2.2.html

Added document types for eTendering: Enquiry, Enquiry Response, Expression Of Interest Request, Expression Of Interest Response, Qualification Application Request, Qualification Application Response, Tender Contract, Tender Status, Tender Status Request, Tender Withdrawal, Unsubscribe From Procedure Request, Unsubscribe From Procedure Response

Added document types for business directories and agreements: Business Card, Digital Agreement, Digital Capability

UBL 2.1 as ISO/IEC 19845:2015 - http://standards.iso.org/ittf/PubliclyAvailableStandards/

The OASIS UBL 2.1 specification has been approved as ISO/IEC 19845 as of 2015-12-15:

UBL 2.2 - http://docs.oasis-open.org/ubl/os-UBL-2.2/UBL-2.2.html

The OASIS UBL 2.2 specification has been approved as an OASIS Standard as of 2018-07-09. Work is underway to revise ISO/IEC 19845 accordingly.

UBL 2.3 requirements gathering - per governance rules at http://docs.oasis-open.org/ubl/UBL-Governance/v1.0/cn01/UBL-Governance-v1.0-cn01.html

The UBL Technical Committee agreed^[8] to begin accepting new suggestions for consideration in a future UBL 2.3, with a target final publication of December 2019. The release will be the first to incorporate the input from the [https://www.oasis-open.org/committees/sc_home.php?wg_abbrev=ubl-payfin UBL Payments and Finance Subcommittee] established in June 2017.

Subsets and customizations of UBL

Danish subsets: OIOXML and OIOUBL

In December 2003 Denmark legislated^[9] the mandatory use of a customization of UBL 0.7, using the OIOXML specification, for electronic invoicing for government procurement starting February 2005. In March 2010 Denmark legislated^[10] the mandatory use of a customization of UBL 2.0, using the OIOUBL specification.

In 2011 the Danish government documented^[11] savings of €500,000,000 having used UBL.

Northern European Subset - NESUBL

As part of the Northern European cooperation on e-commerce and e-procurement, representatives from Denmark, Sweden, Norway, Finland, UK and Iceland set up a working group for developing a Northern European subset of UBL 2.0 documents. The main focus of NES is to define the semantic use of UBL 2.0 as applied to specific business processes. To achieve this the UBL 2.0 standard is restricted on additional levels by using "profiles" that apply to defined business situations.^[12] The use of individual elements is specifically described to avoid conflicting interpretation. Additionally each country has developed guidelines that describe the application of the NESUBL subset to domestic business practices. The goal is to enable companies and institutions to implement e-commerce by agreeing to a specific profile and thus eliminate the need for bilateral implementation. Additional countries have shown interest in joining the work. The NESUBL subset was published in March 2007.^[13]

Since its publication, NESUBL subset has influenced government eProcurement initiatives across Europe, for example in Denmark, Sweden, Norway, Iceland, The Netherlands, Turkey. It is also the basis for an eProcurement initiative, ePrior, by the European Commission, Directorate General's of the European Commission, starting with the Directorate General for Information Technology (DIGIT).^[14]^[15] It is also the basis of the syntax for business documents created by the CEN/BII (Business Interoperability Initiative).^[16]^[17]

European-wide deployment of UBL in PEPPOL

[https://www.peppol.eu/ PEPPOL], the Pan-European Public Procurement Online project now maintained by [https://www.peppol.eu/about-openpeppol OpenPEPPOL], adopts the work products of [https://standards.cen.eu/dyn/www/f?p=204:7:0::::FSP_ORG_ID:1883209&cs=1E81C9C833655EEDC7010C8D0A2FB786C CEN/TC434] and [https://standards.cen.eu/dyn/www/f?p=204:7:0::::FSP_ORG_ID:1976650&cs=175E298F320429229DD35C9E22F4E8F76 CEN/TC440] that include UBL customizations and syntax serializations of different document types for European business processes. The goal of PEPPOL is to enable public procurement across borders within the EU.^[18]

It was reported^[19] that CEN/TC434 has unanimously agreed to endorse UBL as one of two syntaxes complying with the forthcoming European Norm on e-Invoicing and will be listed in a specific CEN Technical Specification.

These efforts support Directive 2014/55/EU on electronic invoicing in public procurement in Europe.

On March 3, 2017 this summary update of recent announcements was published, including references to Austria, Belgium, Denmark, Italy (Emilia-Romagna region), Netherlands, Norway, Sweden.

Spanish UBL version based in CCI

In Spain, UBL is being used primarily for electronic invoice encoding. The UBL Spanish Localization Committee has been actively developing UBL awareness and has created implementation guidelines to allow easy adoption of UBL based on previous work done by CCI.

UBL Turkish Customization - UBL-TR

The UBL Turkish Localization Subcommittee customized the UBL 2.0 to be used in eInvoice process in Turkey. [https://www.ibm.com/support/knowledgecenter/en/temp_sterlingb2bcloud/einvoicing/SCN_eINV_Turkey_Definitions.htm See also the IBM Knowledge Center.]

Czech UBL Customization - ISDOC

The SPIS consortium (currently named ICT unie) created an UBL 2.0 customization ISDOC to be used for e-Invoicing in the Czech Republic. The recently released ISDOC 6 supports e-Requests too.^[20]

Peruvian UBL Customization - SUNAT

SUNAT, the national customs and tax administration for Peru, supports^[21] a customization of UBL 2.0. Plans have been announced^[22] by SUNAT to migrate to UBL 2.1

Belgian UBL Customization - e-fff

In December 2011 the Belgian government specified^[23] a customization of UBL to maximize the interoperability of the electronic invoice between Belgian actors.

Swedish UBL Customization - Svefaktura

SFTI, the joint project of the Swedish Association of Local Authorities and Regions (SKL), Financial Management Authority (ESV) and the government contracting authority specified Svefaktura, a UBL customization.

As of November 1, 2018 it will be mandatory^[24] for Swedish electrical authorities to use PEPPOL.

Colombian UBL Customization - DIAN

DIAN, the Colombian national tax and customs directorate, implements ^[25] UBL 2 as the XML document format for electronic invoicing.

Norwegian UBL Customization - EHF

Difi, the Norwegian agency for Public Management and eGovernment, has chosen^[26] to use CEN BII as a base for the EHF formats and the Universal Business Language (UBL) as a foundation for the implemented syntax.

Dutch UBL Customization - UBL-OHNL and Simplerinvoicing

UBL-OHNL is a Dutch government-specific customization for submitting documents via Digipoort.

Simplerinvoicing is a community of e-invoicing, ERP and accounting software providers making e-invoicing in UBL available for everyone. It includes access to the PEPPOL network for secure and reliable transfer.

In response to the European Directive 2014/55/EU the Dutch government has mandated^[27] XML Invoicing for all contracts signed after January 1, 2017 using the UBL-OHNL customization via Digipoort or the Simplerinvoicing customization via PEPPOL.

Australia and New Zealand use of UBL

As part of a national initiative to increase the proportion of businesses participating in the Australian digital economy the Digital Business Council endorsed ^[28] an Interoperability Framework in 2016. The initial version of the framework includes a set of policies, standards and guidelines to promote the economy-wide adoption of eInvoicing. A subset of UBL 2.1 for the invoice and business response document was included in this initial release. The subset was initially based on a working draft of the [https://standards.cen.eu/index.html European Committee for Standardization's] work under the [https://standards.cen.eu/dyn/www/f?p=204:7:0::::FSP_ORG_ID:1883209&cs=1E81C9C833655EEDC7010C8D0A2FB786C CEN/TC 434 - Electronic Invoicing project]

In 2017 OASIS established a [https://www.oasis-open.org/committees/sc_home.php?wg_abbrev=ubl-australia localisation subcommittee] to promote the harmonised use of UBL and to support the broader market adoption across Australia. The subcommittee facilitates an open dialogue for information sharing and collaboration, under the auspices of OASIS transparent governance and operating procedures.

In February 2019 "the two countries’ intention to jointly adopt the Pan-European Public Procurement Online (PEPPOL) interoperability framework for trans-Tasman e-invoicing" was announced^[29] by the Prime Ministers of New Zealand and Australia.

Italian use of UBL

The future of e-invoicing in Italy will facilitate the correct implementation of the national Technical Rules for Interoperability between e-Procurement platforms (Circolare 3 AgID) and the automation of the end-to-end procurement process, based on PEPPOL or, where a PEPPOL specification is not available, by implementing a CEN BII profile using the OASIS UBL 2.1 syntax.^[30] In the long term, likely by 2022, the objective is to migrate to a single global standard, UBL, still supporting the other mandatory syntax with translations, and phasing out the national format.

Singaporean use of UBL

Singapore has established the first PEPPOL Authority outside of Europe^[31] with the Info-communications Media Development Authority (IMDA) to help businesses in Singapore to benefit from digitalisation and better position themselves to plug into the international marketplace.

United States and Canadian use of UBL

On October 4, 2018 the Business Payments Coalition e-Invoicing Subcommittee^[32], an open technical committee consisting of US, Canadian, and Mexican interests in electronic invoicing and facilitated by the US Federal Reserve Bank of Minneapolis, released^[33] its first review of the semantic model of an invoice, expressed using the business objects of OASIS UBL 2.2.

National adoptions

Corporate support of UBL

Industry support of UBL

Textile Clothing and Footwear industry - eBiz-TCF

The e-Freight Framework

Danish Industry

Products supporting UBL

Tools for working with UBL documents and models

Community and developer resources

The UBL Developer Mail List is an open unmoderated list hosted by OASIS for developers to collaborate and post questions. Visit the OASIS mail list manager to subscribe.

The UBL online community is an open wiki-based forum hosted by OASIS for the community to build persistent resources for sharing information about UBL and news from users and vendors.

Regional UBL user/developer communities

Blogs/articles/essays related to UBL

The chair of the committee, G. Ken Holman, has published a number of [https://www.linkedin.com/today/author/gkholman?trk=pprof-feed essays related to UBL on LinkedIn].

UBL Vocabulary Development

The OASIS UBL Naming and Design Rules Version 3.0 documents how the UBL Technical Committee applies the OASIS Business Document Naming and Design Rules Version 1.0 specification for defining a business document creating XSD schemas on the basis of business objects described using the UN/CEFACT Core Component Technical Specification 2.01.

The committee has published a reference^[44] for one to create one's own UBL subset schema by starting from the same resources used by the committee to publish the UBL distribution.

The committee announced^[45] the first public review of the OASIS Business Document Naming and Design Rules Version 1.1^[46] proposed OASIS Standard with new rules for creating JSON validation artefacts for JSON documents, complete with the OASIS Committee Note^[47] of all UBL 2.1 document types as JSON schemas and all UBL 2.1 example documents as JSON documents, beginning February 1, 2017 and closing April 1, 2017.

References

1. ^UBL 2.0 implementation library Retrieved on 2009-12-21.
2. ^{{cite web | url=http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl | title=UBL official homepage | accessdate=2007-03-31}}
3. ^Article by Tim Bray: "Don’t Invent XML Languages" Retrieved on 2007-05-29.
4. ^{{cite web | url=http://www.unimaze.com/support/resources/on-ubl | title=On UBL (an overview) | accessdate=2008-02-09}}
5. ^{{Cite web|url=http://ubl.xml.org/wiki/history-of-ubl|title=History of UBL {{!}} UBL XML.org|website=ubl.xml.org|access-date=2017-01-11}}
6. ^{{Cite web|url=https://www.oasis-open.org/committees/ubl|title=OASIS Universal Business Language (UBL) Technical Committee|last=|first=|date=|website=|archive-url=|archive-date=|dead-url=|access-date=}}
7. ^{{Cite web|url=http://docs.oasis-open.org/ubl/UBL-Governance/v1.0/UBL-Governance-v1.0.html|title=UBL Maintenance Governance Procedures Version 1.0|website=docs.oasis-open.org|access-date=2017-11-08}}
8. ^{{Cite web|url=https://lists.oasis-open.org/archives/ubl/201701/msg00013.html|title=Minutes of Atlantic UBL TC call 18 January 2017 15:00UTC|website=lists.oasis-open.org|access-date=2017-02-01}}
9. ^{{Cite web|url=http://www.oio.dk/XML/standardisering/eHandel/materialer/OIOXMLeInvoice|title=Danish statute for OIOXML eInvoice|last=|first=|date=|website=www.oio.dk|publisher=|access-date=2016-09-29}}
10. ^{{Cite web|url=http://oioubl.info/documents/en/OIOUBLStatute.pdf|title=Executive Order on Information in, and Transport of, OIOUBL Electronic Invoices for Electronic Settlement with Public Authorities|last=|first=|date=|website=|publisher=|access-date=}}
11. ^{{Cite web|url=https://www.oasis-open.org/committees/download.php/36397|title=E-Invoicing in Denmark|last=|first=|date=|website=|publisher=|access-date=}}
12. ^{{cite web | url=http://www.unimaze.com/support/resources/on-nesubl | title=On NESUBL (an overview)}}
13. ^{{cite web | url=http://www.nesubl.eu | title=NES official homepage | accessdate=2007-03-31 |archiveurl = https://web.archive.org/web/20070320000433/http://www.nesubl.eu/ |archivedate = 2007-03-20}}
14. ^{{cite web | url=http://www.epractice.eu/cases/ePRIOR | title=IDABC e-Invoicing and e-Ordering project for public procurement, by Pieter Breyne | accessdate=2010-04-03}}
15. ^{{cite web|url=http://www.epractice.eu/en/library/288906|title=Analysis of Business Requirements for e-Invoicing in a Public Procurement Context : Final Study|last=Breyne|first=Pieter|author2=Philip Van Langenhove |author3=Joao Frade |author4=Maarten Daniëls |date=31 March 2009|publisher=European Commission|accessdate=5 January 2012}}
16. ^{{cite web|url=http://spec.cenbii.eu/|title=The CEN / BII workshop results|accessdate=2010-04-03}}
17. ^{{cite web|url=http://www.cen.eu/cen/Sectors/Sectors/ISSS/Activity/Pages/Ws_BII.aspx|title=The CEN / BII official homepage|accessdate=2010-04-03}}
18. ^{{cite web | url=http://peppol.eu/ | title=PEPPOL, Pan European Public Procurement Online | accessdate=2010-04-03}}
19. ^{{Cite web|url=https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Agreement+on+syntaxes+complying+with+the+forthcoming+European+standard+%28EN%29+on+Electronic+Invoicing|title=2017-01-26: Agreement on syntaxes complying with the forthcoming European standard (EN) on Electronic Invoicing - CEF Digital - CEF Digital|website=ec.europa.eu|access-date=2016-11-07}}
20. ^ISDOC 6: Nový formát elektronické fakturace má zlepšit transparentnost veřejných zakázek
21. ^{{Cite web|url=http://www.edicomgroup.com/en_US/news/4081|title=E-invoicing in Peru|access-date=2016-09-29}}
22. ^{{Cite web|url=https://translate.google.com/translate?hl=en&sl=es&u=http://www.sunat.gob.pe/legislacion/superin/2016/anexo-067-2016.pdf&prev=search|title=Google Translate|website=translate.google.com|access-date=2016-09-29}}
23. ^{{Cite web|url=http://www.e-fff.be/NL/doc03.php|title=e-fff|website=www.e-fff.be|access-date=2016-09-29}}
24. ^{{Cite web|url=http://www.esv.se/contentassets/5cb651dd8cbf4425bc50f0d4c37c8db8/esv-cirkular-2015-3.pdf|title=Ekonomistyrningsverkets cirkulärserie över föreskrifter och allmänna råd|last=|first=|date=|website=|archive-url=|archive-date=|dead-url=|access-date=2017-03-17}}
25. ^{{Cite web|url=http://www.dian.gov.co/contenidos/otros/fac_electronica.html|title=Dirección de Impuestos y Aduanas Nacionales de Colombia|website=www.dian.gov.co|access-date=2016-10-27}}
26. ^{{Cite web|url=https://vefa.difi.no/ehf/guide/invoice-and-creditnote/2.0/en/|title=EHF Invoice and Creditnote|last=eGovernment|first=Agency of Public Management and|website=vefa.difi.no|access-date=2016-12-01}}
27. ^{{Cite web|url=http://eeiplatform.com/17338/mandatory-xml-e-invoicing-towards-dutch-central-agencies-as-from-1-january-2017/|title=Mandatory XML e-invoicing towards Dutch central agencies as from 1 January 2017 - E-invoicing Platform|website=eeiplatform.com|access-date=2016-12-01}}
28. ^{{Cite web|url=http://www.itnews.com.au/news/australia-now-has-a-national-standard-for-e-invoicing-431943|title=Australia now has a national standard for e-invoicing|website=iTnews|access-date=2016-09-28}}
29. ^{{Cite web|url=http://www.beehive.govt.nz/release/joint-statement-prime-ministers-rt-hon-jacinda-ardern-and-hon-scott-morrison-mp-auckland-22|title=Joint Statement by Prime Ministers the Rt Hon Jacinda Ardern and the Hon Scott Morrison MP Auckland, 22 February 2019|website=The Beehive|language=en|access-date=2019-02-22}}
30. ^{{Cite web|url=https://ec.europa.eu/docsroom/documents/25521/attachments/1/translations/en/renditions/native|title=Study on the practical application and implementation of the European e-Invoicing standard|last=|first=|date=|website=|archive-url=|archive-date=|dead-url=|access-date=}}
31. ^{{Cite news|url=https://peppol.eu/singapore-first-peppol-authority-outside-europe/|title=Singapore first PEPPOL Authority outside Europe - Peppol|last=Works|first=Strøm|date=2018-05-22|work=Peppol|access-date=2018-09-25|language=en-US}}
32. ^{{Cite news|url=https://fedpaymentsimprovement.org/payments-efficiency/b2b-payments/electronic-invoicing/|title=Electronic Invoicing -|work=FedPayments Improvement|access-date=2018-10-17|language=en-US}}
33. ^{{Cite web|url=https://bpceinvcttee.page.link/shareddrive|title=BPC semantic models - Google Drive|website=bpceinvcttee.page.link|language=en|access-date=2018-10-17}}
34. ^{{Cite web|url=https://store.csagroup.org/ccrz__ProductDetails?cartID=&sku=2704106&viewState=DetailView |title=CAN/CSA-ISO/IEC 19845:16|last=|first=|date=|website=ShopCSA|language=en|archive-url=|archive-date=|dead-url=|access-date=2017-02-18}}
35. ^{{Cite web|url=https://www.msc.com/bel/notices/2016-february/msc-belgium-presents-e-invoicing|title=MSC Belgium presents e-invoicing {{!}} MSC|website=www.msc.com|access-date=2016-09-29}}
36. ^{{Cite web|url=https://entreprises.edf.com/fichiers/fckeditor/Commun/Entreprises/pdf/Guide%20technique%20facture%20EDF%20en%20XML%20V1.2.pdf|title=Guide technique Traduction des factures EDF en XML Version 1.2|last=|first=|date=|website=|publisher=|access-date=}}
37. ^{{Cite web|url=http://www-05.ibm.com/support/operations/ca/en/e-invoicing.html|title=IBM Electronic Invoicing - Canada|date=2017-02-01|website=www-05.ibm.com|language=en-CA|access-date=2017-03-17}}
38. ^{{Cite web|url=https://www.eimpactproject.eu/the-e-freight-framework|title=The e-Freight Framework - e-Impact|website=www.eimpactproject.eu|language=en-US|access-date=2017-11-07}}
39. ^{{Cite web|url=http://clearviewtrade.com/#referencer|title=CLEARVIEW TRADE - ClearView Trade|website=clearviewtrade.com|language=da-DK|access-date=2017-11-10}}
40. ^{{Cite web|url=http://www.akretion.com/blog/akretion-adds-support-for-ubl-based-electronic-orders-in-odoo|title=Akretion {{!}} Akretion adds support for UBL-based electronic orders in Odoo|website=www.akretion.com|language=en|access-date=2017-11-15}}
41. ^{{Cite web|url=https://blog.tradeshift.com/the-hidden-oasis-a-universal-business-language/|title=The hidden OASIS: a Universal Business Language - Tradeshift Blog|date=2013-05-21|language=en-US|access-date=2016-10-02}}
42. ^{{Cite web|url=http://ublready.com/ubl-ready-participants/|title=UBL Ready participants, taking the next step in e-invoicing: UBL e-invoicing {{!}} UBL Ready {{!}} E-invoicing|website=ublready.com|language=en-GB|access-date=2017-03-10}}
43. ^{{Cite web|url=http://ublready.com/get-started-guide/|title=Get Started Guide to become UBL Ready in five easy steps {{!}} UBL Ready {{!}} E-invoicing|website=ublready.com|language=en-GB|access-date=2017-03-10}}
44. ^¹{{Cite web|url=https://docs.google.com/document/d/1RSvewwdS-lp4sl-gYHI5gjNxrgXXqCc5wuA6UI5hhWA/view|title=UBL spreadsheet editing instructions|access-date=2016-09-28}}
45. ^{{Cite web|url=https://www.oasis-open.org/news/announcements/ubl-2-1-json-alternate-representation-v1-0-and-business-document-naming-and-desig|title=#UBL 2.1 JSON Alternate Representation v1.0 and Business Document Naming and Design Rules start public reivew - ends April 1st {{!}} OASIS|website=www.oasis-open.org|language=en|access-date=2017-02-01}}
46. ^{{Cite web|url=http://docs.oasis-open.org/ubl/Business-Document-NDR/v1.1/Business-Document-NDR-v1.1.html|title=Business Document Naming and Design Rules Version 1.1|website=docs.oasis-open.org|access-date=2017-02-01}}
47. ^{{Cite web|url=http://docs.oasis-open.org/ubl/UBL-2.1-JSON/v1.0/UBL-2.1-JSON-v1.0.html|title=UBL 2.1 JSON Alternative Representation Version 1.0|website=docs.oasis-open.org|access-date=2017-02-20}}