draft-seantek-windows-image-00.txt   draft-seantek-windows-image-01.txt 
Network Working Group S. Leonard Network Working Group S. Leonard
Internet-Draft Penango, Inc. Internet-Draft Penango, Inc.
Intended Status: Informational December 17, 2014 Intended Status: Informational September 4, 2015
Expires: June 20, 2015 Expires: March 7, 2016
Windows Image Media Types Windows Image Media Types
draft-seantek-windows-image-00 draft-seantek-windows-image-01
Abstract Abstract
This document registers media types for certain image formats This document registers media types for certain image formats
promulgated in Microsoft Windows, namely image/wmf, image/x-wmf, promulgated in Microsoft Windows, namely image/wmf, image/x-wmf,
image/emf, image/x-emf, and image/bmp for use with Windows Metafile, image/emf, image/x-emf, and image/bmp for use with Windows Metafile,
Enhanced Metafile, and Windows Bitmap formats. Originally designed Enhanced Metafile, and Windows Bitmap formats. Originally designed
for Microsoft Windows 2.0 and 3.0, these image files are intended to for Microsoft Windows 2.0 and 3.0, these image files are intended to
be portable between applications and devices, and may contain both be portable between applications and devices, and may contain both
vector and raster graphics. vector and raster graphics.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 4, line 16 skipping to change at page 4, line 16
structures. As the 90s wore on, the venerable BMP got boosts with structures. As the 90s wore on, the venerable BMP got boosts with
support for additional color spaces, color profiles, and compression support for additional color spaces, color profiles, and compression
formats. The same basic format can be used to convey 2-bit black-and- formats. The same basic format can be used to convey 2-bit black-and-
white bitmaps with a 1-bit alpha mask from the '80s, and full-color white bitmaps with a 1-bit alpha mask from the '80s, and full-color
Ultra HD images on leading-edge displays. BMP is a building block of Ultra HD images on leading-edge displays. BMP is a building block of
other formats, including Windows Metafiles, Windows Icons, and other formats, including Windows Metafiles, Windows Icons, and
Windows Cursors. Windows Cursors.
Many implementations of BMP were created because of Windows' Many implementations of BMP were created because of Windows'
commercial success in the 1990s. Usage of the format for interchange commercial success in the 1990s. Usage of the format for interchange
has [[probably?]] declined since the advent of PNG (for lossless has declined since the advent of PNG (for lossless raster graphics)
raster graphics) and JPEG (for lossy raster graphics); however, a and JPEG (for lossy raster graphics); however, a large body of free
large body of free and commercially available BMP artwork exists. and commercially available BMP artwork exists. Since Windows Icons
Since Windows Icons are a building block of "favicon.ico" Web are a building block of "favicon.ico" Web technology, an implementer
technology, an implementer would almost certainly need to support would almost certainly need to support this format for basic
this format for basic interoperability. interoperability.
Microsoft publicly documented the BMP format as early as the 1992 Microsoft publicly documented the BMP format as early as the 1992
Windows 3.1 SDK (in the Windows Metafile documentation). Since 2007 Windows 3.1 SDK (in the Windows Metafile documentation). Since 2007
Microsoft has released the format specification [MS-WMF], which Microsoft has released the format specification [MS-WMF], which
includes most components of the Windows Bitmap format, under its Open includes most components of the Windows Bitmap format, under its Open
Specification Promise [MS-OSP]. See Section 2.2.2.9 of [MS-WMF] Specification Promise [MS-OSP]. See Section 2.2.2.9 of [MS-WMF]
(DeviceIndependentBitmap Object). BMP data begins with a (DeviceIndependentBitmap Object). BMP data begins with a
BITMAPFILEHEADER and is followed by one of the bitmap headers BITMAPFILEHEADER and is followed by one of the bitmap headers
(BITMAPINFOHEADER, BITMAPV4HEADER, or BITMAPV5HEADER), optional color (BITMAPINFOHEADER, BITMAPV4HEADER, or BITMAPV5HEADER), optional color
table data, bitmap data, and optional profile data, in that order table data, bitmap data, and optional profile data, in that order
skipping to change at page 6, line 38 skipping to change at page 6, line 38
Explorer). Explorer).
Fragment identifier considerations: None. Fragment identifier considerations: None.
Additional information: Additional information:
Deprecated alias names for this type: image/x-wmf Deprecated alias names for this type: image/x-wmf
Magic number(s): D7 CD C6 9A (little-endian DWORD 0x9AC6CDD7) Magic number(s): D7 CD C6 9A (little-endian DWORD 0x9AC6CDD7)
File extension(s): .wmf File extension(s): .wmf
Macintosh file type code(s): Macintosh file type code(s):
????. A uniform type identifier (UTI) of "????" is RECOMMENDED. None. A uniform type identifier (UTI) of "com.microsoft.wmf" is
RECOMMENDED.
Person & email address to contact for further information: Person & email address to contact for further information:
Sean Leonard <dev+ietf@seantek.com> Sean Leonard <dev+ietf@seantek.com>
Restrictions on usage: None. Restrictions on usage: None.
Author/Change controller: Sean Leonard <dev+ietf@seantek.com> Author/Change controller: Sean Leonard <dev+ietf@seantek.com>
Intended usage: COMMON Intended usage: COMMON
skipping to change at page 9, line 5 skipping to change at page 9, line 5
Deprecated alias names for this type: image/x-emf Deprecated alias names for this type: image/x-emf
Magic number(s): 01 00 00 00 (little-endian DWORD 0x00000001), Magic number(s): 01 00 00 00 (little-endian DWORD 0x00000001),
corresponding to the EMR_HEADER Type field. corresponding to the EMR_HEADER Type field.
The next field (EMR_HEADER Size) should be The next field (EMR_HEADER Size) should be
at least 88 (little-endian DWORD 0x00000050). at least 88 (little-endian DWORD 0x00000050).
File extension(s): .emf File extension(s): .emf
(for both EMF and EMF+ content) (for both EMF and EMF+ content)
Macintosh file type code(s): Macintosh file type code(s):
????. A uniform type identifier (UTI) of "????" is RECOMMENDED. None. A uniform type identifier (UTI) of "com.microsoft.emf" is
RECOMMENDED.
Person & email address to contact for further information: Person & email address to contact for further information:
Sean Leonard <dev+ietf@seantek.com> Sean Leonard <dev+ietf@seantek.com>
Restrictions on usage: None. Restrictions on usage: None.
Author/Change controller: Sean Leonard <dev+ietf@seantek.com> Author/Change controller: Sean Leonard <dev+ietf@seantek.com>
Intended usage: COMMON Intended usage: COMMON
 End of changes. 6 change blocks. 
12 lines changed or deleted 14 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/