HTTP attributes are noncomformant

[Oberon00]

Please compare

opentelemetry-js/packages/opentelemetry-plugin-http/src/enums/AttributeNames.ts

Lines 21 to 24 in af5a364

	HTTP_HOSTNAME = 'http.hostname',
	COMPONENT = 'component',
	HTTP_METHOD = 'http.method',
	HTTP_PATH = 'http.path',

with https://github.com/open-telemetry/opentelemetry-specification/blob/8f4377c15e44e1d9348edec7cabea2a7107a6877/specification/data-http.md. There is no http.hostname (there are net.host.name and http.host and http.server_name though), and there is no http.path (there is http.target though which may or may not be what http.path was meant for).

[OlivierAlbertini]

I'm closing this issue since it's a duplicated of #373. Feel free to discuss on this one or reopen if you are not agreed

[Oberon00]

Well it's not exactly a duplicate because IIRC http.path and http.hostname did never exist in the semantic conventions for OpenTelemetry.

[OlivierAlbertini]

Well it's not exactly a duplicate because IIRC http.path and http.hostname did never exist in the semantic conventions for OpenTelemetry.

Yes. OpenTelemetry didn't provide a spec when we start to write http plugin (OpenCensus spec was used) and when they did they didn't provide something about host or target.

https://github.com/open-telemetry/opentelemetry-specification/blob/600149f531ad62efb3a3dc96007781c3604ebdec/specification/data-semantic-conventions.md

Also I think that we are not the only one who did that
e.g https://github.com/open-telemetry/opentelemetry-go/blob/b863b8f6ab9eff876b15ef36e1192e1ddfd0f91d/plugin/othttp/handler.go#L33

open-telemetry/opentelemetry-dotnet@faa2b38#diff-27ba31dbe3c643485ab4e902909cd984R26

...

Btw, it's not a big deal and we will sync to new spec version.
Thanks @Oberon00 for the heads up and noticing this.