MHonArc v2.5.0b2 -->
ubl message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ubl] Additional errors in UBL V1.0 cd2 Spreadsheet
Thanks Saito-san.
As I remember it, we were aware that there were further
definitions of this type (though it is good that you have
provided a list) and it was decided that these further definitions
could be left for the timebeing and we would just fix those in
the Invoice model. However, if this is an exhaustive list then
there may be some who'd like to see all of these changed.
I'm not sure how this would affect our schedule though so
personally I'd prefer that we stick to our initial plan. This
is partly because it wasn't agreed by all that these are in fact
'errors' since the wording could be seen as correct. (If there
were zero occurences then the BIE would not actually be used
so 'one or more' means 'when this is used then one or more'.) The
general feeling though was that it was worth our changing those
cases highlighted earlier to remove possible misinterpretation
but to leave the others, perhaps for later.
All the best
Stephen Green
----- Original Message -----
From: "Yukinori Saito" <saito-yukinori@fujielectric.co.jp>
To: "UBL TC" <ubl@lists.oasis-open.org>
Sent: Tuesday, August 31, 2004 8:30 AM
Subject: [ubl] Additional errors in UBL V1.0 cd2 Spreadsheet
> Dear Stephen Green or UBL TC members,
>
> We (JPLSC) held a face-to-face meeting in Tokyo today.
> We reviewed Japanese Translation Spreadsheets again.
> We noticed the following additional errors in UBL V1.0 cd2 Spreadsheet.
> The errors, which we think, are inconsistency between Cardinality and
> Definition.
> The Cardinality of the following BIEs are all "0..n". However, the
> Definition says "one or more".
>
> 1. Order
> AdditionalDocumentReference
> AllowanceCharge
>
> 2. Order Change
> OrderReference
>
> 3. Despatch Advice
> OrdeReference
>
> 4. Receipt Advice
> OrdeReference
> DespatchDocumentReference
>
> 5. Reusable
> (1) BuyerParty
> AdditionalAccountID
> (2) InvoiceLine
> OrderLineReference
> DespatchLineReference
> ReceiptLineReference
> (3) Item
> TaxCategory
> (4) LineItem
> AllowanceCharge
> (5) ReceiptLine
> OrderLineReference
> DespatchLineReference
> OrederedItemIdentification
> (6) SellerParty
> AdditionalAccountID
> (7) TransportHandlingUnit
> HandlingUnitDespatchLine
> ReceivedHandlingUnitReceiptLine
>
> My suggested fix is to change the Definition like the following.
> This suggested fix is that UBL TC has fixed the errors at the same errors
in
> Invoice like these.
>
> Insert '(optionally)' in front of 'with one or more' in the Definition.
>
> Best Regards,
> Yukinori Saito
> -------------------------------------------
> Yukinori Saito
> Fuji Electric Information Service Co., Ltd. (FIS)
> e-mail: saito-yukinori@fujielectric.co.jp
> Tel: +81-3-5435-7333 Fax: +81-3-5435-7513
> -------------------------------------------
>
>
>
> 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
.
>
>
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]