Marc,
Thanks for noticing we have already got the attribute defined - I'll normatively reference it from the PWG Raster spec and then we can decide whether to require it for IPP Everywhere at the F2F...
On Sep 19, 2011, at 1:32 PM, Yousey, Marc wrote:
> PWG 5100.7 already defines the attribute ‘print-content-optimize’ with values of ‘photo’, ‘graphics’, ‘text’ and ‘text-and-grahics’. Can’t we just reference that from the ipp everywhere spec as being required?
>> M.
>>> From: ipp-bounces at pwg.org [mailto:ipp-bounces at pwg.org] On Behalf Of Paul Tykodi
> Sent: Monday, September 19, 2011 8:35 AM
> To: 'Michael Sweet'
> Cc: ipp at pwg.org> Subject: RE: [IPP] Addition to PWG Raster Spec
>> Hi Mike,
>> If we follow the idea to put the new value in JPS3 because it is a better fit and we also reach a point where we believe that PWG Raster is stable but JPS3 still needs some work to be completed, I believe that our “customers” could make an informed decision as to whether they believed it would be in their best interest to begin developing software that was compliant with the draft PWG Raster specification knowing that changes were still possible but not probable while we waited for JPS3 to be finished.
>> Best Regards,
>> /Paul
> --
> Paul Tykodi
> Principal Consultant
> TCS - Tykodi Consulting Services LLC
>> Tel/Fax: 603-343-1820
> Mobile: 603-866-0712
> E-mail: ptykodi at tykodi.com> WWW: http://www.tykodi.com> From: ipp-bounces at pwg.org [mailto:ipp-bounces at pwg.org] On Behalf Of Michael Sweet
> Sent: Monday, September 19, 2011 10:45 AM
> To: Ira McDonald
> Cc: ipp at pwg.org> Subject: Re: [IPP] Addition to PWG Raster Spec
>> Ira,
>> I agree it isn't a great fit in PWG Raster, but if we put it in JPS3 then JPS3 has to be completed before we can finish PWG Raster...
>> On Sep 19, 2011, at 6:42 AM, Ira McDonald wrote:
>>> Hi Mike,
>> About putting "print-content-type" (or whatever name) into
> PWG Raster rather than JPS3.
>> I suggest this is an architectural error - it's NOT just useful
> for PWG Raster - it's useful for any raster or other opaque
> document format.
>> It was the broader use case that we were concerned about
> in the Open Printing Job Ticket API work.
>> Cheers,
> - Ira
>> Ira McDonald (Musician / Software Architect)
> Chair - Linux Foundation Open Printing WG
> Co-Chair - IEEE-ISTO PWG IPP WG
> Chair - TCG Embedded Systems Hardcopy SWG
> IETF Designated Expert - IPP & Printer MIB
> Blue Roof Music/High North Inc
>http://sites.google.com/site/blueroofmusic>http://sites.google.com/site/highnorthinc> mailto:blueroofmusic at gmail.com> Christmas through April:
> 579 Park Place Saline, MI 48176
> 734-944-0094
> May to Christmas:
> PO Box 221 Grand Marais, MI 49839
> 906-494-2434
>>> On Mon, Sep 19, 2011 at 12:31 AM, Michael Sweet <msweet at apple.com> wrote:
> Glen,
>> I was more thinking "where to put it in the header", but I've since decided to put PrintQuality in one of the empty cupsInteger slots and put your PrintContentType in the OutputType string field.
>>> Ira,
>> As for which specification, since the first use is in the PWG Raster Format spec, I'm thinking we should put it in the PWG Raster Format spec and then include it in the list of required IPP Everywhere job template attributes...
>> Thoughts?
>>>> On Sep 12, 2011, at 3:53 PM, Petrie, Glen wrote:
>>>> New Attribute
> PrintContentType: Text, Text+Graphics, Graphics(vector), Photo
> This is combined with “OutputType” to optimize output.
> This was big discussion in JTAPI definition and it was determine that is necessary to have both values.
>> We don't have this in the semantic model or IPP yet. Where do you propose I put this?
>> I am not sure what you mean “where do you propose I put this”?
>> If you mean --
> Within the PWG Raster it can occupy the first; no, better yet the last 4 bytes of the vender data space and shorten the vendor data space.
>> If you mean--
> Where will the information come from in a SM or IPP “job ticket”; then, I agree there is no source. But if an application choices to create a PWG Raster file and knows the PrintContentType value; then the application can fill in the field. The default value of zero (‘0’) can represent the value of “unknown” or “not specified”. So the enum could be
>> typedef enum {
> NotSpecifed = 0,
> TextOnly,
> TextAndGraphics,
> GraphicsOnly,
> Photo
> } ContentTypeEnum
>>>>>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean. _______________________________________________
>> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>> __________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>>>> __________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
________________________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20110919/463250a2/attachment-0001.html>