Agreed, but I am using "special position" in the sense that it was used earlier, in the PRO document, to describe attributes that are outside the normal attribute groups, placed either in the transport layer or in a fixed position in the application/ipp body.
>
> At 05:00 PM 6/5/98 , Paul Moore wrote:
> > I think we are approaching group consensus on this. I propose that
> >we remove "printer-uri" and "job-uri" as request Operation attributes, but
> >leave them in their special position in the protocol.
> >
> > [Paul Moore] What 'special position'?
> >
>
> --=====================_33814923==_.ALT
> Content-Type: text/html; charset="us-ascii"
>
> <html>
> <font size=3>We agreed recently that the following operation attributes
> would be ordered.<br>
> attributes-charset (always first for requests and
> responses)<br>
> attributes-natural-language (always second for
> requests and response)<br>
> printer-uri or job-uri (always third for requests,
> though we are discusses whether it should be present)<br>
> job-id (always fourth for requests if present )<br>
> <br>
> At 05:00 PM 6/5/98 , Paul Moore wrote:<br>
> ><x-tab> </x-tab>I think we
> are approaching group consensus on this. I propose that<br>
> >we remove "printer-uri" and "job-uri" as request
> Operation attributes, but<br>
> >leave them in their special position in the protocol. <br>
> ><br>
> ><x-tab> </x-tab>[Paul
> Moore] What 'special position'? <br>
> > </font><br>
> </html>
>
> --=====================_33814923==_.ALT--
>
>
>