Diff for History of UBL
Tue, 2008-04-29 00:46 by tim.mcgrath | Thu, 2008-05-29 13:40 by carolgeyer | ||
---|---|---|---|
< previous diff | next diff > | ||
Changes to Body | |||
Line 16 | Line 16 | ||
success of adoption and the emergence of multiple uses and applications
| success of adoption and the emergence of multiple uses and applications
| ||
like browsers, publishers, booksellers, and so on. <br />
| like browsers, publishers, booksellers, and so on. <br />
| ||
- | <br />
| ||
<br />
| <br />
| ||
After a 3-year effort the first version of UBL was released . This first
| After a 3-year effort the first version of UBL was released . This first
| ||
Line 22 | Line 21 | ||
xCBL and leveraged the knowledge of UN / EDIFACT solving
| xCBL and leveraged the knowledge of UN / EDIFACT solving
| ||
a basic eprocurement business process, defining the order , logistical documents and invoice. <br />
| a basic eprocurement business process, defining the order , logistical documents and invoice. <br />
| ||
- | <br />
| ||
<br />
| <br />
| ||
This first version was used
| This first version was used
| ||
Line 43 | Line 41 | ||
A dictionary of terms that allows international preservation the unique
| A dictionary of terms that allows international preservation the unique
| ||
semantic components in different languages (Spanish, Chinese,
| semantic components in different languages (Spanish, Chinese,
| ||
- | Japanese, Korean and Danish) </li>
| + | Japanese, Korean and Danish)</li>
|
</ul>
| </ul>
| ||
<p>
| <p>
| ||
- | <br />
| ||
- | <br />
| ||
In addition to the
| In addition to the
| ||
development of these elements were also detected some technical
| development of these elements were also detected some technical
| ||
problems or difficulties. Challenges that have not had a technical
| problems or difficulties. Challenges that have not had a technical
| ||
solution and who have faced and resolved in the second version of the
| solution and who have faced and resolved in the second version of the
| ||
- | standard. Basically <br />
| + | standard. Basically: <br />
|
- | <br />
| + | |
</p>
| </p>
| ||
<ul>
| <ul>
| ||
Line 62 | Line 57 | ||
schemes in accordance with regulatory requirements sectoral and / or
| schemes in accordance with regulatory requirements sectoral and / or
| ||
national, specifically, the rules of restriction and extension of the
| national, specifically, the rules of restriction and extension of the
| ||
- | schemes. </li>
| + | schemes.</li>
|
</ul>
| </ul>
| ||
<p>
| <p>
| ||
- | <br />
| ||
- | <br />
| ||
In November 2006 UBL 2.0 was released. That new release resolves all
| In November 2006 UBL 2.0 was released. That new release resolves all
| ||
these issues and further expands the UBL 1.0 eprocurement process with
| these issues and further expands the UBL 1.0 eprocurement process with
| ||
Line 74 | Line 67 | ||
to European
| to European
| ||
legislation in the area of procurement and electronic invoicing.
| legislation in the area of procurement and electronic invoicing.
| ||
+ | </p>
| ||
+ | <p>
| ||
+ | In May 2008 <a href="http://docs.oasis-open.org/ubl/os-UBL-2.0-update/os-UBL-2.0-update.html">UBL 2.0 Errata 01</a> was <a href="http://lists.oasis-open.org/archives/tc-announce/200805/msg00011.html">approved by the OASIS UBL Technical Committee</a>.
| ||
</p>
| </p>
| ||
History of UBL
In 2001, within OASIS, Jon Bosak, one of the inventors of XML markup language proposed the creation of a technical committee with the objective of creating a first set of business documents based on the CCTS (ISO 15000 part 5) to facilitate electronic business adoption tasks by companies and public administrations. This technical committee was called Universal Business Language.
The
major advantages of this new approach to the world of electronic data
interchange compared to existing models so far are that for the first
time defines electronic documents according to the CCTS and secondly
the TC will to produce an open standard, royalty-free and free of use. Those are
the same conditions that led the Web to the
success of adoption and the emergence of multiple uses and applications
like browsers, publishers, booksellers, and so on.
After a 3-year effort the first version of UBL was released . This first
version 1.0 of UBL was based on the preliminary work carried out by
xCBL and leveraged the knowledge of UN / EDIFACT solving
a basic eprocurement business process, defining the order , logistical documents and invoice.
This first version was used
to develop many elements that have been crucial in the development of
version 2.0. For example
- The naming and design rules ( NDR), which give names to define the components ,
- The mechanisms and devices that facilitate the transformation of XML documents into HTML or PDF readable by individuals,
- A dictionary of terms that allows international preservation the unique semantic components in different languages (Spanish, Chinese, Japanese, Korean and Danish)
In addition to the
development of these elements were also detected some technical
problems or difficulties. Challenges that have not had a technical
solution and who have faced and resolved in the second version of the
standard. Basically:
- Treatment of code lists, its definition and validation, as well as mechanisms to its restriction based on specific business requirements, and
- Mechanisms for customization of the schemes in accordance with regulatory requirements sectoral and / or national, specifically, the rules of restriction and extension of the schemes.
In November 2006 UBL 2.0 was released. That new release resolves all these issues and further expands the UBL 1.0 eprocurement process with many new commercial transactions, and therefore new electronic documents. In addition, all the documents and components in UBL 1.0 have been reviewed to conform to European legislation in the area of procurement and electronic invoicing.
In May 2008 UBL 2.0 Errata 01 was approved by the OASIS UBL Technical Committee.