Presentation Agenda

1
Presentation Agenda

• Introduction
• Overview of the Transport Layer
• Respective Responsibilities
• Overview of Extensible Markup Language (XML)
• SDS Data Exchange Specification
• Schedule

2
What Are We Building?

• A new secure Student Data System that includes...
• A database that will support the integration of
  the K-12 common components and the sharing of
  data
• Expansion of Student Tracking function to
  identify children and youth who are not
  registered in an approved education program
• A flexible and timely student record keeping
  system
• Enhanced functions to streamline business
  processes

3

• Schools / School Divisions will exchange
  information by
• Paper forms (with a sunset strategy to yield cost
  savings)
• Online data entry via web pages
• Electronic file transfer of XML data files
  (batch)
• Electronic XML data exchange (real-time)

4
New Student Data System
MIS (Outside Scope)
School
Ad hoc Reports for the Department
Standard Reports for Schools
Student Data System
Report Generator
Online Screens for Schools
Nightly Update
Online Screens For the Department
Student Data System Ad hoc Reporting
Real-time / Electronic File Transfer (Demo,
Enrolment, Registration, Final Marks)
Real-time / Electronic Data Exchange
(Demographics and Final Marks)
Department
Standard Reports for the Department
School Software
5
Schools / school divisions will have these
self-serve functions...
Web
XML
?
?
Generate and retrieve Saskatchewan Learning
IDs Enroll, register and withdraw students Mass
re-enroll their students Enter review final
marks for students Query graduation requirements
(counseling) Enter and review PAA module
tracking information Simplified distance
learning course registration Ability to establish
base school for students Submit electronic data
and receive feedback (real-time and
batch) Educator Profile
?
?
?
?
?
?
?
?
?
?
?
?
?
?
?
6
Data Communication Client Options
Real Time Exchange
1. Direct creation and transmission of XML
documents
Batch Exchange
1. Using SDS application, browse client network
for batch XML file for upload 2. Retrieve
results from SDS application
7
Data Communication Standards
HTTPS
1. Transport
2. Method
POST
3. Container
.XML
4. Security
System Authentication and XML-Embedded
User Credentials
8
Real-Time Data CommunicationModel
School Software
Internet / Firewall
Internet / Firewall
Request
Oracle DB

School Database
SDS Learning Database
HTTPS
View Results
Web Server
Process Results
Saskatchewan Learning
School System
9
Batch Exchange Data CommunicationModel
School Software
Internet / Firewall
Internet / Firewall
Select Data File
Oracle DB

SDS Learning Database
HTTPS
User Workstation
Web Server
Process Results
Saskatchewan Learning
School System
10
School / School Division Responsibilities
1. Provide Network and Security configuration
information
2. Develop the ability to generate and parse XML
documents
3. Develop the ability to initiate a HTTPS
connection, send, and receive Authentication
Credentials and XML documents
11
Department Responsibilities
1. Review and approve client network and security
configurations
2. Authenticate HTTPS connection
3. Accept, validate, and respond to authorized
XML requests
4. Ensure Data Security
12
Overview of XML

• What is XML?
• Extensible Markup Language
• Used to facilitate data exchange between
  partners, using common terminology
• Looks like HTML, but provides a semantic
  description of information

13
Example 1 - XML Fragment
ltnamegt ltfirstgtEdwardlt/firstgt ltlastgtTellerlt/lastgt
lt/namegt
14
Well Formed XML

• There is only one root element
• Every starting tag must have a corresponding
  closing tag
• XML tags can be nested but must not overlap
• Element names must obey XML naming conventions

15
Valid XML

• For a document to be valid, it must
• be well formed
• conform to a specification
• We will use XML Schema (.xsd files) to define the
  specification

16
Example 2
ltendangered_speciesgt ltanimalgt ltname
languageenglishgtTigerlt/namegt ltname
languagelatingtpanthera tigrislt/namegt
lt/animalgt lt/endangered_speciesgt
17
SDS Data Exchange Specification

• Message Types
• Types of Dialogues
• Examples

18
Message Types

• Events (new or changed data)
• Requests for Data
• Responses to Requests and Events
• Each message has one or more objects
• Each object is one business transaction

19
Types of Dialogues
Sending student demographic, enrollment and/or
class registration data
School

Event - new and/or changed data
Department
Response - status of data received
errors Learning ID Number and birth date for
records without Learning ID Number in the
original Event
20
Types of Dialogues
Sending student marks
School

Event - student marks
Department
Response - status of data received errors
21
Types of Dialogues
Quick enrollment

School
Department
Response - demographic data and/or course
history
22
Types of Dialogues
Requesting course history for students (e.g. at
the end of a term)
School

Request - course history
Department
Response - course history
23
School Mark Example
ltStudentClassMark RefId"1"gt ltStudentIdentificatio
ngt ltDeptAssignedPersonIdgt123456789lt/DeptAssignedPe
rsonIdgt ltBirthDategt1987-10-31lt/BirthDategt lt/Studen
tIdentificationgt ltClassIdentificationgt ltSchoolIdgt1
234567lt/SchoolIdgt ltClassIdgtMathA30
Alt/ClassIdgt ltStartDategt2004-02-01lt/StartDategt ltEnd
Dategt2004-06-25lt/EndDategt lt/ClassIdentificationgt lt
SchoolMarkInfogt ltSchoolMarkgt82lt/SchoolMarkgt lt/Scho
olMarkInfogt lt/StudentClassMarkgt
24
Summary / Wrap

• Web resources available
• www.sasked.gov.sk.ca\sds\xml
• Test / validation environment will be available
  for vendors
• Business and Technical contact (email)
• student.records_at_sasked.gov.sk.ca

25
Vendor Data Exchange Schedule

• Vendor Questions Sept. 23 - Oct. 31, 2003
• Development Nov. 1 - Jan. 15, 2004
• Technical Testing Jan. 15 - Mar. 1, 2004
• System Testing Mar. 1 - May 1, 2004
• Client Validation May 1 - Jun. 30, 2004
• Implementation August 2004