Case sensitive - Tag207

, ,
1

Imported from previous forum

2

Hi All,

Should Tag207 be case sensitive? Or can it accept any FIX value without verifying the case?

Thanks

3

Yes, it should be case sensitive. Tag 207 is a string data type, and according to vol 1 of the FIX spec, all string fields are case sensitive. Also, since this field is bound to ISO 10383, it is required that the values match the domain definition by the rule (all upper case).

Best regards,
Jochen

Hi All,

Should Tag207 be case sensitive? Or can it accept any FIX value without
verifying the case?

Thanks

4

[ original email was from Joshua Derrick - joshuaderrick@mac.com ]
To clarify - ISO 10383 does not impose uppercase characters. The standard itself only limits value to alphanumeric characters.

This being said, all Market Identifier Codes (MIC) that have been registered to date are in all capital case.

If however, a MIC was registered with lowercase characters, this would be a valid MIC code under the ISO 10383 standard. So while Tag 207 may not support multiple cases, in theory, perhaps it should. Granted, no MIC’s are registered this way currently, but the standard does not prevent it.

Yes, it should be case sensitive. Tag 207 is a string data type, and
according to vol 1 of the FIX spec, all string fields are case
sensitive. Also, since this field is bound to ISO 10383, it is
required that the values match the domain definition by the rule (all
upper case).

Best regards, Jochen

Hi All,

Should Tag207 be case sensitive? Or can it accept any FIX value
without verifying the case?

Thanks

5

Therefore to conclude, MIC can be either in upper or lower case as registered. Thank you all.

To clarify - ISO 10383 does not impose uppercase characters. The
standard itself only limits value to alphanumeric characters.

This being said, all Market Identifier Codes (MIC) that have been
registered to date are in all capital case.

If however, a MIC was registered with lowercase characters, this would
be a valid MIC code under the ISO 10383 standard. So while Tag 207 may
not support multiple cases, in theory, perhaps it should. Granted, no
MIC’s are registered this way currently, but the standard does not
prevent it.

Yes, it should be case sensitive. Tag 207 is a string data type, and
according to vol 1 of the FIX spec, all string fields are case
sensitive. Also, since this field is bound to ISO 10383, it is
required that the values match the domain definition by the rule (all
upper case).

Best regards, Jochen

Hi All,

Should Tag207 be case sensitive? Or can it accept any FIX value
without verifying the case?

Thanks

6

Would the registration authority avoid such conflicts of having two exchanges differentiated only by capitalization? For example, Exchange A is assigned “xabc” and exchange B is assigned “XABC”.

Therefore to conclude, MIC can be either in upper or lower case as
registered. Thank you all.

To clarify - ISO 10383 does not impose uppercase characters. The
standard itself only limits value to alphanumeric characters.

This being said, all Market Identifier Codes (MIC) that have been
registered to date are in all capital case.

If however, a MIC was registered with lowercase characters, this would
be a valid MIC code under the ISO 10383 standard. So while Tag 207 may
not support multiple cases, in theory, perhaps it should. Granted, no
MIC’s are registered this way currently, but the standard does not
prevent it.

Yes, it should be case sensitive. Tag 207 is a string data type, and
according to vol 1 of the FIX spec, all string fields are case
sensitive. Also, since this field is bound to ISO 10383, it is
required that the values match the domain definition by the rule
(all upper case).

Best regards, Jochen

Hi All,

Should Tag207 be case sensitive? Or can it accept any FIX value
without verifying the case?

Thanks