...
- We need to go through the mock-up code and (a) make sure the components used are compatible with our IPR regime for distribution, and (b) insert into each file (HTML, JS, etc) the applicable copyright notice and reference to the license.
2. We should probably move the mock-up code into a subversion (or similar) repository so we can effectively start tracking version
3) Proposed Active Client Selector trigger:
- ulx://path-to-RP-metadata-JSON-for-HTTP
- ulxs//path-to-RP-metadata-JSON-for-HTTPS
4) Finnish selector use case
- Walkthrough of Finnish selector use case (eg SP-driven IdP grouping and priorities) see http://kantarainitiative.org/confluence/display/ulx/Use+Case+Finnish+services+for+citizens
5) Unresolved issues from previous meeting
6) ULX in HTTP request header
- Proposal: include ISA-related preference info in HTTP request header
- Info
- Most important: the user's choice of cloud selector URL
- Also: a set of user's preferred service providers (e.g. IdPs)
- How?
- Long term: Browsers could build this in
- Short term: a small browser extension could implement
- Why?
- Would provide a standard way for the user to exert their preference
Next Meeting
- Time: 08:00 PT | 11:00 ET | 16:00 UTC/GMT (Time Chart)
- Skype: +9900827042954214
- US Dial-In: +1-201-793-9022
- Room Code: 295-4214