News for hackers. Stuff that matters.
Re:Public.resource.org wins appeal on right to publish the l... by rayiner on Saturday July 21, 2018 @11:14AM (#17582258)
ISO is composed of people and companies that develop standards for other people to use. What is wrong with charging for that? What’s the other business model for paying for that effort? The “open” and “free” HTML standardization process, for example, has totally broken down, and now is “might makes right” (whatever Chrome does is the standard). Would that be preferable for ISO standards?

It costs money to develop standards. Paying a fee to access them (so long as you are not forced to by law) is just about the least objectionable way of paying for the work to be done.

Re:Public.resource.org wins appeal on right to publish the l... by alexchamberlain on Saturday July 21, 2018 @11:28AM (#17582312)
You could charge a fee to the companies displaying the mark or those able to certify it, whilst making the standard free to read.
Re:Public.resource.org wins appeal on right to publish the l... by delfinom on Saturday July 21, 2018 @11:29AM (#17582320)
But there are hundreds of ISO specs.

In a product design alone, I may have 10-15 ISO specs, we don't stick on 10-15 labels on the outside and it would be ridiculous to stick on a sticker for a spec that just details minimum hole size spacing in a circuit board.

Re:Public.resource.org wins appeal on right to publish the l... by rspeer on Sunday July 22, 2018 @03:50AM (#17585730)
I enjoy claiming that code I write is "ISO 3 compliant" when I pick arbitrary numbers from a limited set of nice arbitrary numbers.