In Europe this is not number 911. Europeans do not care what number is emergency call in America.
Also this is foolish to associate nine-eleven with emergency (by Apple design). Proper call for Siri are: call nine-one-one, call emergency, call police...
If the US used the international date format instead of their backwards MM/DD/YYYY system, there would be no problem, because if would be 11/9, not 9/11.
If the US used the international date format instead of their backwards MM/DD/YYYY system, there would be no problem, because if would be 11/9, not 9/11.
Except, the only standard International Date Format that makes any sense (and alleviates the entire confusion between the two commonly-used month-first and day-first date formats) is ISO-8601 — the "you're both wrong!" YYYY-MM-DD HH:MM:SS format.
It sorts properly without special parsing, it's completely unambiguous, it's your new best friend. (And it doesn't permit the use of slashes in the date component, to further differentiate itself from the Two Evil Formats™.)
Unfortunately, ISO-8601 (in the interests of precision/unambiguity) makes no allowances for yearless dates.
Which is why the HTML5 Specification, § 2.4.5.3 Yearless Dates, builds on the RFC3339 subset of ISO-8601 by defining a supported format for dates without years. Sensibly, they follow the most-significant-to-least-significant-component ordering of ISO-8601, meaning that the supported HTML5 Time-datetime format for a yearless date is "MM-DD". (Two digits are always required, so "9-11" is not actually a valid HTML5 date. It would have to be "09-11".)
Comments
In Europe this is not number 911. Europeans do not care what number is emergency call in America.
Also this is foolish to associate nine-eleven with emergency (by Apple design). Proper call for Siri are: call nine-one-one, call emergency, call police...
Do you see number "11" anywhere on keyboard?
Good thing this didn't happen in Europe. The EU would have heavily fined Apple and banned Siri.
It's 112 throughout Europe.
If the US used the international date format instead of their backwards MM/DD/YYYY system, there would be no problem, because if would be 11/9, not 9/11.
Except, the only standard International Date Format that makes any sense (and alleviates the entire confusion between the two commonly-used month-first and day-first date formats) is ISO-8601 — the "you're both wrong!" YYYY-MM-DD HH:MM:SS format.
It sorts properly without special parsing, it's completely unambiguous, it's your new best friend. (And it doesn't permit the use of slashes in the date component, to further differentiate itself from the Two Evil Formats™.)
Unfortunately, ISO-8601 (in the interests of precision/unambiguity) makes no allowances for yearless dates.
Which is why the HTML5 Specification, § 2.4.5.3 Yearless Dates, builds on the RFC3339 subset of ISO-8601 by defining a supported format for dates without years. Sensibly, they follow the most-significant-to-least-significant-component ordering of ISO-8601, meaning that the supported HTML5 Time-datetime format for a yearless date is "MM-DD". (Two digits are always required, so "9-11" is not actually a valid HTML5 date. It would have to be "09-11".)
Sorry!