RE: [ubl] 1.0 Issues list where is the documentation of my 226 reusable differences?

["Michael Dill" <dill2@gefeg.com>]

Stephen,
as I remember we started a QA and said that the comparision of UBL Package
Spreadsheet with the EF generated ones is one of the ways to do it.
Meanwhile you noted a number of discrepancies. In order to follow a
systematic approach, I have the following questions:
In one of yours emails you said that you did the comparision job already and
Mavis does not have to do anything. Did I understand you correctly? Please
confirm explicitly, if possible.

If yes, then, please send to Anne the documentation of the complete
spreadsheet comparision. In respect of reusable I found 226 differences
between Package and EF generated UBL spreadsheet. And I did not compare all
comparable entries. E.g. have you compared the Definition? Thus I'd like to
have a complete list of everything, which is comparable, or we should ask
Mavis to do it, as she agreed to do. Imho we have to go through the data in
a systematic manner.

Best Regards,
Michael

-----Original Message-----
From: Stephen Green [mailto:stephen_green@seventhproject.co.uk]
Sent: 09 June 2004 06:03
To: ubl@lists.oasis-open.org
Subject: Re: [ubl] 1.0 Issues list


Anne,

> Michael, Stephen, Mavis: if you consider your investigation complete
> enough at this time I can add the issues raised in your comparison as
> best as I can glean from the email thread, but a summary would be helpful.
>

Here are the issues/bugs I found with a diff between the EF generated
spreadsheets
and the package spreadsheets. (A reminder that Michael found other issues
too.)

A. Schema Bugs

1. Operator Code (in 'reusable')   this should  have DataType Qualifier
'Operator'
    in the EF model but this is missing.
    In the CAC Schema the OperatorCode element is defined as
     ' type="udt:CodeType"'
    when it should be
     ' type="opr:OperatorCodeType"'
     In the CAC Schema the Operator Code codelist Schema module isn't
imported
     when it should be (with namespace prefix 'opr')

2.  PaymentMeansCode (in 'reusable')  this is incorrectly named in the CAC
Schema
     PaymentMeansTypeCode since it was changed to PaymentMeansCode.
     The DataType Qualifier is correct: 'Payment Means' but the Property
Term is
     incorrect as 'Means Type' when it should be 'Payment Means' and the
Property
     Term Qualifier is incorrect with 'Payment' when it should be empty.

     There is a further, error in the package sdt spreadsheet (see below)

B.  1.0cd Package Model Spreadsheet Bugs/Issues

1.  StreetName (in 'reusable')   this has Representation Term 'Text' whereas
     AdditionalStreetName has it as 'Name' (as does the EF model)

2.   AllowanceChargeReasonCode (in 'reusable')  has incorrect DataType
      'Code. Type' which should be 'Allowance Charge Reason_ Code. Type'
      and the DataType Qualifier is 'Reason Code'
      when it should be 'Allowance Charge Reason'.

3.   PaymentMeansCode (in 'specialized datatypes' / text file) the codelist
text file
      is named 'PaymentMeansTypeCode' (and referenced as such in the
spreadsheet).
      It should be 'PaymentMeansCode'.

4.   LineExtensionTotal in OrderChange   has the DataType Qualifier 'UBL'
missing


Note: Some of these may duplicate the bugs reported by Chee-Kai (e.g. A1,
A2, B2 and B3). Chee-Kai's analysis revealed other bugs not revealed using
this particular diff.

All the best

Steve





To unsubscribe from this mailing list (and be removed from the roster of the
OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/ubl/members/leave_workgroup.php
.