RFC 1980: A Proposed Extension to HTML : Client-Side Image Maps
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2854.
Current document in this lineage: RFC 2854 — The 'text/html' Media Type
In plain English — editorial summary, not part of the RFC
The markup language known as "HTML/2.0" provides for image maps. Image maps are document elements which allow clicking different areas of an image to reference different network resources, as specified by Uniform Identifier (URIs). The image map capability in HTML/2.0 is limited in several ways, such as the restriction that it only works with documents served via the "HTTP" protocol, and the lack of a viable fallback for users of text-only browsers. This document specifies an extension to the HTML language, referred to as "Client- Side Image Maps," which resolves these limitations.
Document record
- Document ID
- RFC1980
- Published
- August 1996
- Authors
- J. Seidman
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 2854
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2376XML Media TypesObsoleted
July 1998
- RFC 2731Encoding Dublin Core Metadata in HTMLObsoleted
December 1999
- RFC 3120A URN Namespace for XML.orgCurrent
June 2001
- RFC 1942HTML TablesObsoleted
May 1996
- RFC 1867Form-based File Upload in HTMLObsoleted
November 1995
- RFC 2187Application of Internet Cache Protocol (ICP), version 2Current
September 1997
- RFC 3087Control of Service Context using SIP Request-URICurrent
April 2001
- RFC 2110MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)Obsoleted
March 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?