The National Archives
Search our website
  • Search our website
  • Search our records
   
 
Image of software box and CD PRONOM
Welcome (PRONOM  home page) About PRONOM Add an entry
Search Help - opens in a new window Information resources - opens in a new window
 
 
 

*Details: File format summary

   
 

 

Search by keyword Search by file format Search by PUID Search by software Search by vendor Search by lifecycles Search by Migration Pathway

Details for:

Save as... XML | CSV Printer friendly version
 
 

Summary

Name AutoCAD Design Web Format
Version 6.0
Other names  
Identifiers MIME:  application/dwf
MIME:  application/x-dwf
MIME:  drawing/x-dwf
MIME:  image/vnd.dwf
MIME:  image/x-dwf
MIME:  model/vnd.dwf
PUID:  x-fmt/49
Family  
Classification Model
Disclosure  
Description AutoCAD Design Web Format (DWF) version 6 is the publishing format of Autodesk software, especially design data, such as 2D vector data, 3D vector data, animations, and metadata. It uses the ZIP file format as the backing store mechanism. The content can be roughly divided into: • DWF metadata files – XML files that contain information pertaining to metadata and structure (author, title, creation time, section dependencies, section ordering, resource file descriptions, roles, MIME types, etc.) and pertaining to the section (page information, design metadata, etc.). The structural metadata is used to create logical objects (collections of files to represent a part or page, etc.). • Resource files – media or other content files that are referenced from the package/section metadata and are usually presentations of design data in various formats (ZGL, W2D, JPG, PNG, AVI, XML, TXT, DOC, etc.) A DWF package must meet the following requirements: • The first 12 bytes of the physical package file must contain the DWF version header. • A manifest.xml file at the root of the zip archive that complies to the manifest.xsd schema • File contents logically organized into sections, one for each component of the composite design. • At least one resource file. • The manifest must contain an <Interfaces> element containing at least one <Interface> sub element that indicates a document interface supported by the DWF package. An example would be the ‘ePlot’ document interface, which implies that the DWF contains at least one valid ePlot page.
Orientation Text
Byte order  
Related file formats None.
Technical Environment  
Released  
Supported until  
Format Risk  
Developed by Autodesk Corporation
Supported by None.
Source The National Archives and Records Administration / The National Archives and Records Administration
Source date 02 Aug 2005
Source description File format information supplied by NARA Information Services/Applied Research Division, The National Archives and Records Administration.
Last updated 28 Aug 2012
Note  
Top of page Top of page
 
         
The National Archives Newsletter Icon

Send me The National Archives’ newsletter

A monthly round-up of news, blogs, offers and events.