CUPS-specific LDAP schema - WHY?

[Jeff Blaine]

> On Jul 7, 2010, at 12:49 PM, Jeff Blaine wrote:
> > Why does CUPS require a custom LDAP schema?
>
> The main reason is that we don't want to discover and use arbitrary =
> LDAP-advertised printers on the network - we are advertising CUPS shared =
> printers and not the laser printer down the hall that was entered into =
> the LDAP directory that needs a special driver.

'printer-more-info' could have been used to provide any
CUPS-specific information or tagging, no?

    http://tools.ietf.org/html/rfc3712#page-14

Can you please point me to the official CUPS LDAP schema?  There
isn't one included with the source distribution.  The only LDAP
schema info I found was hardcoded in C files, and that doesn't
list syntax info, etc.

> Feel free to provide a patch to use the RFC 3712 schema as an option, or =
> to provide a backend that does regular printer discovery using LDAP...
>
> http://www.cups.org/str.php
>
> >=20
> > Why doesn't CUPS work with RFC 3712 LDAP data instead?
> >=20
> >    "Lightweight Directory Access Protocol (LDAP): Schema
> >     for Printer Services"
> >=20
> >    http://tools.ietf.org/html/rfc3712
> > _______________________________________________
> > cups-dev mailing list
> > cups-dev at easysw.com
> > http://lists.easysw.com/mailman/listinfo/cups-dev
>
> ________________________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
>
>