The provisions for some specific object types shall be as defined in this section.
In all cases the categorization depends on the SOP Class of the objects, enabling a client, or application building an HTML page for the client, to determine in advance of the request what the requirements will be.
In this category are all object instances of SOP classes defined in PS3.3 that consist of a single image frame, instances of multi-frame SOP Classes that contain only one frame, or object instances that consist of single frame accessed from instances of multi-frame SOP Classes using the "frameNumber" parameter.
The Server shall be able to send a response for each of the following MIME types:
WADO-URI and WADO-WS
application/dicom
image/jpeg
WADO-RS
application/dicom
application/octet-stream
application/dicom+xml
If the contentType parameter is not present in the URI or WADO-WS request, the response shall contain an image/jpeg MIME type, if compatible with the 'Accept' field of the GET method. If the contentType parameter is not present in the WADO-RS request, the response is dependent on the 'Accept' field and the requested resource.
When an image/jpeg MIME type is returned, the image shall be encoded using the JPEG baseline lossy 8 bit Huffman encoded non-hierarchical non-sequential process ISO/IEC 10918.
The choice of image/jpeg as the default for continuous tone images is a consequence of the universal support by Web Clients.
The Server should also support the following MIME types for WADO-URI or WADO-WS:
image/gif
image/png
image/jp2
The Server should also support the following MIME types for WADO-RS:
image/dicom
image/dicom+jpeg
image/dicom+rle
image/dicom+jpeg-ls
image/dicom+jp2image/dicom+jpx
The Server may also support other MIME types.