How does UBL cope with the need for customization to meet different business requirements?
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 t
Related Questions
- I would like to sell Qwest products, but am unable to meet the sales requirements listed for Business Partner Program membership. How can I still participate?
- Since all homes must meet the requirements of the Manitoba Building Code, what makes an R-2000 Home different?
- How does UBL cope with the need for customization to meet different business requirements?
