SWIFT Standards Developer Kit case study - GEFEG.FX
SWIFT Standards Developer Kit case study - GEFEG.FX
SWIFT Standards Developer Kit case study - GEFEG.FX
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Working with Normalised Schemas<br />
Example business requirement:<br />
“In a specific business context Clearstream supports only the „ISIN‟ and<br />
„Common code‟ elements for all fund messages.”<br />
Normalised schemas<br />
Message A Message B<br />
Id<br />
• All message schemas „include‟ a schema<br />
containing the common complexTypes<br />
originating from ISO 20022 UML Message<br />
Components.<br />
• The element „Id“ of complexType<br />
„SecurityIdentification3Choice“ exists only<br />
once and the business requirement needs<br />
to be described only once.<br />
Self-contained schemas<br />
Message A Message B …<br />
Id Id<br />
• The element „Id“ of complexType<br />
„SecurityIdentification3Choice“ is<br />
generated in the production schemas as<br />
often as each individual message requires<br />
it.<br />
• Thereby each message schema contains<br />
all required artifacts.<br />
Design-time Production time
Change language