News for hackers. Stuff that matters.
Re:“ISO obstructs adoption of standards by paywalling them” by linksbro on Monday March 08, 2021 @02:32PM (#26390403)
Perhaps it will be beneficial in the discussion to add examples of other orgs e.g. IETF, Unicode. Unicode spec is fully available[1] and their funding comes from a membership-model rather than a pay-model[2].

ISO's argument is compelling but we see other standards organizations taking different approaches and more or less still finding success.

[1] http://www.unicode.org/versions/Unicode13.0.0/ [2] https://home.unicode.org/membership/why-join/

Re:“ISO obstructs adoption of standards by paywalling them” by Mindless2112 on Monday March 08, 2021 @02:41PM (#26390514)
Also ECMA (C# and JavaScr... er, ECMAScript) which provides standards at no cost vs ANSI (no notable language specs since C and Pascal) which charges a fee.
Re:“ISO obstructs adoption of standards by paywalling them” by leowbattle on Monday March 08, 2021 @05:49PM (#26392721)
Last year I finished the school year early because of the coronavirus lockdown and had too much free time - so I wrote an interpreter for CLR bytecode (https://github.com/Leowbattle/clr_lite). The ECMA-335 standard contained everything I needed to know for that project: documentation of the EXE format, VM instructions, etc.

I learned a lot doing this project, and I would never have been able to do it without free access to the standard. So I think Tim is right to recognise the value open standards provide to hobbyist programmers.

Re:“ISO obstructs adoption of standards by paywalling them” by gsnedders on Monday March 08, 2021 @06:18PM (#26392996)
> ECMAScript

ECMAScript is nowadays amusing because the ISO standard for it is literally a single page document… that normatively references the ECMA published document.

Re:“ISO obstructs adoption of standards by paywalling them” by tonyarkles on Monday March 08, 2021 @07:20PM (#26393552)
Apparently 3 pages. AND STILL COSTS 38 CHF ($40 USD)! https://www.iso.org/standard/73002.html
Re:“ISO obstructs adoption of standards by paywalling them” by runiq on Monday March 08, 2021 @07:42PM (#26393762)
I mean, you can download the PDF version for free here: https://standards.iso.org/ittf/PubliclyAvailableStandards/c0...
Re:“ISO obstructs adoption of standards by paywalling them” by RcouF1uZ4gsC on Monday March 08, 2021 @02:57PM (#26390700)
ANSI for languages now operates under the aegis of ISO. For the C and C++ languages, ANSI is one of the voting member bodies.
Re:“ISO obstructs adoption of standards by paywalling them” by 1f60c on Monday March 08, 2021 @04:45PM (#26392063)
I think "ECMA C#" lags behind C# as implemented in .NET, but still.
Re:“ISO obstructs adoption of standards by paywalling them” by EricE on Monday March 08, 2021 @04:02PM (#26391495)
If I have a choice or am in a position to influence a decision, I always push for open standards orgs like OASIS: https://www.oasis-open.org
Re:“ISO obstructs adoption of standards by paywalling them” by smarx007 on Monday March 08, 2021 @05:25PM (#26392471)
OASIS is good but there member orgs need to pay membership dues and do it every year. I think ISO encourages independent experts from public sector and academia to provide expert feedback without paying for membership.

Though, I think that ISO can be fully funded by the national standards bodies on an annual basis just like OASIS is funder by companies and not charge for PDFs.

Re:“ISO obstructs adoption of standards by paywalling them” by r3un1 on Monday March 08, 2021 @02:49PM (#26390599)
I'm afraid that you are comparing apples and Walmart.

Unicode is a standard for encoding characters. ISO is an organisation that _creates_ standards for just about anything.

Unicode became a standard as a result of beating other competing standardisations. ISO declares that whatever they came up with is the standard, no competition required. Hence the effectiveness of the business model.

Re:“ISO obstructs adoption of standards by paywalling them” by wodenokoto on Monday March 08, 2021 @02:54PM (#26390663)
Parent is talking about the Unicode Consortium, not the character encoding, that the consortium is responsible for.

https://en.wikipedia.org/wiki/Unicode_Consortium