What are you trying to achieve?

The Semantic Convention Tooling SIG is working on updating the schema specification here

What did you expect to see?

We want to update this specification with the following goals:

• The current schema file denotes only differences between versions. We'd like to be able to publish the current definitions for consumption.
• The weaver tool now supports "automatic" difference detection from previous version. We would like the Telemetry Schema file to be fully derived from this capability, ensuring
• We would like to require features of Telemetry Schema have matching implementation, either in the collector or elsewhere, prior to being in the specification.

Given all of these, we think a reboot to a 2.0 file format is in order.

Additional context.

So longer term goals of the Semantic Convention tooling group:

• Application Telemetry OTEP: Long term vision for allowing easy exchange of telemetry definitions between tooling vendors and opentelemetry users.
• Component Telemetry Schema: Making it easy for developers to define metrics, logs, spans, etc. and publish schemas for consumption.
• Resolved Telemetry Schema: Proposal for how to construct the existing Telemetry Schema in the Specification.

** Active Tasks**

• Create issues for active tasks (@jsuereth)
• [design] Decide on how Telemetry Schema will be consumed going forward weaver#612 (@lquerel @dineshg13)
• Formalize allowed transformations for V2.0 based on what weaver diff currently supports weaver#613 (@lquerel @lmolkova )
• Decide on a transformation language for migrations weaver#614 (@jsuereth @dineshg13 )