Clarify how log appender use Scope name and attributes

[tigrannajaryan]

Resolves #3562

Resolves #2358

I moved the recommendations for appenders to a separate file named supplementary-guidelines.md. Similar to other signals this file will contain non-normative recommendations.

[tigrannajaryan]

I think this also resolves #2358

[Oberon00]

supplementary-guidelines is a separate top-level directory at the moment. I'd suggest to keep the location of supplementary guidelines consistent (though personally I prefer the way of this PR).

[tigrannajaryan]

supplementary-guidelines is a separate top-level directory at the moment. I'd suggest to keep the location of supplementary guidelines consistent (though personally I prefer the way of this PR).

We have the exact same approach for metrics, with supplementary-guidelines.md file a sibling of the api file: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/supplementary-guidelines.md

The directly you refer to is for "other" stuff that does not fit in the signals' directories.

[carlosalberto]

Let's discuss the supplementary guidelines location in #3587 instead (not a blocker for this PR).

[github-actions]

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

[tigrannajaryan]

@open-telemetry/specs-logs-approvers please review.

[jack-berg]

Just a small text change, but this is more appropriate as a supplementary guideline 👍

[github-actions]

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

[arminru]

@tigrannajaryan fyi https://status.lfx.dev/incidents/ssyv13fbdprf

[tigrannajaryan]

/easycla