[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: removing nodes to parent based on all child nodes

Subject: Re: removing nodes to parent based on all child nodes not having text value
From: "Cindy Lard" <Cindy.Lard@xxxxxxxxxxx>
Date: Fri, 05 Dec 2008 09:32:19 -0600
Re:  removing nodes to parent based on all child nodes
Thank you all so much for your help.  The example data was not correct as you
pointed out.  The input and desired output should have been as follows:

Input

<Registration>
     <UserName>DID1901</UserName>
     <ActivityType>25</ActivityType>
     <ActivityDate>2008-10-30T12:10:26</ActivityDate>
     <RegistrationCounty>19</RegistrationCounty>
     <Registrants>
          <Registrant>
               <Entity>
                    <Individual>
                         <Prefix/>
                         <FirstName/>
                         <LastName/>
                         <Middle/>
                         <Suffix/>
                    </Individual>
                    <Business>
                         <MailingAddress>
                               <Address>
                                    <MailingAddressType/>
                                    <MailingAddressLine1>123
Street</MailingAddressLine1>
                                    <MailingAddressLine2/>
                               </Address>
                         </MailingAddress>
                    </Business>
               </Entity>
          </Registrant>
     </Registrants>
</Registration>



Output

<Registration>
     <UserName>DID1901</UserName>
     <ActivityType>25</ActivityType>
     <ActivityDate>2008-10-30T12:10:26</ActivityDate>
     <RegistrationCounty>19</RegistrationCounty>
     <Registrants>
          <Registrant>
               <Entity>
                    <Business>
                         <MailingAddress>
                               <Address>
                                    <MailingAddressType/>
                                    <MailingAddressLine1>123
Street</MailingAddressLine1>
                                    <MailingAddressLine2/>
                               </Address>
                         </MailingAddress>
                    </Business>
               </Entity>
          </Registrant>
     </Registrants>
</Registration>


In this case there only needs to be either <Individual> or <Business> under
<Entity>.  Either the registration is for an individual or business. Both
should not exist in the same file.  Because the business registration
information is being pulled from a legacy system certain information required
in the XML may not be available, such as <MailingAddressType/> and
<MailingAddressLine2/> as in the preceding example.  However, if any
descendant element of a child has a text value such as
<MailingAddressLine1>123 Street</MailingAddressLine1> it's parent and siblings
all need to be copied even if those siblings have no text value the nodes need
to be copied.  If no descendant elements have a text value as is the case with
<Individual> that node and all descendant nodes of that element need to be
stripped out.  Wow, I hope that wasn't too confusing.

All the templates I have used thus far will strip out any element with no text
value, which removes the needed (dare I say required) elements of
<MailingAddressType/> and <MailingAddressLine2/> under the <Address> element.


I really appreciate all the help!!!

Current Thread

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.