Agree. Usually the parties developing a standard have a incentive to make it difficult for others to implement. They can claim it's open, while still limiting competition.
I remember when the first HTTPS spec came out, and me and everyone else were saying how hard it was to follow. And someone from Netscape came out and said the text was "intentionally terse".
I tried to use ISO 1016 for writing a software design doc with some success, but it was like pulling teeth.
First, you needed multiple ISO dictionaries to find out what half the words are referring to, and even then things are ill-defined.
For example, one of the required sections in an ISO SDD is the Context, but nowhere is context defined or described.
The standards just seem like a web of academic garbage with no connection to reality.
Woe to anyone that must implement them as part of their job.