JPEG is often used in place of JFIF. JFIF is the JPEG File Interchange Format, the main image file format defined by the Joint Photographic Experts Group. The JFIF MIME type is 'image/jpeg' (defined in RFC 1341) and its most common file name extensions are '.jpg', '.jpe', '.jpeg', '.jfif', '.jfi'.
JFIF is most commonly used for photorealistic images at 24 bits per pixel, using lossy compression. The higher the degree of compression (the smaller the file size), the lower quality the image is. It is a trade-off between size and quality.
Alternatively, JPEG is used (again, improperly) to refer to Exif images. Exif is the Exchangeable image file format, a specification for the file format used by digital cameras. Exif uses existing image formats such as JFIF and TIFF, and adds support for metadata tags (comments, creation time, copyright, etc.). It was created by Japan Electronic Industry Development Association (JEIDA).
GIF, the graphic interchange format, is a bitmap image format introduced by CompuServe in 1987. It is possibly the most commonly used image file format on the Internet. The GIF MIME type is 'image/gif' with the file extension '.gif'. It supports up to 256 colors and supports LZW lossless compression (meaning there is no trade-off between quality and size), but larger images usually have much larger file sizes than with other formats.
GIF also supports animations and transparency (two things the main JFIF standard do not support).
A URL is a uniform resource locator, as defined in RFC 1738. It was defined primarily by Tim Berners-Lee (credited with having created the World Wide Web) at CERN (a particle accelerator lab) and other members of the URI working group of the IETF. URL provides a generic syntax for describing locations on the Internet. URL has largely been superceded by URI. An example URL (with permitted quoting marks) is
.
A URI is a uniform resource identifier, defined in RFC 2936, provides a generic syntax for the location of resources (files or streams, for example) on the Internet. URI can basically be semtantically translated as:
[scheme ":"]["//" [username [":" password] "@"] host [":" port]]path["?" query]["#" fragment]
where bracketed groups ("[ ... ]") are optional and quoted items are string literals. Some example URIs follow:
/question/;_ylt=Ah78hEWZdiAlRiqzZaqAppsezKIX (just a path)
//answers.yahoo.com (an "authority" with only host name, and an empty path)
http:/question (scheme and path)
http://anonymous:user@example.com:80/some/file?a=b&c=d#item (all optional parts included)
//127.0.0.1 (an authority made up of an IPv4 address)
ftp://bob:le214@[::1]:2100/docs (::1 is an IPv6 address)
telnet://www.my.site:1080
file:///some/random/file
FTP is the file transfer protocol, defined in RFC 959. FTP supports authoritative file management capabilities using the typical client-server paradigm. To quote RFC 959, "The objectives of FTP are 1) to promote sharing of files (computer programs and/or data), 2) to encourage indirect or implicit (via programs) use of remote computers, 3) to shield a user from variations in file storage systems among hosts, and 4) to transfer data reliably and efficiently."
Telnet is a high level TCP protocol. It's primary purpose is to provide a simple mechanism for a client to communicate with a server and vice versa. A telnet client is often used for other text-based protocols or remote textual user interfaces.
The Internet Gopher Protocol is a "distributed document search and retrieval protocol", defined in RFC 1436. The Gopher RFC defines a gopher as "software following a simple protocol for burrowing through a TCP/IP internet." It is largely defunct now, replaced by the World Wide Web.
RFC, which is repeated in this answer several times, stands for "request for comments". RFCs are open standards or genuine requests for comments. RFCs define almost every part of the Internet and are maintained by the IETF, another acronym mentioned in here.
IETF is the Internet Engineering Task Force, an ISOC (Internet Society) organisation. IETF does not accept RFCs as standards until they have actually been implemented and gone through the whole RFC process described in RFC 2026, the Internet Standards Process.
As already described as concisely as it can get, img is an abbreviation for image, used in HTML, and src is likewise an abbreviation for source (the URI of a resource).