I agree with Clay. XSL should be your first choice (barring, also as Clay
suggests, deep skills in any other technology that will work and little or
no skills in XSL).
I am always very wary of "round-tripping" where, I like to joke, the
operative term is "trip," as in it will trip you up. While this is sometimes
unavoidable, great care should be taken before committing to such a
workflow. Round-tripping is inherently fragile since the code supporting to-
and fro- is typically very, very tightly aimed at the narrowest successful
set of elements/attributes/features. Changes to either side of the trip can
cause problems, even seemingly unrelated changes. Applications (custom and
off-the-shelf) on both sides of the trip can become version bound when
scarce resources prevent the testing necessary to vet an upgrade. Etc. etc.
etc.
On Mon, Aug 16, 2010 at 12:20 PM, Carolyn Herlin
<->wrote:
> I have a need to pull selected information from my "master" XML file and
> write it to an XML file with a different DTD. I'll need a separate process
> to take information from that separate XML file and put it back in my
> "master." Does any one have suggestions about the best way to go about this?
>
>
>
> Thanks,
>
> Carolyn Herlin
>
>
>
>