Date: Fri, 29 Mar 2024 05:27:13 -0500 (CDT) Message-ID: <930814985.30316.1711708033655@PUBEDFIPRDWEB5.public.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30315_158265560.1711708033654" ------=_Part_30315_158265560.1711708033654 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Ed-Fi Interchange Schemas define the structure of the X= ML that transports the data between systems, as shown below. Interchange sc= hemas can contain as much or as little data as required. In most cases, dif= ferent interchange schemas will be used to reflect different use cases or t= o deal with different periodicities of interchange.
Ed-Fi Interchange Schemas
The Ed-Fi Data Standard v2.2 contains a set of 21 Stand= ard Interchange Schemas. These represent field-tested schemas based on the = un-modified, non-extended Ed-Fi Core XML Schema to handle many common data = exchange use cases. (See the section Ed-Fi Standard Interchange Schema f= or background information and a list of pre-composed schema.)
The Ed-Fi Core XML Schema provides a library of buildin= g blocks from which to compose interchange schemas, as depicted in the diag= ram below. Ed-Fi Interchanges are constructed by referencing the complex ty= pes for domain entities, Descriptors, and associations.
However, implementations often have use cases beyond th= ose covered by the Standard Interchange Schemas. This section provides= guidance to technical personnel on applying the Standard to create custom = interchanges.
In creating interchanges using the Ed-Fi Data Standard,= there are several additional considerations that may require additional an= alysis, including:
Detail on how to compose a custom interchange schema can be found on the= following pages:
Find out more about how to develop solutions based on the Ed-Fi Data Sta= ndard v2.2: