Question: FIXimate Frame URL names

, ,
1

Imported from previous forum

2

Are the names of the URL of the messages (and components) fixed and do not change?

Example, will always FIX 5.0 SP02 message execution report will be in:
http://www.fixprotocol.org/FIXimate3.0/en/FIX.5.0SP2/body_5756.html

And Message NewOrderSingle in:
http://www.fixprotocol.org/FIXimate3.0/en/FIX.5.0SP2/body_495268.html

And how are the frame names (e.g. ‘5756’ and ‘495268’) were generated?

Can I place links to these URLs (in my documentions) knowing that they will always show the same content?

Many thanks

3

Are the names of the URL of the messages (and components) fixed and do not change?

Example, will always FIX 5.0 SP02 message execution report will be in:
http://www.fixprotocol.org/FIXimate3.0/en/FIX.5.0SP2/body_5756.html

And Message NewOrderSingle in:
http://www.fixprotocol.org/FIXimate3.0/en/FIX.5.0SP2/body_495268.html

And how are the frame names (e.g. ‘5756’ and ‘495268’) were generated?

Can I place links to these URLs (in my documentions) knowing that they will always show the same content?

Many thanks

Yuval - I would not rely on these names remaining constant - if we add a component or a message this will likely change.

The Field reference URLs are identity based and accessible via typing URL: http://fixprotocol.org/FIXimate3.0/en/FIX.5.0SP2/tag1.html

Let me investigate and see why an opaque identifier was used instead of a domain based key such as messageA.html or msgTypeA.html. There was probably a good reason for the choice (but then again maybe not ;)).

This is a powerful feature having a URL resolvable reference to the spec - I use the URL for fields all the time.

I have a queue of extension packs in front of addressing this issue, so I am not sure I would rely on it being available in the timeframe of your initiative.