attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns:o = "urn:schemas-microsoft-com:office:office"><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII"> <META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD> <BODY> <DIV>NOTE:  Please send any comments on this note to the <A href="mailto:pwg@pwg.org">pwg@pwg.org</A>, instead of a Reply-ALL.  We don't want to use PWG-ANNOUNCE for discussion threads, just announcements.</DIV> <DIV> </DIV> <DIV>Harry has pointed out that we shouldn't number PWG standards with IEEE-ISTO numbers, either in the file name or on the first page and page headers until they are approved (past PWG Last Call).  Then we avoid leaving holes in the numbering space and mis-leading readers into thinking that a draft is an approved standard.  Also the file names can be more meaningful while they are drafts.</DIV> <DIV> </DIV> <DIV>At the PWG Semantic Model call today with a lot of attendees, we agreed to remove the numbers from the next drafts and use the new file naming scheme and the old copy should be deleted from the PWG site.  If a document isn't being updated in the next couple of weeks, then the existing document should be renamed on the PWG site.</DIV> <DIV> </DIV> <DIV>On the first page and page headers, instead of the IEEE-ISTO number, put 5100.x for IPP documents and 510n.y for documents for new categories, such as IPPFAX, that haven't any documents approved.</DIV> <DIV> </DIV> <DIV>For a file naming scheme for drafts before they are approved, the file names for PWG documents intending to become IEEE-ISTO documents, we agreed to the following simple file naming scheme:</DIV> <DIV> </DIV> <DIV>pwg-group-aaa-bbb-Vnn-yymmdd.doc, .pdf</DIV> <DIV>pwg-group-aaa-bbb-Vnn-yymmdd-rev.doc, .pdf, red-lined versions</DIV> <DIV> </DIV> <DIV>where:</DIV> <DIV>pwg indicates a pwg document</DIV> <DIV>group indicates the group and probably is the short DL name, i.e, ipp, sm, ifx, psi, etc.</DIV> <DIV>aaa-bbb are meaningful words or abbreviations (see below, but keep it fairly short so the file URL don't line wrap in email)</DIV> <DIV>Vnn is the version number starting at V01 and incrementing by one (authors can increment the date for the same version while yymmdd is the year month and day, so that they sort in ascending order by date.</DIV> <DIV> </DIV> <DIV>No underlines, since they look like spaces in underlined URLs</DIV> <DIV>No spaces, since they don't work in some systems.</DIV> <DIV> </DIV> <DIV>In order to make the web site for each project point to a stable URL, each document should be copies twice to the PWG site with the stable file name being:</DIV> <DIV> </DIV> <DIV>pwg-group-aaa-bbb-latest.doc, .pdf</DIV> <DIV> </DIV> <DIV>where the rest of the file name before the latest is invariant with successive versions and is the same pwg-group-aaa-bbb as the file name that has the version number and the date.</DIV> <DIV> </DIV> <DIV>(We need to update the IPP web page to use the durable URL and start posting file twice so the the IPP web page is as good as the other PWG groups in always pointing to the latest draft of each document).</DIV> <DIV> </DIV> <DIV>Here are some suggested names for the existing IEEE-ISTO versions of PWG IPP documents showing their existing URL and the suggested URL on the following line:</DIV> <DIV> </DIV> <DIV> <INS>1.       </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:46>IEEE-ISTO 5100.5-2002</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:49> [doc-obj]</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:55>, “Internet Printing Protocol (IPP): Document Object, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:57>Hastings, T. and P. Zehler</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-15T16:53>, September 7, 2002</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-15T16:57>, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:29>work in progress, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-15T16:57><A href="ftp://ftp.pwg.org/pub/pwg/new_DOC/IPP-Document-Object-020927.pdf">ftp://ftp.pwg.org/pub/pwg/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:30>new_DOC/IPP-Document-Object-020927.pdf</A> </INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:30></INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:30><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-15T16:57><A href="ftp://ftp.pwg.org/pub/pwg/new_DOC/pwg-ipp-document-object-V01-020927.pdf">ftp://ftp.pwg.org/pub/pwg/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:30>new_DOC/pwg-ipp-document-object-V01-020927.pdf</A></INS></INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:48><o:p></o:p></INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:48>2.       </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:48>IEEE-ISTO 5100.6-2002 [</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T23:14>not</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:48>-srv]</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:57>, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:49> “Distributed Notification Service”</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:57>, Hastings, T., Lewis, H., and I</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T23:09>.</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-08T12:57> McDonald</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-15T16:54>, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:35>October 3</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-15T16:54>, 2002</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-15T16:57>, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:29>work in progress, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-09-15T16:57><A href="ftp://ftp.pwg.org/pub/pwg/new_NOT/ipp-dist-not-service-021003-rev.pdf">ftp://ftp.pwg.org/pub/pwg/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:31>new_NOT/ipp-dist-not-service-021003-rev.pdf</A> </INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:31> <A href="ftp://ftp.pwg.org/pub/pwg/new_NOT/pwg-ipp-dist-not-service-V01-021003-rev.pdf">ftp://ftp.pwg.org/pub/pwg/<INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:31>new_NOT/pwg-ipp-dist-not-service-V01-021003-rev.pdf</A> </INS></INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25><o:p></o:p></INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25>3.       </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25>IEEE-ISTO 5100.7-2002 [prod-print2],  “</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:32>Production Printing Attributes – Set 2</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25>”, Hastings, T., and </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:34>D. Fullman</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:33>,</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25> September 27, 2002, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:30>work in progress, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25><A href="ftp://ftp.pwg.org/pub/pwg/new_PPE/pwg-ipp-prod-print-set2-020927.pdf">ftp://ftp.pwg.org/pub/pwg/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:28>new_PPE/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:27>pwg-ipp-prod-print-set2-020927.pdf</A> </INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:27> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25><A href="ftp://ftp.pwg.org/pub/pwg/new_PPE/pwg-ipp-prod-print-set2-V01-020927.pdf">ftp://ftp.pwg.org/pub/pwg/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:28>new_PPE/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:27>pwg-ipp-prod-print-set2-V01-020927.pdf</A> </INS></INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25><o:p></o:p></INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25>4.       </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25>IEEE-ISTO 5100.8-2002 [</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:26>color</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25>],  “</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:36>Color and Imaging Attributes</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25>”, Hastings, T., </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:35>and D. Fullman, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:36>October 8</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25>, 2002, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:30>work in progress, </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25><A href="ftp://ftp.pwg.org/pub/pwg/new_COLOR/pwg-ipp-color-and-imaging-021008.pdf">ftp://ftp.pwg.org/pub/pwg/new_COLOR/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:28>pwg-ipp-color-and-imaging-021008.pdf</A> </INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:28> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25><A href="ftp://ftp.pwg.org/pub/pwg/new_COLOR/pwg-ipp-color-and-imaging-D01-021008.pdf">ftp://ftp.pwg.org/pub/pwg/new_COLOR/</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:28>pwg-ipp-color-and-imaging-D01-021008.pdf</A> </INS></INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-11T17:55><o:p></o:p></INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-11T22:47>5.       </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-11T17:55>IEEE-ISTO 5100.9-2002 </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T16:13>[actual] </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T16:11>Internet Printing Protocol (IPP), “-actual” attributes extension</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T16:12>, Carney, D., and H. Lewis, work in progress, October 18, 2002. </INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T16:12><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-08T21:25><A href="ftp://ftp.pwg.org/pub/pwg/new_ACT/pwg-ipp-actual-attributes-V01-021018.pdf">ftp://ftp.pwg.org/pub/pwg/new_ACT/pwg-ipp</INS>-actual-attributes-V01-021018.pdf</A></INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T16:12>And the following two have not yet been published at all and will be published without numbers using the agreed scheme:</INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-22T14:45>6.       </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-22T14:45>IEEE-ISTO 5100.10-2002 [</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-22T14:47>mime-parm]  Internet Printing Protocol (IPP), “PWG MIME Standard parameters</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-22T14:48> for Document Formats”, McDonald, I, and T. Hastings, work in progress </INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-22T14:48><A href="ftp://ftp.pwg/org/pub/pwg/new_MIMEPARM/pwg-ipp-mime-parm-D01-0210xx.pdf">ftp://ftp.pwg/org/pub/pwg/new_MIMEPARM/pwg-ipp-mime-parm-D01-yymmdd.pdf</A></INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T15:34>7.       </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T15:34>IEEE-ISTO 5100.11-2002 [pnsp], “</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T15:34>Internet Printing Protocol (IPP): Distributed Notification Service - Printer to Notification Server Protocol (PNSP)”, I. McDonald, <draft-mcdonald-ipp-dist-not-pnsp-00.txt>, work in progress, September 25, 2002</INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-22T14:49>. </INS> <INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-22T14:49><A href="ftp://ftp.pwg/org/pub/pwg/new_NOT/pwg-ipp-pnsp-D01-yymmdd.pdf">ftp://ftp.pwg/org/pub/pwg/new_NOT/pwg-ipp-pnsp-D01-yymmdd.pdf</A> </INS><INS cite=mailto:Thomas%20N.%20Hastings dateTime=2002-10-17T15:38><o:p></o:p></INS></DIV> <DIV class=OutlookMessageHeader align=left> </DIV> <DIV class=OutlookMessageHeader align=left>The IPPFAX documents should use the above scheme for the IPPFAX Protocol and PDFax documents (and UIF put into historical), instead of using 5102.1 for IPP FAX protocol, 5102.2 for UIF and 5102.3 for PDFax.  So their numbers would be:</DIV> <DIV class=OutlookMessageHeader align=left>510n.x and file name, say, pwg-ifx-protocol-V12-yymmdd.doc and pwg-ifx-pdfax-V03-yymmdd.doc</DIV> <DIV class=OutlookMessageHeader align=left> </DIV> <DIV class=OutlookMessageHeader align=left> On a related note to PWG process, Rick Seeler points out that according to our PWG process, all of the above documents should be labeled as versions of PWG Proposed Standards, not PWG Draft Standards.</DIV> <DIV class=OutlookMessageHeader align=left> </DIV> <DIV class=OutlookMessageHeader align=left>Tom</DIV> <BLOCKQUOTE> <DIV class=OutlookMessageHeader dir=ltr align=left> </DIV> <DIV class=OutlookMessageHeader dir=ltr align=left> </DIV> <DIV class=OutlookMessageHeader dir=ltr align=left> -----Original Message----- From: Harry Lewis [mailto:harryl@us.ibm.com] Sent: Thursday, October 24, 2002 08:56 To: imcdonald@sharplabs.com; hastings@cp10.es.xerox.com; Dennis Carney Cc: don@lexmark.com Subject: Recent ISTO drafts </DIV> Guys... I'm not sure we should be grabbing numbers (ex.5100.10) for DRAFTS! The process should recognize that a draft may not be approved. The number should probably be assigned AFTER approval. ---------------------------------------------- Harry Lewis IBM Printing Systems ---------------------------------------------- </BLOCKQUOTE></BODY></HTML>