Clarify case sensitivity for unique element names

[kleihan]

XML keys are case sensitive. However, FIX Latest has a convention not to create multiple names for the same element type that are only unique because of case sensitivity. There is an exception that has caused problems for QuickFIX that generates uppercase names for codes, e.g. BUY and Side_BUY for Side(54)=1 (Buy).

The exception is the deprecation of a code for BenchmarkCurveName(221), i.e. Euribor and EURIBOR both exist in the Orchestra repository, but the former has been deprecated.

      <fixr:code id="221003" name="Euribor" value="Euribor" sort="3" added="FIX.4.3" deprecated="FIX.5.0SP2" deprecatedEP="132" updated="FIX.5.0SP2" updatedEP="132">
        <fixr:annotation>
          <fixr:documentation purpose="SYNOPSIS">
                        EURIBOR (deprecated use enum EURIBOR instead)</fixr:documentation>
          <fixr:documentation purpose="ELABORATION">
                        Deprecated use of EURIBOR for the enumeration.</fixr:documentation>
        </fixr:annotation>
      </fixr:code>

      <fixr:code id="221015" name="EURIBOR" value="EURIBOR" sort="15" added="FIX.5.0SP2" addedEP="132">
        <fixr:annotation>
          <fixr:documentation purpose="SYNOPSIS">
                        Euro interbank offer rate</fixr:documentation>
        </fixr:annotation>
      </fixr:code>

This issue is to clarify whether element names the unique constraints of names in the Orchestra standard should remain case sensitive. The FIX Protocol or others may have a convention to be case insensitive.

[kleihan]

Orchestra Subcommittee July 15:

• There is a difference in relevance of case sensitivity between element names and element values.
• Element values should always be case sensitive, i.e. a different spelling is a different value.
• Code generators have to deal with the issue of values being different in spelling, e.g. QuickFIX.
• Element names should also be case sensitive, but two elements with a different spelling should never be used to express different semantics.
• No change to the Orchestra schema but the specification should clarify case sensitivity.