Data Standard v3.2 (most recent version is 3.2a) introduces changes to the core data model around the domains commonly captured in student information systems and assessment systems. It is the successor to Ed-Fi Data Standard v3.1. The documentation below describes important principles and features of this release, and where to locate detailed information on specific data model changes.
Release Features
Non-breaking for API Binding
The changes proposed in this release are intended to be non-breakingto most API clients. "Non-breaking" in this context generally means that data model changes are additive and optional, datatypes are generalized or field lengths are expanded. However, any change to a data model is potentially breaking given the specific API client behavior, so all API users are cautioned to review the changes carefully.
Introduction of Deprecation
In order to limit the impacts to field work derived from the API, including to help make the API binding changes non-breaking, the RFC proposes deprecation of data model elements. Deprecation as a concept is new to Ed-Fi specifications. Deprecation communicates that a data element or other API behavior is intended for removal in a future release, and likely in the next major release. Deprecation is therefore a recommendation to avoid use of certain data fields or features. Deprecation may be accompanied by information listing alternative or preferred options.
Changes to Core Student Domains
This release contains many changes to data domains commonly represented in Student Information Systems. These changes are described in detail in ED-FI RFC 20 - CORE STUDENT API
Changes to Assessment Domains
This release contains many changes to data domains commonly represented in Student Information Systems. These changes are described in detail in ED-FI RFC 22 - ASSESSMENT OUTCOMES API
All Changes
The chart below lists all changes included in Data Standard v3.2a.