...
http://groups.google.com/group/wg-ulx/browse_frm/thread/71cb40fccefe7079
Scott: I still think we need a "see all" option (as we've stated in our requirements).
Scott: I don't understand what Andrea's alternative to the "icons" are.
Scott: I think the "keyword" point is good. We need to think of all the kinds of things that the user might want to type on. We don't have a space for that kind of arbitrary information.
Bob: Yes, it seems like this could be a pretty useful open-ended mechanism. ?
Scott: I'm going to mention a Shib call after this. And we'll see if there's interest in having a keyword option. I don't think we should categorize further than just a keyword.
Keith: Aren't categories for higher education useful?
...After some discussion the general consensus was that we should only use keywords and not categories...
Scott: Looks like he has an alternative presentation model. Not sure this is an improvement, but I'll wait to see what others think.
Bob: He showed federation logos if there wasn't a "direct" logo.
Scott: The initial part looks similar. E.g. if you type "ohio" then you just get Ohio State. But if you type "nor" you get a giant list of IdPs. I'm suggesting is that simplicity is better than complexity.
Scott: Shib does not assume that icons will always be available.
Keith: If the top 6 that are there by default and without them then it looks.
Paul: Suggest we change our prototype so that it gracefully degrades if an icon isn't availalble.
...there was general consensus on this...
Scott: I personally would de-emphasize the icons when you start typing.
Keith: If there are small number of entries then showing all of the logos works well. It's natural to select.
Paul: We would have had to come up with a gracefull way to degrade anyway when our mockup becomes dynamic.
2) Trent's email
http://groups.google.com/group/wg-ulx/browse_frm/thread/6dea05e0dcb854c0#
...
- We need to go through the mock-up code
- make sure the components used are compatible with our IPR regime for distribution
- insert into each file (HTML, JS, etc) the applicable copyright notice and reference to the license.
- Move the mock-up code into a subversion (or similar) repository so we can effectively start tracking version
PAUL: To explore doing the above.
3) Proposed Active Client Selector trigger:
- ulx://path-to-RP-metadata-JSON-for-HTTP
- ulxs//path-to-RP-metadata-JSON-for-HTTPS
Paul presented the above...
Scott: I foresee political problems getting agreement on the scheme name (ulx) above.
Paul: Actually this brings up another problem. We detect the header and look a the "capabilities".
Scott: This is an old trick. But the W3C is against folks creating new schemes. The right way to do this is mime types, but as has been
4) Finnish selector use case
...