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

[Tomasz Wolniewicz <twoln AT umk.pl>]

Hi Mikael,
   thanks for the comments.

Please seem some comments in-line.

W dniu 2015-01-26 o 14:29, Mikael Linden pisze:
> Looks promising,
> My short feedback
>
> - in the main listing, prefer readability to detail
>    * By default, show lang="en" elements only (eduGAIN SAML2 metadata
> profile makes is SHOULD), allow user to select another language.
Hmm, this is not see obvious. There are a lot of French entities without
a English name. I could define the algorithm to be show English and in
not present show all other values.  I would not want to all language
selection into the GUI, exepr for English no other language can be
considered to be universally supported, the only reaonable approach
would be a checkbox - show all languages, but frankly I think that the
current approach is OK for now.
>    * make mdui:description a floating comment that appears when the mouse
> is moved over the entity
I was considering a floating comment with description and possibly other
information, but was a bit worried about what it would meant for
performance with potentially thousands of entities on the list. I would
need to send the additional information within the page, I think that
using AJAX calls for something like that would be too slow.  Still I
might as well try.
>
> - for entity categories
>    * use full name of EC instead of URI. Place a legend to the end of the
> page.
>    * each EC only once in the drop-down list and place two checkboxes next
> to it: "Entity Category" and "Entity Category Support"
Fine
>
> - "Entity details" vs. "Show full XML": I prefer both
>    * "Entity details": I think  it is good to have verbose human-readable
> details available
>    *"Show full XML": at least I need that when I have to find out how an
> entity appears in eduGAIN metadata and how it is broken
>    * speaking with my CoCo hat on, It would be nice if "Entity details"
> would display the "health status" (green/yellow/red) of a CoCo SP, as
> diagnosed by the CoCo monitor. See
> https://wiki.edugain.org/Monitoring_tool_instructions
I will take a look at that.

Tomasz

>
> Cheers,
> mikael
>
> -----Original Message-----
> From: Tomasz Wolniewicz [mailto:twoln AT umk.pl] 
> Sent: 26. tammikuuta 2015 12:03
> To: edugain-discuss AT geant.net
> Subject: Re: [eduGAIN-discuss] Locations for 'local' eduGAIN metadata
>
> Hi,
>   at http://technical.edugain.org/entities2.php I have presented another
> go at the entity listing. I have tried to include remarks I receiver form
> this list, but mainly the new approach is influenced by off-list
> discussion with Tom Scavo.
>
> The current approach is role-oriented, rather then Organisation oriented
> as before, which was one of the main things that Tom questioned.
> I have also dropped showing AAs which are in the same entity as an IdP and
> have no displayname of their own.
>
> Cases of missing MDUI DisplayName are clearly marked, as this can cause
> issues for Discovery Service and service catalogues.
>
> Unless someone comes up with something else, there are two issues which
> would need to be resolved:
>
> 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.
>
> 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.
> Tom Scavo thinks that this is overkill since people can read XML which,
> after all contains the full information and not just selected by us (this
> is why I intend to keep the full XML anyway). I would like to hear it
> people think about such functionality. If it is a general feeling that it
> is of no use then there is no point in implementing it.
>
> Cheers
> Tomasz
>

-- 
Tomasz Wolniewicz    
          twoln AT umk.pl        http://www.home.umk.pl/~twoln

Uczelniane Centrum Informatyczne   Information&Communication Technology Centre
Uniwersytet Mikolaja Kopernika     Nicolaus Copernicus University,
pl. Rapackiego 1, Torun               pl. Rapackiego 1, Torun, Poland
tel: +48-56-611-2750     fax: +48-56-622-1850       tel kom.: +48-693-032-576