Extensions for Financial Services (XFS) - XFS4IoT Specification - Release 2021-1 Release Candidate
XFS4IoT has been identified as a successor to XFS 3.x to meet the following requirements: 1. Replace the XFS and J/XFS standards in the marketplace. 2. Target industries – Retail Banking. 3. Operating System Agnostic and Technology and Language Adaptable. 4. Multi-Vendor – Able to run common core high level functionality on multiple vendors hardware, while providing access to finer level device API granularity. 5. Flexibility – enabling new hardware topologies, device types and functionality to be rapidly adapted. 6. Support end to end application level security. 7. Should not prevent the use of a low resource computing environment. 8. Provide a good developer experience by providing a well-documented API that is easy to learn, is quick to market and reduces risk by exposing an unambiguous interface. 9. Leverage existing standards. Within the overall requirements specified in the Charter, the opportunity has been taken to solve some of the issues with the 3.x interface while retaining all the same functionality: 1. Binary data structures makes adding new functionality difficult due to compatibility issues, leading to multiple redundant versions of the same command appearing in many of the existing device classes. To resolve this, a flexible text based approach has been adopted including the wide use of default parameters.
ΚΩΔΙΚΟΣ ΠΡΟΪΟΝΤΟΣ:
CWA 17852:2022
XFS4IoT has been identified as a successor to XFS 3.x to meet the following requirements: 1. Replace the XFS and J/XFS standards in the marketplace. 2. Target industries – Retail Banking. 3. Operating System Agnostic and Technology and Language Adaptable. 4. Multi-Vendor – Able to run common core high level functionality on multiple vendors hardware, while providing access to finer level device API granularity. 5. Flexibility – enabling new hardware topologies, device types and functionality to be rapidly adapted. 6. Support end to end application level security. 7. Should not prevent the use of a low resource computing environment. 8. Provide a good developer experience by providing a well-documented API that is easy to learn, is quick to market and reduces risk by exposing an unambiguous interface. 9. Leverage existing standards. Within the overall requirements specified in the Charter, the opportunity has been taken to solve some of the issues with the 3.x interface while retaining all the same functionality: 1. Binary data structures makes adding new functionality difficult due to compatibility issues, leading to multiple redundant versions of the same command appearing in many of the existing device classes. To resolve this, a flexible text based approach has been adopted including the wide use of default parameters.
