Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated name change to InBloom from SLC/SLI

...

This is a generic use case for accessing any "cloud-based" or otherwise hosted application, usually in a multi-tenant environment.  This would include email and other office-type applications (GoogleDocs, Office365, etc.), outsourced payroll systems, SalesForce, Learning Management Systems (LMS), Library Services and other Content Providers, etc.  Single Sign-On access through the use of SAML assertions (or other federation credentials) would eliminate many of the accounts K-12 users are currently forced to maintain at each of these resources.

(Joint "Early College" joint High School/Community College Programs - 5th Year)

These programs allow High School students to take college courses at a local community college in their Junior and Senior years to finish with a High School Diploma as well as an Associate Degree.  Access to the College systems could be provided via a federated login to the local high school Identity Provider (IdP) if the Community College system is running federated applications.

...

Specific Use Cases for K-12 Federation

(InBloom - formerly Shared Learning Collaborative - SLC)

The Shared Learning Collaborative (SLC) InBloom is working on a national data warehouse to provide longitudinal data tracking for K-12 students that would provide a means for tracking student progress and assessments (including the Common Core State Standards implementation in 2014), even when the student moves between states.  Much of this data is lost or unavailable to a new school (district) when a student starts at a new location.  The Shared Learning Infrastructure (SLI) InBloom "data warehouse" would hold the student data, and be accessible via federated access using the teachers' and staff's local credentials.

...