J. Keith Wedinger
Senior Software
Developer
Sterling
Commerce
keith_wedinger@stercomm.com
-----Original Message-----
From: Allen Chang [mailto:achang@electroneconomy.com]
Sent: Friday, March 02, 2001 2:33 PM
To: Wedinger, Keith
Subject: RE: To Buy, or to Build? That is the q...Thanks a lot, Keith!I bought a book and I know that the operations I mentioned in the previous email can be done, but the latest question is, if I have<Node Id="2001" Name="Statement1">
<Input>
<Parameter Key="Line 1" Value="use #2002# here" />
</Input>
</Node>
<<Node Id="2002" Name="Statement2">
<Input>
<Parameter Key="Line 1" Value="a" />
</Input></Node>and I want to go through my entire xml and find all the references of #{Id}#, and then find the Node with that id, and replace the references with the name of the found node, so that for example, the third line would become<Parameter Key="Line 1" Value="use Statement2 here" />Can I do that with XSLT? and if yes, I assume I'll need "xsl:choose" or "xsl:if" with a lower level template?Thanks a meg!-Allen-----Original Message-----
From: Wedinger, Keith [mailto:Keith_Wedinger@stercomm.com]
Sent: Friday, March 02, 2001 4:17 AM
To: Xml-Dev (E-mail)
Subject: RE: To Buy, or to Build? That is the q...Without seeing a sample of the resultant document, my first recommendation would be to use XSLT to transform your documents. Perhaps you can post a sample result?J. Keith Wedinger
Senior Software Developer
Sterling Commerce
keith_wedinger@stercomm.com-----Original Message-----
From: Allen Chang [mailto:achang@electroneconomy.com]
Sent: Thursday, March 01, 2001 5:22 PM
To: 'xml-dev@lists.xml.org'
Subject: To Buy, or to Build? That is the q...OK, OK, that expression WAS a little overused. Anyway...
Dear XML Masters,
I need your expert opinion on the following question.
The task: updating versions of my own XML documents,
Question #1: Can I find/buy something ready to use, or do I have to write a little tool?I need to {add and replace} {names and values} of {elements and attributes}.
For example, my document would have something like
<Level1>
<Level2>
<Element1 attribute1="attribute1ValueA">
element1ValueA
<Element1/>
<Element1 attribute1="attribute1ValueB">
element1ValueB
<Element1/>
<Level2/>
<Level1/>To convert an older version of this kind of document to a newer version, I need to be able to add attributes or whole new elements, or replace (which would include "delete") Element1, attribute1, attribute1ValueA or element1ValueA.
Notice the elements are nested, and can be repeating (like "Element1"). I mentioned this since I heard some of the tools wouldn't handle it.
Question #2: If I do write it, I think I would need to use instruction/mapping statements similar to SQL statements, right?
Thanks for your help in advance! (and I need the answer ASAP =) )
Allen Chang
Software Engineer
Electron Economy
achang@electroneconomy.com
(408)597-3331