Christian Neumüller

That function is made available to the code generator template here: https://github.com/open-telemetry/build-tools/blob/main/semantic-conventions/src/opentelemetry/semconv/templating/code.py#L204 So you should be able to do `{{attr.brief | render_markdown()}}` in the Jinja template.

Yeah, the docs are lacking 😔

Have you tried just running it over everything, i.e. `-v ${SCRIPT_DIR}/opentelemetry-specification/semantic_conventions` without `/trace`? If you only want span conventions, I think you can use the `--only span` cmdline option (https://github.com/open-telemetry/build-tools/blob/main/semantic-conventions/src/opentelemetry/semconv/main.py#L211-L215)

Is this still a concern?

See also https://github.com/open-telemetry/build-tools/pull/79#discussion_r851360604: > These tests are not designed as integration tests, they are targeted feature tests and it makes no sense to drag in a full spec yaml. These...

The tool should also lint enum ids (and actually all ids), see #59

~~I'm working on this~~ Actually I'll only validate IDs for now (i.e. #59). We already have enums that do not conform to the current rule (namely http.flavor=1.0 or 2.0). So...

I think the other way round would be better: https://github.com/pypa/setuptools_scm

@open-telemetry/technical-committee I think you are still the only ones that have access to view the mentioned settings. Please check. @sakshi-1505 For Python we already use both mypy and pylint, and...

Are we really sure we need this? We have enough compatibility problems and under-documentation with what Jinja templates can access. If we expose this, even more changes will be breaking...