Customize by Using Extended Ed-Fi Core XML Schema
To build upon Part 4 and conclude this example, we will create an interchange schema, using these extensions, that includes the new extended core. This final step is relatively straightforward, as follows:
- Create the base EXTENSION-Interchange-HSGeneratedStudentTranscript-Extension_Example.xsd, including the EXTENSION-Ed-Fi-Extended-Core.xsd.
- Define the interchange as InterchangeHSGeneratedStudentTranscript with elements:
- Student of type Student
- StudentSchoolAssociation of type StudentSchoolAssociation
- StudentAcademicRecord of type EXTENSION-StudentAcademicRecordExtension
- CourseTranscript of type CourseTranscript
- ReportCard of type ReportCard
- Grade of type Grade
- StudentSectionAssociation of type StudentSectionAssociation
- StudentAssessment of type StudentAssessment
- School of type School
- PostsecondaryInstitution of type EXTENSION-PostsecondaryInstitution.
The following is the resulting interchange schema:
In this example, we've walked through XML restrictions, XML extensions, how to add new complex types to an existing XML core schema, and how to build an interchange based on the extended core schema – every conformant method of customization available in the Ed-Fi Extensions Framework.
Developers' Guide Documentation Contents
Find out more about how to develop solutions based on the Ed-Fi Data Standard v2.2: