attachment-0001

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.0.4712.0"> <TITLE>Conf Call Summary</TITLE> </HEAD> <BODY>  Next meeting is Friday March 14 at 10am Summary: Media Sizes supported. Width: Intersection of A4 and letter. Clip box � inch in from each side.  If won’t fit on renderer’s page, can scale image (require isomorphic scaling) and must notify the receiving user.   --- What about length?  In the Feb 25 call we had pondered not bounding the length of a page an allowing the device to split the image across pages. Resolution: Require a min/max?                 In the data – min and max in the data stream, not discrete values, but ranges or ok.  300 pdi min. 1200 max.                 On the output device – 300 min.  No maximum.                 Image must be +- a point of the original size.  (not per inch, per object) Required ColorSpace(s) – Require the device to support sRGB and gray gama 2.2; the sender can pick either of the two but MUST include the profile in the pdf/is data stream � Only thing left to negotiate is buffer size….Just pick a size and then not negotiate. Put a stake at 4meg and turn during interop..  Remove memory size attribute   Still open: �� Sender-URI Stamps. �� Coloring of attributes based on compression. (Resolutions) ToDo: �� Walk through references section and split into Normative-v-Informative -----Original Message----- From: Gail Songer Sent: Tuesday, February 25, 2003 1:01 PM To: 'ifx@pwg.org' Subject: Conf Call Summary Today’s Conference Call Summary: � Drop Flate from list of pdfis-compressions-supported (this used to be pdfis-profiles-supported) Make Masking mandatory for the receiver. Require both the sender and the receiver to support and use Banding.� Drop support for Tiling. Color-space will be ICC with only the sRGP color profile.� A pdfis device wouldn’t have to process the profile, but the inclusion of the profile in the datastream would allow a PDF reader to process the document. � Coloring by pdfis compression schemes: �� No longer need the following attributes: <UL><UL> pdfis-compressions-supported (all compressions are required) pdfis-color-spaces-supported (only one colorspace) pdfis-data-encryption-supported �(encryption types do not very based on compression) pdfis-cache-size-k-octets-supported (we will just pick a single required number) pdfis-orientation-supported – all images will be in landscape. � </UL></UL> Still Open: �� Media Sizes supported. Width: Intersection of A4 and letter. Clip box � inch in from each side.  If won’t fit in renderer, can scale image (required isomorphic scaling) and must notifiy the receiving user. �� Resolution: Require a min/max?                 In the data – min and max in the data stream, not discrete values, but ranges or ok.  300 pdi min. 1200 max.                 On the output device – 300 min.  No maximum.                 Image must be +- a point of the original size.  (not per inch, per object) �� Sender-URI Stamps. �� Coloring of attributes based on compression. (Resolutions) �� Required ColorSpace(s) – sRGB and gray gama 2.2 � Only thing left to negotiate is buffer size….Just pick a size and then not negotiate 4meg.  No memory size attribute   ToDo: �� Walk through references section and split into Normative-v-Informative � � � </BODY> </HTML>