>> >The problem with using http: for printers is that it hides the fact
>> >that the resource is a printer.
>> ... and the problem with "ipp:" is that it hides the fact that
>> the protocol is really HTTP!!!
>I guess I consider it more important for the URL to describe the
>end resource that it's providing, than for it to describe the
>underlying protocol(s). We don't have tcp: or ip: URLs; we have
>URLs for higher level services. Some URL schemes don't imply a
>particular protocol. However, for every URL scheme that uses the
>name of a protocol, the URL names the highest layer protocol
>on the stack, rather than some lower layer.
As always, in HIS hands,
Joel H. Bennett
All charming people, I fancy, are spoiled. It is the secret of their
-- Oscar Wilde: 1854-1900, Irish writer