BREAKING: Define url.scheme in terms of logical operation in HTTP server semconv

[trask]

Resolves open-telemetry/opentelemetry-specification#3442

Changes

Define url.scheme in terms of logical operation in HTTP server semconv.

There are two reasons I think this is a good change.

Reason 1

I believe one of the motivations for these attributes on the server side is to reconstruct the original URL:

• server.address
• server.port
• url.path
• url.query
• url.scheme

(e.g. server.address and server.port are captured from the Host header)

Reason 2

We should have a place to capture the scheme used by the immediate peer soon, under something like tls.protocol.name (#21).

Merge requirement checklist

• CONTRIBUTING.md guidelines followed.
• CHANGELOG.md updated for non-trivial changes.
• schema-next.yaml updated with changes to existing conventions.

[Oberon00]

I think we should add a paragraph to the HTTP spec on how to reconstruct the URL (basically just the list you have added in the PR description), this would also be useful for instrumentation writers to clarify how to fill in the components.