3.2.1 Abstract Data Model
This section describes a conceptual model of a possible data organization that an implementation might need to maintain to participate in this protocol. The organization described in this section is provided to facilitate the explanation of how the protocol behaves. This specification does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this specification.
The Web Point-and-Print Protocol depends on an abstract data model that maintains printers. The print server behaves as if it hosted the following objects in the specified hierarchy.
List of Printers: Each printer represents a physical print device or a number of homogeneous physical devices that are installed on the print server. Each printer object maintains the following data elements:
A name that uniquely identifies the printer.
A reference to a printer driver object for the printer.
Per-user printer device settings in a _DEVMODE structure ([MS-RPRN] section 2.2.2.1).
List of Drivers: Each printer driver represents the software component responsible for converting print content submitted by applications into device-specific commands. Each printer driver object maintains the following data elements:
A name that uniquely identifies the printer driver.
A list of well-known modules (that is, rendering module, configuration module, and data module).
Additionally, each printer driver object maintains the following optional data elements:
A list of dependent files.
Information on the printer driver manufacturer, printer driver time stamp, and version.
The abstract data model can relate each printer to a single printer driver ([MS-RPRN] section 3.1.1).