Many other standards organizations have figured out funding models that don't shut out hobbyists, the interested public, academics, and professionals with tangential (rather than direct, funded) interest. ISO has not. They are behind the times in this regard.
ISO is full of vested interests that don't want hobbyists, the interested public, academics, and professionals to access the documents and be able to implement them at a lower cost.
Ask HN: Why are ISO standards so expensive?
31–40 of 91 posts
Re: Ask HN: Why are ISO standards so expensive?
#32Many other standards organizations have figured out funding models that don't shut out hobbyists, the interested public, academics, and professionals with tangential (rather than direct, funded) interest. ISO has not. They are behind the times in this regard.
ISO is full of vested interests that don't want hobbyists, the interested public, academics, and professionals to access the documents and be able to implement them at a lower cost.
Re: Ask HN: Why are ISO standards so expensive?
#33I needed to look at a 15+ year old IEEE spec, and thought "hey I'm a member, certainly I have access to it!". Nope. They wanted like $50 from a member. For a 15+ year old spec.
I let my membership lapse after that. Just couldn't figure out a way that it was worth $250+ year.
Re: Ask HN: Why are ISO standards so expensive?
#34Earlier quoted context omitted.
ISO is full of vested interests that don't want hobbyists, the interested public, academics, and professionals to access the documents and be able to implement them at a lower cost.
I don't think $100 can really be considered a major roadblock to any technology professional capable of doing a standardized implementation...
Re: Ask HN: Why are ISO standards so expensive?
#35Earlier quoted context omitted.
ISO is full of vested interests that don't want hobbyists, the interested public, academics, and professionals to access the documents and be able to implement them at a lower cost.
I don't think $100 can really be considered a major roadblock to any technology professional capable of doing a standardized implementation...
But today's complex computer systems depend on hundreds of thousands of interfaces, and those interfaces are depended on by millions of organizations. Their business model inhibits standardization, instead of aiding it.
Re: Ask HN: Why are ISO standards so expensive?
#36I've often thought that if standards organizations were truly interested in encouraging the use of their standards, they would make them freely available and recover their operation costs some other way. Even worse than the standards orgs themselves is IHS which acts as an electronic library (gatekeeper troll) for these orgs. In theory they are providing a service of managing electronic copies of expensive standards…
Re: Ask HN: Why are ISO standards so expensive?
#37Re: Ask HN: Why are ISO standards so expensive?
#38Earlier quoted context omitted.
I don't think $100 can really be considered a major roadblock to any technology professional capable of doing a standardized implementation...
having a copy of a single ISO standard is virtually never gonna work. too many references.
Re: Ask HN: Why are ISO standards so expensive?
#39I've been part of a team developing C++ compilers and run-time libraries. We used the final draft, which (at least for C++) is freely available. I suspect anyone relying on the final text (were it to differ from the last public draft) would be disappointed to discover that pretty much no-one uses it. It doesn't seem to me to be a terrible trade-off to say that ad-hoc use via public drafts is fine, but if you need to…
One is reminded of the legal fight over the public posting of Georgia's penal code.
Re: Ask HN: Why are ISO standards so expensive?
#40I've been part of a team developing C++ compilers and run-time libraries. We used the final draft, which (at least for C++) is freely available. I suspect anyone relying on the final text (were it to differ from the last public draft) would be disappointed to discover that pretty much no-one uses it. It doesn't seem to me to be a terrible trade-off to say that ad-hoc use via public drafts is fine, but if you need to…
When I want to reference an official specification, it is gennerally not a need. I can normally satisfy my own usecase by hacking together enough knowledge from reverse engineering and public sources (often with less effort then actually reading the spec requires), but I view it as my responsabilty to be spec compliant wherever possible.
A spec is only as good as it is followed. By not making the spec free, it is less valuable to me even if I pay for it, because there are now even more noncompliant systems out there I might need to interlop with.