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

9. UBL customization
[> 10.][< 8.0][^^^]
9.0 When to customize UBL
[> 10.][< 9.][^^][^^^]
Many criteria are considered when determining when and how to customize UBL
[[1] - the use of UBL
[[2] - stakeholders
 [2] - profiles of deployment
 [2] - business vs. technical
][1] - the scope of UBL
[[2] - more documents in UBL than needed
 [2] - fewer documents in UBL than needed
][1] - the size of UBL
[[2] - more information items in UBL than needed
 [2] - fewer information items in UBL than needed
][1] - the perspective of UBL
[[2] - closed environment or open environment?
[[3] - compatible or conformant?
][2] - taking advantage of existing UBL-based resources
]]
The UBL committee is not a certification authority
[[1] - it is not in the OASIS UBL Technical Committee charter to review, comment, measure or certify a UBL customization
[[2] - responsible only for "Standard UBL" and associated publications
 [2] - responsible to define conformance and compatibility but not enforce it or measure it
 [2] - committees can claim conformance or compatibility of their customization, but it is up to users to measure or confirm such is true
][1] - however a community defines a customization is up to the community
[[2] - following TC guidelines may help in identifying and meeting objectives
 [2] - one is not obliged to follow TC guidelines
]]
There are common basic steps in the process of creating a UBL customization
[[1] - define the profile
[[2] - what business function is being satisfied by the customization?
][1] - define the processes
[[2] - which transactions are needed to enact the business function?
][1] - determine the documents
[[2] - which documents are used in the transactions?
][1] - determine the document contents
[[2] - what information items are in the documents?
][1] - specify the restrictions and extensions
[[2] - which existing constructs are not needed and therefore are pruned
 [2] - which non-existent constructs must be added to the existing constructs
][1] - emit the other artefacts
[[2] - what support will the user community need?
]]

*** 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.