Yes, there are good use cases. But we can't cover everything. . . The group decided not to discuss multiple signatures at all in the spec. I suppose we could change all the SHALLs to SHOULDs in section 4.1.3 (Signature Generation) but I would expect interoperability problems with doing things not in the spec. We started considering all the problems with Signature ordering and decided not to go down that path. If we exclude all Signature elements, all we are missing is the case of signing over another Signature (I sign then my boss signs) and we don't have to worry about signature ordering. If you want to create a signature over something else, you could, just by changing the Transform for your one Signature. However, if something else signs afterwards, your signature would be broken (the end would not know to exclude the new signature when validating yours). Does everyone still agree? Regards, David Fischer Drummond Group.