Issue Tracker
[uAchieve 4.5 Applications]
[uAchieve 5.0 Applications]
[Training & Conferences]

Page tree
Skip to end of metadata
Go to start of metadata

This documents offers tips on handling XML documents.


Transferology uses the following de facto standards for sending XML documents over HTTP (or HTTPS):

  • Transferology sends the standard HTTP request headers Content-Type and Content-Length
  • The Content-Type is always "text/xml"
  • The Content-Length will be the actual document size
  • By default, Transferology sends the XML document within the HTTP body
  • A school can change their Transferology settings so Transferology sends the XML as an HTML form field (i.e., HTTP request parameter and value)
  • Transferology uses the POST method to send the XML

A data capture of the HTTP POST from Transferology will appear similar to this:

POST /uselect-int/document/xml HTTP/1.1
Content-Type: text/xml
Content-Length: 3087
Host: www.someschool.edu:80
Connection: keep-alive

<RequestDocument xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.transfer.org/xsd/RequestDA_s1h.xsd">
        <TransactionType>Request Degree Audit</TransactionType>
                    <StudentTypeStatus>CAS Student</StudentTypeStatus>

Transferology expects external interfaces to also adhere to these de facto standards.

Use an XML Parser

Transferology sends well-formed XML documents. However, well-formed documents can have an XML version declaration, extra spaces, non-required attributes and elements, empty elements, and name spaces that make it difficult to parse with a home grown parser or, even worse, straight text/string comparisons.


Avoid the temptation to write your own XML parser. Instead, use an existing XML parser.


Within the context of Transferology, it is normal for an XML document to contain HTML. For the HTML to be correctly transferred between Transferology and an external system, both systems must use and accept the two standard methods of escaping markup within text per XML 1.0 specification, Section 2.4 Character Data and Markup. To summarize, the HTML content must either be wrapped within an XML <![CDATA[...]]> section or escape any characters that are one of the five predefined XML entities. The following table identifies the five predefined XML entities with their string escaped representations:


String Escape