Website Glossary vs. Spec Glossary

[svrnm]

There are two glossaries now, one on the website (https://opentelemetry.io/docs/concepts/glossary/) and one in the spec (https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md).

From an end-user perspective this is confusing. An ideal solution would be having only one, but I assume that's not an easy task: My assumption is (I might be wrong here!), that the glossary in the spec are binding definitions of what the terms mean in the context of the spec and that the glossary on the website enriches those by additional terms that either might not be relevant for the spec or don't need a binding definition.

Based on that assumption I suggest two steps:

• Short term it would be good if the website glossary would link to the spec and call out the differences
• Long term it would be great if the website glossary would pull in the glossary from the spec and enrich it with additional terms.

Beyond that, the glossary includes a few definitions I think should be part of the spec glossary, e.g. service (see https://github.com/open-telemetry/opentelemetry-specification/issues/2050)

[chalin]

Relevant to this issue: #866

[chalin]

Note that this work would likely fall under #770.

[svrnm]

@chalin rg. #866, this would require that the terms from both glossaries are merged? Not sure if this is easy to have the ones from the website all added to the spec