Re: Final Draft UBL 2.0 Schemas

[jon.bosak@sun.com]

I'm taking the message below to mean:

 - Yes, there should be enumerated values for hardwired UBL code
   lists in the file UBL-SpecializedDatatypes-2.xsd.

 - The enumerations aren't there because the spreadsheet for
   UBL-SpecializedDatatypes-2.xsd doesn't contain the appropriate
   file names.

I'm further assuming that the schemas are (at this point) known to
be defective only in that they will not trap bad values for the
hardwired code lists using xsd validation.

If any of this is incorrect, please tell me.

If this is correct, then unless someone can fix the problem and
have the revised schemas to me by the end of the day today (Friday
23 December), I propose to use the schemas as they are now and
explain this as a known issue in the release notes.

Jon

   Date: Thu, 22 Dec 2005 14:25:18 -0800
   From: Sylvia Webb <swebb@gefeg.com>
   Cc: ubl@lists.oasis-open.org

   All,

   I found the problems.  One is with the qDT spreadsheet. EDIFIX creates a
   Note entry based on the filename in Column S with this filename and uses it
   for the export process.

   The names are either missing, inconsistent, or have extensions like .doc or
   preceded by a URL.  

   The first value in Column S must contain "= filename.txt" without the
   quotes. 

   The master spreadsheets need to be corrected and resubmitted.

   The second problem is with one of the EDIFIX configuration files. Betty, I
   will send you a fix for this.

   I am attaching a older spreadsheet that included the correct code list
   filenames. This file should only be used for information purposes and not a
   template.

   Regards,
   Sylvia