categoryType/@section is use="required" but never included in FIX data (schema bug)

[noelmcloughlin]

The repositorytypes.xsd (v1.1-rc2) declares the section attribute on categoryType as use="required".

fix-orchestra/repository/src/main/resources/xsd/repositorytypes.xsd

Line 116 in 9d29211

<xs:attribute name="section" type="fixr:Name_t" use="required"/>

However the XML data published by the community consistently omit this attribute:

File	Repository	Categories missing section
OrchestraFIXLatest.xml	fix-orchestra	Common, Fields, ImplFields
mit_2016.xml	fix-orchestra	Common, Fields, ImplFields
OrchestraFIXLatest.xml	orchestrations	Common, Fields, ImplFields
OrchestraExamples-v11-RC1.xml	orchestrations	Common, Fields, ImplFields
OrchestraFIX44.xml	orchestrations	Common

This XSD constraint is stricter than the data it is meant to describe - the over-constraint should be considered schema bug.

Example
https://raw.githubusercontent.com/FIXTradingCommunity/fix-orchestra/refs/heads/master/repository-util/src/test/resources/OrchestraFIXLatest.xml

      <fixr:category FIXMLFileName="components"
                     componentType="Message"
                     includeFile="fields"
                     name="Common"/>

XSD validation failure:

cvc-complex-type.4: Attribute 'section' must appear on element 'fixr:category'.

Suggested fix

<!-- before -->
<xs:attribute name="section" type="fixr:Name_t" use="required"/>

<!-- after -->
<xs:attribute name="section" type="fixr:Name_t"/>

[kleihan]

@noelmcloughlin Thank you for raising the issue. It is a violation in the way that FIX Latest is using Orchestra v1.0. It is not a bug in the Orchestra schema. Orchestra is not FIX-specific and can be used for any protocol.

The background is that the FIX Protocol used the name "Common" early on to identify groups and components that are used in more than one category of a section or even across sections. Hence it could not be limited to a single section. Adding a dummy section "NONE" for category "Common" would resolve the schema violation. There may be other options.

Note that we are looking into Orchestra sections and categories with #290 and in the context of ISO 20022. It is quite likely that Orchestra v1.1 will make changes to the current definitions, including the hierarchical nature of sections and categories.

[patricklucas]

@kleihan I don't think FIX Latest has an issue—it only claims to be Orchestra 1.0-compliant, where section is still optional. Once FIX begins publishing an Orchestra 1.1(-rcX)-compliant repository, something will need to be done, but I don't think there's any bug currently, either in the FIX Latest Orchestra repository or in the Orchestra 1.1-pre schema.

[kleihan]

@patricklucas thank you for the clarification. I missed the fact that we had only added the requirement with #191. Hence, no impact on FIX Latest right now and maybe also not going forward, depending on the resolution of #290.

@noelmcloughlin please only use Orchestra v1.0 schema to validate FIX Latest. The metadata attribute dcterms:conformsTo defines the Orchestra version being used:

  <fixr:metadata xmlns:dcterms="http://purl.org/dc/terms/">
    <dcterms:creator>FIX Protocol Ltd.</dcterms:creator>
    <dcterms:description>FIX Latest as of Extension Pack 303</dcterms:description>
    <dcterms:publisher>FIX Protocol Ltd.</dcterms:publisher>
    <dcterms:title>OrchestraFIXLatest</dcterms:title>
    <dcterms:rights>Copyright (c) FIX Protocol Ltd. All Rights Reserved.</dcterms:rights>
    <dcterms:format>application/xml</dcterms:format>
    <dcterms:conformsTo>Orchestra v1.0</dcterms:conformsTo>
    <dcterms:created>2026-06-03T00:00:00.000Z</dcterms:created>
    <dcterms:source>Orchid</dcterms:source>
  </fixr:metadata>