Work is currently well underway on defining the new SIF v3.0 infrastructure ... the "wire" part of "CEDS on the Wire". It is being guided by the following set of informal development “Commandments”, which give a flavor of what that wire will look like once it it completed.
The SIF v3.0 infrastructure:
- Shall leverage functionality now provided by modern middleware technologies
- Shall provide a clear migration path for current suppliers and end users of SIF infrastructure technology
- Shall lower the barrier to entry for new vendors, thereby helping to increase the number of new SIF infrastructure technology providers.
- Shall not drop any existing functionality (whether optional or mandatory) in the current release which has been utilized by significant numbers of SIF end users, without supplying a viable alternative - because issuing a new release will not change the underlying use cases.
- Shall be capable of reuse without change to support the Data Model of any SIF locale (US, AU, UK).
- Shall extend and not compromise existing data security
- Shall not weaken "out of the box" interoperability between SIF-conformant applications.
- Shall extend the SIF standard into new developer environments such as REST without fragmenting SIF adopters into separate non-interoperable communities.
In the next posting we will explore the extended set of high level infrastructure functionality which will be supported by SIF v3.0, in accordance with the above commandments.