MHonArc v2.5.2 -->
ubl-ndrsc message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [ubl-ndrsc] RE: [ubl-lcsc] Newest version of the OO-design position paper.
From: "CHIUSANO, Joseph" <>
To: "'Michael C. Rawlins'" <>,"''" <>
Date: Fri, 23 Aug 2002 10:45:24 -0400
Title: RE: [ubl-ndrsc] RE: [ubl-lcsc] Newest version of the OO-design po sition paper.
Hi Mike,
Some thoughts:
<Excerpt>
Buyer, Ship to,
Carrier, etc., all probably go to very different database tables in most
applications.
</Excerpt>
Or potentially not - of course, one could have a single database table for Party information that contains some type of "indicator" field that identifies the Party Type. I think the most important point is that it is highly probable that such grouped information (at a certain level) may very well be stored in a single database table (but I think this is really a side point - I just used it for example purposes).
<Excerpt>
You also assume that the application which writes the data
to a database is going to use XPath. Some may, but most now aren't and
won't any time soon.
</Excerpt>
Yes - this was just for example purposes, as it was easiest to demonstrate the hierarchical aspect using XPath. But I think the same concept can hold for other access means - there can definitely be efficiencies gained by increased information organization (grouping).
Regards,
Joe
> **************************************************************************
> Joseph M. Chiusano
> Logistics Management Institute
> 2000 Corporate Ridge
> McLean, VA 22102
> Email:
> Tel: 571.633.7722
> **************************************************************************
>
