<book xmlns="http://docbook.org/ns/docbook" xmlns:xl="http://www.w3.org/1999/xlink" version="5.0">
  <title>CP-1447</title>
  <subtitle>Clarify 8 bit in Extended JPEG Transfer Syntax</subtitle>
  <chapter>
    <title/>
    <informaltable rules="all" frame="box">
      <tr>
        <td rowspan="1" colspan="1" valign="top">
          <para>Status</para>
        </td>
        <td rowspan="1" colspan="1" valign="top">
          <para>Submitted</para>
        </td>
      </tr>
      <tr>
        <td rowspan="1" colspan="1" valign="top">
          <para>Date of Last Update</para>
        </td>
        <td rowspan="1" colspan="1" valign="top">
          <para>2015/01/14</para>
        </td>
      </tr>
      <tr>
        <td rowspan="1" colspan="1" valign="top">
          <para>Person Assigned</para>
        </td>
        <td rowspan="1" colspan="1" valign="top">
          <para>David Clunie</para>
          <para><link xmlns:xlink="http://www.w3.org/1999/xlink"
            xlink:href="mailto:dclunie@dclunie.com"/></para>
        </td>
      </tr>
      <tr>
        <td rowspan="1" colspan="1" valign="top">
          <para>Submitter Name</para>
        </td>
        <td rowspan="1" colspan="1" valign="top">
          <para>David Clunie</para>
          <para><link xmlns:xlink="http://www.w3.org/1999/xlink"
            xlink:href="mailto:dclunie@dclunie.com"/></para>
        </td>
      </tr>
      <tr>
        <td rowspan="1" colspan="1" valign="top">
          <para>Submission Date</para>
        </td>
        <td rowspan="1" colspan="1" valign="top">
          <para>2014/09/14</para>
        </td>
      </tr>
    </informaltable>
    <informaltable rules="all" frame="box">
      <tr>
        <td rowspan="1" colspan="1" valign="top">
          <para>Correction Number CP-1447</para>
        </td>
      </tr>
      <tr>
        <td rowspan="1" colspan="1" valign="top">
          <para>Log Summary: Clarify 8 bit in Extended JPEG Transfer Syntax</para>
        </td>
      </tr>
      <tr>
        <td rowspan="1" colspan="1" valign="top">
          <para>Name of Standard</para>
          <para>PS3.5 2015a</para>
        </td>
      </tr>
      <tr>
        <td rowspan="1" colspan="1" valign="top"><para>Rationale for Correction:</para>
          <para>In the description of default Lossy JPEG Compression Transfer Syntaxes (10.3), it is
            specified that there is one Transfer Syntax for 8 bit images (.50) and another for 12
            bit images (.51).</para>
          <para>In the table mapping JPEG processes to Transfer Syntaxes (A.4.1), the .51 Transfer
            Syntax is listed as supporting both 8 and 12 bits. The difference between the 8 bit JPEG
            baseline process (used for .50) and 8 bit JPEG extended process 2 (used for .51) is not
            described in the existing text. The difference (defined in the JPEG standard) involves
            the use of a different SOF marker segment, and the possibility of more tables being used
            in the extended process. Some implementors have incorrectly assumed that a baseline JPEG
            bitstream can be encoded in the .51 Transfer Syntax but the marker segment will then be
            incorrect (SOF0 rather than the SOF1 required).</para>
          <para>There is further discussion of 8 versus 12 bits, the JPEG processes and the Transfer
            Syntaxes in the general description of JPEG (8.2.1), which requires that implementations
            support specific processes as defaults.</para>
          <para>Annex F further describes the JPEG coding processes, and adds more confusion by the
            presence of a "capable of performing" column, which includes process 1 for .51, in
            addition to processes 2 and 4, with the rationale that the processes (described in the
            JPEG standard) build upon one another (even though the encoded bitstreams use different
            marker segments, which is not considered in Annex F). There is no definition of "capable
            of performing", whether it applies to encoders or decoders, or what part of the JPEG
            standard (10918-1 or 10918-2) defines this, if any.</para>
          <para>Informative text is added to emphasize that though 8 bit images can be encoded in
            either the .50 and .51 Transfer Syntaxes, the bitstreams are different. Further, a
            recommendation is added that the .50 Transfer Syntax be used for 8 bit images unless the
            additional features of the extended process are required, particularly since support of
            the baseline process is required anyway (by 8.2.1). The "capable of performing" column
            heading is replaced with "capable of decoding" to be consistent with ISO 10918-2's
            asymetric encoding and decoding requirements for the processes listed.</para>
        </td>
      </tr>
      <tr>
        <td rowspan="1" colspan="1" valign="top">Correction Wording:</td>
      </tr>
    </informaltable>
  </chapter>
  <chapter>
    <title/>
    <section>
      <title/>
      <informaltable rules="all" frame="box">
        <tr>
          <td>
            <para><emphasis role="italic">Amend DICOM PS3.5 as follows:</emphasis></para>
          </td>
        </tr>
      </informaltable>
    </section>
    
    <section xml:id="sect_8.2" label="8.2" status="2">
      <title>Native or Encapsulated Format Encoding</title>
      <section xml:id="sect_8.2.1" label="8.2.1" status="3">
        <title>JPEG Image Compression</title>
        <para>DICOM provides a mechanism for supporting the use of JPEG Image Compression through the Encapsulated Format (see <olink targetdoc="PS3.3" targetptr="PS3.3" xrefstyle="select: labelnumber"/>). <xref linkend="sect_A" xrefstyle="template: Annex %n"/> defines a number of Transfer Syntaxes that reference the JPEG Standard and provide a number of lossless (bit preserving) and lossy compression schemes.</para>
        <note>
          <para>The context where the usage of lossy compression of medical images is clinically acceptable is beyond the scope of the DICOM Standard. The policies associated with the selection of appropriate compression parameters (e.g., compression ratio) for JPEG lossy compression is also beyond the scope of this standard.</para>
        </note>
        <para>In order to facilitate interoperability of implementations conforming to the DICOM Standard that elect to use one or more of the Transfer Syntaxes for JPEG Image Compression, the following policy is specified:</para>
        <itemizedlist>
          <listitem>
            <para>Any implementation that conforms to the DICOM Standard and has elected to support any one of the Transfer Syntaxes for lossless JPEG Image Compression, shall support the following lossless compression: The subset (first-order horizontal prediction [Selection Value 1) of JPEG Process 14 (DPCM, non-hierarchical with Huffman coding) (see <xref linkend="sect_F" xrefstyle="template: Annex %n"/>).</para>
          </listitem>
          <listitem>
            <para>Any implementation that conforms to the DICOM Standard and has elected to support any one of the Transfer Syntaxes for 8-bit lossy JPEG Image Compression, shall support the JPEG Baseline Compression (coding Process 1).</para>
          </listitem>
          <listitem>
            <para>Any implementation that conforms to the DICOM Standard and has elected to support any one of the Transfer Syntaxes for 12-bit lossy JPEG Image Compression, shall support the JPEG Compression Process 4.</para>
          </listitem>
        </itemizedlist>
        <para>...</para>
      </section>
    </section>
    
    <section xml:id="sect_10" label="10" status="1">
      <title>Transfer Syntax</title>
      <section xml:id="sect_10.3" label="10.3" status="2">
        <title>Transfer Syntaxes for a DICOM Default of Lossy JPEG Compression</title>
        <para>DICOM defines defaults for Lossy JPEG Image Compression, one for 8-bit images and the other for 12-bit images. JPEG coding Process 1 (identified by Transfer Syntax UID = "1.2.840.10008.1.2.4.50") is used for 8-bit images. JPEG coding Process 4 (identified by Transfer Syntax UID = "1.2.840.10008.1.2.4.51") is used for 12-bit images. This implies that:</para>
        <orderedlist numeration="loweralpha">
          <listitem>
            <para>If an Application Entity issues an A-ASSOCIATE request where any offered Abstract Syntaxes is associated in one or more Presentation Context(s) with a JPEG lossy compression Transfer Syntax, at least one of the Presentation Contexts that include this Abstract Syntax, shall include the appropriate DICOM Default Lossy JPEG Compression Transfer Syntax.</para>
            <note>
              <para>Offering Abstract Syntax (AS1) in two Presentation Contexts with Transfer Syntaxes JPEG lossy (JL1) and (JL2) is not valid, but offering AS1-JL1, AS1-JL2 and AS1-JLD is valid because the DICOM Default JPEG Lossy Transfer Syntax (JLD) is present in at least one of the Presentation Contexts that are based on Abstract Syntax (AS1).2. The DICOM Default Transfer Syntax (uncompressed) may be offered if the sender has access to the original pixel data in an uncompressed or lossless compressed form.</para>
            </note>
          </listitem>
          <listitem>
            <para>If an Application Entity that supports one or more Lossy JPEG Transfer Syntaxes receives an A-ASSOCIATE indication corresponding to a request that follows the requirements specified in <xref linkend="sect_10.3" xrefstyle="select: labelnumber"/> (a), every Presentation Context related to a given Abstract Syntax cannot be rejected in an A-ASSOCIATE response for the reason that the DICOM Default lossy JPEG Transfer Syntax is not supported.</para>
          </listitem>
        </orderedlist>
        <note>
          <para><emphasis role="bold"><emphasis role="underline">The 12 bit default Transfer Syntax
            1.2.840.10008.1.2.4.51 can also be used to encode 8 bit images, but the bit stream
            required is not identical to that used in the 8 bit default Transfer Syntax
            1.2.840.10008.1.2.4.50 (see <xref linkend="sect_A.4.1" xrefstyle="select: labelnumber"
            />).</emphasis></emphasis></para>
        </note>
      </section>
    </section>   
    <section xml:id="sect_A" label="A" status="1">
      <title>Transfer Syntax Specifications (Normative)</title>
      <section xml:id="sect_A.4.1" label="A.4.1" status="3">
        <title>JPEG Image Compression</title>
        <para>The International Standards Organization ISO/IEC JTC1 has developed an International
          Standard, ISO<emphasis role="bold"><emphasis role="strikethrough">/IS-</emphasis><emphasis role="underline"> </emphasis></emphasis>10918-1 (JPEG Part 1) and an
          International <emphasis role="bold"><emphasis role="strikethrough"
            >Draft</emphasis></emphasis> Standard, ISO<emphasis role="bold"><emphasis role="strikethrough">/IS-</emphasis><emphasis role="underline"> </emphasis></emphasis>10918-2 (JPEG Part 2), known as the JPEG
          Standard, for digital compression and coding of continuous-tone still images (see <xref
            linkend="sect_F" xrefstyle="template: Annex %n"/> for further details).</para>
        <para>A DICOM Transfer Syntax for JPEG Image Compression shall be identified by a UID value, appropriate to its JPEG coding process, chosen from <xref linkend="table_A.4-3" xrefstyle="select: labelnumber"/>.</para>
        <table frame="box" rules="all" xml:id="table_A.4-3" label="A.4-3">
          <caption>DICOM Transfer Syntax UIDs for JPEG</caption>
          <thead>
            <tr valign="top">
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">DICOM Transfer Syntax UID</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">JPEG coding process</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">JPEG description</emphasis>
                </para>
              </th>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1.2.840.10008.1.2.4.50</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>1</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>baseline</para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1.2.840.10008.1.2.4.51</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>2(8-bit),4(12-bit)</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>extended</para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1.2.840.10008.1.2.4.57</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>14</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>lossless, non-hierarchical</para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1.2.840.10008.1.2.4.70</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>14</para>
                <para>(Selection Value 1)</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>lossless, non-hierarchical, first-order prediction</para>
              </td>
            </tr>
          </tbody>
        </table>
        <note>
          <orderedlist numeration="arabic">
            <listitem>
              <para>DICOM identifies, to increase the likelihood of successful association, three Transfer
                Syntaxes for Default JPEG Compression Image processes (see <xref linkend="sect_8.2.1"
                  xrefstyle="select: labelnumber"/> and <xref linkend="sect_10"
                    xrefstyle="template: Section %n"/>).</para>
            </listitem>
            <listitem>
              <para><emphasis role="bold"><emphasis role="underline">Different JPEG processes may
                    use different SOF marker segments. E.g., the baseline JPEG process 1 used with
                    the 1.2.840.10008.1.2.4.50 Transfer Syntax uses the SOF0 marker, whereas the
                    extended process 2 used with the 1.2.840.10008.1.2.4.51 Transfer Syntax uses the
                    SOF1 marker. Accordingly, even though both bit streams encode 8 bit images using
                    DCT and Huffman coding, they are not identical. Further, the extended process 2
                    may (but is not required to) use more AC and DC tables (up to 4 of each, rather
                    than 2, per ISO 10918-1 Section F.1.3).</emphasis></emphasis></para>
              <para><emphasis role="bold"><emphasis role="underline">It is not compliant to send bit
                    streams with the SOF0 marker using the 1.2.840.10008.1.2.4.51 Transfer Syntax,
                    but it is recommended that receivers of the 1.2.840.10008.1.2.4.51 Transfer
                    Syntax be able to decode bit streams with the SOF0 marker (this asymmetry is
                    consistent with ISO 10918-2 requirements; see <xref linkend="sect_A.4.1"
                      xrefstyle="select: labelnumber"/>).</emphasis></emphasis></para>
            </listitem>
            <listitem>
              <para><emphasis role="bold"><emphasis role="underline">It is recommended that lossy
                compressed 8 bit images be encoded with the 1.2.840.10008.1.2.4.50 Transfer Syntax
                rather than the 1.2.840.10008.1.2.4.51 Transfer Syntax, unless the additional
                features of the extended process are required, particularly since support of the
                1.2.840.10008.1.2.4.50 Transfer Syntax is required for 8 bit images anyway (as
                described in <xref linkend="sect_8.2.1" xrefstyle="select: labelnumber"/>) and to
                avoid confusion with the use of 12 bit images encoded with Process 14 in the
                1.2.840.10008.1.2.4.51 Transfer Syntax (defined as a DICOM Default Transfer Syntax
                for 12 bit images in <xref linkend="sect_10.3" xrefstyle="select: labelnumber"
                />).</emphasis></emphasis></para>
            </listitem>
          </orderedlist>
        </note>
        <para>If the object allows multi-frame images in the pixel data field, then each frame shall be encoded separately. Each fragment shall contain encoded data from a single-frame image.</para>
        <note>
          <para>Though a fragment may not contain encoded data from more than one frame, the encoded data from one frame may span multiple fragments. See note in <xref linkend="sect_8.2" xrefstyle="select: labelnumber"/>.</para>
        </note>
        <para>For all images, including all frames of a multi-frame image, the JPEG Interchange Format shall be used (the table specification shall be included).</para>
        <note>
          <para>This refers to the ISO 10918-1 "interchange format", not the <emphasis role="bold"
                ><emphasis role="strikethrough">DIS</emphasis><emphasis role="underline"
              >ISO</emphasis></emphasis> 10918-5 JPEG File Interchange Format (JFIF).</para>
        </note>
        <para>If images with Photometric Interpretation (0028,0004) YBR_FULL_422 or YBR_PARTIAL_422, are encoded with JPEG coding Process 1 (non hierarchical with Huffman coding), identified by DICOM Transfer Syntax UID "1.2.840.10008.1.2.4.50"the minimum compressible unit is YYCBCR, where Y, CB, and CR are 8 by 8 blocks of pixel values. The data stream encodes two Y blocks followed by the corresponding CB and CR blocks.</para>
      </section>
    </section>
    
    <section xml:id="sect_F" label="F" status="1">
      <title>Encapsulated Images As Part of A DICOM Message (Informative)</title>
      <section xml:id="sect_F.1" label="F.1" status="2">
        <title>Encapsulated JPEG Encoded Images</title>
        <para>The International Standards Organization (ISO/IEC JTC1/SC2/WG10) has prepared an International Standard, ISO<emphasis role="bold"><emphasis role="strikethrough">/IS-</emphasis><emphasis role="underline"> </emphasis></emphasis>10918-1 (JPEG Part 1) and International <emphasis role="bold"><emphasis role="strikethrough">Draft </emphasis></emphasis>Standard ISO<emphasis role="bold"><emphasis role="strikethrough">/IS-</emphasis><emphasis role="underline"> </emphasis></emphasis>10918-2 (JPEG Part 2), for the digital compression and coding of continuous-tone still images. This standard is collectively known as the JPEG Standard.</para>
        <para>Part 1 of the JPEG Standard sets out requirements and implementation guidelines for the coded representation of compressed image data to be interchanged between applications. The processes and representations are intended to be generic in order to support the broad range of applications for color and grayscale still images for the purpose of communications and storage within computer systems. Part 2 of the JPEG Standard defines tests for determining whether implementations comply with the requirements of the various encoding and decoding processes specified in Part 1 of the JPEG Standard.</para>
        <para>The JPEG Standard specifies lossy and lossless code processes. The lossy coding is based on the discrete cosine transform (DCT), permitting data compression with an adjustable compression ratio. The lossless coding employs differential pulse code modulation (DPCM).</para>
        <para>The JPEG Standard permits a variety of coding processes for the coder and decoder. These processes differ in coding schemes for the quantified data and in sample precision. The coding processes are consecutively numbered as defined in the International Draft Standard ISO<emphasis role="bold"><emphasis role="strikethrough">/IS-</emphasis><emphasis role="underline"> </emphasis></emphasis>10918-2 (JPEG Part 2), and are summarized in <xref linkend="table_F.1-1" xrefstyle="select: label"/>. The simplest DCT-based coding process is referred to as Baseline Sequential with Huffman Coding for 8-bit Samples.</para>
        <table frame="box" rules="all" xml:id="table_F.1-1" label="F.1-1">
          <caption>JPEG Modes of Image Coding</caption>
          <thead>
            <tr valign="top">
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">No.</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">Description</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">Lossy</emphasis>
                </para>
                <para>
                  <emphasis role="bold">LY</emphasis>
                </para>
                <para>
                  <emphasis role="bold">Lossless</emphasis>
                </para>
                <para>
                  <emphasis role="bold">LL</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">Non-Hierarchical</emphasis>
                </para>
                <para>
                  <emphasis role="bold">NH</emphasis>
                </para>
                <para>
                  <emphasis role="bold">Hierarchical</emphasis>
                </para>
                <para>
                  <emphasis role="bold">H</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">Sequential</emphasis>
                </para>
                <para>
                  <emphasis role="bold">S</emphasis>
                </para>
                <para>
                  <emphasis role="bold">Progressive</emphasis>
                </para>
                <para>
                  <emphasis role="bold">P</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">Transform</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">Coding</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">Accepted Bits</emphasis>
                </para>
              </th>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1</para>
                <para>2</para>
                <para>4</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>Baseline</para>
                <para>Extended</para>
                <para>Extended</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>LY</para>
                <para>LY</para>
                <para>LY</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>NH</para>
                <para>NH</para>
                <para>NH</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>S</para>
                <para>S</para>
                <para>S</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>DCT</para>
                <para>DCT</para>
                <para>DCT</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>Huffman</para>
                <para>Huffman</para>
                <para>Huffman</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>8</para>
                <para>8</para>
                <para>12</para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>14</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>Lossless</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>LL</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>NH</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>S</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>DPCM</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>Huffman</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>2-16</para>
              </td>
            </tr>
          </tbody>
        </table>
        <para>The different coding processes specified in the JPEG Standard are closely related. By extending the capability of an implementation, increasingly more 'lower level' processes can also be executed by the implementation. This is shown in <xref linkend="table_F.1-2" xrefstyle="select: label"/> for Huffman Coding.</para>
        <para>Inclusion of a JPEG-coded image in a DICOM message is facilitated by the use of specific
          Transfer Syntaxes that are defined in <xref linkend="sect_A"
            xrefstyle="template: Annex %n"/>. Independent of the JPEG coding processes, the same
          syntax applies. The only distinction for different processes in the syntax <emphasis
            role="bold"><emphasis role="underline">(apart from different SOF marker segments in the
              JPEG bit stream)</emphasis></emphasis> is the UID value. <xref linkend="table_F.1-5"
                xrefstyle="select: label"/> lists the UID values in the Transfer Syntax for the various
          JPEG coding processes for reference.</para>
        <table frame="box" rules="all" xml:id="table_F.1-2" label="F.1-2">
          <caption>Relationship Between the Lossy JPEG Huffman Coding Processes</caption>
          <thead>
            <tr valign="top">
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">Process</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">1</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">2</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">4</emphasis>
                </para>
              </th>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">1</emphasis>
                </para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>*</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>*</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>*</para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">2</emphasis>
                </para>
              </td>
              <td align="center" colspan="1" rowspan="1"/>
              <td align="center" colspan="1" rowspan="1">
                <para>*</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>*</para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">4</emphasis>
                </para>
              </td>
              <td align="center" colspan="1" rowspan="1"/>
              <td align="center" colspan="1" rowspan="1"/>
              <td align="center" colspan="1" rowspan="1">
                <para>*</para>
              </td>
            </tr>
          </tbody>
        </table>
        <para>* Coding process of column can execute coding process of row</para>
        <table frame="box" rules="all" xml:id="table_F.1-5" label="F.1-5">
          <caption>Identification of JPEG Coding Processes in DICOM</caption>
          <thead>
            <tr valign="top">
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">DICOM Transfer Syntax UID</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">JPEG process</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">JPEG description</emphasis>
                </para>
              </th>
              <th align="center" colspan="1" rowspan="1">
                <para>
                  <emphasis role="bold">capable of <emphasis role="strikethrough">performing</emphasis><emphasis role="underline">decoding</emphasis></emphasis>
                </para>
              </th>
            </tr>
          </thead>
          <tbody>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1.2.840.10008.1.2.4.50</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>1</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>baseline</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>1</para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1.2.840.10008.1.2.4.51</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>2,4</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>extended</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>1,2,4<emphasis role="bold"><emphasis role="underline"> (see
                  Note)</emphasis></emphasis></para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1.2.840.10008.1.2.4.57</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>14</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>lossless NH</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>14</para>
              </td>
            </tr>
            <tr valign="top">
              <td align="center" colspan="1" rowspan="1">
                <para>1.2.840.10008.1.2.4.70</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>14</para>
                <para>Selection Value 1</para>
              </td>
              <td align="center" colspan="1" rowspan="1">
                <para>lossless NH, first-order prediction</para>
              </td>
              <td align="center" colspan="1" rowspan="1"/>
            </tr>
          </tbody>
        </table>
        <note>
          <para><emphasis role="bold"><emphasis role="underline">Though the coding processes (2, 4)
                described in ISO 10918-1 are capable of decoding the other listed process (1), the
                bit stream uses different SOF marker segments. I.e., the baseline JPEG process 1
                used with the 1.2.840.10008.1.2.4.50 Transfer Syntax uses the SOF0 marker, whereas
                the extended process 2 used with the 1.2.840.10008.1.2.4.51 Transfer Syntax uses the
                SOF1 marker. Accordingly, even though both bit streams encode 8 bit images using DCT
                and Huffman coding, they are not identical.</emphasis></emphasis></para>
          <para><emphasis role="bold"><emphasis role="underline">ISO 10918-2 describes compliance
                tests for decoders, and requires that implementations of specific extended processes
                (such as 2 and 4) be capable of decoding bit streams of related baseline processes
                (such as 1) (ISO 10918-2 Section 7.4 Compliance tests for DCT-based sequential mode
                decoding processes). The converse is not true for encoders however, and the presence
                of SOF marker segments not defined by the specific process is not compliant (ISO
                10918-2 Section 5.1.1 Non-hierarchical coding processes syntax compliance test
                Tables 1 and 2).</emphasis></emphasis></para>
        </note>
      </section>
    </section>
  </chapter>
</book>
