At last. It's time the whole would gets on board with open standards that are truly open, and there is explosive devopment going on in the world of new approaches to media production and distribution that this can only aid.
It's net-head vs. Bell-heads all over again, and one of the biggest reasons for the success of the IETF standards was the no-cost availability of all their standards.
Once upon a time, acquiring a standard involved writing to a far away address and then waiting "six to eight weeks" for a paper document to show up in your mailbox. By 1995 (when internet access became common) SMPTE was seventy years old. Certain, uh, expectations had become concretized by then, and it took considerable time and effort to overcome those.
Because these bodies want to maintain a moat for the products made by member companies. No more, no less.
A great example of this is the GigE Vision/GenICam standards that are used by basically all machine vision cameras, which were accessible to non-licensees but not usefully implementable (these standards explicitly prohibited their use in implementing any open source implementation of the standards). So essentially all they could be used for were (1) as a licensee producing closed-source software for their own cameras, or (2) you as customer trying to complain to your camera/software vendor that they failed to implement some part of the standard correctly.
I don't think the benefits of charging for your work are mysterious. It's reasonable to believe that certain works should not be behind paywalls, but not understanding is kind of a confusing stance.
There was a time when buying the Ansi C standard cost over $200 but you could get Herb Schildt’s “Annotated Ansi C Standard” for $20, which some said reflected the value he added to the process.
If your entire goal is to create a standard... it seems like giving anyone access to the materials needed to _adhere_ to said standard is prerequisite.
Unless the goal is not to create standards, but instead to control access to said standard.
The people requiring adherence to a specific standard are not the people who then need to pay to see what they're supposed to be adhering to :(.
Strictly, just because the standard costs money doesn't mean that the information within it is otherwise unavailable. The C++ spec is an amusing example of this: the actual spec costs $$$, but the final draft is freely available. I can't imagine they sell many copies. I know that back when I was employed to work on a C++ compiler I only had access to the draft.
If demonstrating conformance is important, I suspect that the cost of access to specifications is only going to be a small fraction of the cost of certification. And as I understand things, it's certification that's the target of charging for specifications.
I am not sure if this is what happens, but I could imagine an arrangement where you have a standard, and in order to advertise that you meet the standard, you are required to pay a fee to the standards body, and that fee is used to fund an audit to verify that you adhere to the standard.
It would be nice if, for example, USB did this so that I know a USB cable actually works with a specific standard before I buy it.
USB-IF does in fact do this and has for years. Certified devices are allowed to have a "Certified USB" logo somewhere on them, usually placed next to the regulatory compliance marks.
In the world they operated in when this started was in a big corporate environment, gatekeeping was a feature. Anyone who needed a standard could already get it for free through their companies records department.
At my first corporate job the first thing I did was checkout and read all the MPEG standards.
But I agree, the whale we need to go after is IEEE.
I wholeheartedly second this. I'm an individual member and a member of a specific IEEE society that sponsors a specific standard and I still have to pay for a copy. In contrast, the same standard has been adapted for specific industries and there are IEC, ITU and a SMPTE specs adopting it and those I can get for free. Doubly irritating because some of the most crucial standards like the 802 family are all paywalled. And it's not like it's warranted because if I need a standard I'm probably a vendor. Take high-speed Ethernet for example, there is such a proliferation of media types, lane counts, line encodings, FEC options and speed combinations that an engineer needs a reference from the source, and instead it's either third-party information or "stolen" PDFs.
The whole world benefits when our infrastructure can stay on spec and those specs are freely available for everyone. Specs are the vaccines holding civilization together.
Both can be true. Promoting a standard isn’t free, and having licensing and certification fees, especially in an industry where such practices make a standardization org get taken more seriously, is a reasonable strategy. We’re lucky that our industry moved in a different direction!
IP licensing and certification are entirely separate from access to standards documentation. Of course certifying conformance to a standard is going to have a cost. But publishing documentation that has already been written is effectively free.
I think people have a flipped understanding of how these standards come to be.
They don't gather industry experts in a conference room and whiteboard out a perfect design that everyone agrees on and then go off to build products.
What happens is that companies develop products and services, and at some point it becomes more useful for those products to inter operate and protocols/interfaces between them need to be agreed upon. Oftentimes it's the mutant bastard children of the existing approaches by multiple stakeholders, encumbered by patents and legacy.
Adherence to a standard is not the goal, defining interoperability between existing systems is. And everyone participating is already a paying member of SMPTE.
This is mostly true, with some exceptions. The Digital Cinema standards (428, 429, 430, etc.) were in fact developed in conference rooms and on whiteboards. It was a greenfield application with no incumbent formats.
I have written software which needed to support SMPTE standards, and to do so I pirated the standard. The standards are initially written to reflect existing systems, but then more systems are developed later.
Well, for ISO it is a business model. And for a lot of standards which have limited interest in a certain industry and you are probably going to spend $2000 on gear to make measurements compatible with the standard it is not so bad to spend 133 CHF on something.
On the other hand I served on a committee and wrote a technical report that costs 133 CHF and personally I'm a bit annoyed that (1) I can't send you a link to read it for free and (2) a friend of mine who worked for the US government and is the only person I ever met who knew how to do complex modelling in OWL couldn't contribute her writing to it because everything US government employees write is supposed to be public domain.
As someone working in standardization: I don't know any standardization organization where the people doing the actual work of writing standards are paid for their work. I certainly am not.
In the organizations I know - including ISO - the money is basically exclusively spent on "overhead".
Partially. Yes. Look at the budgets of these orgs and you'll see what I mean.
I use the term similar to who it's used for non-profit. The orgs I'm involved with are almost exclusively not involved in the actual standards creation.
If the secretariats were to shut down tomorrow I'd say the actual work on the standards could continue without anyone noticing.
No. In such organizations the money goes towards all of the usual things such as tax, building rental, utilities, and licences, as well as employee salaries and social security contributions.
BSI Group, for example, paid 26.1% tax (25% corporation tax plus some other stuff) according to its 2025 financial statement.
In my direct experience, the people who write the standard texts get a room to sit in, power for laptops, a whiteboard, and tea/coffee and biscuits, a few days per year.
>This move is part of a broader effort to modernize the organization's Standards development and publication processes. Recent initiatives include:
>Adopting GitHub-based workflows for version control
>Issue tracking and automation
>Transitioning to structured HTML-based authoring
>Implementing an integrated publishing pipeline that streamlines document creation, review, validation and release.
I am not entirely sure the Hosting on Github, Issue tracking and automation, and HTML-based authoring are all good thing. Although I would guess it is still better than what they had.
And on another note, can anyone pin point the significance of making this entirely Free? SMPTE doesn't hold any patents. And I don't believe their original standards were hard to access. Are there any significant impact of this announcement?
>can anyone pin point the significance of making this entirely Free?
It's critical for data encodings (codecs, metadata,) because without free standards developers will attempt to reverse engineer from sample files, resulting in poor interoperability and causing chaos for those implementers that actually do bother to acquire and read the spec.
Society of Motion Picture and Television Engineers.
The SMPTE standards have been very important for cinematography and television, especially for professional applications.
Their importance has decreased since the transition to digital video, when many relevant standards have been issued by other organizations, but many SMPTE standards are still important, especially regarding the formats used for distributing digital movies for movie theaters.
Didn't realize they were so broad in scope. The only thing I had heard of was "SMPTE codes" used in audio recording to sync up multiple multi-track recording machines, so that e.g. you could record 30 tracks using two 16-track recorders (with one track on each machine used for the sync). I never bothered to look up what SMPTE meant.
At last. It's time the whole would gets on board with open standards that are truly open, and there is explosive devopment going on in the world of new approaches to media production and distribution that this can only aid.
It's net-head vs. Bell-heads all over again, and one of the biggest reasons for the success of the IETF standards was the no-cost availability of all their standards.
Remember buying the 430.10 standard pdf back in the days in order to build subreader.io's cinema integration. Nice that it is openly available now!
I don't understand why any standards body would consider not doing this as a default.
Once upon a time, acquiring a standard involved writing to a far away address and then waiting "six to eight weeks" for a paper document to show up in your mailbox. By 1995 (when internet access became common) SMPTE was seventy years old. Certain, uh, expectations had become concretized by then, and it took considerable time and effort to overcome those.
Because these bodies want to maintain a moat for the products made by member companies. No more, no less.
A great example of this is the GigE Vision/GenICam standards that are used by basically all machine vision cameras, which were accessible to non-licensees but not usefully implementable (these standards explicitly prohibited their use in implementing any open source implementation of the standards). So essentially all they could be used for were (1) as a licensee producing closed-source software for their own cameras, or (2) you as customer trying to complain to your camera/software vendor that they failed to implement some part of the standard correctly.
Construction codes are still pay walled.
NEC (electric) is $170: https://www.nfpa.org/product/nfpa-70-national-electrical-cod...
IPC (plumbing) is $130: https://webstore.ansi.org/standards/icc/iccipc2024
And there are many others.
(I will say the YC company https://up.codes/ makes these much more accessible, and deals with local variants to these regulations)
Great advertisement!!!! this website is getting tiring
I don't think the benefits of charging for your work are mysterious. It's reasonable to believe that certain works should not be behind paywalls, but not understanding is kind of a confusing stance.
There was a time when buying the Ansi C standard cost over $200 but you could get Herb Schildt’s “Annotated Ansi C Standard” for $20, which some said reflected the value he added to the process.
Buying the ANSI C standard still costs about $300. Same for C++.
https://webstore.ansi.org/standards/iso/isoiec98992024?sourc...
Nobody does it. gcc/clang implement it from the "drafts", which are published online due to the need to discuss them prior to standardization.
Somewhere along the line, especially with Internet in late 00s people understand the term Open to be the same as Free. When in reality they are not.
But now it is all too late to debate and fix this.
If your entire goal is to create a standard... it seems like giving anyone access to the materials needed to _adhere_ to said standard is prerequisite.
Unless the goal is not to create standards, but instead to control access to said standard.
The people requiring adherence to a specific standard are not the people who then need to pay to see what they're supposed to be adhering to :(.
Strictly, just because the standard costs money doesn't mean that the information within it is otherwise unavailable. The C++ spec is an amusing example of this: the actual spec costs $$$, but the final draft is freely available. I can't imagine they sell many copies. I know that back when I was employed to work on a C++ compiler I only had access to the draft.
If demonstrating conformance is important, I suspect that the cost of access to specifications is only going to be a small fraction of the cost of certification. And as I understand things, it's certification that's the target of charging for specifications.
I am not sure if this is what happens, but I could imagine an arrangement where you have a standard, and in order to advertise that you meet the standard, you are required to pay a fee to the standards body, and that fee is used to fund an audit to verify that you adhere to the standard.
It would be nice if, for example, USB did this so that I know a USB cable actually works with a specific standard before I buy it.
USB-IF does in fact do this and has for years. Certified devices are allowed to have a "Certified USB" logo somewhere on them, usually placed next to the regulatory compliance marks.
In the world they operated in when this started was in a big corporate environment, gatekeeping was a feature. Anyone who needed a standard could already get it for free through their companies records department.
At my first corporate job the first thing I did was checkout and read all the MPEG standards.
But I agree, the whale we need to go after is IEEE.
> the whale we need to go after is IEEE.
I wholeheartedly second this. I'm an individual member and a member of a specific IEEE society that sponsors a specific standard and I still have to pay for a copy. In contrast, the same standard has been adapted for specific industries and there are IEC, ITU and a SMPTE specs adopting it and those I can get for free. Doubly irritating because some of the most crucial standards like the 802 family are all paywalled. And it's not like it's warranted because if I need a standard I'm probably a vendor. Take high-speed Ethernet for example, there is such a proliferation of media types, lane counts, line encodings, FEC options and speed combinations that an engineer needs a reference from the source, and instead it's either third-party information or "stolen" PDFs.
The whole world benefits when our infrastructure can stay on spec and those specs are freely available for everyone. Specs are the vaccines holding civilization together.
Both can be true. Promoting a standard isn’t free, and having licensing and certification fees, especially in an industry where such practices make a standardization org get taken more seriously, is a reasonable strategy. We’re lucky that our industry moved in a different direction!
IP licensing and certification are entirely separate from access to standards documentation. Of course certifying conformance to a standard is going to have a cost. But publishing documentation that has already been written is effectively free.
I think people have a flipped understanding of how these standards come to be.
They don't gather industry experts in a conference room and whiteboard out a perfect design that everyone agrees on and then go off to build products.
What happens is that companies develop products and services, and at some point it becomes more useful for those products to inter operate and protocols/interfaces between them need to be agreed upon. Oftentimes it's the mutant bastard children of the existing approaches by multiple stakeholders, encumbered by patents and legacy.
Adherence to a standard is not the goal, defining interoperability between existing systems is. And everyone participating is already a paying member of SMPTE.
This is mostly true, with some exceptions. The Digital Cinema standards (428, 429, 430, etc.) were in fact developed in conference rooms and on whiteboards. It was a greenfield application with no incumbent formats.
I have written software which needed to support SMPTE standards, and to do so I pirated the standard. The standards are initially written to reflect existing systems, but then more systems are developed later.
It’s a proprietary standard moving to an open standard
Well, for ISO it is a business model. And for a lot of standards which have limited interest in a certain industry and you are probably going to spend $2000 on gear to make measurements compatible with the standard it is not so bad to spend 133 CHF on something.
On the other hand I served on a committee and wrote a technical report that costs 133 CHF and personally I'm a bit annoyed that (1) I can't send you a link to read it for free and (2) a friend of mine who worked for the US government and is the only person I ever met who knew how to do complex modelling in OWL couldn't contribute her writing to it because everything US government employees write is supposed to be public domain.
As someone working in standardization: I don't know any standardization organization where the people doing the actual work of writing standards are paid for their work. I certainly am not.
In the organizations I know - including ISO - the money is basically exclusively spent on "overhead".
Is "overhead" a euphemism for administrator salaries?
Partially. Yes. Look at the budgets of these orgs and you'll see what I mean.
I use the term similar to who it's used for non-profit. The orgs I'm involved with are almost exclusively not involved in the actual standards creation.
If the secretariats were to shut down tomorrow I'd say the actual work on the standards could continue without anyone noticing.
There is a reason that at least the EU is considering modernizing the system. https://single-market-economy.ec.europa.eu/consultations/pub...
ISO, CEN, CENELEC, ETSI are stuck very much in the past.
So yes. Overhead.
No. In such organizations the money goes towards all of the usual things such as tax, building rental, utilities, and licences, as well as employee salaries and social security contributions.
BSI Group, for example, paid 26.1% tax (25% corporation tax plus some other stuff) according to its 2025 financial statement.
In my direct experience, the people who write the standard texts get a room to sit in, power for laptops, a whiteboard, and tea/coffee and biscuits, a few days per year.
It costs money to operate a website, too.
From [1],
>This move is part of a broader effort to modernize the organization's Standards development and publication processes. Recent initiatives include:
>Adopting GitHub-based workflows for version control
>Issue tracking and automation
>Transitioning to structured HTML-based authoring
>Implementing an integrated publishing pipeline that streamlines document creation, review, validation and release.
I am not entirely sure the Hosting on Github, Issue tracking and automation, and HTML-based authoring are all good thing. Although I would guess it is still better than what they had.
And on another note, can anyone pin point the significance of making this entirely Free? SMPTE doesn't hold any patents. And I don't believe their original standards were hard to access. Are there any significant impact of this announcement?
[1] https://www.smpte.org/setting-the-standards-free?hsCtaTracki...
>can anyone pin point the significance of making this entirely Free?
It's critical for data encodings (codecs, metadata,) because without free standards developers will attempt to reverse engineer from sample files, resulting in poor interoperability and causing chaos for those implementers that actually do bother to acquire and read the spec.
Off-topic, but also the title of the first album of the progressive supergroup Transatlantic.
What the heck is SMPTE?
Society of Motion Picture and Television Engineers.
The SMPTE standards have been very important for cinematography and television, especially for professional applications.
Their importance has decreased since the transition to digital video, when many relevant standards have been issued by other organizations, but many SMPTE standards are still important, especially regarding the formats used for distributing digital movies for movie theaters.
But they are getting back in the game with SMPTE 2110 which is a standard that describes how to send digital media over an IP network.
Explained here: https://www.youtube.com/watch?v=jk9xpH5aUtk
https://en.wikipedia.org/wiki/Society_of_Motion_Picture_and_...
Didn't realize they were so broad in scope. The only thing I had heard of was "SMPTE codes" used in audio recording to sync up multiple multi-track recording machines, so that e.g. you could record 30 tracks using two 16-track recorders (with one track on each machine used for the sync). I never bothered to look up what SMPTE meant.
I saw it and thought it was an extension to the the SMTP standard.
Also the name of prog supergroup Transatlantic's first album, SMPT:E, a play on the band members names.
I thought it was the Transatlantic album (StoltMorsePortnoyTrewavas)