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] Compound operation Verify & Sign


Yes Trevor, I concur. If the core is limited to this generic Options
directive and no attempt is made to standardize response elements across
profiles as Nick is suggesting, I agree 100%. 

-----Original Message-----
From: Trevor Perrin [mailto:trevp@trevp.net] 
Sent: November 4, 2003 1:39 PM
To: Edward Shallow; 'Nick Pope'
Cc: dss@lists.oasis-open.org
Subject: RE: [dss] Compound operation Verify & Sign

At 10:08 AM 11/4/2003 -0500, Edward Shallow wrote:
>Content-Transfer-Encoding: 7bit
>
>Yes Trevor it could be as simple as that.
>
>Aside from the point that the illustration below is too general, I 
>agree with your stance. I suspect that the exact nature of the request 
>option has to be a little clearer and express exactly what is desired 
>of the service, but your point is taken.

Could we just have a generic <RequestUpdatedSignature> Option in the core,
and then if a profile supports multiple ways of updating a signature, it can
define its own options to select them?


Trevor 




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