An open discussion list for topics related to the eduGAIN interfederation service.

[Tom Scavo <trscavo AT internet2.edu>]

On Mon, Jan 26, 2015 at 5:02 AM, Tomasz Wolniewicz <twoln AT umk.pl> wrote:
>
> http://technical.edugain.org/entities2.php

Much improved! Thanks, Tomasz.

> 1. Entity categories - I have provided a "friendly naming" approach, Tom
> thinks that this may be misleading and do more harm then good, and
> suggests just using the URIs. Unfortunately, using URIs might need that
> we need to make a visual difference between
> http://macedir.org/entity-category and
> http://macedir.org/entity-category-support  (how). Of course the naming
> question is both about the display and the list in the filter.
> On thing is NOT practical - a friendly name followed by URI, this just
> gets too long. So please advise on how I should proceed with this.

I don't really know but here's a suggestion (let's see how it goes).
Ignore all entity attributes that do not have one of the above two
names and then display all the entity attribute values (not the names)
on the UI. Filtering is also based on the full URI value. In essence,
do not make a distinction between the two entity attribute names
listed above. Focus on the entity attribute value.

> 2. Entity details. If you click on this you will just see a popup with
> nothing useful inside, but this is where I intended to put nicely
> formatted information about this entity, therefore not just display
> names, but also description, contact information, requested attributes
> list, logo (however this is more complex then would appear at a first
> glance), etc.

I don't think there's a need to list keys and endpoints so I think
that's more-or-less a complete list.

> Tom Scavo thinks that this is overkill since people can
> read XML

After reading Peter's comments, I retract that statement :-) What you
are calling "entity details" is probably useful, as long as you don't
display keys and endpoints (which I don't think you had in mind
anyway).

Tom