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.
Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. We have re-considered RFEs 23979 (now APPC-I-28) and 23980 (now APPC-I-36) in tandem with one another so this comment is being placed onto both records. Unfortunately on this occasion we do not intend to take either of these suggestions further forward at this time. Whilst both represent valid technical demands, we feel that the business priority of these items does not justify holding them open any longer. The main justification for this stance is that for technical users, there is a relatively straight forward "workaround" to achieve the basic desired usecase under discussion. At their heart, DFDL schema models use annotations to hold the data required to furnish the "logical" xsd structure with the additional info needed to describe the wire format. At the center of this requirement we suspect is the need for an external XML schema tool to be able to tolerate the existence of these annotations. XML schema annotations are a valid part of the specification so we believe it is reasonable for XML schema tool vendors to tolerate the existence of annotations. In addition, even if this is not the case, it is relatively easy for a user to separate the DFDL annotations into a separate physical schema document (linked using import/include statements) ... this approach would help interoperability of import and export.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - WebSphere
Product family - Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Connectivity and Integration
Product - IBM Integration Bus (WebSphere Message Broker) - IIB
Thanks for raising this reasonable requirement Joerg, which is straightforward from an engineering point of view, given the relationship between XSD and DFDL. We'll investigate this for a follow-on release or fixpack.