Infrastructure (Global) 3.2.1 Changes

June, 2016

Summary 3.2

Updates introduced in this SIF Specification include: Query By Example, enabling intuitive queries in both XML and JSON; Change Since, empowering retrevial of just the differences; Named XQuery Parameters, simplifying supporting our most powerful query mechanisms; HEAD, get just the headers when they contain everything you need; Media Types Support Generalized, move data that is neither XML nor JSON in the standard way; and Functional Services, coordinating one or more data exchanges such that they have a beginning, middle, and an end.

Changes

Query By Example
Changes Since
Named XQuerys Parameters are now enumerated outside the Script
Addition of HEAD functionality for Request Connector
Mime Types Support Generalized
Functional Services now have their own connector and job object definition

June, 2016

Errata for Previous Releases

OAuth Query Parameters have been Corrected
CodeItem is now repeatable inside a CodeSet
DynamicQuery and Paged are now optional for a Provider

March, 2017

Summary 3.2.1

The primary driving factor in creating this fix release was difficulties encountered when using the jobId to setup and deliver events to the owning Adaptor. The updates enumerated below covers changes in this mechanism and other points of confusion discovered through real world usage. Please use this release instead of SIF Infrastructure (Global) 3.2.

Fixes

Clarified OAuth authentication in the Environment (using "Bearer").
Dropped footnote about Directed Events as that concept is not yet fully describe in the specification.
Dropped jobId header.
Added option for service consumers to setup a subscription for job objects (similar to any other object).
Added fingerprint header.
Added a fingerprint element to the environment.
Added "initialization" to the job object as a more scalable way to start one or more jobs, especially when many are created at the same time.
Clarified the role of the applicationKey throughout the documentation.
Dropped references to XML Filtering and other possible "value add" technology that are not explicitly described as part of the specification.
Corrected the Code Sets Registry utility service XML Schema to not require a source and namespace throughout.
Relaxed the contentType (and Accept) header to allow for any media type throughout the documentation.

March, 2017

Full 3.2 to 3.2.1 Deltas

Our new policy and procedure for releasing a specification requires a full delta from the previous version. For this release of the Global Infrastructure, we have provided PDFs of the four normative volumes of the specification with track changes enabled.

Deltas