Explain the choice to have the semantic conventions library depend on the API

[tailg8nj]

I'd like to understand the choice to make the semantic conventions library depend on the API library.

This was introduced in #3586

My understanding is this repository leverages the yaml semantic conventions defined by the community to generate Python files, and prior to that PR, generally just constants.

From what I see, scripts/semconv/templates/semantic_metrics.j2 was modified to include helper functions to actually create different Instruments. Shouldn't this be an API concern?

I've checked the Golang and JS repos and those jinja templates do not generate API level invocations.

See also: open-telemetry/semantic-conventions#551