[Accessibility conventions are described at the bottom of the page]
*** This is a free preview excerpt of a commercial publication. ***

10. Customization specification
[> 11.][< 9.0][^^^]
10.0 Customization specification
[> 10.0.1][> 11.][< 10.][^^][^^^]
At least two ways to view interoperability when customizing UBL for one's own purposes
[[1] - model-level interoperability (UBL compatibility)
[[2] - objective to be create new information items and messages based on UBL library of constructs
][1] - document-level interoperability (UBL conformance)
[[2] - objective to be able to interchange UBL messages
]]
In these two diagrams, the thin-edged ovals represent the set of vocabulary information items (names and namespaces) for an implementation of UBL, while the thick-edged ovals represent the basis upon which the vocabularies are derived
[[1] - the top diagram illustrates how there is no overlap of vocabularies between UBL, the Korean Customs Service implementation of UBL and the New TradeNet implementation of UBL
[[2] - the business objects in all vocabularies are derived from UBL business objects
][1] - the bottom diagram illustrates how there is a big overlap of vocabulary between UBL, the North European Subset (NES), and the BII vocabulary
[[2] - both the NES and BII vocabularies use a subset of the UBL vocabulary
[[3] - opportunity to add extensions, though in practice this hasn't yet happened
][2] - all three vocabularies are based on the information items and unqualified data types of UBL, thus the XSD module is utilized in the declaration of the constructs
]]
[Figure 10.1:
The diagram is split horizontally into two halves.
The top half is titled "Model-level interoperability" and subtitled "UBL Compatibility". Above an oval labeled "UBL" annotated with "base business object definitions" are three separated and non-overlapping ovals labeled "Korean Customs Service", "UBL" and "New TradeNet", each annotated with "vocabulary and namespaces".
The bottom half is titled "Document-level Interoperability" and subtitled "UBL Conformance". Above an oval titled "UBL UDT" and annotated with "base information items and unqualified data types" are three overlapping ovals titled "UBL", "NES" and "BII" where the group of three is annotated with "vocabulary and namespaces".
]
10.0.1 Expressing a conformant UBL subset
[> 11.][< 10.0][^][^^][^^^]
The W3C schema modules for a conformant UBL subset express the customization constraints
[[1] - customization fragments partially overwrite a copy of the UBL xsd/ and xsdrt/ directories
]
The following subset schema fragments replace the UBL schema fragments:
[[1] - the document schema (e.g. Statement, Waybill, etc.)
 [1] - the definition of ABIE (and, therefore, ASBIE) constructs
 [1] - the definition of BBIE constructs
 [1] - all unused constructs are removed from the fragments
]
[Figure 10.2: Schema replacements for customization
A chart illustrating the dependencies of schema fragments has boxes for each schema file, starting with the Document Schema box at the top representing an invoice, or an order, or other UBL document, in that document type's namespace.
The Document Schema imports the Common Aggregate Components (cac), Common Basic Components (cbc) and Common Extension Components (ext) fragments.
The Common Aggregate Components (cac) fragment imports the Common Basic Components (cbc), Unqualified Datatypes (udt) and Qualified/Specialized Datatypes (qdt) fragments.
The Common Basic Components (cbc) fragment imports the Unqualified Datatypes (udt) and Qualified/Specialized Datatypes (qdt) fragments.
The Qualified/Specialized Datatypes (qdt) fragment imports the Unqualified Datatypes (udt) fragment.
The Common Extension Components (ext) fragment imports the Common Basic Components (cbc) and Unqualified Datatypes (udt) fragments, and includes the Extension Content Datatype (ext) fragment.
Shown to the side in a box labeled "Customization Restriction Replacement Schemas" are the replacement Customization Document Schema, Customization Aggregate Components (cac) and Customization Basic Components (cbc) fragments as required for the customization.
]

*** This is a free preview excerpt of a commercial publication. ***

This is an accessible version of Crane's commercial training material. The content has been specifically designed to assist screen reader software in viewing the entire textual content. Figures are replaced with text narratives.

Navigation hints are in square brackets:
[Tx.x] and [Fx.x] are textual representations of the applicability icons;
[digit] indicates list depth for nested lists;
[link [URL]] indicates the URL of a hyperlink if different than link;
[EXAMPLE] indicates an example listing of code;
[FIGURE] indicates the presence of a figure replaced by its description;
[>] jumps forward;
[<] jumps backward;
[^] jumps to start of the section;
[^^] jumps to the start of the chapter;
[^^^] jumps to the table of contents.
Suggestions for improvement are welcome: [info@CraneSoftwrights.com]
Book sales: [http://www.CraneSoftwrights.com/links/trn-acc.htm]
Information: [http://www.CraneSoftwrights.com/links/info-acc.htm]
This content is protected by copyright and, as there are no means to protect this accessible version from plagiarism, please do not make any commercial edition available to others.

+//ISBN 1-894049::CSL::Presentation::UBL//DOCUMENT Practical Universal Business Language Deployment 2009-02-12 13:50UTC//EN
Practical Universal Business Language Deployment
Third Edition - 2009-02-12
ISBN 978-1-894049-23-8
Copyright © Crane Softwrights Ltd.