EDS enhancement entity category

[Scott Koranda]

On Tue, Aug 18, 2015 at 8:18 AM, Tom Scavo <trscavo at gmail.com> wrote:

> On Tue, Aug 18, 2015 at 7:05 AM, Scott Koranda <skoranda at gmail.com> wrote:
> >
> >> ...that is certainly *not* how a mature ID selector would work. Instead
> >> I think you'd find that the DS would list all IdPs, but highlight
> >> those it _believed_ to have a greater chance of working and possibly
> >> telling the user why another IdP might not work for this particular SP.
>
> Can you describe what you mean by "highlight?"
>

Those are Leif's words and not mine. Please ask Leif what he meant.


>
> > Could it fit into the roadmap for the Shibboleth SP and the
> > EDS to have the SP pass through more information into the JSON
> > feed, such as the metadata entity categories with which an IdP
> > is tagged, and then the EDS have the ability to mark in the UI
> > those IdPs that meet a particular condition, ie. being tagged
> > with a particular entity category?
>
> Can you be more specific about you mean by "mark in the UI?"
>

I am not a UI expert and so will defer to others.

My naive input (which I do not care to debate but only offer to help
stimulate discussion) is that the lines in a drop down table that represent
IdPs that do not support REFEDs R&S would be "grayed" or have color applied
in some way.

Then we could in the HTML around the page supply a key to indicate what
that color means.

Again I am not a UI expert and cannot say if that approach can be made
properly accessible.


> > The use case I am most interested in would be to have the EDS
> > visually distinguish between IdPs that are tagged with the
> > REFEDS R&S entity category and those that are not.
>
> I'm not sure how one would "visually distinguish" IdPs on the
> discovery interface such that the interface is 1) accessible, and 2)
> understandable.
>

I argue I can make it understandable for my user community.


>
> The problem you have loosely described seems to be at least as
> difficult as user consent.
>

Not for my user community.


>
> > If you think this could fit into the Shibboleth SP and EDS
> > road map please let me know and I will file a JIRA ticket(s).
>
> Per-entity metadata is going to turn discovery on its head, so I'm not
> sure it makes sense to continue further down the same path we're on
> now.


I can say that the LIGO project has the EDS deployed in about 10 SPs. We
could consume this enhancement immediately were it offered.

Thanks,

Scott K for LIGO
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20150818/6cbbc6f1/attachment.html>