The Competencies and Academic Standards Exchange (CASE) Service Specification v1.1 is the definition of how systems achieve the exchange of information about academic standards, competencies, and/or skills. The goal for CASE is to replace the current ways of documenting a learning standard and competency, typically in a PDF or HTML document, by one which is both human and machine-readable. Using this CASE v1.1 specification will make it possible to electronically exchange academic standards, competencies, and/or skills between applications, systems, and tools.

This document is released for public adoption and implementation of the CASE Service 1.1 Specification. Public contributions, feedback on adoption of the specification, comments and questions can be emailed to: support@1edtech.org

The structure of the rest of this document is:

CASE 1.1 serves as a minor upgrade to CASE 1.0. CASE 1.1 still consists of two distinct services that were available in previous version, which are: CASE Provider and CASE Consumer. The goal for CASE 1.1 is to release a small update to address active integration concerns as well as provide clarity for implementing organizations. The sections below describe an overview of the new API path and each new feature. The new API path and any added features will be checked during the review process for CASE 1.1 Provider and CASE 1.1 Consumer certifications.

In Tables 3.1 and 3.2, the following should be noted:

For a CASE Service 1.1 implementation the 'Endpoint' value should be appended to the string '/ims/case/v1p1/'; The 'Mode' is used denote whether the system is responsible for issuing the request (Init) or responding to the request (Resp).

The set of endpoints that MUST be supported by a Service Provider is listed in Table 3.1.

Table 3.1 The endpoints that must be supported by a compliant CASE Service Provider.

The set of OPTIONAL endpoints that MAY be supported by a Service Provider is listed in Table 3.2.

Table 3.2 The endpoints that MAY be supported by a compliant CASE Service Provider.

The functional capabilities of such systems are:

• They must support all of the required endpoints;
• They may support any of the optional endpoints;
• They must supply all of the required data fields in the JSON payloads;
• They must be capable of supplying all of the optional data fields in the JSON payloads (conformance testing requires ALL data fields to be populated);
• They must not provide extension data fields in the JSON payloads;
• They may support the endpoint payload pagination query parameters. If supported the corresponding response HTTP header extensions MUST be supported;
• They may support the endpoint payload filtering query parameters;
• They may support the endpoint payload sorting query parameters;
• They may support the endpoint payload field selection query parameter.

The Conformance Test System used to certify a CASE 1.1 Service Provider is available at: https://validate.imsglobal.org/CASEv1p1_CTS_ServiceProvider/index.html

In Tables 4.1 and 4.2, the following should be noted:

• For a CASE Service 1.1 implementation the 'Endpoint' value should be appended to the string '/ims/case/v1p1/';
• The 'Mode' is used denote whether the system is responsible for issuing the request (Init) or responding to the request (Resp).
• For CASE 1.1 Consumer Certification Requirements, an additional endpoint value was included to ease with implementations: Required as a minimum either a CFPackage or CFItem must be supported.

The functional capabilities of such systems are:

• They must support all of the required endpoints;
• They must 'handle' all of the required data fields in the JSON payloads;
• They may 'handle' any of the optional data fields in the JSON payloads;
• The presence of extension data fields in the JSON payloads should not cause the systems to fail but the handling of these messages is implementation dependent;
• They may support the endpoint payload pagination query parameters. If supported the corresponding response HTTP header extensions MUST be supported;
• They may support the endpoint payload filtering query parameters;
• They may support the endpoint payload sorting query parameters;
• They may support the endpoint payload field selection query parameter.

NOTE: From a conformance perspective, 'handle' means that the consumer must store the data in a persistent manner and must demonstrate that storage. Conceptually, if a read request was made to the service consumer for that record then all of the data supplied by the service provider should be recovered.

The Conformance Test System used to certify a CASE 1.1 Service Consumer is available at: https://validate.imsglobal.org/CASEv1p1_CTS_Consumer/

A system that successfully achieves CASE Service certification will have a certain set of functional capabilities. CASE Service certification does NOT guarantee interoperability for ALL features between ALL other CASE Service compliant solutions. The set of functional properties that a CASE Service certified product may have is shown in Table 5.1.

Table 5.1 A comparison of the certifications available for a CASE Service compliant product.

Some key points to note from Table 5.1 are:

• A system could be certified as a service provider, a service consumer or a service provider/service consumer;
• For a service provider ONLY the 'getCFRubric' operation is OPTIONAL;
• For a service consumer ONLY the 'getCFItem' OR 'getCFPackage' operation is REQUIRED;
• ALL systems MUST support the 'getCFItem' operation.

Title: 1EdTech Competencies and Academic Standards Exchange Service (CASE) v1.1: Conformance and Certification

Editors:

Susan Haught, 1EdTech Consortium, Inc. Colin Smythe, 1EdTech Consortium, Inc.

Co-chair:

Pepper Williams, Common Good Learning Tools, Inc.

Version: 1.1

Version Date: 24th, January, 2025

Status: 1EdTech Final Release

Summary: The 1EdTech Competencies and Academic Standards Exchange (CASE) Service is used to exchange information about the learning and education competencies. This standard defines a set of data models for competency frameworks, competency documents, competency definitions, competency associations, rubrics, rubric criterions and rubric criterion levels. It also describes how this data can be exchanged using a set of service calls. This document contains the definition of conformance and certification for service consumers and service providers.

Revision Information: First release of this specification.

Purpose: For public adoption.

Document Location: https://www.imsglobal.org/case/

Revision History

This section is non-normative.