cantor.2 at osu.edu
Tue Nov 18 11:31:54 EST 2014
On 11/18/14, 3:43 PM, "Peter Schober" <peter.schober at univie.ac.at> wrote:
>And what this would mean for other SP implementations, which wouldn't
>know how to tell those multiple values apart. Of course, if you're
>already sending e.g. Greek script/glyphs and latin script as multiple
>values of the same attribute you already have that problem.
From a representational point of view, certainly, I get it, just add
xml:lang to the AttributeValue element. The trick is how that translates
to pulling data from data connectors and somehow knowing the language (and
I have no idea how this relates to LDAP options).
As a basic feature, I can certainly get something into 3.0 to add the
option to specify a language to the encoders, but that may not be the
right thing to do, so I'm reluctant without having really thought it
through with some clear requirements to meet. The tricky part is
understanding multiple values with different languages, which really has
to ripple back into the IdPAttributeValue types and then we have to build
new encoders that handle that. And I don't see where the language info
will come from (apart from scripts).
More information about the users