It is unsatisfactory to store printer settings in OS-dependent binary formats like DEVMODE structures. This is a considerable security concern (DEVMODE structures are loaded directly into device driver memory), as well as lacking cross-platform adaptability. There is also no interoperability with print settings as currently defined.

Default DEVMODE stucture should be XML, optional within binary adressable by a unique identifier.
Or better

Model device settings in XML for interoperability and platform neutrality. In any case, require a datatype or format identification for these settings like a MIME type or XML Namespace, so that a processing application can decide whether and how to interpret that information. Require applications to round-trip unknown device settings.

- Part 1, Section 15.2.14

Te

Proposed Disposition of DIS 29500 Comment DE-0010 (Modified: 2008-01-04) Agreed; One of the primary design goals for the Office Open XML formats was to provide open and XML-conformant independence from proprietary formats and features. DEVMODE structures are found in the large corpus of existing binary documents, and DIS 29500 defines a format for high-fidelity representation of those documents. As such, it allows for storage of the DEVMODE structure within the package, to preserve the content of those structures in existing binary documents. The members of Ecma TC45 felt that failure to preserve this existing content would be perceived as a loss of fidelity and interoperability by persons who have found the presence of this structure useful in existing documents. We note that there are many types of non-XML content allowed in common office document formats, including image and media formats. In the case of printer settings, there does not currently exist an ISO/IEC standard for storing this information in an XML-based format. If and when such a format becomes available, DIS 29500 will be able to use that format for storage of printer settings, and implementers may then choose to convert existing DEVMODE structures to an XML-based alternative if so desired. In order to encourage more interoperable documents, the following changes will be made to Part 1 §15.2.14: 15.2.14 Printer Settings Part Content Type: application/vnd.openxmlformats-officedocument.spreadsheetml.printerSettings (in SpreadsheetML documents) application/vnd.openxmlformats-officedocument.wordprocessingml.printerSettings (in WordprocessingML documents) Root Namespace: not applicable Source Relationship: http://schemas.openxmlformats.org/officeDocument/2006/relationships/printerSettings An instance of this part type contains information about the initialization and environment of a printer or a display device. The layout of this information data structure is application-defined. [Note: It is recommended that a Printer Settings Part contain well documented XML content for improved interoperability; however, there is no requirement on the format of the content contained in a Printer Settings Part. end note] [Example: An Office Open XML producer on Windows might store the DEVMODE structure defined here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/gdi/prntspol_8nle.asp , while an application on the Mac OS might choose to store the print record defined here: http://developer.apple.com/documentation/Carbon/Reference/CarbonPrintingManager_Ref/Reference/reference.html . end example] A SpreadsheetML package is permitted to contain at most one Printer Settings part per Chartsheet, Dialogsheet, or Worksheet part, and that part shall be the target of an implicit relationship from a Chartsheet (§12.3.2), Dialogsheet (§12.3.7), or Worksheet (§12.3.24) part. A WordprocessingML package is permitted to contain zero or more Printer Settings parts, one per sectPr element, each a target of an explicit relationship from a Main Document (§11.3.10) or Glossary Document (§11.3.8) part. [Example: The following SpreadsheetML Worksheet part-relationship item contains a relationship to a Printer Settings part, which is stored in the ZIP item ../printerSettings/printerSettings1. bin xml : <Relationships xmlns="..."> <Relationship Id="rId4" Type="http://.../printerSettings" Target="../printerSettings/printerSettings1.bin"/> </Relationships> where the contents of PrinterSettings.xml could contain the following XML: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <PrinterSettings xmlns="..."> <PrinterSetting name="PropertyName" value="PropertyValue" /> </PrinterSettings> end example] Similar Comments: CL-0044 , CL-0049 , CO-0005 , CO-0147 , CO-0148 , DE-0153 , DK-0106 , DK-0152 , DK-0160 , FR-0019 , GB- 0047 , IN-0053 , IN-0079 , IR-0006 , KR-0003 , NZ-0014 , US-0037