metadata UI displayname and multiple application overrides

[Tom Scavo]

On Mon, Apr 16, 2012 at 12:47 PM, Peter Schober
<peter.schober at univie.ac.at> wrote:
> * Jeff Silverman <jeff at moodlerooms.com> [2012-04-16 18:42]:
>> I'm sure I'm missing something. However, I don't see any way to fill
>> "<mdui:DisplayName>" in separately for each entityID in the InCommon
>> Metadata generator.
>
> I guess the assumption was that if you want seperate logical SPs these
> would each have their own entityId and hence their own MDUI info.

Just to be clear, the OASIS MDUI spec calls for one set of user
interface elements per role (such as the SPSSODescriptor role) in
metadata. As I said previously, SAML metadata permits multiple
AttributeConsumingService elements, each with its own ServiceName (in
which case MDUI DisplayName is not necessary), but InCommon doesn't
support multiple such elements, primarily because software tends to
only support one. This led us to the conclusion that we need a single
MDUI DisplayName in metadata for the entire SP entity descriptor,
which is what we have.

Tom