Partager via

2.2.3.1.2 responseType Type Definition

  • Article

The schema definition for the responseType type is as follows:<2>

   <!-- RESPONSE TYPE-->
   <xs:complexType name="responseType">
     <xs:sequence>
       <xs:element name="credentialsResponse" type="tns:credentialsResponseType" 
                   minOccurs="0" maxOccurs="100"/>      
     </xs:sequence>
     <xs:attribute name="requestID" type="tns:max64CharStringType"/>
     <xs:attribute name="version" type="tns:versionType" use="required"/>
     <xs:attribute name="serverVersion" type="tns:versionType" use="optional"/>
     <xs:attribute name="to" type="tns:mrasUriType"/>
     <xs:attribute name="from" type="tns:mrasUriType"/>    
     <xs:attribute name="reasonPhrase" type="tns:reasonPhraseType" use="required"/>    
   </xs:complexType>

The following table describes the responseType type's attributes.

Attribute

Description

requestID

Type max64CharStringType, as defined in section 2.2.4.8. If the request is malformed (based on the rules in section 3.1.5.1.1), this attribute is not present. If present, this attribute MUST have the same value as the requestID attribute in the request.

version

Type versionType, as defined in section 2.2.4.12. The version MUST be set as specified in section 3.1.5.2.2.

serverVersion

Type versionType, as defined in section 2.2.4.12. This is an optional attribute. If present, this SHOULD be the server version with a value of "3.0"<3>.

to

Type mrasUriType, as defined in section 2.2.4.11. If the request is malformed (based on the rules in section 3.1.5.1.1), this attribute is not present. If present, this attribute MUST have the same value as the to attribute in the request.

from

Type mrasUriType, as defined in section 2.2.4.11. If the request is malformed (based on the rules in section 3.1.5.1.1), this attribute is not present. If present, this attribute MUST have the same value as the from attribute in the request.

reasonPhrase

Type reasonPhraseType, as defined in section 2.2.4.7. Specifies the reason for the error. A detailed description of when each error message is thrown is provided in section 3.1.5.