Release multiple complete schema files

[thompson-tomo]

Currently we release 1 single collection of json schema files (8 files) however to improve shareability and distribution it would be useful if we opted to release a complete file from from local references.

I am mindful that this would lead to a growth of the file size and to accommodate for this I would propose to release 3 complete files:

• Core: only defines schema upto the extension points. This is useful when vendors/languages want to define their own collection of extensions based on what they support.
• OTEL: core + extensions defined in otel spec.
• Complete: OTEL + any other extensions which has a configuration definition.

[jack-berg]

Hey @thompson-tomo - does #425 solve this issue?

[thompson-tomo]

@jack-berg I see #425 as an example of the complete file which is 1 of the 3 files mentioned.

[jack-berg]

Ok.

to improve shareability and distribution

Could you elaborate on this? The repository maintains I believe what you're calling "OTEL: core + extensions defined in otel spec".

Core: only defines schema upto the extension points. This is useful when vendors/languages want to define their own collection of extensions based on what they support.

If I understand correctly, this would omit types representing built-in extension implementations like batch processor, otlp exporter, parent sampler, etc. If a language doesn't support a particular type or property, we have a mechanism to track it and for users to discover it. As for vendors wishing to have distributions that omit core components: 1. is this a real thing? 2. i'm not sure otel the project should jump through extra hoops to facilitate distributions that lack key pieces. The set of built-in types is fairly small and narrow in scope.

Complete: OTEL + any other extensions which has a configuration definition.

I think we need to find ways for other extension components to publish their schema, but I want it to be a distributed solution rather than centralized in this repo.