XSL is good, but it isn't magic.
You can use it to create a unique id string for an element, but you have to tell it the basis for identifying elements. For example, in your sample document you have a Ship_To_First_Name element and a Ship_To_Last_Name element.
Suppose you have two customers named "John Smith". You couldn't use a combination of first name and last name to uniquely identify individual customers. "Well," you might say, "then I'll combine first name, last name, Ship_To_Address_1, Ship_To_Address_2, Ship_To_City, Ship_To_State, and Ship_To_Zip to use as the basis for a unique identifier."
That will work to differentiate the two John Smiths, but suppose one of the John Smiths enters a
subsequent order and calls himself "John L. Smith", or "J. Smith". How will you
be able to tell XSL that these are the same person?
You'll have to go back to your database adminstrator and ask if there is a column in the
customer table with a name like "customer_id" that uniquely identifies a
customer.
--
Charles Knell
cknell(_at_)onebox(_dot_)com - email
-----Original Message-----
From: Brandon Schenz <brandons(_at_)midwestsports(_dot_)com>
Sent: Fri, 24 Sep 2004 12:37:10 -0400
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] "FLAT" XML to Hierarchical XML
That will be another problem that I hoped would be able to be fixed by
the XSL.
*Brandon Schenz*
Midwest Sports Supply
Phone: 513-956-4900
Fax: 513-956-4910
E-mail: brandons(_at_)midwestsports(_dot_)com
cknell(_at_)onebox(_dot_)com wrote:
I don't see a customer id element or attribute in the sample source
XML you provided. How will you uniquely identify each customer?
--+------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--