Docs: ECMA C# and CLI Standards page is out of date

[KexyBiscuit]

Issue description

ECMA C# and CLI Standards page is out of date.

[BillWagner]

Thanks for noting that @KexyBiscuit

@gewarren Do you know who owns the page linked above? I can get them the updated links for the C# ECMA standard.

[gewarren]

@vicushin can you help route this to right person? The page that's out of date is https://visualstudio.microsoft.com/license-terms/ecma-c-common-language-infrastructure-standards/.

[victoriagrows-xx]

Send this to @VSCOM Site [e-mail].

---

From: Genevieve Warren [e-mail]
Sent: Friday, February 15, 2019 3:13:52 AM
To: dotnet/docs
Cc: Victoria Cushing; Mention
Subject: Re: [dotnet/docs] ECMA C# and CLI Standards page is out of date (#10469)

@vicushinhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fvicushin&data=02%7C01%7CVictoria.Cushing%40microsoft.com%7C2764cecc5a864a10b0a908d692b8f048%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636857720341249802&sdata=Mm9KkaEkat7QkVKwS5iPevcQAn1sUamIA7Ey34LJCaQ%3D&reserved=0 can you help route this to right person? The page that's out of date is https://visualstudio.microsoft.com/license-terms/ecma-c-common-language-infrastructure-standards/https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fvisualstudio.microsoft.com%2Flicense-terms%2Fecma-c-common-language-infrastructure-standards%2F&data=02%7C01%7CVictoria.Cushing%40microsoft.com%7C2764cecc5a864a10b0a908d692b8f048%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636857720341259806&sdata=ANe4HkyprKiQs%2FGjMsx9WZXwLwnn6%2BoufZKVGEC7S6U%3D&reserved=0.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fdocs%2Fissues%2F10469%23issuecomment-463776426&data=02%7C01%7CVictoria.Cushing%40microsoft.com%7C2764cecc5a864a10b0a908d692b8f048%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636857720341259806&sdata=9OxH4svh9RbUeYVSB2MaiGgv%2ByOzDrjXxMWjkq3Cg0I%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAg3Ea9A_3MKmAcLd21LidBb8HP9eBQjxks5vNcOAgaJpZM4a7YzH&data=02%7C01%7CVictoria.Cushing%40microsoft.com%7C2764cecc5a864a10b0a908d692b8f048%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636857720341269814&sdata=mgT25xZ31kQTW8Lc0gsu%2FbjlOyCm%2BGzwCOLUI3%2Fe5Ws%3D&reserved=0.

[mairaw]

Have this been sent? Otherwise, I can. /cc @CarolEidt

[BillWagner]

@mairaw Not to my knowledge.

The C# 5.0 ECMA spec is available on the ECMA site

[KexyBiscuit]

And ISO/IEC 23270:2018 is published.

Well, ECMA site is a little bit out of date either.

[BillWagner]

@KexyBiscuit ISO voted to approve the ECMA 5.0 standard. Those two documents match.

[mairaw]

Is this still an issue?

[BillWagner]

Yes, most of the links 404 from the page referenced in the original issue. they should be updated to the correct downloads from this ECMA hosted page

[victoriagrows-xx]

Hi all,

I (and the VSCOM team) are not on point for licensing pages. Please check with @Paul [e-mail].

Thanks,
Victoria

---

From: Bill Wagner [e-mail]
Sent: Monday, April 29, 2019 2:45 PM
To: dotnet/docs
Cc: Victoria Cushing; Mention
Subject: Re: [dotnet/docs] ECMA C# and CLI Standards page is out of date (#10469)

Yes, most of the links 404 from the page referenced in the original issue. they should be updated to the correct downloads from this ECMA hosted pagehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ecma-international.org%2Fpublications%2Fstandards%2FStnindex.htm&data=01%7C01%7CVictoria.Cushing%40microsoft.com%7C40dbd6c9413a4791a4f208d6ccebfabf%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=m1FhY%2FD1IjFAEWB%2FGWNHR1AP36QsUKL7RWy2r8AnbyE%3D&reserved=0

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fdocs%2Fissues%2F10469%23issuecomment-487755403&data=01%7C01%7CVictoria.Cushing%40microsoft.com%7C40dbd6c9413a4791a4f208d6ccebfabf%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=mhyDcYAx6t3rr7A0ziJIMvbX6vgkRWZj1%2F0McP9oVbg%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIG4I25VVMLBNCP6AABVOYDPS5T7BANCNFSM4GXNRTDQ&data=01%7C01%7CVictoria.Cushing%40microsoft.com%7C40dbd6c9413a4791a4f208d6ccebfabf%7C72f988bf86f141af91ab2d7cd011db47%7C1&sdata=6WObfnv8REVmwrMEG71dPBgLE9ZrjTmeq48i7oEkwn0%3D&reserved=0.

[mairaw]

I started an internal thread on this. Let's see if we can get this fixed!

[mairaw]

I added Paul to the thread. Let's see if we can get this fixed!

[paul]

Wrong @paul, though :stuck_out_tongue:

[BillWagner]

This has been fixed. The links are correct now.

[KexyBiscuit]

The file in Microsoft Implementation Specific Version paragraph requires Corporate account, is that expected?

[mairaw]

I don't think so @KexyBiscuit. I'm following up with the team.

[CarolEidt]

The file should be accessible to all - I presume it just needs to be relocated to a public location.