A application designed to help a programmer understand and explore an API.
See SIS Baseline Profile.
A code framework built on the SIF Common Framework which iimpements or supports behaviours required by the SIS Baseline Profile. These include caching of dependent objects, and automated querying for their dependencies.
An XML Schema is a language for expressing structures and constraints for data objects and elements.
An educational institution providing primary and secondary education, prior to tertiary education (college or university).
Sharable Content Object Reference Model (SCORM) is a collection of standards and specifications for web-based e-learning. It defines communications between client side content and a host system called the run-time environment (commonly a function of a learning management system). SCORM also defines how content may be packaged into a transferable ZIP file.
See State Education Agency
|Yes||Yes||Yes||Selective Message Blocking|
(SMB) Allows an agent to tell the ZIS to suspend delivery of event messages until further notice.
A set of defined functionality encapsulated behind a standardized CRUD interface, which is implemented by a Service “Provider” for clients (the “Service Consumers”) to utilize.
Referenced in SIF 3.0 Base Architecture documentation.
A Service Consumer implementation makes requests of, and subscribes to and receives Events from, one or more Service Provider components.
Referenced in the SIF 3.0 Base Architecture documentation.
SIF 2.x Equivalent: Client
An interface supporting one or more of the standardized CRUD (Create, Query (READ), Update and Delete) data requests on objects of a specific type. Ex: Student Data Object Service
A Service Provider implementation accepts, processes and responds to requests from Consumers for object type or function-specific services, and publishes related Events in accordance with the type of Service Provider Interface it is implementing.
Every independent Service Provider initially registers as a Service Consumer, and may be (and generally is) a Consumer of one or more other Services.
SIF 2.x Equivalent: Object Provider
A Functional Service encapsulates stateful process behavior as well as the data exchanged between applications implementing that process.
It does this by supporting all four methods of a Data Object Service Provider interface, but applies them to Object Services rather than Object data elements.
When a Consumer issues a “create” Request to a Functional Service, it results in the creation of a new executing instance of the Service (a “Job”) rather than a new instance of a data object.
From a conceptual point of view, each Job instance contains a set of named “phases”, identical to every other Job created by that Function Service. These discrete phases define and encapsulate the subactions which need to be done, but they do not explicitly determine the ordering (since the phases defining a Function may be executed in different order, depending upon the implementation and the needs of the site where the Functional Service is deployed).
Once created, the Job instance can be queried to find out where in the process it is (what is happening, what is the current status of each completed phase) and the Job may issue Events as its internal phases are completed.
Each Job Phase is represented by:
- A Phase name
- A status (NotStarted, InProgress, Completed, Failed)
- A defined Object Service corresponding to that Phase (which supports some or all of the set of service operations)
The creator of the Job can therefore:
Example: StudentLocator, EndOfYearRollover
- Monitor the status of the Job (through querying the Job instance or by receiving Job level Events)
- Interact with the Job at any phase by issuing Query, Create, Modify and Delete requests (the meaning of which are determined by the Functional Service itself).
- Receive Events from the various Phases of the Job
While the SIF 3.0 infrastructure is independent of the Data Model defining the payloads it carries, the following general Object Service framework must be supported by all Service Providers.
An Object Service is the “authoritative source” for all data elements contained in all data objects of a specific type, and services some or all of the following requests:
Depending upon the object type, the corresponding Data Object Service may:
Whenever an Object Service receives a Request for an operation it does not support, it must return, “operationNotSupported”.
- Publish an Event whenever an object is Created
- Publish an Event whenever an object is Deleted
- Publish an Event whenever certain (or any) elements in an Object are updated
- Restrict the range of possible Queries
An authentication system.
The SIF-specific component which provides the RESTful interface between the application and its partners. For Consumers, this is a very thin wrapper and can often be coded by the application developers rather than utilizing a 3rd party.
When used in the SIF Certification program, this is the software component that ties a product to any SIF Environment.
There are two basic varieties of Adapter, each corresponding to an earlier SIF 2.x equivalent:
- Service Consumer Adapter - (SIF 2.x equivalent) Client Agent
- Service Provider Adapter - (SIF 2.x equivalent) Object Provider Agent
Essentially each Service Consumer and Service Provider application may include a separate adapter component to communicate with other applications via the Environments Provider interface. For example, a SIF 3.0 Brokered Environment may integrate a student information application, a learning management application, and a library automation application. An adapter component acts as a bridge between each application and the Environments Provider interface.
Adapters never communicate with other adapters directly. Instead, each adapter uses the Environments Provider interface as a trusted intermediary that brokers the exchange of data with other adapters.
Previously known as a 'SIF Agent' in all SIF Solutions prior to SIF 3.x.
The liaison between an application and the ZIS. An agent is responsible for sending messages to and receiving messages from the ZIS. For incoming messages, an agent translates the XML message into the data recognized by its application, and applies any changes to the application’s data. An agent is also responsible for monitoring changes in the data associated with its application, assembling it into a SIF message, and submitting it to the ZIS.
|Yes||Yes||Yes||SIF Certification Agreement|
The agreement between the applicant and the SIF Certification Authority, which contains the legal commitment by the applicant to the conditions of the SIF Certification Program.
|Yes||Yes||Yes||SIF Certification Authority|
The Certification Authority is the regulatory team who administer and ensure compliance of any product completing the SIF Certification Program. The Access 4 Learning Community, formerly the SIF Association, is officially sanctioned as the Certification Authority.
|Yes||Yes||Yes||SIF Certification Authority Help Desk|
A4L Staff member(s) tasked with responding to certification needs and opportunities.
|Yes||Yes||Yes||SIF Certification logo|
The A4L Community’s certification logo or other marks as designated from time to time by the Community.
|Yes||Yes||Yes||SIF Certification Register|
A web-based record of all SIF Certified products, which is maintained by the Certification Authority.
|Yes||Yes||Yes||SIF Certified product|
A product or service that has successfully completed the certification process and for which the Solution Provider has been notified in writing by the Certification Authority that certification has been achieved for such product or service.
A product which conforms to the SIF standard, but has not been certified.
|Yes||Yes||Yes||SIF Implementation Specification|
A data standard that describes how education applications can share data.
A SIF xPress solution is comprised of a contemporary implementation model as an Application Programming Interface (API); an underlying, market-driven use case; and the use of the SIF 3 Infrastructure Specification combined with a use-case centric Data Model designed for ease of use.
|Yes||Yes||Yes||SIF Zone Services|
WSDL-defined service applications which will run over the extended SIF infrastructure.
The acknowledgement message used in every message exchange. The receiver of a message returns the Ack to let the sender know the message was received, or if there was an error.