> -----Original Message----- > From: fedora-directory-users-bounces at redhat.com > [mailto:fedora-directory-users-bounces at redhat.com] On Behalf > Of speedy zinc > Sent: Tuesday, October 18, 2005 5:38 PM > To: General discussion list for the Fedora Directory server project. > Subject: Re: set of attributes? > > For example, I have my HR app, let's say I create a schema, > and I want to call my set of attr hrApp, which contains > departmentnumber, manager, ... > > So when I do ldapsearch, instead of using > > (manager=john) > > I can do > > (hrApp.manager=john) > > that would be used as "standard" ldap query syntax :) OK I think I understand what you don't understand :) The objectclass attribute values are like your hrApp, in that they are what determine which attributes an entry _must_ have and which attributes an entry _may_ have. So, taking the inetorgperson objectclass, which happens to allow the manager attribute (which is dn syntax so it points to the manager entry itself) your filter would be: (&(objectclass=inetorgperson)(manager=uid=john,dc=my,dc=org)) > > I'm looking at the CoS, but really don't know how to use it. > The concept of CoS seems like aspect programming to me, but > my understanding from the manual is that, the value of > attributes in CoS is shared by the entries, and not the definition. > Yes it is a way to share common attribute/value pairs among many entries - not really what you are after.
