This website uses cookies to store information on your computer. Some of these cookies are used for visitor analysis, others are essential to making our site function properly and improve the user experience. By using this site, you consent to the placement of these cookies. Click Accept to consent and dismiss this message or Deny to leave this website. Read our Privacy Statement for more.
Print Page | Contact Us | Sign In | Join the A4L Community
SIF Infrastructure Specification 3.3
Share |
 

This is a significant release of the infrastructure as it adds: 

  • Privacy Integration,
  • Version Indication/Negotiation,
  • PESC JSON Adoption,
  • Cleaner & More Consistent Schemas & Artifacts, and
  • other Clarifications. 

A full account of all the changes in this Infrastructure Specification release can be found here - Delta PDF, XSD PDF.

Those looking to incorporate privacy into their interoperability should look at the Data Protection Enforcer Service Volume, Privacy Obligations Utility Service, and Privacy Obligations Document (POD) Infrastructure Payload. 

 

SIF Infrastructure Specification 3.3 documentation

 Document Name Description

Read This First

Contains a set of frequently asked questions (FAQs) to assist a technical readership ranging from those only casually interested in the SIF Standard to those actively planning to adopt it.

Base Architecture

SIF Infrastructure 3.3 represented a major release of the SIF Standard.  Currently unused functionality in SIF 2.x was deprecated or replace entirely, and significant new, non-backward compatible functionality has been added.

Infrastructure Services

All Service Consumers and Service Providers in a SIF 3 Environment interact only through and with the Environments Provider Interface. The implementation of this interface provides the infrastructure underlying the SIF 3 Environment, and is defined at three levels: Direct, Brokered, Administrative.
Utility Services A Data Service that provides a data object related to the SIF Infrastructure, rather than an object which is part of a particular locale-specific data model. 

Functional Services

A functional service consists of: a 'functional service' definition describing the service; a 'Job Object' format for communicating intent, status, and results; and one or more 'Phases' which accomplish the Job, step-by-step.

Data Protection Enforcer Service

The SIF 3.3 infrastructure introduces services that provide functionality in regard to data protection legislation. The services are intended to be “support” styled services. That means that SIF cannot enforce nor is it responsible for enforcing data privacy legislation; but it can provide utilities that simplify the implementation of data protection obligations that a particular implementation may be required to adhere to.

Includes an example of the Privacy Obligation Document (POD).

Version Indication & Negotiation

Links to the other standards we are seeking to adopt and embed.  This is where we lay out how to start adopting PESC JSON, however if you are pursuing the technology, you should check the standard here.
Infrastructure Payloads Our globally consistent format for defining our data models, which we now use to produce infrastructure artifacts describing our payloads.

 

 

PODcontents

  • SIF Association (dba Access 4 Learning (A4L) Community)

  • PO Box 1024, New Albany, Ohio 43054-1024

  • Phone: +1.202.621.0547

  • staff@A4L.org