In my book, a standard isn't open if you have to pay $$ to obtain/use it.

That is, ISO standards aren't open.

@encthenet EXACTLY!

#OpenStandards require neither #licensing nor #paywall the specs.

@encthenet in fact, I'd argue that even Amazon's shitty #S3 #API is an #OpenStandard since there are multiple drop-in reimplemetations and unlike say #Oracle, #Amazon doesn't even try to ban those.

Cuz #API|s and #ABI|s are critical.

@kkarhan @encthenet This misses the whole point of why we have companies like ISO. Their job as the standard organization is to make a fair forum for discussion of the standard. Else it can very easily end up being more biased towards some specific cases than it would have been otherwise. "Amazon's shitty #S3 #API" is only put into the world to serve the needs of Amazon, they don't need to care for how anyone else wants it to be which is the thing that Standard.

That said I still think they should be free of charge. @twitter@jonsneyers one of the JPEG XL authors would also agree with that, and they are actually trying to make a difference in that space. https://www.theregister.com/2021/07/31/iso_paywall_battle/
Akkoma

@erk @encthenet Well, whilst #ISO, #DIN, #ANSI & Co. only take existing standards and reward them with their blessing, I think they should mandate those to be truly open.

For example I'd cnsider the acceptance of #OOXML to be the biggest Mistake of ISO since not only did they already accepted #OpenDocument as superior option, but at >6.000 (!!!) pages "specification" it's practically impossible to implement OOXML by anyone but #Microsoft.

@kkarhan @encthenet
That one is a bit of an outlier, so much in fact that there is a whole Wikipedia about it https://en.wikipedia.org/wiki/Standardization_of_Office_Open_XML

But the standard of OOXML is actually free to access through ECMA-376, but even then I would not consider it a very open standard because of the process of which it was created.

https://www.ecma-international.org/publications-and-standards/standards/ecma-376/
Standardization of Office Open XML - Wikipedia

@erk @encthenet I'd also not consider it an "open standard" since it basically relies on multiple, non-#FLOSS technologies, some even #patented by #Microsoft - to be used.

In fact, the reference implementation is #MicrosoftOffice and there are no 100% feature-complete alternatives.

It only exists to undermine #OpenDocument and sabotage it's deserved market dominance.

@kkarhan @erk @encthenet MS also lobbied that vote heavily. It was not made a a technical decision at ISO.

@davidwmaxwell @erk @encthenet OFC not.

Why else would they've agreed on >6.000 pages of #bloatware within less than half the time it took for #SVG [ ~ 1.000 pages]...