RE: [dss] "Required" Designation on SignatureObject within VerifyRequest

[Trevor Perrin <trevp@trevp.net>]

At 12:02 AM 4/19/2004 -0400, Edward Shallow wrote:
>Trevor,
>
>I like your suggestion on optional outputs scoping. Very neat and tidy.
>But for the same reason, I don't like a brand new SignatureObject
>sub-element. Especially since I do not want to use it all in the scenario we
>are discussing. I simply want to Verify the InputDocument (i.e. the
>DocumentWithSignature). In fact it would work nicely with you new scoping
>suggestion. I do not think it changes the entire semantic.


Right now the semantics of <SignaturePtr> is "verify this signature".  With 
your change <SignaturePtr> would become usable as a "document pointer", not 
a signature pointer, with the semantics "verify all the signatures in this 
document".

This semantics would require new result codes, processing rules, and 
optional ouputs "scoping".  I would rather these things be in a profile, 
not core.  If they're in a profile, then it seems appropriate for the 
"thing" that triggers them to be in the profile with them - i.e. to have a 
new <SignatureObject> sub-element, instead of making a syntactic change to 
the core which only makes sense in conjunction with a particular profile.


Trevor