Orchestra provides category and section elements to group messages, groups and components in a hierarchical manner. A message, group or component can belong to a single category and a category can belong to a single section.
ISO 20022 only groups messages, but in two different ways (business areas and message sets) that are non-hierarchical. Business areas are functional categories, e.g. Regulatory Reporting, grouping messages by major financial activity or industry domain. Message set are subsets of messages from a single or from multiple business areas, e.g. the message set "Investment Funds" spans 6 business areas. ISO 20022 currently has a total of 32 business areas and 66 message sets.
It seems that the Orchestra element category can be used for ISO 20022 business areas. However, Orchestra requires a category definition to include the attribute section. This prevents the ISO 20022 messages inside a single business area from being part of different message sets.
Making the attribute section optional for category definitions and adding it as an optional attribute to message definitions could be a solution if a message cannot be a part of more than a single ISO 20022 business area or message set. Whilst this is true for business areas, it is not true for message sets, e.g. auth.031 (Financial Instrument Reporting Status Advice) is used by four message sets. This could be resolved with a sequence of section references for a message definition or with a sequence of message references for a section definition.
The relevance of the attribute category for groups and components is a separate issue. It is an optional attribute an used by FIX Latest. See issue #93 where the use of reserved category names such as "Common" and "Global" were discussed. The downside of this approach is the related maintenance effort, i.e. a component initially used in only one category of a section needs to have its attribute category changed to "Common" or even "Global", depending on where it is being re-used. Re-using a component should not require a change of its definition. ISO 20022 does not explicitly link a component to a business or message set. The usage of a component can be derived from the logical model. This may also be a useful change for FIX Latest when using Orchestra v1.1 instead of Orchestra v1.0.
Orchestra provides
categoryandsectionelements to group messages, groups and components in a hierarchical manner. A message, group or component can belong to a single category and a category can belong to a single section.ISO 20022 only groups messages, but in two different ways (business areas and message sets) that are non-hierarchical. Business areas are functional categories, e.g. Regulatory Reporting, grouping messages by major financial activity or industry domain. Message set are subsets of messages from a single or from multiple business areas, e.g. the message set "Investment Funds" spans 6 business areas. ISO 20022 currently has a total of 32 business areas and 66 message sets.
It seems that the Orchestra element
categorycan be used for ISO 20022 business areas. However, Orchestra requires a category definition to include the attributesection. This prevents the ISO 20022 messages inside a single business area from being part of different message sets.Making the attribute
sectionoptional for category definitions and adding it as an optional attribute to message definitions could be a solution if a message cannot be a part of more than a single ISO 20022 business area or message set. Whilst this is true for business areas, it is not true for message sets, e.g. auth.031 (Financial Instrument Reporting Status Advice) is used by four message sets. This could be resolved with a sequence of section references for a message definition or with a sequence of message references for a section definition.The relevance of the attribute
categoryfor groups and components is a separate issue. It is an optional attribute an used by FIX Latest. See issue #93 where the use of reserved category names such as "Common" and "Global" were discussed. The downside of this approach is the related maintenance effort, i.e. a component initially used in only one category of a section needs to have its attributecategorychanged to "Common" or even "Global", depending on where it is being re-used. Re-using a component should not require a change of its definition. ISO 20022 does not explicitly link a component to a business or message set. The usage of a component can be derived from the logical model. This may also be a useful change for FIX Latest when using Orchestra v1.1 instead of Orchestra v1.0.