spreadsheet errors exposed in UBL 2.0 PRD2 Schema

[Tim McGrath <tmcgrath@portcomm.com.au>]

in the draft set of schemas sent by sylvia yesterday 
(http://lists.oasis-open.org/archives/ubl/200607/msg00007.html) i note 
the error log entry that says...

>
> BBIE "Status. Reason. Code": DT conflict. Created element "ReasonCode_2".


this is because we have two BBIEs called Reason.Code, one in Allowance 
Charge and one in  Status.  This would normally be considered a 
legitimate re-use of Reason.Code.  however, the Allowance Charge. Reason 
Code uses the datatype Allowance Charge Reason_ Code. Type and the 
Status. Reason . Code doesn't (and should not).  This is an error in the 
spreadsheet.

it seems to me that these are two different reason codes.  the Reason. 
Code in Allowance Charge should be qualified for the specific data type 
it uses.  So its DEN should be Allowance Charge. Allowance Charge_ 
Reason. Code (qualifying the property term) and its UBLName is therefore 
AllowanceChargeReasonCode.  for the same reason (pun intended) we should 
qualify the Reason. Code in Status as being a Status. Status_ Reason. 
Code.   in fact i suspect were BBIEs are code types there is often a 
qualifier.

this solution is also consistent with how we deal with Exemption and 
Reject Reason Codes.

this leads me to suggest we start a change request for making editorial 
changes to the spreadsheets?  as peter is on leave Alan Lemming 
(allem@wmdata.com) is taking his role as editor.  these changes should 
only be applied if we have cause to generate a new set of schemas after 
the draft set Syvlia posted yesterday.

i have already sent the following to the PSC list...

* we are still calling the document element UBLVersion, it should be UBL 
Version (two words). this is in all document models
* in Receipt Advice we have cardinality of 0..n for LineCountNumeric - 
not what i think we meant. (should be 0..1)
* we still have some cardinalities expressed as "1..1" and others as 
just "1" (eg ReceiptAdvice)  (should be just "1")
* in RemittanceAdvice the definitions of PayerReference and 
InvoicingPartyReference (and their examples) copy that of 
PaymentOrderReference. they need their own definitions (and examples)
* in the Reminder spreadsheet, the worksheet name says "Invoice".

also from the TSC....
*  the cardinality of ContainedPackage within Package is 0..1 , it 
should be 0..n.


swebb@gefeg.com wrote:

>The document revision named UBL 2.0 PRD2 Schema (UBL2.0_PRD2.zip) has been
>submitted by Ms. Sylvia Webb to the OASIS Universal Business Language (UBL)
>TC document repository.  This document is revision #3 of UBL 2.0_WD5.zip.
>
>Document Description:
>Public Review Draft 2 Schema with missing ExtensionElementType
>
>View Document Details:
>http://www.oasis-open.org/apps/org/workgroup/ubl/document.php?document_id=19038
>
>Download Document:  
>http://www.oasis-open.org/apps/org/workgroup/ubl/download.php/19038/UBL2.0_PRD2.zip
>
>Revision:
>This document is revision #3 of UBL 2.0_WD5.zip.  The document details page
>referenced above will show the complete revision history.
>
>
>PLEASE NOTE:  If the above links do not work for you, your email application
>may be breaking the link into two pieces.  You may be able to copy and paste
>the entire link address into the address field of your web browser.
>
>-OASIS Open Administration
>
>  
>

-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160
web: http://www.portcomm.com.au/tmcgrath