Table of Contents | ||||||||
---|---|---|---|---|---|---|---|---|
|
Logistics
- Time: 08:00 PT | 11:00 ET | 16:00 UTC/GMT | 18:00 CEST (Time Chart)
- Skype: +9900827042954214
- US Dial-In: +1-201-793-9022
- Room Code: 295-4214
Agenda
1) Roll Call
Voting:
- Scott Cantor
- RL "Bob" Morgan
- Keith Uber
- Paul Trevithick
- Benoit Bailleux
- Philippe Clement
Non-voting:
- Valeska O'Leary
Not present
- Axel Nennker
- John Bradley
- Gael Gourmelen
- Trent Adams
- Bob Pinhero
Quorate meeting (6 of 6)
2) Minutes
Approved the following minutes:
3) Towards v5: unmet requirements in v4
We agreed that v4 worked well for the case where there are a relatively small number (<20?) of well known IdPs (that generally have highly designed logos that are highly distinctive visually).
We agreed that v4 did not meet the following requirements:
- Searching when there are large numbers (20+) of IdPs
- In v4 the "search results" replace the "preferred" IdPs and are displayed only by (large) logos. This has the following problems:
- Not all IdPs have logos
- The large logos take up too much space--so only a few search results can be shown
- In v4 the "search results" replace the "preferred" IdPs and are displayed only by (large) logos. This has the following problems:
- v4 has no support for keywords (e.g. a city/geolocation or other keyword) that could help a person find the IdP they are looking for
- if v5 supports textual search results (i.e. the name of the IdP) we need to support the case where N>1 IdP share the same textual name (and thus must be disambiguated via keywords)
We agreed that Paul would work with Valeska on some new designs that would address the unmet requirements mentioned above.
Keith: should use v5 to fork prototype and show different cases: many IdPs, a handful, just a couple, show some possible optimizations in each case
Keith: talked about Finnish? use case with 12 or so IdPs with very
different characteristics
RLBob: currently a custom web page...
Keith: if we could get the details from the metadata, should still fit ULX
model
RLBob: small vs. large icons?
Scott: maybe designers could have input on how useful smaller icons would be?
4) WebFinger
Paul suggested that our ULX design should include (optional of course) support for WebFinger. In WebFinger you express a user account in email form, so one can do a domain lookup against it to discover IdPs
Scott: question is whether it will be used to point to real discovery of IdPs, or directly derive IdP from domain, seems like the latter ends up more likely
RLBob: not sure how to represent it in current UI, doesn't overlap well with search box
Paul: clearly not workable for all cases, but maybe for some
RLBob: needs more discussion to work into prototype
Next Meeting (Jan 10th)
- Time: 08:00 PT | 11:00 ET | 16:00 UTC/GMT | 18:00 CEST (Time Chart)
- Skype: +9900827042954214
- US Dial-In: +1-201-793-9022
- Room Code: 295-4214