3.1.5.2.2 With Content Negotiation
The message flow between a client and a server on subsequent requests for the XML file containing the resource list, with content negotiation, is shown in the following figure.

Figure 5: Message flow between TSWPP client and TSWPP server on subsequent requests with content negotiation
In the preceding figure, the TSWPP client has already obtained the .ASPXAUTH cookie as shown in section 3.1.5.2.1. This cookie is set in the HTTP request header (section 2.2.3) and the XML file containing the resource list is requested.
The client requests that the server generate a resource list adhering to the XML schema version 2.0 by specifying the parameter "radc_schema_version=2.0" as either an HTTP Header or as an URL parameter (section 2.2.5).
When the client requests that the resource list adhere to a schema version, the server SHOULD return an XML resource list conforming to XML schema (XSD) version 2.0 as specified in section 2.2.1.
If the server provides a cookie authentication mechanism, the server SHOULD authenticate the user's access by using the .ASPXAUTH cookie (section 3.3.1.1) and MUST return the XML file to the client.