On the 1st January 2018, I officially took on the post of SMPTE Standards Vice President. The role has responsibility for all of SMPTE’s standardisation activities and it fills me with equal measures of excitement and terror.
A big thank you to Alan Lambshead who, after 4 years as Standards Vice President is handing over the post to me. I think it is entirely fitting that mid-way through Alan’s final set of Face-to-Face meetings we see the publication of SMPTE ST2110. And many within the industry see this new standard as a turning point towards a new IT based future.
So, what exactly is a standard and why is it important that ST 2110 is more than a white paper published on a few vendors’ websites?
A standard
As a Cambridge man, I found the Cambridge English Dictionary definitions of the word standard are:
(countable noun) level of quality.
e.g. We have very high safety standards in this laboratory.
(countable noun) a pattern or model that is generally accepted.
e.g. This program is an industry standard for computers.
(countable noun) a pattern or model that is generally accepted.
e.g. This program is an industry standard for computers.
(adjective) usual rather than special, especially when thought of as being correct or acceptable.
e.g. These are standard procedures for handling radioactive waste.
SMPTE standards and the processes to make them embody the ideas of quality, correct and accepted. This is where some of the friction arises in this new software world we live in. I hear many people asking for the standards process to be quicker and for it to be more thorough and more accurate and for the resulting documents to be free. These are all great ideals, but they are conflicting requirements.
If you have read this far in the article, then I am sure that you have found yourself in a room with smart people who have firmly held, but differing opinions on some technical issue. It could be “should we optimise for speed of writing the specification or speed of building the resulting product?” It could be “do we prioritise low latency or low complexity in the design?”. These types of trade offs do not have a universal correct answer and smart people with differing vested interests need to compromise if these issues come up during the creation of a standard.
|