Obsolete normative reference to ECMA-402, ECMAScript 2015 Internationalization API Specification.

[allenwb]

Clause 3 of both the Ecma hosted 2022 edition and the TC39 hosted 2023 draft of ECMA-262 list the 2015 edition of ECMA-402 as a normative reference. Shouldn't that be updated to the current edition or have an "or later" added?

[syg]

@tc39/ecma402-editors The issue seems to be the 402 specification has the year number included as part of its name, which is why there's this reference to "2015" that @allenwb brought up. Is it possible to rename the 402 specification to drop the year number in the official name?

[ryzokuken]

judging from tc39/ecma402@1ec32f3, there's a bunch of places where the year is hardcoded...

[gibson042]

@syg Can you elaborate on what you mean by "rename the 402 specification to drop the year number in the official name"? Both ECMA-262 and ECMA-402 follow the same pattern AFAICT.

Draft: "ECMAScript® $year {Language,Internationalization API} Specification"

• https://tc39.es/ecma262/multipage/
• https://tc39.es/ecma402/

Published edition: Adds a prefix like "ECMA-$number, $nth edition, $month $year"

• https://262.ecma-international.org/13.0/
• https://402.ecma-international.org/9.0/

I'd be happy to remove the date from the part that is shared between draft and published edition, but only if we do so for both ECMA-262 and ECMA-402.