+<!--#######################################################################-->
+
+<HR size="1"><ADDRESS style="align: right;"></ADDRESS>
+<H2>
+ <A CLASS="anchor" NAME="missing">
+ <B>Missing features</B></A>
+</H2>
+We know the following are missing; don't loose time looking for them ...<br>
+We know they could be helpfull. We shall add them some day.<br>
+Any contribution is welcome.
+<UL>
+<LI> Decoders
+ <UL>
+ <LI> gdcm doesn't read yet JPEG-LS encoded files.
+ <UL>
+ We said 'JPEG-LS', not Lossless Jpeg ...<br>
+ [JPEG-LS is the basis for new lossless/near-lossless compression
+ standard for continuous-tone images intended for JPEG2000.
+ The standard is based on the LOCO-I algorithm
+ (LOw COmplexity LOssless COmpression for Images)
+ developed at Hewlett-Packard Laboratories]
+ </UL>
+ <LI> gdcm doesn't read yet JPEG2000 encoded files.
+ <UL>
+ But we are working on it.
+ </UL>
+ <LI> gdcm doesn't read yet MPEG2 encoded files.
+ <UL>
+ But we are working on it.
+ </UL>
+ </UL>
+<LI>Reader
+ <UL>
+ <LI> Allow user to tell <TT>gdcm::Document</TT> constructor he just wants
+ to load a given list of <TT>DocEntries</TT>
+ (to save CPU time and RAM space)
+ <LI> Allow 'frame by frame' reading (should be helpfull for huge
+ multiframe images)
+ <LI> Allow subvolume selection / frames selection before reading.
+ <LI> Expose Read/Decompression mechanisms to allow user getting
+ information from <tt>DICOMDIR</TT> <br> -or from his own Data Base-
+ and reading his images without parsing
+ the header, one more time.
+ </UL>
+ <LI>Writer
+ <UL>
+ <LI> Allow user to tell the Writer he doesn't want to write down
+ <TT>SeqEntry</TT> (if any)
+ <LI> Allow user to tell the Writer he doesn't want to write down
+ <TT>Shadow groups</TT> (if any)
+ <LI> Allow user to tell the Writer which compression mode he wants<br>
+ (Right now, no one is available)
+ <LI> Allow user to tell the Writer he wants to split a
+ <TT>Multiframe</TT> image into a serie of
+ <TT>Single frame</TT> images.
+ <LI> Allow user to tell the Writer he wants to agregate a
+ Serie of <TT>Single frame</TT> images into a
+ <TT>Multiframe</TT> image.
+ </UL>
+<LI>Reader / Writer
+ <UL>
+ <LI> Full <TT>Icon Image</TT> management (Read and Write)
+ <LI> Full <TT>Overlays</TT> management (Read and Write) <br>
+ both for '<TT>ACR-NEMA</TT> style' (using groups <TT>0x6000</TT>
+ and nexts) and '<TT>DICOM V3</TT> style' (using Sequences)
+ </UL>
+<LI> <TT>DICOMDIR</TT>
+ <UL>
+ <LI> <TT>DICOMDIR</TT> full management (not limited to
+ <TT> PATIENT</TT>/<TT>STUDY</TT>/<TT>SERIE</TT>/<TT>IMAGE</TT>)
+ <LI> Allow user to add an entry (belonging to the file header Dicom
+ entries)to the default entry list, before
+ making a <TT>DICOMDIR</TT> from a root directory
+ <LI> Allow user to add an entry of his owns (for instance an <TT>Icon</TT>
+ to each image, or to each Serie).
+ </UL>
+<LI> SerieHelper
+ <UL>
+
+ <LI> An accurate <TT>SerieHelper</TT> <br>
+ Right now <TT>SerieHelper</TT> only works on 'bona fide Series', and
+ breaks on wrongly forged Series.<br>
+ We are still looking for any heuristics...
+ <LI> A <TT>SerieHelper</TT> that would use the <TT>DICOMDIR</TT> (if any)
+ instead of parsing all the files within the Root Directory
+ </UL>
+<LI> Other
+ <UL>
+ <LI> 16-bits-LUT full Management
+ <LI> User friendly management of <TT>Rescale Slope</TT> and
+ <TT>Rescale Intercept</TT>
+ <LI> Allow parsing the <TT>Shadow groups</TT> against a user supplied
+ private <TT>Dicom Dictionary</TT> (pfff!...)
+ </UL>
+</UL>