In more recent years, we have seen this public collaborative process popularized and validated in a number of areas: notably the open source movement and, perhaps most strikingly, Wikipedia (www.wikipedia.org). Wikipedia is particularly interesting because it popularized the “wiki” – a technology specifically developed to support exactly the kind of collaborative process that has been at the core of FIX since its beginnings. The traditional FIX collaborative culture and wiki technology are a marriage made in heaven. Enter FIXwiki.
Located at www.fixprotocol.org/fixwiki, FIXwiki is a FIX-specific wiki website that provides a comprehensive and authoritative view of the FIX specification. There is a FIXwiki page for each FIX message, component, field, value or type. In addition to definitions taken from the specification, each page also has an area for user comments, clarifications, corrections, examples or suggestions. It enables representatives from FPL Member firms to actively contribute additional information, provide comments, and share knowledge and insight to support the future development of the FIX Protocol messaging standard and is viewable by the broader FIX user community, providing a valuable reference tool for all market participants.
FIXwiki is not intended to replace the existing FIX forums. The forums are ideal for discussions and it is likely that FIXwiki postings will contain many references to those discussions. A wiki, however, provides a better repository for capturing the clarifications, interpretations and examples of the FIX Protocol that come out of such discussions.
FIXwiki is generated automatically from the official FIX repository, which is the computer readable database underlying the FIX specification. Therefore, FIXwiki and the FIX specification can never drift apart – they are derived from the same underlying data. In fact, it is even possible that FIXwiki could eventually become the specification. Currently, the FIX specification is in the form of a series of Microsoft Word or PDF documents. However, the full text of those documents could be ported to FIXwiki.
As a trial, a significant part of the specification has been converted and is now available on FIXwiki for general review. There are a number of clear advantages to having the complete specification in wiki form, but there are also advantages in keeping it in its current form. Members of the electronic trading community are encouraged to take a look at the trial pages and share their thoughts.
It is clear that FIXwiki is a valuable collaborative tool for keeping FIX close to the industry it serves, but it is no silver bullet. No matter how good your tools and processes may be, any highly collaborative process, such as that used in the development of FIX, will have its challenges. In the end, the most important resource behind FIX is the people comprising the FIX community. However, people are fallible and mistakes will be made. The community review process will sometimes fail and things will enter into the standard that should not – needing to be deprecated and removed in later versions. The more engaged our community is with the development of FIX, the fewer mistakes will be made but this democratic model isn’t perfect and it never will be.
Winston Churchill said, “No one pretends that democracy is perfect or all wise. Indeed, it has been said that democracy is the worst form of government except all those other forms that have been tried from time to time.” He could have been talking about FIX.
If you are interested in finding out more about FIXwiki and the FPL Discussion Forums please visit: www.fixprotocol.org.