+1.
We can add it to section 7.1 (service URIs)
On Aug 6, 2014, at 3:43 PM, Zehler, Peter <Peter.Zehler at xerox.com> wrote:
> All,
>> Given that IPP FaxOut and IPP Scan have set requirements on the path components of the service’s URL perhaps the new implementers guide can do the same for print (e.g. “ipp/print”). I would hope going forward any additional service mappings will have similar path component requirements.
>> The requirement in scan is
> “Each instance of a Scan Service is identified by a URI. The path component of an IPP Scan URI MUST be “/ipp/scan” for the only (or default) instance of the service on an Imaging Device and “/ipp/scan/instance-name” for each additional, non-default instance on the Imaging Device.”
>> Peter Zehler
>> <image001.png>
> Email: Peter.Zehler at Xerox.com> Office: +1 (585) 265-8755
> Mobile: +1 (585) 329-9508
> FAX: +1 (585) 265-7441
> US Mail: Peter Zehler
> PARC, A Xerox Company
> 800 Phillips Rd.
> M/S 128-27E
> Webster NY, 14580-9701
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140806/00c20f9b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4881 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140806/00c20f9b/attachment.p7s>