Should a library explicitly target .NET Core 3?

With the release of .NET Standard 2.0, it's advised to target .NET Standard 2.0, even if you target 1.x already.

https://learn.microsoft.com/en-us/dotnet/standard/net-standard:

However, targeting lower .NET Standard versions introduces a number of support dependencies. If your project targets .NET Standard 1.x, we recommend that you also target .NET Standard 2.0. This simplifies the dependency graph for users of your library that run on .NET Standard 2.0 compatible frameworks, and it reduces the number of packages they need to download.

Now another big change is near! .NET Core 3 and I see that Microsoft also is targeting .NET Core 3 for Microsoft packages.

For example, Microsoft.Extensions.Logging is targeting .NET Standard 2.0 and also .NET Core 3 (.NETCoreApp 3.0):

I compared the XML files and both APIs look the same (maybe not the best way to compared them)

Now the question ;)

As a library maintainer that depends on Microsoft.Extensions.Logging, who trying to support .NET Core 3:Should I also target .NET Core 3 - or is just .NET Standard 2.0 good enough if I don't need specific stuff of .NET Core 3?