The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. OAuth 2.0 is published as IETF RFC 6749. The 1EdTech Security Framework makes extensive use of OAuth 2.0.

• OAuth 2 Scopes – scopes are an optional feature in OAuth 2.0 to label the conditions for obtaining an access token. Use of OAuth 2.0 scopes is mandatory in 1EdTech service-based specifications.

In relation to the CASE standard, an official URL is a URL from the original source.

OneRoster® is a standard developed by 1EdTech. OneRoster allows for the exchange of roster data between learning management systems and student information systems and learning tools. The data exchanged can include information about students, teachers, classes, grades, and course materials. Institutions can save valuable instructional and administrative time with a low cost and scalable way to streamline the management and secure delivery of digital IDs, product use rostering, and transmission of assignment, scores, and grades across all digital resources. For more information, see 1EdTech's Educational Data and Analytics and Digital Curriculum initiatives and OneRoster Project Group Activity.  

Learn more about this work: https://www.imsglobal.org/activity/onerosterlis

Supports the exchange of gradebooks data in the form of: results, lineItems, collections of lineItems (categories) and score-scales. It is also possible to exchange information about assessment activities in the form of assessment lineItems and assessment results.

Supports the ability to manage the allocation of resources to classes, courses and users.

Supports the secure transfer of data related to enrollments. This service exchanges information about users, classes, organizations, and enrollments

Open architecture is a way of designing technology systems that make adding, upgrading, and swapping components easy. 1EdTech focuses on an open architecture that allows educational institutions to add and change components within their system. For example, this might be a student information system or learning management system or a content provider.

Open Badges are portable image files that include information about accomplishments associated with the image. In other words, Open Badges contain detailed metadata about achievements. Who earned a badge, who issued it, and what does it mean? The data is all inside the badge. 1EdTech is responsible for managing and advancing the Open Badges standard, which provides a secure framework to digitally capture and visually present achievements that are verifiable and portable to help learners differentiate their career readiness or college-readiness in an increasingly competitive world. For more information, see 1EdTech's Digital Credentialing Initiative and Digital Credentials and Badges Project Group Activity. Higher Education Institutional Members may be interested in the Digital Credentials & CBE Innovation Leadership Network; for more information see Higher Ed Innovation Leadership Networks.

Learn more about this work: https://www.imsglobal.org/activity/openbadges

 The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs. It allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or network traffic inspection. When properly defined, a consumer can understand and interact with the remote service with minimal implementation logic. An OpenAPI definition can then be used by documentation generation tools to display the API, code generation tools to generate servers and clients in various programming languages, testing tools, and many other use cases. Many of the 1EdTech standards have OpenAPI-based descriptions for the defined services, including CASE, OneRoster, Comprehensive Learner Record, and Open Badges.

OpenID Connect (OIDC) is a simple identity layer on top of the OAuth 2.0 protocol. It allows Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner. OIDC allows clients of all types, including Web-based, mobile, and JavaScript clients, to request and receive information about authenticated sessions and end-users. The specification suite is extensible, allowing participants to use optional features such as encryption of identity data, discovery of OpenID Providers, and session management, when it makes sense for them.

The abbreviation for Open ID Connect, a specification published by the OpenID Foundation.

OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the end user based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the end user in an interoperable and REST-like manner. This specification defines the OpenID Connect Core functionality: authentication built on top of OAuth 2.0 and the use of claims to communicate information about the end user. It also describes the security and privacy considerations for using OpenID Connect

The OpenID Connect Discovery specification defines a mechanism for an OpenID Connect Relying Party to discover the End-User's OpenID Provider and obtain information needed to interact with it, including its OAuth 2.0 endpoint locations.

OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. It enables Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner. The OpenID Connect Dynamic Client Registration specification defines how an OpenID Connect Relying Party can dynamically register with the End-User's OpenID Provider, providing information about itself to the OpenID Provider, and obtaining information needed to use it, including the OAuth 2.0 Client ID for this Relying Party.

The OpenID Foundation is a non-profit international standardization organization of individuals and companies committed to enabling, promoting and protecting OpenID technologies. Formed in June 2007, the Foundation serves as a public trust organization representing the open community of developers, vendors, and users. OpenID Foundation assists the community by providing needed infrastructure and help in promoting and supporting expanded adoption of OpenID. This entails managing intellectual property and brand marks as well as fostering viral growth and global participation in the proliferation of OpenID.

This is a specification under development by 1EdTech. The OpenVideo Metadata specification defines a format for creating rich media content that describes captured rich media in a standardized way such that management solutions that support the standard can exchange the media. The goal of the OpenVideo Metadata specification is to make it simple and easy for educational institutions to manage all of their captured content, in a way that is agnostic to the software and hardware they used to capture it. The standard aims to remove siloed data and long integration projects by creating one simple, standardized format that describes captured rich media, as well as a process by which this media can be transferred into a media management solution that supports the format.  Learn more about this work: https://www.imsglobal.org/activity/openvideo