Well, I think the X- stuff is used for different purposes. It's for schema definitions themselves. We are using X-IS-HUMAN-READABLE and X-SCHEMA extensions in schema element definitions. But I may be missing something here so I am not talking being sure.
On 1/22/07, Stefan Seelmann <[EMAIL PROTECTED]> wrote:
Very interesting. RFC4520 section 3.5 says: Options beginning with "x-" are for Private Use and cannot be registered. So if ADS would accept such private options the user could define his/her own options. street;x-home street;x-work Regards, Stefan Enrique Rodriguez schrieb: > On 1/21/07, Emmanuel Lecharny <[EMAIL PROTECTED]> wrote: > ... >> Well, I don't know to much about famillies, but I think that we might >> workaround the problem of first email, second email, etc by using >> attribute descriptions options : >> >> mail;primary: [EMAIL PROTECTED] >> mail;office: [EMAIL PROTECTED] > > Could this technique also be used for multiple attributes that are > typically grouped together? As a specific example, would you do this > with addresses, say for a shipping address vs. a secondary shipping > address? > > In RFC 2596 the technique is used for language codes: > > streetAddress: 1 University Street > streetAddress;lang-en: 1 University Street > streetAddress;lang-fr: 1 rue Universite > > Would it make sense to handle shipping address vs. secondary shipping > address attributes (from RFC 2256: X.500 User Schema) this way? > > street;home: 5 Main St. > street;work: 10 Commercial Way > ... similarly for st, l, and c (state, locality, and country). > > Enrique
-- Ersin
