<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
First of all, please use xmlsec mailing list for all questions about
xmlsec library.<br>
<br>
Yes, xmlsec needs to have a new template for each signature it performs
because<br>
it puts signature results in the template. However, the template does
not need to be <br>
a standalone XML file. For example, in your case, you can put two
templates in the <br>
same document and just provide different "start nodes" for two
different signatures.<br>
The way you select "start nodes" is completely up to you.<br>
<br>
Aleksey<br>
<br>
Julianne Bielski wrote:<br>
<blockquote type="cite"
cite="midOF9D6A7DA3.01FB03F7-ON87256DBA.00721F41-85256DBA.00729EEB@us.ibm.com"><br>
<font size="2" face="sans-serif">Aleksey,</font>
<br>
<br>
<font size="2" face="sans-serif">So, is the idea with your library
that
you create a fresh signature template for each signature in a single
xml
document that you want verified?</font>
<br>
<br>
<font size="2" face="sans-serif">For example, if I have an xml
document
with a detached signature for a remote file as well as an enveloped
signature
that's a signature over the document itself, must I create two
signature
templates from my original xml document and feed them in separately to
the xmlsec APIs?</font>
<br>
<br>
<font size="2" face="sans-serif">Alternatively, can I give the xmlsec
APIs an XPATH pointer to each individual signature element?</font>
<br>
<font size="2" face="sans-serif"><br>
-- Regards,<br>
<br>
J. Bielski<br>
</font>
</blockquote>
</body>
</html>