I added the following to the model document:
If a Printer object supports this optional operation, it MUST support URIs
of the following type:
'http': The Printer object will perform an HTTP/1.1 GET operation
'ftp': The Printer object will use an FTP 'get' operation. If the URI does
not indicate a name or password in the URI itself, the Printer object will
use anonymous FTP generating (if prompted) some password in the form of an
Internet mail address.
I intended to add the phrase "The Printer object OPTIONALLY supports URIs of
other types." but I forgot. I will add it. I thought this was the intent
of the
discussion:
if support for print-by-reference, then support for http: and ftp: with
optional
support for uri's of other types.
Scott
>>> "Turner, Randy" <rturner@sharplabs.com> 09/24 4:47 PM >>>
> I guess I would like the wording
> to say that these are the minimal schemes accepted, and
> make sure that other schemes can be specified but not
> guaranteed to be supported.
> Now that I think about it, that may have been the accepted
> text, but I left the meeting thinking that this might have been
> left out.