"Required" Designation on SignatureObject within VerifyRequest

["Edward Shallow" <ed.shallow@rogers.com>]

All,

    To make things easier on clients when creating a VerifyRequest, would it
be possible to relax the [Required] designation on the SignatureObject for
the simplest of scenarios where there is only one InputDocument and the
signature is contained therein. There would be no WhichDocument ambiguity
and the client would be relieved of having to construct the SignaturePtr
element. This would be sort of like the DocumentWithSignature type presently
used as OptionalOutput. In fact, could DocumentWithSignature itself not be
used as input on a VerifyRequest if both SignatureObject and InputDocuments
were made optional ? This would be more semantically correct for this
scenario which I contend would be the most common. Thoughts ?

     Section 5.1.2 line 1121 of the core spec Draft 18 has a typo ...
Ptarroduced ...

Ed