Can .NET support "No explicit parent Span/SpanContext allowed" spec item?

[Oberon00]

The tracing API specification was changed on September 23 to only allow a full Context as explicit parent, and a SpanContext alone or Span alone is no longer allowed. Spec references:

• Consider using Context as the unique way to specify parenthood opentelemetry-specification#510 "Consider using Context as the unique way to specify parenthood"
• Spans's parent must be passed as Context instead of Span(Context)s. opentelemetry-specification#875 "Span's parent must be passed as Context instead of Span(Context)s."

(How) is .NET going to implement this change?

Relatedly, I see the spec compliance matrix has "unknown" listed in this row https://github.com/open-telemetry/opentelemetry-specification/blob/master/spec-compliance-matrix.md#traces "No explicit parent Span/SpanContext allowed".

[cijothomas]

Thanks for raising this.
Can't think of an easy fix here in Otel repo. We need to plan and propose something for the next .NET cycle, as this won't be a trivial change. Keeping this issue open.

[github-actions]

This issue was marked stale due to lack of activity and will be closed in 7 days. Commenting will instruct the bot to automatically remove the label. This bot runs once per day.

[cijothomas]

Un-stale. This issue is unresolved.
Due to the use of async-local everywhere to pass around implicit Context, I think no-one is actually hitting any issue, but its still better to keep issue as open given this is a spec requirement that .NET is not able to comply with.