Imported from previous forum
[ original email was from Jim Northey - jnorthey@lasalletech.com ]
We need to be able to differentiate option strategies (combinations, spreads, etc.) from options, futures, stock. These strategies can also contain underlying legs, such as Futures or Stock. Does anyone see a problem with defining a new enumeration for SecurityType="MLEG" (For multi-leg instrument?).
Also a related issue, for underlying that are indexes does anyone see a problem using "INDX" for the SecurityType to represent an index? Since this is specifically an underlying index that is synthetically priced by the exchange maybe "UNX" or "UIND" would be better. (I am avoiding "NDX" as that is a trademarked name for a specific index option).
[ original email was from Ryan Pierce - rpierce@taltrade.com ]
> Also a related issue, for underlying that are indexes does anyone see a problem using "INDX" for the SecurityType to represent an index? Since this is specifically an underlying index that is synthetically priced by the exchange maybe "UNX" or "UIND" would be better. (I am avoiding "NDX" as that is a trademarked name for a specific index option).
I am very interested in this issue.
When creating the Market Data messages, we faced a similar problem. How does one send a Market Data Request for all stocks in an index?
My thought was that the issue was a global one of general symbology, not one specific to Market Data, hence action on this was deferred.
Does anyone know of any industry standards for representing different indexes?