Create labels for semantic-conventions repository

[arminru]

In the spec, we currently distinguish between the following semconv-related aspects:

• spec:*: trace, metrics, logs, resource
• semconv:* area: HTTP, Database, Messaging
• project-management-related: priorities, triaging results, GA blockers for certain areas (done with project boards instead recently)

(see https://github.com/open-telemetry/opentelemetry-specification/labels)

Should we follow the same pattern here or come up with a new approach?

[reyang]

Here is what I suggest:

1. Do not have the artificial separation of trace/metrics/logs/resource - we want semantic conventions to be defined across all the telemetry signals (e.g. HTTP status could should apply to logs/metrics/traces.
2. Instead of using labels for areas (e.g. database), just use folder structure (combined with issue template).

[joaopgrassi]

Instead of using labels for areas (e.g. database), just use folder structure (combined with issue template).

Not sure if I'm missing something, but how would using folder structure replace using labels? Or did you mean use the same "folder structure" as labels? If we want to move away from semconv specific to signals, using "areas" sounds the best approach, no?

[joaopgrassi]

I think this is related to this and my suggestion is documented: https://github.com/open-telemetry/semantic-conventions/pull/292#issuecomment-1908486583. Essentially we could create labels for the areas we have in the registry.

[joaopgrassi]

Now that https://github.com/open-telemetry/semantic-conventions/pull/777 was merged, and we have labels for areas that match the files in model/registry should we close this?