ws-i test tool issue ?

Hi All,

    When I check ws-i bsp compliance of the following soap message[1]
    with the test tool (download from [2]) , 

    the analyzed report with BasicSecurityProfile-1.1-TAD always
    complains BSP3070 assertion failed and a wsse:KeyIndetifier 

    element does NOT contain a EncodingType attribute (i.e., it is NOT
    the case that "./self::wsse:KeyIdentifier[@EncodingType]").

    But the BasicSecurityProfile-1.1 says it is not required if it
    refers to a SAML token :

    R3070 Any STR_KEY_IDENTIFIER that refers to a SECURITY_TOKEN other
    than a SAML_TOKEN MUST specify an EncodingType attribute

    

    Is this a bug in test tool or it doesn't support
    saml-token-profile-1.1 ?

     

    [1]

      <ds:KeyInfo Id="KI-BCF3790C6A856CAB8013662645516286">

           <ns4:SecurityTokenReference xmlns:ns4="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"

                     xmlns:wsse11="http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd"

                     wsse11:TokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.0">

               <ns4:KeyIdentifier

                                ValueType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID">_3DF61F55AC044E478A13662645512771</ns4:KeyIdentifier>

           </ns4:SecurityTokenReference>

      </ds:KeyInfo>

    

    

    [2]http://www.ws-i.org/Testing/Tools/Attach_17_WSI_Test_Java_WGD_BSP_1.1.zip

    

    

    Thanks,

    Jim