On Thu, Jan 20, 2011 at 8:42 PM, Cantor, Scott E. <> wrote:
>> It seems the <mdui:UIInfo> element is applicable at the level of the
>> <AttributeConsumingService> element but there doesn't seem to be a
>> mechanism to do that. Related to this, it seems the precedence
>> described in section 2.3.3 is wrong. Shouldn't the ServiceName and the
>> ServiceDescription in the <AttributeConsumingService> element take
>> precedence over the <mdui:UIInfo> child elements?
>
> Creating that precedence just amounts to omitting the extension, so there's no need to define such an ordering. If the extension is present, then it's meant to take over.
Yes, I see that now. If an SP defines one or more
<AttributeConsumingService> elements, it should probably just omit
<mdui:DisplayName> and <mdui:Description>. Still, there's no way to
apply the other elements (logos, e.g.) at the level of the service.
sigh.
Tom
