Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories Maps & Type Trees
Created by Guest
Created on Mar 2, 2026

FINPLUS readme_xsd.txt should contain the reference to the package and schema version it relates to

Currently the FINPLUS readme_xsd.txt file header doesn't indicate any information to the package or schema version it relates to.  Only further down in the document, the publication dates are listed under the Schema section.  This can cause misunderstandings and mixups for multiple reasons :

  •  business teams within the banks receive communication from financial institutions reversing the schema version (which don't always include the xml schema publication date).
  • customers may have multiple schema deployed on their development workstation.  Having a clear header in each readme_xsd.txt avoids mixups

To ensure no confusion with the versioning of the schema can arize, it would be a great advantage to have all information related to the schema version summerized in the readme_xsd.txt header of each marketplace.  An ideal header in the readme_xsd.txt would contain the following information :

=========================================================================================
Pack for Financial Payments Plus v<V.R.M.F> - <marketplace> Schema validation example readme
Document Modified: <dd Month ccyy>
Document version : <v.r>
XML Schemas Published: <dd Month ccyy>
XML Schemas version : <v.r>
=========================================================================================

 

For example for NBOR ReGIS :

=========================================================================================
Pack for Financial Payments Plus v11.0.2.0 - NBOR ReGIS Schema validation example readme
Document Modified: 10 October 2025
Document version : <in case this would add any value>
XML Schemas Published: 25 August 2025
XML Schemas version : 1.3
=========================================================================================