Forcing SHA1 signing via metadata

[Andrew Morgan]

The SecurityConfiguration wiki page[1] mentions that we can use relying 
party metadata to specify the signing algorithm to use, instead of 
modifying the relying-party.xml file.

I'm reading the profile document[2] for that, but it isn't exactly clear 
what I need to put in my manual metadata I'm writing.  Is there an example 
that sets SHA1 signing?  :)  If so, could an example be added to the wiki?

Thanks,
 	Andy

[1] https://wiki.shibboleth.net/confluence/display/IDP30/SecurityConfiguration
[2] http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-metadata-algsupport-v1.0-cs01.html