1EdTech Glossary

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

A software package is a collection of files or LTI links and information about those files. In 1EdTech, a package describes data structures to ensure the interoperability of digital content with content creation tools and platforms (LMS, SIS, CMS.)

"Zips" and "SCORMS" are commonly known packages. In this course we will talk about a package called Common Cartridge.

Portable Custom Interaction, an item interaction defined in the QTI specification as an extension that references all of the code that is required to implement the user interface and behavior of the interaction when used to render and interact with the item containing the portable custom interaction.

This is one of the core components in the LTI Advantage specification.  In LTI parlance, the platform serves as the service consumer as they are consuming and making available the tool.  

 A tool platform or, more simply, platform has traditionally been a Learning Management Systems (LMS), but it may be any kind of platform that needs to delegate bits of functionality out to a suite of tools. In LTI 1.x a Platform was known as a Tool Consumer.

In prior versions of LTI this was called the ‘tool consumer’ but that verbiage does not align with industry standard terminology and was retired.

Personal Needs and Preferences. A PNP is a user profile as used in APIP and QTI 3 using the AfA standard. A PNP for a user will contain information that describes their accessibility needs and/or support preferences.

The Privacy Framework, contains the definition of a set of rules and methodologies to be supported by future 1EdTech specifications so that implementers can implement the specification correctly, all whilst enabling the implementer to efficiently and transparently meet local requirements regarding privacy information storage and exchange.