Date: Thu, 28 Mar 2024 19:49:54 -0500 (CDT) Message-ID: <2043315018.30190.1711673394014@PUBEDFIPRDWEB5.public.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30189_1933322917.1711673394012" ------=_Part_30189_1933322917.1711673394012 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Ed-Fi Request for Comment 12: ED-FI DATA STANDARD v3.0d
Product: Ed-Fi Data Standard v3.0
Affects: Ed-Fi Unifying Data Model, Ed-Fi ODS / API, Ed-Fi Standard Interc=
hange Schema
Obsoletes: Ed-Fi Request for Comment 10: ED-FI DATA STANDARD v3.0c=
span>
Obsoleted By: Data Standard 3.0
Status: Inactive
Ed-Fi Alliance
March 30, 2018
Release Candidate 1
Please note that this data standard is designated as Release Can= didate 1. Active work on the standard has ceased and final version= will be published once the data model designs have been validated in imple= mentations. Users should expect minimal-to-no differences between this vers= ion and the final version.
This Request for Comment (RFC) includes materials that describe proposed= revisions to the Ed-Fi Data Standard. The material in this RFC is designat= ed v3.0d to distinguish the artifacts from previous releases and subsequent= RFC material. This draft material is intended to support review and commen= t, and should not be used in active implementation work.
Data Standard v3.0d introduces some major changes from Data Standard v2.= 0. The data model updates also continue the process of expanding and, where= necessary, revising the model to address common needs in the field work of= the Ed-Fi community. Users and reviewers are advised to read carefully&nbs= p;Ed-Fi RF= C 12 - Change Log for v3.0d.
The resulting work is designed to deliver a stronger, more flexible, and= improved core data model, but also be of a size and scope such that existi= ng implementations can adjust and upgrade systems without undue cost and co= mplexity.
A public sandbox featuring the REST API bindings for v3.0d is available = at: https://api.ed-fi.org/v3/docs/.
This RFC includes the following material:
Community feedback is critical to the RFC process, and the Alliance welc= omes feedback from anyone.
Feedback does not need to be long or comprehensive. It is enough to cite= a particular K=E2=80=9312 use case where the model would or would not be a= ble to represent a common data exchange scenario. However, if readers have = more lengthy written feedback, existing reports, or alternative fully artic= ulated data models, please feel free to share those.
The primary mechanism for feedback is via the Ed-Fi Alliance general pro= ject in the Ed-Fi Tracker. Licensees can s= ubmit new RFC 12 feedback by clicking this link (login required). = Licensees and the general public can view existing feedback here: http://tracker.ed-fi.org/projects/EDFI/= (login not required). When entering a feedback ticket, please ref= erence the change or specific fix on which you are commenting, if applicabl= e.
If you need an account for the Tracker, please go to http://www.ed-fi.org/access-request/ (note the Getting Involved and Contrib= uting if you are curious about what Ed-Fi Alliance services you ca= n access).
Community discussion is also welcome via Ed-Fi Slack.
Links to additional information, draft documentation, and other non-norm= ative content related to this RFC will be added below as they become availa= ble.