[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [security-services] Proposal to correct LDAP/X.500 profileattribute
I'm fine with the original option 2 if that's what folks are more comfortable with. That just means that the encoding must be signaled out-of-band (in the same way that the profile itself is signaled). Option 6 is just an extension of option 2 that preserves the in-band signaling of the encoding (what we were trying to do with x500:Encoding) using xsi:type, but it does come at the expense of having to define extensions of the pre-defined types when alternate encodings are being used. -Greg On 6/6/06 6:02 PM, "Scott Cantor" <cantor.2@osu.edu> wrote: > Sorry for missing the call, was at a conference. > >> 6. A variation on 2 and 3, which is to: >> a. remove the x500:Encoding attribute and document that the LDAP >> encoding uses xsi:type string and base64Binary >> b. document that other encodings should define new types > > I don't hate it, but I guess my concern here is that I'd hate to just rule > out some other encoding using string or base64, moreso string. It's not just > the XML data type that's being outlined in there, it's also the transform > from LDAP syntax to XML. It's not impossible to imagine other such > transforms still leading to string. > > I don't see a major advantage in that none of the options really fixes the > problem of how to change or replace the profile without disruption of SAML > 2.0 specs, otherwise I would obviously concede to that one. > > -- Scott > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]