If this effort is too much for the IPP worker bees to
assume, I'll be more than happy to do the extract/post
myself, if you'd prefer.
...jay
----------------------------------------------------------------------
-- JK Martin | Email: jkm@underscore.com --
-- Underscore, Inc. | Voice: (603) 889-7000 --
-- 41C Sagamore Park Road | Fax: (603) 889-2699 --
-- Hudson, NH 03051-4915 | Web: http://www.underscore.com --
----------------------------------------------------------------------
Scott Isaacson wrote:
>
> I wouldn't mind an issues list, but the ones that you mentioned were all raised and discussed at the last meeting. See comments below.
>
> >1. "printer-uri" or "job-uri" mandatory and required op att? Form?
>
> Discussed and resolved at the 5/20-21 meeting. See new text to be published by 5/29.. Meeting notes
> due out soon.
>
> >2. Mixed case allowed in 'naturalLanguage' and 'charset' values?
>
> What is the issue? The model document syntax rules for charset and naturalLanguage state that IPP does not allow mixed case. 4.1.9 'charset' currently says:
>
> "Though RFC 2046 requires that the values be case-insensitive US-ASCII, IPP requires all lower case to simplify comparing by IPP clients and Printer objects."
>
> 4.1.10 'naturalLanguage' currently says:
>
> "Though RFC 1766 requires that the values be case-insensitive US-ASCII, IPP requires all lower case to simplify comparing by IPP clients and Printer objects."
>
> >3. 'client-error-request-uri-too-long' vs.
> >'client-error-request-value-too-long' ? Types applied to?
>
> Discussed and resolved at the 5/20-21 meeting. See new text to be published by 5/29 Meeting notes
> due out soon.
>
> >4. "attributes-charset" and "attributes-natural-language" must always be
> >positioned up front?
>
> Discussed and resolved at the 5/20-21 meeting. See new text to be published by 5/29 Meeting notes
> due out soon.