Robert Pająk

I have update the PR so that the it contains only clarification changes.

PTAL @open-telemetry/specs-logs-approvers

> I am supportive of this clarification. @tigrannajaryan PTAL. I did my best to address my concerns with minimal changes.

Side note: Actually some logging libraries allow duplicate keys (https://go.dev/play/p/fzIswL0Le7j). OTLP (and JSON) allows also passing such data. EDIT: I will create a separate issue (or PR for it).

> > Side note: Actually some logging libraries allow duplicate keys > > Still good to merge this PR, given this detail, for the March's release? @carlosalberto It is good...

> @pellared Oops, lint is failing. The failure is not caused by the changes from this PR.

Changing to draft per https://github.com/open-telemetry/opentelemetry-specification/pull/3938. Especially given this PR contains normative language.

> Backporting the CVE fix to older releases is needed to maintain security while continuing to use specified otel semconv implementations. What version(s) do you have in mind? Cannot you...

Now, I see that the specification currently only requires implementing parsing of YAML: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/configuration/file-configuration.md#parse @codeboten should we change to draft (or even close) this PR? WDYT?

`otelmongo` has currently no codeowners Also see https://github.com/open-telemetry/opentelemetry-go-contrib/issues/4678