[Accessibility conventions are described at the bottom of the page]

A. OpenOffice 3 UBL customization environment
[> A.1][< 14.3.1][^^^]
A.1 OpenOffice 3 UBL customization environment
[< A.][^^][^^^]
A.1.1 OpenOffice 3 UBL customization environment
[> A.1.2][< A.][^^][^^^]
Crane Softwrights Ltd.'s profile2ods package is a pair of OpenOffice 3 XML filters
[[1] - enables OpenOffice 3 to specify and save a subset of the published UBL 2.0 document models
 [1] - supports the export of developer resources supporting a subset specification
]
Developer resources:
[[1] - human-readable HTML reports for consistency review
[[2] - see [Figure 3.8] for an example
 [2] - all of Crane's model reports are created with this tool using 32 profiles
[[3] - one profile includes all document types
 [3] - one profile for each document type
]][1] - pruned W3C Schema XSD files
[[2] - see [Expressing a conformant UBL subset - Section 10.0.1] for the role these play
][1] - synthesized XSLT and Python instance filters
[[2] - see [Figure 11.1] for the role these play
][1] - XML and text document context XPath reports
[[2] - see [Chapter 7.] for the roles these play
]]
The package is found as a ZIP file linked from the sales page for this book
[[1] - http://www.CraneSoftwrights.com/sales/publd/
 [1] - your book purchase password is needed to get access to the package
]
The readme.html documentation includes all of the necessary documentation to install, uninstall and use these filters.
A new profile document is created from scratch using the profileCustomization template in "filter 1":
[Figure 15.1: New document from template menus
A screen shot illustrates the invocation of the menu items File / New / Templates and Documents / Profile Filter 1 of 2 by Crane Softwrights Ltd. / profileCustomization.
]
There are thirty-seven sheets when editing the profiles:
[[1] - Configuration
[[2] - managing the exportation and user interface properties
 [2] - specifying the artefacts to be created during the exportation process
][1] - Profiles
[[2] - managing the meta data for each profile
][1] - Summary document types
[[2] - managing which document types are in which profiles
][1] - Individual document types (32)
[[2] - managing which components are in each document type for each profile
][1] - Help
[[2] - context-sensitive help information
][1] - Support
[[2] - there is no user serviceable data in this sheet
]]
The customization is saved as an OpenOffice ODS file for maintenance
[[1] - faster operation than using the XML format
 [1] - preserves all information, including user-defined meta data
]
Creating the artefacts is triggered by exporting the document using the "Profile Export Filter"
[[1] - artefact creation governed by settings on the configuration page
]
A.1.2 Configuration sheet
[> A.1.3][< A.1.1][^][^^][^^^]
Used to configure the various export activities
[Figure 15.2: Configuration sheet
A screen shot illustrates the configuration sheet.
]
[[1] - location of input schema files to be pruned
 [1] - nature of outputs
[[2] - "permitted" subsets include all items with explicitly specified cardinality
 [2] - "strict" subsets include only items with explicitly specified cardinality
][1] - location of output artefact directories
 [1] - indications of export activity for each output artefact directory
 [1] - specification of language for definitions and business terms
]
Use File / Export... to emit the selected artefacts
[[1] - the primary output file is a text file reporting the results of exporting multiple UBL artefacts
]
Example export report from the hands-on exercise:
[Example A-1: Example export report
01  Crane's OASIS UBL 2.0 profile editor report output
02  --------------------------------------------------
03  
04  Run time: 2009-02-11 20:50z
05  Determining requirements...
06  Analyzing project information...
07  Export version suffix:
08  Export nature: Strict
09  Producing results for profiles: Exercise
10  
11  Profile short name: Exercise
12  Profile title: Exercise - Customization exercise
13  Models in profile: CommonLibrary
14  
15  HTML production:
16   Output HTML report file: file:///c:/publd/exer/Exercise/Exercise.html
17  Schema production: not active
18  Filter production: not active
19  XPath full text production: not active
20  XPath minimal text production: not active
21  XPath XML production: not active
22  XPath Instance production: not active
23  
24  End of report.
]
A.1.3 Profiles sheet
[> A.1.4][< A.1.2][^][^^][^^^]
Used to define properties of profiles
[Figure 15.3: Profiles sheet
A screen shot illustrates the profiles sheet.
]
[[1] - column action is only engaged when files are saved and opened as XML
[[2] - very long tasks to save and open the files as XML
 [2] - user meta data is not preserved when using the XML format for saving the information
 [2] - much more efficient to save and open the files in ODS when not needing to change the number of profiles
][1] - the short name property is an identifier used for uniqueness across all profiles
[[2] - participates in file naming conventions during export
][1] - all other properties are documentary and do not impact on the specification
[[2] - defining the title is useful for distinguishing the titles of reports from various configurations
]]
Example values drawn from BII documents for illustration
[[1] - Domain:
[[2] - Post award procurement
][1] - Process:
[[2] - Ordering - Fulfillment - Billing - Payment
][1] - Title:
[[2] - Advanced Procurement with Dispatch
][1] - Document reference:
[[2] - CEN/ISSS WS/Profile BII13
][1] - Description:
[[2] - Profile description for Advanced Procurement with Dispatch
][1] - Commentary:
[[2] - e.g. status information, participants, discussion, etc.
]]
A.1.4 Document types sheet
[> A.1.5][< A.1.3][^][^^][^^^]
Used to specify the inclusion of document types in each profile
[Figure 15.4: Document types sheet
A screen shot illustrates the document types sheet.
]
[[1] - any non-blank value can be used (the programmatic default is "X")
 [1] - data entry in white cells is used during the export process
 [1] - data entry in yellow cells is ignored during the export process and the XML save format
 [1] - defining a profile's short name enables white cells on this sheet
 [1] - specifying a document type on this document types sheet enables the corresponding white cells on the corresponding document type sheet
]
A.1.5 Document type sheet
[> A.1.6][< A.1.4][^][^^][^^^]
Used to specify cardinalities of items and item-level user-defined meta data in each profile
[Figure 15.5: Document type sheet
A screen shot illustrates the document type sheet.
]
[[1] - each new cardinality cell is constrained based on the model cardinality
 [1] - items with unspecified new cardinalities are included in permitted models but not in strict models
 [1] - data entry in white cells is used during the export process
 [1] - data entry in yellow cells is ignored during the export process and the XML save format
]
User-defined meta data can be defined on each sheet
[[1] - instructions for modification of the cell widths and headings are in the readme.html file
]
A.1.6 Profile tool methodology
[< A.1.5][^][^^][^^^]
Objective is to configure and support a customization of UBL
[[1] - what UBL standard constructs are needed?
 [1] - what UBL standard optional constructs can be discarded?
 [1] - what extensions need to be added?
]
The OpenOffice environment is for collaboration and specification
[[1] - export human-readable HTML report for review
[[2] - are all of the constructs pruned as required?
 [2] - are any constructs over-pruned to the point of being impossible to be UBL valid?
][1] - when ready for testing or deployment, export other artefacts
[[2] - schemas for validation of the instance against the subset specification
 [2] - filters for pruning incoming UBL instances to test conformance against the subset
 [2] - text and markup reports as developer tools for stylesheets and other applications acting on subset instances
]]
Extension components and new document types are crafted by other tools
[[1] - the profile tool's sole purpose us to prune the published UBL 2.0 document models
 [1] - using other means create the replacement "Extension Content Datatype" module and new document schemas
]
Customization validation environment created from old and new components
[[1] - copy all schema fragments from UBL 2.0 update package
 [1] - overlay fragments replacing complete schemas with the pruned schemas
 [1] - overlay fragment replacing extension data type module with customization extension
 [1] - add customization extension support fragments
 [1] - see [Figure 13.5] for the schema replacements
]
Customization validation processing model
[[1] - use a filter configured to only pass those constructs allowed for the customization
 [1] - see [Figure 5.2] for the processing model
[[2] - the version filter (F) is replaced with the customization filter
]]


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.