Next in thread → Next in month →

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

From
Trevor Perrin <>
Date
2003-09-15T21:12:22+00:00
ID
Thread
Re: [dss] REFORMULATED ISSUE#2: SIGNATURECONTENTS (SIGN REQUEST DISCUSSION)
At 11:05 PM 9/15/2003 +0200, Andreas Kuehne wrote:
>Content-Transfer-Encoding: 7bit
>
>Hi Trevor !
>
>>I think the idea is we'd envelope B, in the case where B is the starting 
>>point for the "signature transforms".
>
>
>Yes, B is what I like to call the 'document' !
>
>
>>So the question is whether the server needs to be able to do an A->B 
>>transform, such as selecting a particular element from one of the Input 
>>Documents.  Alternatively, we would require the client to do any 
>>"selection transforms" on the client side, and send the resulting B 
>>elements as just other Input Documents.
>
>It seems to that we are just building an additional transformation 
>service. This can be convenient, but I think it makes harder to understand 
>what the DSS actually does. Or we should call it 'digital signing and 
>other handy things'-service.

The A->B "selection transform" wouldn't have to be a general purpose 
transform.  It could just allow selection of a single XML element from one 
the Input Documents.

But I agree with you that the client could do this work, if desired.  So I 
don't see a compelling reason to support this.

Trevor
Next in thread → Next in month →