And readers could choose the specific standard version, just like the old MSDN library does, switching between different .Net Framework versions. I guess cross-platform class library developers are tend to target "netstandard1.x", but the only API references availabe now is the .Net Core API docs. This might bring confusion and inconvenience.
I think it would be best to create an API reference using the API versions for the specific packages using the map here.
The .NET Standard version could then be mapped to that package's API version
(i.e. instead of using only netstandard1.3, use (package name)+(API version of package) and map that to netstandard1.x)
API reference already exists: https://docs.microsoft.com/en-us/dotnet/core/api/index.
It does not currently support different framework versions, but that support is planned: https://github.com/dotnet/core-docs/issues/772.
I think this issue should be closed and any discussion should move there.
Closing per above recommendation -- https://github.com/dotnet/core-docs/issues/772 tracks the issue.
Most helpful comment
API reference already exists: https://docs.microsoft.com/en-us/dotnet/core/api/index.
It does not currently support different framework versions, but that support is planned: https://github.com/dotnet/core-docs/issues/772.
I think this issue should be closed and any discussion should move there.