Date: Fri, 29 Mar 2024 02:58:05 -0500 (CDT) Message-ID: <1215381176.30278.1711699085723@PUBEDFIPRDWEB5.public.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30277_551529087.1711699085721" ------=_Part_30277_551529087.1711699085721 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This series of five how-to exercises will walk you thro= ugh the various methods available to extend the Ed-Fi XML Schema. The techn= iques outlined in the Ed-Fi Extensions Framework are applied to create a si= ngle extended core from which many interchanges may be derived, as depicted= below.
Extended Core Schema
All restricted types, extended types, and new type= s are encapsulated in a new extended core XSD file.
To get started with this how-to example, creat=
e a base XSD file to house the extended core. Name the file EXTENSION-Ed-Fi=
-Extended-Core.xsd, include
the Ed-Fi-Core.xsd using the follo=
wing code:
<?xml= version=3D"1.0" encoding=3D"UTF-8"?> <xs:schema xmlns:xs=3D"http://www.w3.org/2001/XMLSchema" xmlns=3D"http:/= /ed-fi.org/0220" xmlns:ann=3D"http://ed-fi.org/annotation" targetNamespace= =3D"http://ed-fi.org/0220" elementFormDefault=3D"qualified" attributeFormDe= fault=3D"unqualified"> <xs:import namespace=3D"http://ed-fi.org/annotation" schemaLocation=3D"S= chemaAnnotation.xsd"/> <xs:include schemaLocation=3D" Ed-Fi-Core.xsd"/> =09. . . </xs:schema>
Extensions created in the following steps will be built in this file.
Continue
Find out more about how to develop solutions based on the Ed-Fi Data Sta= ndard v2.2: