News for hackers. Stuff that matters.
Re:RFC 3339 vs. ISO 8601 by em500 on Sunday October 24, 2021 @07:08AM (#28976779)
This is very neat, but maybe not completely accurate. "2021-10-24 11:02:03Z" is outside iso8601 in the figure, but I think it's valid iso8601. True, "T" is the One True date-time separator in iso8601 (IMO its biggest wart, as it looks awful for human eyes: "2021-10-24T11:02:03Z"). But according to the draft standard[1], page 21:

> By mutual agreement of the partners in information interchange, the character [T] may be omitted in applications where there is no risk of confusing a date and time of day representation with others defined in this International Standard

[1] The actual ISO standard is not freely available, but the Library of Congress has free draft standards: https://www.loc.gov/standards/datetime/iso-tc154-wg5_n0038_i... https://www.loc.gov/standards/datetime/iso-tc154-wg5_n0039_i...

Re:RFC 3339 vs. ISO 8601 by Arcorann on Sunday October 24, 2021 @07:46AM (#28977036)
There are some non-trivial changes between the draft standards and the final ISO 8601:2019-1 standard, one of which relates to making the use of T stricter, and the mentioned provision was removed.

Regardless, ISO 8601 has generally discouraged using spaces within expressions. From ISO 8601:2004, section 3.4.1:

> Unless explicitly allowed by this International Standard the character "space" shall not be used in the representations.

Similarly, from ISO 8601:2019-1, section 3.2.1:

> The character "space" shall not be used in the expressions.

However, through looser interpretation of the standard, "2021-10-24 11:02:03Z" could be allowed if treated as a date representation followed by a space followed by a time representation (note that the formal time representation in ISO 8601:2019-1 is T11:02:03Z, but it allows omission of T for extended format as per 5.3.5).

Re:RFC 3339 vs. ISO 8601 by letmeinhere on Sunday October 24, 2021 @09:15AM (#28977609)
ISO business model is so strange; in order to make money they have to hide the actual standard from the vast majority of engineers that it relates to, so we just assume whatever was proposed was close enough.
Re:RFC 3339 vs. ISO 8601 by marcosdumay on Sunday October 24, 2021 @11:00AM (#28978528)
Yes, on practice the draft becomes the actual standard.

That is, unless it's in a regulated industry that is required by law to follow the actual standard. Then it disobeys the law most of the time, and "disobey" the market the rest of the time and everything breaks. Also, it leaves the people with a secret law that nobody can know the consequences.

The ISO governance should be changed ASAP. It was never good, and nowadays it's a disaster.

Re:RFC 3339 vs. ISO 8601 by skissane on Sunday October 24, 2021 @03:38PM (#28981185)
> The ISO governance should be changed ASAP. It was never good, and nowadays it's a disaster.

ISO was founded in 1947, and back then very many of its standards were about physical objects – pipe threads, screws, bearings, belts, film, steel, plastic, rubber, textiles, etc – and even today they still have many standards on those kinds of topics. Imagine you are an aerospace engineer in the 1970s, and you need a copy of the new standard ISO 46:1973 (Aircraft — Fuel nozzle grounding plugs and sockets) – if nobody at your work has a copy, you just order it and pay for it with the company's money (expense it, get your boss to sign the purchase order, whatever). Nobody would have a problem with that and you wouldn't think there was anything inappropriate about it either, it would just seem totally normal to anybody in the 1970s.

The problem is that technology and culture have changed and ISO hasn't kept up – especially for software-related standards. We are an industry in which there are lots of independent contractors and self-employed people and small businesses, it is easy to be self-taught, in which multi-billion dollar companies will charge millions for software packages and then include in their code some open source library that someone maintains as an unpaid hobby, in which many employers baulk at paying for things which in prior decades employers would have just paid for without question. The culture has changed from one in which people are used to paying money for physical books in person or via mail order, to one in which they expect to get information from the Internet instantaneously and for free.

And it is probably mostly in software that people complain about this. I could be wrong, but I would guess that for aerospace engineers it is no more an issue today than in the 1970s. Even if ISO were to charge a few hundred dollars for a standards document, it would still be a lot cheaper than most things aerospace engineers deal with, and your employer will pay for it, who cares. At big firms such as Airbus or Boeing, they probably have some kind of subscription so their engineers just get access to all new ISO standards automatically.

Re:RFC 3339 vs. ISO 8601 by marcosdumay on Sunday October 24, 2021 @09:27PM (#28983597)
Mandated ISO standards in 1947 was absurd secret law too. Democracy is not that new of a concept.

It's just that both regulations were much lighter so much fewer people would be affected, and at that time the world was in an extremely totalitarian mood, divided by two countries that imposed dictatorships wherever they went. But entrepreneurship existed by then just like it does now, and you can bet many people went poorer because they couldn't access the standards.

Also, they were much less accessible. If you couldn't just go to a library to read them because they weren't free, it meant most people could not get them at all. It was not just a matter of getting in a phone and calling the ISO customer center.

Re:RFC 3339 vs. ISO 8601 by skissane on Sunday October 24, 2021 @11:08PM (#28984136)
> Mandated ISO standards in 1947 was absurd secret law too. Democracy is not that new of a concept.

In the 1940s, if you wanted to read legislation, there was no downloading it for free off the Internet – either you purchased a printed copy, or found a library that held it – and you may have had to travel some distance to do so, there was no guarantee that your neighbourhood public library did. Most people viewed charging for printed copies of legislation as acceptable, given that it cost money to print them. So, in that sense, legally mandated ISO standards weren't fundamentally different from laws in general. Prior to the 1990s, when the Internet began to change people's expectations, the idea that everyone was entitled to a free personal copy of all legislation was not widely accepted, and few would have labelled that situation as anti-democratic or as "absurd secret law".

> It was not just a matter of getting in a phone and calling the ISO customer center.

In the 1940s, rather than calling the ISO secretariat in Switzerland directly, you would have called your national standards body, who acted as a reseller. Buying standards then was only harder than today in the sense that buying anything back then was harder than today.

Re:RFC 3339 vs. ISO 8601 by dataflow on Monday October 25, 2021 @05:24AM (#28985917)
> the idea that everyone was entitled to a free personal copy of all legislation was not widely accepted

Was the idea that everyone is entitled to a copy of all legislation at cost widely accepted? Or did most people believe the the publisher (or the legislature?) should overcharge them and stand to make a profit off it?

I don't know how much "at cost" would be for ISO, but something tells me it wouldn't be an identical 158 CHF for both PDF and paper.

Re:RFC 3339 vs. ISO 8601 by marcosdumay on Monday October 25, 2021 @09:28AM (#28987529)
Neither. Access to legislation must be possible at no cost for everybody. Otherwise you can't expect people to follow it.

Of course, that doesn't entitle you to a copy, making it available at libraries is already enough.

Re:RFC 3339 vs. ISO 8601 by skissane on Monday October 25, 2021 @06:27PM (#28993964)
> Neither. Access to legislation must be possible at no cost for everybody. Otherwise you can't expect people to follow it.

In the real world, most people follow legislation without ever reading it. People build a rough mental model, based on media sources, government websites, common sense, etc, which divides acts into "probably illegal", "probably legal", and "grey area". If they stick to the "probably legal", they are unlikely to have any legal problems. If they are seriously considering venturing into the "probably illegal" or "grey area" zones, a wise person hires a lawyer and gets some professional legal advice first. The majority of the population has no hope of ever understanding legislation – something people on this website tend to forget, because most people on this website are significantly more intelligent and better educated than the average person is. And even those of us who aren't intimidated by legislation and case law and law textbooks, in the way that the average person is, ought to remember the old adage "A man who is his own lawyer has a fool for a client"–if you don't have the formal training and real-world experience of an actual lawyer, it is easy to make a costly mistake–e.g reading some law literally, and unfortunately you never found the case law which interprets it to mean something quite different from what it literally says. Keep the amateur lawyering as a hobby, maybe some real world situations where the cost of being wrong is low (such as challenging a parking ticket), and rely on a professional for anything actually important.

> Of course, that doesn't entitle you to a copy, making it available at libraries is already enough.

Well, ISO standards are freely available at some libraries. Generally national libraries, major public research libraries, university libraries (some of which are open to general public, others restrict admission to staff/students/etc.) Your local public library probably doesn't have any copies of ISO standards–mine doesn't. But, my local public library doesn't seem to have copies of legislation and case law either – my local public library has very little in the way of serious/professional/academic legal texts, just some very introductory stuff aimed at the general reader.

Re:RFC 3339 vs. ISO 8601 by skissane on Monday October 25, 2021 @05:56PM (#28993639)
I honestly don't think the average person thought much about the cost of buying legislation. Even today, I think the average person feels intimidated by legislation and doesn't want to read it even if it is all freely available.

As far as the official version of federal/national legislation goes – in 1947, in both the US and the UK, that was sold by a government agency overall at cost or even at a loss. ("Overall at cost" meaning, they might sometimes have made a profit on an individual print run, but profits they made on some print runs were balanced by losses on others, so they didn't make a profit overall.)

However, most lawyers preferred to use private editions published by for-profit publishers, which added copyrighted notes providing cross-references to other relevant legislation, important court decisions, etc. So the "raw" version of the legislation was available at-cost but the version most lawyers actually used was not. And that remains true today – most lawyers don't rely on the freely available versions on the web, they use expensive commercial subscription services (Westlaw, LexisNexis, etc) which add lots of very useful privately copyrighted notes–and you really need the information in those notes to properly interpret the law, because if you don't have cross-references to other legislation and case law, you won't know what it really means in practice–and although you could probably reconstruct those notes yourself to some extent (such as by searching free case law databases for references to a certain section of legislation), doing so is laborious and likely to be error-prone (it is easy to miss something important because you didn't use the exactly right search term, etc). So even now, access to the law is not as "free" as many think it is.

> I don't know how much "at cost" would be for ISO, but something tells me it wouldn't be an identical 158 CHF for both PDF and paper.

I think from ISO's viewpoint, it is "at cost", because they are not just including the cost of printing or hosting the download, but also the administrative and editorial costs of producing the underlying standard. ISO is a not-for-profit body and any profit it makes is reinvested into the standard development process. By contrast, when you buy a copy of an Act/Statute from the government print office, you are not paying for the actual running costs of the Congress/Parliament/etc which produced the legislation – that is paid for through taxation – whereas ISO being a private body can't levy taxes.

That's not to say that ISO has to use their current model. They could make all their standards freely available and try to recover the editorial/administrative costs through some other mechanism – charging membership fees to corporations, government grants, etc. However, while those methods are feasible – other standard bodies use them – I think ISO would respond that they would make ISO more dependent upon and more beholden to corporate and government interests than they currently are. I suppose the critical response to that is that ISO already is quite beholden to corporate and government interests, and it is hard to see how it could get any more beholden, but ISO would not agree with that.

Re:RFC 3339 vs. ISO 8601 by zinekeller on Monday October 25, 2021 @01:51AM (#28984818)
Very good summary. While it is true that ISO is stuck in time, at the same time its model weren't out-of-place when it was implemented, similar to how copyright laws now seems weird or plain wrong to many here while a century back (outside US, because theirs was weirder) it was widely accepted to compensate corporations who have took their time to record and stamp those phonographs.
Re:RFC 3339 vs. ISO 8601 by ademarre on Sunday October 24, 2021 @04:13PM (#28981446)
> software-related standards. We are an industry in which there are lots of independent contractors and self-employed people and small businesses, it is easy to be self-taught

Consider also the pace of innovation in software and networking—the internet at large. I think it's both a consequence and a cause of the change in culture you described.

Re:RFC 3339 vs. ISO 8601 by eli on Sunday October 24, 2021 @09:14PM (#28983533)
It should not be legal to incorporate proprietary standards into law.
Re:RFC 3339 vs. ISO 8601 by saghm on Monday October 25, 2021 @12:39AM (#28984541)
At least in the US, it's fairly hard to outlaw changing laws in certain ways since the people with the power to pass new laws are equally able to change past ones, including the ones that limit their power. The way to do something like this would be to put it in the Constitution, which isn't able to be changed through legislation alone, but it seems that for the time being, adding new amendments isn't really something we're doing as a country.
Re:RFC 3339 vs. ISO 8601 by eli on Monday October 25, 2021 @09:24AM (#28987487)
To be clear: I'm not requesting any new rights, merely the enforcement of existing legal principles that laws cannot be copyrighted by a private entity and that people have a fundamental right to freely read the laws that bind them.

Carl Malamud has been fighting this point worldwide with some success for decades. For example here's the state or Oregon agreeing: https://public.resource.org/oregon.gov/index.html

Re:RFC 3339 vs. ISO 8601 by dv_dt on Sunday October 24, 2021 @01:00PM (#28979742)
Yup, I wonder if an issuing group pays a fee on new versions as well as a maintenance fee would work out.
Re:RFC 3339 vs. ISO 8601 by ademarre on Sunday October 24, 2021 @03:36PM (#28981179)
There are very many things I never would have discovered and learned if IETF RFCs were not free. The most useful knowledge I've acquired about building things on the internet came from there.

Industries that are more reliant on ISO or other non-free standards are surely worse off because of it.

Re:RFC 3339 vs. ISO 8601 by concordDance on Sunday October 24, 2021 @10:34AM (#28978280)
> There are some non-trivial changes between the draft standards and the final ISO 8601:2019-1 standard, one of which relates to making the use of T stricter, and the mentioned provision was removed

Yes, and? The draft standard is the pretty much everyone actually uses. For most purposes it's the "real" one.

Re:RFC 3339 vs. ISO 8601 by mlyle on Sunday October 24, 2021 @12:47PM (#28979599)
Robustness principle. There's no way you should be relying upon a draft to emit things that violate the real standard.
Re:RFC 3339 vs. ISO 8601 by convolvatron on Sunday October 24, 2021 @05:13PM (#28981988)
there is never any final difference...since you work in a group, and every change is vetted, it only gets ratified when everyone says 'yep, no more changes'
Re:RFC 3339 vs. ISO 8601 by euroderf on Monday October 25, 2021 @01:39PM (#28990745)
Couldn't they permit "_" in place of "T" ? It's not a space, and it certainly makes a date_time string quicker to parse at a glance.
Re:RFC 3339 vs. ISO 8601 by colejohnson66 on Sunday October 24, 2021 @10:00AM (#28977955)
Tangent: what’s the point of these “international standards” when I have to pay to know the standard I’m following? Sure, I can use final drafts, but I shouldn’t have to.

It honestly seems like a racket. Businesses collaborate to write a standard that costs hundreds of dollars, and then brand new small businesses can’t afford to assert that they follow them.

Re:RFC 3339 vs. ISO 8601 by ethbr0 on Sunday October 24, 2021 @10:41AM (#28978344)
If they just sold test validators and certification services instead ("Certified by ISO"), it'd be such a healthier dynamic.
Re:RFC 3339 vs. ISO 8601 by marcosdumay on Sunday October 24, 2021 @11:02AM (#28978541)
ISO shouldn't sell anything. It doesn't have a profit motive and can be financed by governments without any problem.
Re:RFC 3339 vs. ISO 8601 by kbenson on Sunday October 24, 2021 @02:49PM (#28980803)
Can and will are two separate things, and even if it happens then you get countries trying to influence decisions with the threat of stopping funding.

That's not to say it wouldn't be better, just that it's not without its own problems.

Re:RFC 3339 vs. ISO 8601 by bluGill on Sunday October 24, 2021 @01:05PM (#28979793)
There is a cost to make a standard. Somehow that needs to be paid.

Though iso isn't really spending its own money from what I can tell, so I don't see where their costs are coming from.

Re:RFC 3339 vs. ISO 8601 by dwheeler on Sunday October 24, 2021 @02:08PM (#28980439)
ISO doesn't pay to develop standards, they assume others will develop the standards.

Historically, the purpose was to pay for printing & distribution. That makes no sense today, but that was its historical justification.

Re:RFC 3339 vs. ISO 8601 by colejohnson66 on Sunday October 24, 2021 @01:12PM (#28979885)
That’s what I’m getting at. The committees are generally funded by big companies who basically sign the rights over to ISO. ISO then charges you hundreds of dollars for a single PDF of a standard (which may contain over a dozen).

It reminds me of scientific journals that do nothing but charge money for other people’s work. It reeks of rent seeking.

Re:RFC 3339 vs. ISO 8601 by tgsovlerkhgsel on Sunday October 24, 2021 @05:57PM (#28982305)
That seems like a great use for taxes. I suspect the economic benefits from the easy accessibility of the standards (just imagine the cost of the approval processes to buy the standards and handle access, plus the cost of the standards remaining inaccessible to smaller players) would outweigh the financial costs.
Re:RFC 3339 vs. ISO 8601 by superjan on Sunday October 24, 2021 @10:55AM (#28978483)
It is great when standards become free, but then we need to agree how else to fund the standardization process. Taxpayer money?
Re:RFC 3339 vs. ISO 8601 by kps on Sunday October 24, 2021 @11:19AM (#28978697)
For the ‘ISO’ standards where I'm aware of the process, development was funded by the participants. ISO is just a rent-seeking gatekeeper, like academic publishers.
Re:RFC 3339 vs. ISO 8601 by dv_dt on Sunday October 24, 2021 @01:07PM (#28979822)
As I have encountered it, the vast cost of the standardization process is already borne outside of ISO because creation and update of the standards is done by outside participants. Hosting the standards documents is a minuscule cost and fees seems mostly a holdover when potentially large bound physical document publishing and distribution was involved.
Re:RFC 3339 vs. ISO 8601 by superjan on Sunday October 24, 2021 @02:06PM (#28980425)
I know they don’t subsidize standard development. But there is still cost for running an organization to manage and coordinate (and maybe translate) what is being standardized over hundreds of topics. Of the 40 million in total income, selling standard documents is 1/4 to 1/3 of their income. You don’t pay for the cost of electronic copies, but for running the organization.

source: https://www.iso.org/files/live/sites/isoorg/files/store/en/P...

Re:RFC 3339 vs. ISO 8601 by dv_dt on Wednesday October 27, 2021 @11:13AM (#29014385)
That’s a tiny amount. The major nations should each pull a budget line item and support it directly and remove costs of accessing the iso standards. That could go under NIST in the US. (Maybe start a service charging for for cryptographically signed standards doc).
Re:RFC 3339 vs. ISO 8601 by jrochkind1 on Sunday October 24, 2021 @07:29PM (#28982896)
Where's the money going? ISO staff? Who do what?
Re:RFC 3339 vs. ISO 8601 by bmn__ on Monday October 25, 2021 @01:05AM (#28984628)
ISO holds meetings where member delegates improve the drafts and negotiate the standards to be.
Re:RFC 3339 vs. ISO 8601 by jrochkind1 on Monday October 25, 2021 @08:02AM (#28986826)
Are some people arguing that doesn't need to happen, or can be done cheaper? Is that argument based on detailed attention to the budget?
Re:RFC 3339 vs. ISO 8601 by everybodyknows on Sunday October 24, 2021 @01:32PM (#28980118)
There's a parallel dysfunction in California, where the legally-enforced version of the electrical code is available on paper only, at a price of $224:

https://catalog.nfpa.org/NFPA-70-National-Electrical-Code-wi...

In democracies it seems taxpayer money can only be had for purposes that please some fraction of the legislators.

Re:RFC 3339 vs. ISO 8601 by watersb on Monday October 25, 2021 @01:32AM (#28984735)
yes. excellent example of a situation almost identical to mandating ISO standards.

Should the Library of Congress nationalize the NPFA?

I got my local library to buy a copy of the National Electrical Code. I can study it... but only at the Reference Desk at the library.

There are some derived texts that are pretty good, that the library will let me have, so long as I renew the checkout, and nobody else wants it.

Hmm.

Re:RFC 3339 vs. ISO 8601 by cmclaren on Sunday October 24, 2021 @08:04AM (#28977136)
Your example is valid in ISO 8601-1:2019.

There are only two possible representations for which "T" is required: hh or hhmm in 'basic' format (i.e. no ":" separator). The former could be confused with a two-digit century, the latter could be confused with a four-digit year. Adding "T" to hh or hhmm solves this.

Any of the following eliminates the "risk of confusion":

  - 'extended' format (hh:mm)
  - decimal fraction (hhmm,m or hh,h; see 5.3.1.4);
  - UTC designator (hhmmZ or hhZ; see 5.3.3), or;
  - time shift (hhmm±hhmm, hhmm±hh, hh±hhmm, or hh±hh; see 5.3.4).
Also worth noting: hhmmss in 'basic' format (i.e. no ":" separator) does not pose a risk of confusion, as YYYYMM in 'basic' format (i.e. no "-" separator) is not permitted by the spec.
Re:RFC 3339 vs. ISO 8601 by rdpintqogeogsaa on Sunday October 24, 2021 @07:38AM (#28976982)
It's correct. Omission means 2021-10-2411:02:03Z, not replacing it with a space instead.
Re:RFC 3339 vs. ISO 8601 by grey_earthling on Sunday October 24, 2021 @07:51AM (#28977067)
Omitting the hyphens and colons is allowed too (IIRC), so I suppose omitting the T is intended for cases like 20211024110203Z — which IMO is a sensible format when there's no ambiguity that this is a date-time.
Re:RFC 3339 vs. ISO 8601 by jfrunyon on Sunday October 24, 2021 @12:46PM (#28979582)
That's a sensible format only for interchange - humans need separators to read it...
Re:RFC 3339 vs. ISO 8601 by kbenson on Sunday October 24, 2021 @02:55PM (#28980854)
They don't need it. It makes it easier, but if you know it's a date and time format, it's pretty easy to read as long as you take care to keep track at which characters your looking at.

Justlikehowinmostcasesepacesmakeiteasiertoreadsomethingbutaren'trequired.

Re:RFC 3339 vs. ISO 8601 by jfrunyon on Thursday October 28, 2021 @06:54PM (#29033088)
Okay. Go try quickly scanning a table or spreadsheet with 1000 rows of that. Good luck.
Re:RFC 3339 vs. ISO 8601 by GoblinSlayer on Monday October 25, 2021 @07:31AM (#28986607)
RFC 3339 is concerned with interoperability problems due to date formats. By adding a space you create interoperability problems. And space-based format uses ' UTC' suffix instead of Z suffix.
Re:RFC 3339 vs. ISO 8601 by LinAGKar on Sunday October 24, 2021 @07:39AM (#28976988)
So that should also be in the dashed circle.