1EdTech Glossary

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.