Diff for Customizations
Thu, 2008-05-15 09:02 by ktolle | Sun, 2009-02-15 16:55 by gkholman | ||
---|---|---|---|
< previous diff | next diff > | ||
Changes to Body | |||
Line 1 | Line 1 | ||
<p>
| <p>
| ||
- | <em><strong> "It is not the strongest of the species that survives,<br />
| + | <em><strong>"It is not the strongest of the species that survives,<br />
|
nor the most intelligent,<br />
| nor the most intelligent,<br />
| ||
but rather the one most responsive to change."</strong></em><br />
| but rather the one most responsive to change."</strong></em><br />
| ||
- | <span style="color: red">Charles Darwin</span>
| + | <span style="color: red">Charles Darwin</span>
|
</p>
| </p>
| ||
<p>
| <p>
| ||
- | In UBL you have the opportunity to react on changes and given requirements by customizing the existing UBL documents following certain rules.<strong>This "Customization Area" of ubl.xml.org allows you to present and discuss your customizations of UBL done or planed </strong>with others in order to reach the highest level of interoperability by re-using existing customizations and to avoid uncontrolled growth of potential wrong customizations.
| + | In UBL you have the opportunity to react on changes and given requirements by customizing the existing UBL documents following certain rules.<strong>This "Customization Area" of ubl.xml.org allows you to present and discuss your customizations of UBL done or planed </strong>with others in order to reach the highest level of interoperability by re-using existing customizations and to avoid uncontrolled growth of potential wrong customizations.
|
</p>
| </p>
| ||
<p>
| <p>
| ||
- |
| + | <u><span style="color: blue">Customization</span> </u>
|
</p>
| </p>
| ||
<p>
| <p>
| ||
- | <span style="color: blue">Customization</span>
| + | 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>
| ||
<p>
| <p>
| ||
- | In many small-business environments, standard forms can satisfy
| + | It is true, however, that different industries have different data requirements, and this has led in the past to the proliferation of variants even in such tightly controlled standards as X12, EDIFACT, and RosettaNet.
|
- | 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>
| ||
<p>
| <p>
| ||
- | It is true, however, that different industries have different
| + | 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. For example, each UBL 2.0 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.
|
- | data requirements, and this has led in the past to the
| + | |
- | proliferation of variants even in such tightly controlled
| + | |
- | standards as X12, EDIFACT, and RosettaNet.
| + | |
</p>
| </p>
| ||
<p>
| <p>
| ||
- | UBL does not attempt a complete solution to this problem but
| + | <strong>Supporting materials produced by customizations</strong>
|
- | instead takes an extremely pragmatic approach that should allow
| + | </p>
|
- | satisfactory solutions in the great majority of real-world cases.
| + | <p>
|
- | For example, each UBL 2.0 schema contains an optional extension
| + | [[Converted from the former support page for UBL 2.0]]
|
- | 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>
| ||
Customizations
"It is not the strongest of the species that survives,
nor the most intelligent,
but rather the one most responsive to change."
Charles Darwin
In UBL you have the opportunity to react on changes and given requirements by customizing the existing UBL documents following certain rules.This "Customization Area" of ubl.xml.org allows you to present and discuss your customizations of UBL done or planed with others in order to reach the highest level of interoperability by re-using existing customizations and to avoid uncontrolled growth of potential wrong customizations.
Customization
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.
It is true, however, that different industries have different data requirements, and this has led in the past to the proliferation of variants even in such tightly controlled standards as X12, EDIFACT, and RosettaNet.
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. For example, each UBL 2.0 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.
Supporting materials produced by customizations