Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated "Use the XML include statement to reference the Ed-Fi Core XML schema or extended Ed-Fi Core XML schema." to indicate extended core schema could be referenced as well; added ellipsis to code lines with open tags;

...

  1. Create a separate XML schema definition file for the interchange schema.
  2. Use the XML include statement to reference the Ed-Fi Core XML schema or extended Ed-Fi Core XML schema.
  3. Create a single new element for the interchange.
  4. Insert an unbounded XML choice statement.
  5. Within the choice, insert elements referencing the desired domain entities, Descriptors, or associations required for the interchange.

...

Code Block
languagexml
<xs:complexType name=”StudentParentAssociation”>
    . . .
	<xs:complexContent>
		<xs:extension base=”ComplexObjectType”>
			<xs:sequence>
				<xs:element name=”StudentReference” type=”StudentReferenceType”/>”StudentReferenceType”>
                . . .
				<xs:element name=”ParentReference” type=”ParentReferenceType”/>”ParentReferenceType”>
                . . .
				<xs:element name=”Relation” type=”RelationType” minOccurs=”0”/>”0”>
                . . .
				<xs:element name=”PrimaryContactStatus” type=”xs:boolean” minOccurs=”0”/>”0”>
                . . .
				<xs:element name=”LivesWith” type=”xs:boolean” minOccurs=”0”/>”0”>
                . . .
				<xs:element name=”EmergencyContactStatus” type=”xs:boolean” minOccurs=”0”/>”0”>
                . . .
				<xs:element name=”ContactPriority” type=”xs:int” minOccurs=”0”/>”0”>
                . . .
				<xs:element name=”ContactRestrictions” type=”ContactRestrictions” minOccurs=”0”/>”0”>
                . . .
			</xs:sequence>
		</xs:extension>
	</xs:complexContent>
</xs:complexType>