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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portal, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Expose common transformation assets (e.g. xQuery and XSL files) in the WMB mapping node for integration with non IBM products
Expose common transformation assets (e.g. xQuery and XSL files) in the WMB mapping node for integration with other products including non-IBM products .
Currently MDM Server ASI tooling uses the same technology as the WMB mapping node and exposes an XSL file representing the transformation. This allows the XSL file to be used by other tools.
The WMB mapping node in the tooling uses xQuery at runtime but does not expose xQuery or xsl assets to the user. WMB appears to inefficiently generate the xQuery file at runtime and not store it.. Currently the WMB mapping node produces a map file (which is an IBM proprietary format) to represent the transformation.
If the WMB mapping node exposed common assets for transformations, these could be shared so that other IBM and non-IBM products could use these transformation assets. This would fit with IBM's strategy to promote open standards and compete on implementation.
I have raised this as a high priority as not being able to share assets leads to inefficient solutions with the same or similar transformations needing to authored in different systems. Having these common assets for transformations would give us a strong story to use WMB to author your transformations, in that we can generate files that comply to open standards that can be re-used across your solution.
Do not place IBM confidential, company confidential, or personal information into any field.