SIF Infrastructure Specification 3.3

Important Note:  While the documentation below is still available, those familiar with REST should appreciate our newer style of documentation made available starting with the release of SIF Infrastructure Specification 3.4.

To view the latest version of the SIF Infrastructure, please click here.

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

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. 

The SIF Infrastructure Implementation Specification 3.3 consists of the following documentation:


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.


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.


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.


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. 


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.


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).


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.

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


Our globally consistent format for defining our data models, which we now use to produce infrastructure artifacts describing our payloads.

SIF Infrastructure Specification 3.3 documentation