OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dss] REFORMULATED ISSUE#2: SIGNATURECONTENTS (SIGN REQUEST DISCUSSION)



Juan Carlos,

You say:

"Imagine you send two documents. For the first one you define three
transformations: you want the server to generate three documents
(A1,A2,A3) and sign them.  For the second you define two
transformations: you want the server to generate two documents
(B1,B2) and sign them.  Now imagine you want A1,A2 and B2 enveloped;
B1 detached and A3 Enveloping the signature."

The last bit about "A3 Enveloping the signature" confuses me.  I understand 
how an InputDocument can envelope the signature.  But you seem to be saying 
the server would return the signature inserted into one of the 
*post-transformed* Input Documents?  I don't think that's what an Enveloped 
Signature means in DSIG.

So when you say:

"Question: HOW TO EASILY IDENTIFY HERE THAT THE DOCUMENT THAT HAS
TO CONTAIN THE ds:Signature IS PRECISELY A3,. The most simple
answer: WELL; JUST INDICATE WITH AN INTEGER THE ORDER NUMBER
OF THE CORRESPONDING DocumentSelector!!. And yes, this would
work, but, at what price?"

I don't think A3 *will* contain the ds:Signature.  The InputDocument that 
was transformed to A3 will contain the signature.  So you would want to 
indicate with an integer the corresponding *InputDocument*, not 
DocumentSelector.

Thus it doesn't make sense to associate a SignaturePlacementType with 
DocumentSelector, as you propose.  Do you agree?

Trevor



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]