Hi Frnz,

I need help in the conext of processing instructions.
the element that i have as a prcessing instructions is having the XML code in it. and now i want to process that value. i.e. apply-templates.....

Here is the code

<?xm-deletion author="procs" time="20010713T180850-1820"
data="&lt;elephant:Billva id=&quot;id_BC98D89B-2502-4225-&quot;
xmlns:elephant=&quot;http:gogle.comelephant.1#&quo t;
xmlnshtml=&quot;http://www.w3.org/1999/xhtml&quot;
xmlnslink=&quot;http://www.w3.org/1999/xlink&quot;&...ant:Num&gt;SEC.
10.&lt;/elephant:Num&gt;&lt;elephant:ActionLine action=&quot;IS_AMENDED&quot;
xlink:href=&quot;urn:elephant:codes:EDC:elephant#x pointer(%2Felephant%3AJokeDoc%2
Felephant%3ACode%2Felephant%3AJokeHeading%5B%40typ e%3D....."?>

In this code i could get the value of the data attribute
The next problem was to remove the &lt; and &gt; that was solved by a replace function.
The actual problem that i am faing now is that i need to again do something like <apply-temlates select="$variable"/> The reason behind is that the value of the data is nothing but a element of the XML itself. Can i give this input to the apply templates so that the templates which i have already written will get applied to this value?

Please help me in this matter.

Thanks in advance.

---------------------------
Vikrant Korde
3i Infotech, Vashi,
Mumbai, Maharashtra, India.

__________________
---------------------------
Vikrant Korde
3i Infotech, Vashi,
Mumbai, Maharashtra, India.

You need to extract the text of the processing instruction and pass it to an XML parser. It's actually worse than it looks, because it's double-escaped: the string value of the processing instruction is not <elephant>...</elephant>, but &lt;elephant&gt;....&lt;/elephant&gt; (because entity references are not recognized as such in processing instructions). You'll probably have to solve that with a bit of string manipulation code.

If you're using Saxon, you could use replace() to do the unescaping, and then call saxon:parse to turn the lexical XML into a tree structure that your XSLT code can process.

At the same time you might have a word with the people who generated this stuff and ask them why they can't use XML the way it was designed to be used.

Michael Kay
http://www.saxonica.com/
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference