UBL-codelist-methodology-0.8-D1-20061124-1750z.zip Details

Document Details     TC Member Document View
Name * UBL-codelist-methodology-0.8-D1-20061124-1750z.zip (1MB)
Description The UBL Methodology for Code List and Value Validation used for contextual validation in XML instances of sets of coded values expressed outside of the instances.
Group OASIS Universal Business Language (UBL) TC
Folder Discussion drafts
Submitter Mr. Ken Holman
Date Submitted Friday, 24 November 2006 01:02pm
Document State Draft (A preliminary unapproved sketch, outline, or version.)
Modified By Mr. Ken Holman on Friday, 24 November 2006 01:03pm
Access This document is visible to OASIS Universal Business Language (UBL) TC and shared with:
  • OASIS Open (General Membership)
  • General Public

Document Revisions
Name # State Submitter Date Action
9
Draft
Mr. Ken Holman
2007-07-28
8
Draft
Mr. Ken Holman
2007-06-29
7
Draft
Mr. Ken Holman
2007-04-23
6
Draft
Mr. Ken Holman
2007-02-26
5
Draft
Mr. Ken Holman
2007-02-11
4
Draft
Mr. Ken Holman
2007-01-02
3
Draft
Mr. Ken Holman
2006-11-24
This doc
2
Draft
Mr. Ken Holman
2006-10-23
1
Draft
Mr. Ken Holman
2006-09-16
0
Draft
Mr. Ken Holman
2006-06-18

Comments  
Subject & Text Submitter Date Action
Initial comment by submitter
Each of the following are comments received and the disposition of those comments:

(1) Methodology works for documents other than UBL
- changed the title of the methodology

(2) Methodology works for information items other than codes
- the methodology refers now to "values" and "value lists" instead of "codes" and "code lists", so as to be inclusive of lists of values for identifiers
- example expanded to include a list of identifiers

(3) Need to support embedded documentation in the context association file
- added support for embedded constructs in foreign namespaces to be used for documentation
- split human-readable identification into three parts:
- title
- identification string for tracking purposes in intermediate files
- description

(4) Need to masquerade external meta data in order to support restriction of a published code list
- a subset code list necessarily has different list meta data than the list from which it is derived
- validation may be required against the complete list, though trading partners are using only a subset
- the declaration of an external code list provides for specifying overriding meta data so that validation sees the masquerade of the full code list and not the actual meta data of the restricted code list

(5) Need to better explain extending a published code list with additional values
- an example is added illustrating extending the UBL payment means code list with an additional code agreed upon between trading partners

(6) Need to add an overview diagram
- two overview diagrams added

(7) Differing specification of similar contexts is confusing to the reader (showing two ways of doing the same thing confuses the reader as to which way should be done)
- changed the two similar constraints to be expressed in the same fashion
- added a new constraint that requires the differing specification of context

(8) Need to add definitions and key concepts
- some have been added but I would like input as to which other terms and concepts should be included to improve on the document

(9) Need to improve error messages to find the information item in error
- a validation error now reports the fully-qualified XPath address to the information item that triggers an error
Mr. Ken Holman
2006-11-24
---