1EdTech Glossary
Key terms and vocabulary.
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | ALL
O |
---|
OAuthThe 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.
| |
Official URLIn relation to the CASE standard, an official URL is a URL from the original source. | |
OneRoster
Learn more about this work: https://www.imsglobal.org/activity/onerosterlis | |
OneRoster Gradebook Service | |
OneRoster Resource ServiceSupports the ability to manage the allocation of resources to classes, courses and users. | ||
OneRoster Rostering ServiceSupports the secure transfer of data related to enrollments. This service exchanges information about users, classes, organizations, and enrollments | ||
Open Badges
Learn more about this work: https://www.imsglobal.org/activity/openbadges | |
OpenAPI 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 ConnectOpenID 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. | |