Note that document-password is an operation attribute in IPP and is specifically omitted from the job ticket for security reasons, so we probably *don't* want it in PJT or the semantic model (at least as a <service>DocumentProcessing element).
On Jan 18, 2012, at 2:59 PM, Petrie, Glen wrote:
>> (I already sent these to Pete, but thought I should put on list for everyone.)
>> DocumentPassword in PJT is defined as Base64Binary and constraint = unlimited. But JPS3 state is it an octetString of length (max) of 1024.
>> I also read the description in JPS3 and it states that the document password in “unencrypted”. I think it would be very important to add the pharse ‘unencrypted’ in the PJT document.
>> Appendix A is not complete sorted. I think there was a cut/paste error DocumentMessage to DocumentNatural Language is repeat in the table. Once on page 43 and again on 44.
>> Title for Figure 5 should be CoverCol DataType instead of Cover DataType
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean. _______________________________________________
> mfd mailing list
>mfd at pwg.org>https://www.pwg.org/mailman/listinfo/mfd
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...