NIST perpetuating wrong notion of ebXML and SOA

I just found this document from 2007.
 
Its out for review and comment:
http://csrc.nist.gov/publications/nistpubs/800-95/SP800-95.pdf
 
Once again we see the notion of "complicated" being attached to ebXML - when in fact the reverse can be the case! 
 
That ebXML contract and secure ebMS exchanges are better suited to much of what people want to do with SOA than a WSDL approach!
 
Suggest we can produce a Top Reasons to Use ebXML for 2009 and submit this as feedback to NIST
(similar to the format of this - http://www.oasis-open.org/committees/download.php/30366/EML-Top-Reasons.pdf)
 
Happy 2009 Everyone!
 
Thanks, DW