The original .NET variations up until 4.8 are called Framework, built into Windows with quite a bit of Windows-dependencies and probably conversely also a bunch of Windows components that depend on it.
The modern core lineage (Core 1 to 3.1 and all "unified" .NET releases after 5) are named so since the "core" parts are platform independent running equally well on f.ex. Linux as Windows for webservers and similar. Desktop API's are moved to packages/SDK's to avoid creeping platform dependant code into the core.
Standard is an even more limited subset meant for developers who want to make libraries for both core and framework.
Now about Mono Framework, Mono was initially built to emulate old .NET Framework (hence Mono Framework) and due to it being intertwined with Windows it makes sense (and feels surprisingly progressive by MS) for Wine to steward these parts.
More modern unified/core .NET versions are meant to be distributed with applications and not bloat up Windows proper(and thus no need for Wine to support in addition to regular Windows API's).
Why Mono was taken into MS initially was to bring in their Xamarin branded crossplatform support for iOS and Android applications.