Hi Stephen, Good point. In my opinion strings should be defined in the schema as case sensitive. If I think about a String being used as a (or part of a) key in a relational DB it comes to my mind that most relational DB Systems ARE case sensitive. Now, if it happens to be that two entries would have the same string as key ('atlas' and 'atlas') the DB would refuse the second entry. Whereas it would be possible if they would have been defined as 'atlas' and 'ATLAS' (or 'Atlas'). This is just a simple example. Generally, I think that case sensivity gives more opportunities to define values. Of course it is application specific. But applications using insensitive strings are not affected if they get a case sensitive string (not the other way round). Felix -----Original Message----- From: glue-wg-bounces@ogf.org [mailto:glue-wg-bounces@ogf.org] On Behalf Of Burke, S (Stephen) Sent: Tuesday, October 30, 2007 4:00 PM To: glue-wg@ogf.org Subject: [glue-wg] Case sensitivity Hi, I just came across a mail I sent a while ago about case-sensitivity in GLUE. I don't think it was ever answered but I still think it's something that should be defined. "Something that just came up is the question of case-sensitivity for strings. It looks to me that the LDAP schema defines all the strings to be insensitive. However, other things may well be case-sensitive, and I thought we had defined everything to be case-sensitive at the schema level. Is that right? Looking at the Glue document the only reference I can see is to VOMS attributes being sensitive." Stephen _______________________________________________ glue-wg mailing list glue-wg@ogf.org http://www.ogf.org/mailman/listinfo/glue-wg