Define case sensitivity of map<string, any> keys in Logs Data Model

[pellared]

Per #3853 (comment)

Changes

Add clarifications to map<string, any> taken from https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/common and make the description more normative.

The spec is stable, but I think that it is rather a clarification or/and straightforward standardization.

[tigrannajaryan]

This was previously an undefined behavior, the PR defines the behavior now and I think such changes should be allowed for Stable documents.

@open-telemetry/specs-approvers any objections to this approach to stability?

[trask]

The spec is stable, but I think that it is rather a clarification

👍

[tigrannajaryan]

Let's keep this open for a while to allow time to object in case someone thinks this is a breaking change.

[jack-berg]

I think this is fine clarification, but that this information is already implied. The common knowledge definition of a map doesn't support duplicate keys. The common knowledge definition of a string is case sensitive, unless specified otherwise.

🤷

[pellared]

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).

[carlosalberto]

Side note: Actually some logging libraries allow duplicate keys

Still good to merge this PR, given this detail, for the March's release?

[pellared]

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 to merge (even if we decide to remove it later).

EDIT: I created #3931

[carlosalberto]

@pellared Oops, lint is failing.

[pellared]

@pellared Oops, lint is failing.

The failure is not caused by the changes from this PR.

[andrzej-stencel]

I'm not sure if the wording here is right. "Case sensitivity MUST be preserved" logically means "if something is case sensitive, it should stay case sensitive; if something is case insensitive, it should stay case insensitive". Doesn't it? 🤔

Perhaps a better wording would be:

The keys in the map are case-sensitive and MUST be unique (duplicate keys are not allowed).

[pellared]

Changing to draft per #3938.
Especially given this PR contains normative language.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 7 days.