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

3. Declaring controlled vocabularies
[> 4.][< 2.0.1][^^^]
3.0 Declaring controlled vocabularies
[> 4.][< 3.][^^][^^^]
Standards are in development for the non-schema-based representation of a list of coded values
[[1] - trading partners may wish to trim or augment the list of coded values acceptable
 [1] - trading partners may wish to use different controlled vocabularies for a given information item found in different document contexts
 [1] - the representation of individual coded values includes documentary information and metadata
[[2] - for detailed value description
 [2] - for long-term maintenance and understanding
][1] - OASIS genericode 1.0
[[2] - [http://docs.oasis-open.org/codelist/genericode]
 [2] - an XML representation standardized by the OASIS Code List Representation Technical Committee
 [2] - [http://www.oasis-open.org/committees/codelist/]
 [2] - "Defining an XML format for interchange, documentation and management of code lists (a.k.a. controlled vocabularies or coded value enumerations) in any processing context"
[[3] - not obliged to use XML format inside the application
 [3] - very common to compile the XML interchange format into an internal processing format
[[4] - e.g. conversion to XSLT
 [4] - e.g. implementation in database stored procedures
][3] - XML is designed for interchange and is not always conveniently structured for real-time processing
]]]
One could use schema enumerations but ...
[[1] - too inflexible for globally-defined information items
[[2] - cannot have different sets of values in different document contexts for a globally-defined information item
][1] - modifying the schemas means using non-standardized schema expressions
[[2] - not bad in and of itself but requires extra assurances for compatibility
 [2] - structural and lexical validation is assured if the standardized schema expressions are treated as read-only
]]
Meta-data-only code list are important as placeholders
[[1] - effectively an infinite set of all possible codes satisfying the lexical rules
 [1] - indicating that a particular information item's value is from a controlled vocabulary but that there is no controlled vocabulary listing a set of codes
 [1] - e.g. only 18 of 91 UBL code lists are published with values, 73 uniquely-categorized code lists have only meta data
 [1] - users have the option of restricting the infinite list into a finite list
]

*** 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 Code List Implementation 2009-02-09 22:30UTC//EN
Practical Code List Implementation
First Edition - 2009-02-09
ISBN 978-1-894049-22-1
Copyright © Crane Softwrights Ltd.