MHonArc v2.5.0b2 -->
ubl message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Definitions for re-used ABIEs was:Re: [ubl] for Anne(?) AW: [ubl]Issues triage ad issue 18,2
i think what you are talking about is the definitions of the ASBIE for Line
Item. Details. That is, where Line Item. Details is re-used it has a different
definitions.
So the place to look for its different usages is at the ASBIE level. We
dont need a qualifier as the context of the ABIE in which the ASBIE appears
gives that.
The qualification (if any) of any ABIE happens when it is re-used (ie when
it is used in an ASBIE) so that is where the qualifers should be.
So we have things like...
ASBIE Order Line. Line Item. defined as "information directly relating to
a line item of a transaction. It identifies the item but only includes details
about the item that are pertinent to one occurrence on a line item, e.g.
quantity etc."
ASBIE Order Line. Seller Proposed_ Substitute Line Item. defined as "the
item(s) that the seller proposes for the substitution - the original ordered
quantity, pricing etc, which may be different from the substituted item.
It is assumed that hazard and shipment details etc will be the same."
ASBIE Order Line. Seller Substituted_ Line Item. defined as "item(s)
replaced by the seller - the original ordered quantity, pricing etc which
may be different from the substituted item. It is assumed that hazard and
shipment details etc will be the same."
and
ASBIE Order Line. Buyer Proposed_ Substitute Line Item. defined as "alternative
item(s) acceptable to the buyer - quantity, pricing etc which may be different
from the preferred item. It is assumed that hazard and shipment details etc
will be the same."
Al these are re-uses of LineItem. Details. All have defintions that relate
to their re-use. None require any qualification of the object class. The
qualification is of the property term (in other words the target object class)
of the ASBIE. The EDIFIX view you attached is not showing the correct definitions.
Saito-san's question is not related to definitions - it is terminology. elsewhere
we refer to seller party but in one place we use the term customer - clearly
this was an oversight and re-inforces the need for a controlled vocabulary.
Michael Dill wrote:
608de23e@gefeg.local">
Hi Anne, hi TC,
please let me propose to add the following comment for this item 18,2 of
Yukinori Saito:
Yukinori Saito wants to change 'customer' to 'seller party'. Behind this we
do have a very basic conceptual question. The definitions in question of
e.g. Line Item. Maximum_ Backorder. Quantity is defined in reusable 'Line
Item. Details'.
Line Item. Details is directly reused in four other ABIEs (see attached
*.doc file). The very basic definition as of the Reusable Library cannot
express the specific needs of these four reusages.
IF UBL agrees that definitions shall be meaningful, THEN a place is needed
where these meaningful definitions shall be written. The current structure
of the spreadsheets does not allow this, but CCTS does requires this, I
think.
There are three or four ABIE needed, which base on 'Line Item. Details'.
These ABIE should restrict the underlying one and can have more specific
definitions due to the specifis usage.
In such a case, they need an Object Class Term Qualifier.IMHO this is what
Mark also mentioned in one of his emails.
Best regards,
Michael
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.
--
regards
tim mcgrath
phone: +618 93352228
postal: po box 1289 fremantle western australia 6160
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]