1 / 15

REF2 Barrier to Effective Federation Use

REF2 Barrier to Effective Federation Use. Rod & Nicole 10:50 – 11:30. Discovery Project. Define standardised practises for logo sizes and error pages / messages used by Service Providers.

nerys
Download Presentation

REF2 Barrier to Effective Federation Use

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. REF2 Barrier to Effective Federation Use Rod & Nicole 10:50 – 11:30

  2. Discovery Project. • Define standardised practises for logo sizes and error pages /messages used by Service Providers. • Design a toolkit for publishers that clearly lays out the business model for embedded discovery and supporting materials for the current technical implementations available. • Establish an editorial board for the toolkit. • https://refeds.terena.org/index.php/Revised_discover_project

  3. MDUI recommendations. • At Arlington it was decided that it is too soon to develop a standard. • Rather we are to develop guidance for federations: • Explicitly check & defend against inter federation clashes. • Careful use of normative language. • Some “statements of the obvious” • So obvious that it took us some time to notice!

  4. MDUI recommendations:Normative and other language. • Distinguish between: • Absolutely required to function. • Aesthetics. • Functional but ignorable. • Section 6 of RFC2119 “Imperatives of the type defined in this memo must be used with care and sparingly. In particular, they MUST only be used where it is actually required for interoperation”

  5. MDUI recommendations:The obvious... • Doing the work yourself is often easier than getting others to do it. • Do what the specifications (particularly MDUI) say. • Do not serve images from a Java Container.

  6. Discovery:The toolkit for publishers. • Commissioned the toolkit for publisher. • Easy way to use the ESPRESSO standard. • Non threatening, but descriptive. • One website, multiple audiences, carefully & simply presented. • Supporting material (references). • Demo site[s?].

  7. Toolkit: Progress. • This had been planned for completion this month. • Delayed but aiming for June. • We get a chance to close on some issue which are still open.

  8. Toolkit:The five steps • Locate the login button top right. • Manage local login. • Chose and install a DS. • Configure for your site & users. • Done.

  9. Toolkit:Demo site(s). • The motivation here is similar to accountchooser.com. • A site “done properly”: • Suggestions for content type? • Offers of a site we can borrow? • Do we need a site “done wrong”?

  10. To Summarise: • MDUI Recommendations. • Toolkit: • Watch this space. • Editorial board: • We are still seeking volunteers.

  11. Barriers for SPs

More Related