I N T R A N E T
                                      
                                 Web Pages
                                      
                             Phantom .map files
                                      
   .map files are part of the server-side mechanism supporting browsers
   incapable of understanding the <MAP> and <AREA> tags. These files look
   nothing like HTML and are a nuisance to maintain in tandem with the
   modern HTML-based image maps. The webserver has now been told how to
   read <MAP> and <AREA> tags in .html files directly, reducing image map
   maintenance to the <AREA> tags alone. The only restrictions imposed on
   <MAP> and <AREA> tags used this way is that they must be the first and
   only thing on a line (whitespace excepted).
   
   Phantom .map behaviour is invoked with something like the following:
<!-- Pretend this is a snippet from the file somefile.html -->

        <MAP NAME="whatever">
        <AREA...> (several of these)
        </MAP>

        <A HREF="somefile.html.whatever.map">
        <IMG SRC="some.gif" ISMAP USEMAP="#whatever">
        </A>

   Conceptually, the <A HREF> is asking the server to look in the file
   somefile.html for whatever.map, ie the <MAP NAME="whatever"> element.
   (If the .whatever had been omitted - somefile.html.map - the server
   would just have used the first <MAP> tag it came across). The ISMAP in
   the <IMG> tag tells older browsers to send the mouse coordinates to
   the server when they request the link surrounding the image. For
   browsers which don't even support this, the .map is turned into a menu
   of options.
   
   As expected, in the same way that USEMAP="otherfile.html#this" will
   refer to a <MAP NAME="this"> in otherfile.html, so <A
   HREF="otherfile.html.this.map"> will refer to the same thing for the
   server-based system.
   
   Since phantom .map files are something which require server support,
   HREF="http://some.server/somefile.html.this.map" would only work if
   some.server supported it. (This refers to reading the map itself, not
   to the links which a map might make, once read.)
   
   The term Phantom is used because the .map files don't actually exist,
   but they appear to.
   
   Old style .map files are still supported by this module.