Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: In Analytic Process Overview, removed step 5 "If required, create a file of types extending the Ed-Fi Core, adding attributes to Core domain and association types, creating new domain and association types, and creating new simple and complex types as required for new attributes." since this example isn't going to contain extensions; in Technical Process Overview - step 2 removed " or extended Ed-Fi Core XML schema" ;

...

  1. Analyze the specific data requirements for the data interchange.
  2. Analyze the specific interchange transactions that are required.
  3. Map the data requirements to the Ed-Fi Unifying Data Model.
  4. Identify the Ed-Fi domain types and association types required for the interchange.
  5. If required, create a file of types extending the Ed-Fi Core, adding attributes to Core domain and association types, creating new domain and association types, and creating new simple and complex types as required for new attributes.
  6. Make sure that extended reference types exist for association references that will require the receiving system to lookup specific instances of education data instances. Furthermore, ensure that the receiving system is capable of performing the required lookups with the identifying data that will be provided.
  7. Create the interchange schema file(s) to match the various interchange transactions, referencing the Core or extended types required for the interchange.

...

  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.

...