Ira observed that he could find the referenced message from Mike Sweet.
Sorry, my error.The message from Mike Sweet was 11 February, not 10
February. It reads as indicated below. Although Mike does not say this, it
might be reasonable to suggest that, if there is insufficient information in
identifying the version of a PDL, is there much benefit in identifying the
PDL family? Nevertheless, I take Mike's comment not to mean that we should
not add variants, but that there is limited benefit in being too thorough.
I am ambivalent about adding a whole list of variants - for example, "PCL3"
isn't enough since (for example) HP's current products use something called
"PCL3GUI" to support RGB bitmap printing - a significant difference.
Similarly, PDF 1.4 and 1.6 are much more prevalent than PDF 1.7, and in fact
ISO 32000 and PDF 1.7 are not quite the same thing. Adobe has also added
extensions to ISO 32000 since its publication, yet it is all just "PDF
For PostScript, I'm not sure that there are any new products (or old
products that would be updated) that support anything other than PS3, so I'm
not sure it is necessary to register PS2. Even if we did register PS2
support, there are a number of optional PS2 features that would also need to
be advertised (TrueType and CID font support, in particular) to make the
An alternate approach would be to *not* include this information in the
command set but instead have separate keys for the major PDLs (PCL, PDF, and
PS), or make them first-class attributes for IPP (and the corresponding
semantic model - "pdf-versions-supported", "pcl-versions-supported", etc...)
so that we can track major versions and extensions needed for a client to
know what kind of data the printer can accept.
Michael Sweet, Senior Printing System Engineer
From: Ira McDonald [mailto:blueroofmusic at gmail.com]
Sent: Monday, February 22, 2010 5:58 PM
To: William Wagner; Ira McDonald
Subject: Re: [WIMS] F2F Minutes posted - Concall 1 March
I can't find ANY message of Mike Sweet's from 10 February
about PDL variants for Printer MIB.
Could you please forward it to the WIMS list?
Even if Mike argued we shouldn't register variants, the strong
concensus of a number of PWG members is that we *should*
and that *is* the only possible resolution of Jerry Thrasher's
PWG Last Call comment against PWG Command Set Format
for IEEE 1284 Device ID.
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
mailto:blueroofmusic at gmail.com
579 Park Place Saline, MI 48176
PO Box 221 Grand Marais, MI 49839
On Mon, Feb 22, 2010 at 5:48 PM, William Wagner <wamwagner at comcast.net>
> The minutes of the February 9 Face-to-face meeting have been posted at
>ftp://ftp.pwg.org/pub/pwg/wims/minutes/wims_100209.pdf. Many thanks to
> for the notes.
>>>> The next WIM/PMP phone conference will be March 1, at 2 PM ET.
>>>> The tentative agenda is:
>> 1. Identify Minute-taker
>> 2. Statement that meeting is held in accord with PWG IP Policy
>> 3. Consideration of Agenda
>> 4. Accept Minutes of February 9 meeting
>> 5. Check on action items:
>> Ø Bill Wagner: send query relative to additions to
> PrtInterpreterLangFamilyTC (done)
>> Ø Bill Wagner: seek acknowledgement of successful PWG last call for
> ID "COMMAND SET" PWG spec
>> Ø Rick Landau: complete CR for Printer Classes and submit to CIM (done)
>> Ø Rick Landau and Ira McDonald: review Print Service related MOFs,
> CRs, and submit to CIM
>> Ø Ira McDonald: continue to address open and new Power Management
> documents issues
>> 6. Consider PWG Last call comments on the 1284 command set IP spec
>> 7. Consider entries to be added to PrtInterpreterLangFamilyTC (especially
> see Mike Sweets message of 10 February.)
>> 8. Further consideration of Power Management Specs (Pending posting of
>> 9. Next Steps
>>>> Bill Wagner, Chairman - Workgroup for Imaging Management Solutions/PWG
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> wims mailing list
>wims at pwg.org>https://www.pwg.org/mailman/listinfo/wims>>
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.