Rex / Tim,
Looks good. This is the Catch22 dilemma that CAM definately helps with - if you make the XSD too restrictive then you risk valid message instances bieng rejected by schema checks - so you make almost everything optional in the XSD.
Then however people have no idea what for a "normal" use context - they really ought to include.
Because CAM has context aware features you can solve this neatly. OWL and RDF help with the semantics - but runtime validation and content assembly is obviously the domain of CAM templates.
Look forward to developing further examples - and also this may be something we can also contribute eventually to OASIS SOA RM/RA work too - as I know they like example patterns too!
Thanks, DW