OASIS Open Mailing List Archives  ·  All Lists  ·  ubl-ndrsc  ·  2004-01

ubl-ndrsc — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

Re: [ubl-ndrsc] FW: More ASBIE Confusion (in UBL)


 MHonArc v2.5.0b2 -->

















ubl-ndrsc message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ubl-ndrsc] FW: More ASBIE Confusion (in UBL)


it may be my misunderstanding the question but  if the core of this is "what types do we give for ASBIEs?" then the answer should be none.  ASBIEs in our schemas are expressed in the documentation only - they describe the semantics of the ASBIE.  so, as Mike says, we are defining ABIEs contained within other ABIEs.  the point is that when an ABIE is contained within another ABIE it has a meaning specific to that containment.  An Invoice Line when it appears within an Invoice is not a good example, a better example is that  a Line Item contained in an Invoice Line  means something different to a Line Item contained in an Order Line.  We express that meaning as an ASBIE. By definition, an ASBIE merely records the use(via containment in our document models) of another ABIE (for a particular context).  This can be seen when we have more than one ASBIE between the same two BIEs. Every time the ASBIE is used it has a unique meaning.  

So, ASBIEs do not need the same tangible expression as ABIEs or BBIEs and therefore it is not useful to try and make them reusable types.  To go down this path would just create additional complexity (as seen by the question about naming) with no added value.

CRAWFORD, Mark wrote:


[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]