UPDF Meeting Minutes
Philadelphia, PA
May 28, 1999

1. <UPDFVersion> and FormatVersion tags

Do we need a major and minor tag for UPDFVersion?
IPP does have a major and minor version. Idea is that a parser can parse 1.0 and 1.2 versions of a UPDF file and it will work reasonably well. However, there is no guarantee that version 2.0 will contain the same or similiar functionality as a 1.0 UPDF file.
It was decided a single tag using a x.xx format is fine.
It was also decided that an additional tag is needed to distinguish between different versions of the UPDF file for a particular printer model. Called <FileVersion>. Examples for usage: Can show a firmware change in the printer. Printer driver may want to take advantage of new capability in later firmware. Or it could be used to show a new render plug-in is available to the driver.
Format of <FileVersion> is uint32. Also it cannot be an empty tag and is mandatory.

2. Checksum

UPDF will not contain a checksum in the UPDF file. While checksums can be generated programmatically, it is not so easy for a human to create. Since we believe most UPDFs will be created by humans, it's best to let the printer driver create any checksums it needs. ISSUE: How is the driver notified that something in the printer has changed. For example, a new paper handling device or addition of memory or a new paper tray.

3. Imaging model to use for PDL description

Look at the different models available today to see if they will work. Two suggestions are the W3C solutions - Scalable Vector Graphics (SVG) and PGML.

4. QuickSets

In the UPDF User Interface section there should be the ability to specify groups of UI settings or other features such as print quality. Printer driver UIs today have that capability.

5. Locale and Default Paper handling

In past meetings there has been quite alot of discussion about listing paper handling defaults for locales. Current proposal is to have a single listing for each locale that particular UPDF supports. Previously, there was some discussion about allowing for a list of defaults for each locale. Since the trend is toward increasing the numbers of locales supported, having a list would result in a very lengthy list of locales for each paper handling default.
Should we put all items for a locale in a separate section or put the locales in each paper handling section? Probably harder for parsers and UPDF writer if paper handling is dispersed throughout the entire file. Define locale in each paper handling section.
Should UPDF show all device capabilities or should it show the current view of the printer?
A Locale white paper is being written to propose how Locales should be specified in the UPDF Spec and also to show how the various OSs support different locales.

6. virtual units

PPD uses 1/72" for units. Most drivers use 7200 as a virtual unit. GPD uses least common multiple. However new printers have odd DPI units and using the least common multiple may have problems. Check into other types of devices to make sure our virtual unit will work for them. Such as digital camera and scanner.

7. User Interface tags

All User interface tages will be optional. It will be up to the printer driver to expose which UI tags it wants to.

Agfa Font Metric Presentation

UPDF Specification

XML Links

Links and info

Mailing Lists

General Discussion: upd@pwg.org

To Subscribe:

• Send mail to majordomo@pwg.org with the following in the body of the message:
  subscribe upd

Archive: ftp://ftp.pwg.org/pub/upd