The European Commission is now making it easier for
companies, in particular Small and Medium Sized Enterprises (SMEs), to
bid for public sector contracts anywhere in EU, thus making a crucial
step towards the Single European Market.
Welcome to UBL.XML.org.
This is the official community gathering place and information resource for the OASIS UBL (ISO/IEC 19845) International Standard. UBL defines a royalty-free library of standard electronic XML business documents such as purchase orders and invoices.
This is a community-driven site, and the public is encouraged to contribute content. Find the appropriate area to contribute to by hovering your pointer over the site area titles listed in orange banner above. This will briefly reveal the area description in a small pop-up box. For more detail, please see our policies and descriptions regarding posting content to certain areas.
In order to receive email notifications of posts to this site, please click top-right on your username next to "Logged in as:", or bottom-right "My account", in order to get to your account page. Go to the "Subscriptions" tab and you'll see 5 different sub-areas. The "categories" and "content types" sub-areas have a number of check-boxes. Click on any or all and then save your selection in order to receive an email notification of a new post in that area of this web site.
introduction to the type udt:IdentifierType
Hi,
I'm new to the UBL-specification and would like to understand the udt:IdentifierType which is used in e.g. the element cbc:ID in UBL-Invoice2.xsd. The type is derived through the common basic component.xsd.
Can someone give me some basic understanding how this type should be used? What does the different attributes schemeID, schemeName, schemeAgencyID, schemeAgencyName, schemeVersionID, schemeDataURI, schemeURI stand for? If possible please add values for these attributes to show usage of it.
thanks in advance!
Electronic Procurement opens doors to cross-border business within the EU
SRDC Ltd.: iSURF eDoCreator 1.0 beta
The iSURF eDoCreator 1.0 beta: Electronic Document Design and Customization Tool allows creation and customization of UN/CEFACT Core Components Technical Specification (CCTS) based document schemas. With its Web accessible user interface, the user are allowed to work collaboratively.
Balisage: The Markup Conference
European Commission rule changes to give boost to e-invoicing
The Commission says the aim of the rule change is to increase the use of electronic invoicing, reduce burdens on business, support small and medium sized enterprises (SMEs) and to help tackle fraud.
International Data Dictionary
The UBL 2.0 International Data Dictionary (IDD) provides descriptions and alternate business terms in a suite of languages.
Committee-published supporting materials
These are resources published by the UBL Technical Committee in support of working with UBL artefacts.
XPath files
These files enumerate all element and attribute information items described by the UBL 2 schemas.
UBL Maintenance Governance Procedures
This Committee Note describes the governance of the process to propose, accept and incorporate changes to the OASIS Universal Business Language (UBL) 2 specifications.
Converted from the former support page for UBL 2.0
These resources were submitted as part of the original UBL 2.0 support page:
http://www.oasis-open.org/committees/download.php/28723/support.htm
UBL Northern European Subset
UN/ECE Recommendation No. 31: Electronic Commerce Agreement
The Electronic Commerce Agreement is intended to serve the commercial requirements of business-to-business electronic commerce partners. It contains a basic set of provisions which can ensure that one or more electronic commercial transactions may subsequently be concluded by commercial partners within a sound legal framework.
Model UBL Letter Agreement and Commentary
The Model UBL Letter Agreement provides a template for contracts between trading partners who wish to treat particular UBL electronic documents as equivalent to their paper counterparts. The Model does not itself constitute a contract and should not be used without legal review, but together with the Commentary it provides a starting point for lawyers and a checklist for discussion with their clients.