complexType "responseType"
Namespace:
Content:
empty, 1 attribute
Defined:
globally in hsinfra.xsd; see XML source
Includes:
definition of 1 attribute
Used:
XML Representation Summary
<...
   
 = 
xsd:string
/>
All Direct / Indirect Based Elements (1):
response
Known Usage Locations
Annotation
This element contains information related to the response message. In current implementations, this information is limited to the role that was computed for the sender, assuming the original request was formed well enough to progress this far through the .NET My Services message-processing system. This header element must be present in all response messages.
XML Source (see within schema source)
<xsd:complexType name="responseType">
<xsd:annotation>
<xsd:documentation>
This element contains information related to the response message.
In current implementations, this information is limited to the role
that was computed for the sender, assuming the original request was formed
well enough to progress this far through the .NET My Services message-processing system.
This header element must be present in all response messages.
</xsd:documentation>
</xsd:annotation>
<xsd:attribute name="role" type="string" use="optional">
<xsd:annotation>
<xsd:documentation>
This optional attribute contains the role
that was computed for the sender. If the original request message was malformed
and did not make it far enough through the message processor to compute
a value for this element, the
<b>role</b>
attribute will be missing from the response header.
This situation typically occurs whenever the identity header is so malformed that the
basic set of sender identity PUIDs cannot be extracted from the service ticket.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
Attribute Detail (all declarations; 1/1)
role
Type:
Use:
optional
Defined:
locally within (this) responseType complexType
This optional attribute contains the role that was computed for the sender. If the original request message was malformed and did not make it far enough through the message processor to compute a value for this element, the <b>role</b> attribute will be missing from the response header. This situation typically occurs whenever the identity header is so malformed that the basic set of sender identity PUIDs cannot be extracted from the service ticket.
XML Source (see within schema source)
<xsd:attribute name="role" type="string" use="optional">
<xsd:annotation>
<xsd:documentation>
This optional attribute contains the role
that was computed for the sender. If the original request message was malformed
and did not make it far enough through the message processor to compute
a value for this element, the
<b>role</b>
attribute will be missing from the response header.
This situation typically occurs whenever the identity header is so malformed that the
basic set of sender identity PUIDs cannot be extracted from the service ticket.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>