Integration
This is an IBM Automation portal for Integration products. 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
As already mentioned, the current support for Draft 4 renders the JSON Validation Node nearly unusable. Converting schemas to older drafts adds unnecessary complexity, introduces potential inaccuracies, and prevents the use of features from newer schema versions. Support for the 2020-12 draft is essential to ensure accurate validation and alignment with modern schema standards.
Hi Ben, IBM Team,
I see here a raining demand at our customer base.
A lot of external systems are already using newer JSON schema formats.
Thus having support for the latest schema would be a real value add.
Adding to the comments from the OP. Requiring the use of obsolete drafts of the schema makes this feature (validation against a JSON schema) almost un-usable. Pretty much any JSON schema currently being created or maintained is using the 2020-12 draft. The need to convert these schema files back to a draft 4 schema to use with ACE is very impractical and makes it difficult to ensure that ACE is validating against the correct, true schema definition.
Idea Review. Thank you for taking the time to raise this enhancement request... As mentioned the specification has moved on since the initial implementation of this feature so it is definitely due to be revisited by product development to update our support statements. Status updated to Future Consideration.
Yes, please.