[glue-wg] Inheritance with the LDAP rendering

Paul Millar paul.millar at desy.de
Mon Mar 30 09:38:23 CDT 2009


Hi Laurence,

On Monday 30 March 2009 13:39:27 Laurence Field wrote:
> I would propose that it would be better to have the same prefix.

From http://forge.ogf.org/svn/repos/glue/LDAP2/ldif/5-03-Location.ldif
> dn: EntityId=testLocation,o=grid
> objectClass: Location
> EntityId: testLocation
> EntityName: Headquarters
[...]
> LocationAddress: 15700 103rd St. Suite 210 Lemont, IL  60439  USA
> LocationPlace: Lemont

So, using the above example, one would publish:

dn: LocationId=testLocation,o=grid
objectClass: Location
LocationId: testLocation
LocationName: Headquarters
[...]
LocationAddress: 15700 103rd St. Suite 210 Lemont, IL  60439  USA
LocationPlace: Lemont

I don't have a strong opinion on this.  If you feel it's better to hide the 
inheritance (and it's feasible to do this) then OK with that.


> However, for the ComputingServices I would prefer the names to be
> retained eg.
>
> ServiceId rather than ComputingServiceId.

I'm not sure why ComputingService should be a special case here.  Is it that 
ComputingServiceId is a bit of a mouthful?

> This would present and inconstancy in the way that we handle
> inheritance.  My two questions would be does everyone agree with the
> above and if so how do we deal with this inconsistency?

I would go for ComputingServiceId to be consistent with other published 
inhereted attributes, but I may have missed something.

Cheers,

Paul.


More information about the glue-wg mailing list