Supercedes Issue 65-8.

From Issue 65-8:
8. Examples missing the xmlns in NLSML in VERIFICATION-COMPLETE message 
bodies. Actually, shouldn't the  http://www.ietf.org/xml/ns/mrcpv2 namespace 
apply to all NLSML documents throughout the specification not just those 
associated with verification?

From Dave Burke's March 21 email:
o Namespace: We have a namespace for enrollment and verification elements
but the rest are assigned to no namespace. That's because NLSML is not a
completed standard and has no namespace defined. MRCP has imported and
extended NLSML based on a discontinued working draft from the W3C. I believe
MRCP's version of NLSML should live completely in the MRCP namespace.
Furthermore, a version attribute really should be added to indicate the
version of MRCP NLSML. Thus the basic structure should be:

<?xml version="1.0"?>
<result version="1.0" xmlns="http://www.ietf.org/xml/ns/mrcpv2">
    ...
</result>