Each service is defined to have 1 or more named output types which can be selected by specifying the appropriate media type in the client's accept header. Additionally, services with more than one output type will also support a query parameter called output. The value of this parameter is the lowercase name of the desired output type (see table, below).
Clients that specify the output parameter will always receive that output type regardless of the Accept headers they send.
In the documentation for each service the list of output types is always given in preferred order.
Determining the Output Format
Services determines the output type to be used in a response in the following order:
- output parameter matches one of the service's output types
- output parameter is supplied but does not match one of the service's output types - a 400 Bad Request response is given
- Media type in the Accept header matches one of the service's output types, tested in preferred order
- */* in the Accept header - the first output type in the output type list is used
- No Accept header - the first output type in the output type list is used
- No other matches - a 406 Not Acceptable response is given
Standard Named Output Types
The following table summarizes the named output types supported in the Platform. Consult the API Documentation for the relevant services to check whether a specific output type is supported.
|Name||Description||Response Content Type||Accept Header||Output Parameter|
|HTML||The HTML response consists of an XHTML document and can be obtained either by specifying mime types of text/html or application/xhtml+xml in the request's accept header or by supplying an "output" query parameter with a value of "html". The response is sent with a content type header equal to the one matched in the accept header or text/html if the output parameter was specified.||text/html orapplication/xhtml+xml(see description)||text/html orapplication/xhtml+xml||html orxhtml|
|RDF||The response consists of an RDF/XML document||application/rdf+xml||application/rdf+xml||rdf|
|XML||The response consists of an XML document||application/xml||application/xml||xml|
|RSS||The response consists of an RSS 1.0 document||application/rss+xml||application/rss+xml||rss1|
|json (plus the user supplied callback value)|
|Turtle||Terse Triple Language||text/turtle||text/turtle||turtle|
Note: for backwards compatibility, where the text/turtle media type is listed, the deprecated application/x-turtle media type is also supported, though it is given a lower weighting during content negotiation