Jack Berg

Seems reasonable if there is demand for it 👍 Presumably this would be a setting for the [OTLP metric exporter](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk_exporters/otlp.md)?

#2619 extended the precedent established in #2404, where the OTLP exporter was given a configuration for temporality preference despite that technically being a reader concern. Here's how I see things:...

> We have received complaints about too many "unrelated" methods that need to be implemented on a MetricExporter, like a temporality selector, as it should already be configured with MetricReaders,...

The java implementation of OTLP JSON is correct. This [test](https://github.com/open-telemetry/opentelemetry-java/blob/main/exporters/logging-otlp/src/test/java/io/opentelemetry/exporter/logging/otlp/OtlpJsonLoggingLogRecordExporterTest.java#L96-L160) demonstrates the OTLP JSON encoded of a complete payload. The referenced example in [Example Log Records](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/data-model.md#example-log-records) is NOT valid OTLP...

Resolved in #4810.

I'm going to close this. The last remaining item is to stop publishing separate SDK artifacts. I don't think this is a good idea, but there doesn't seem to be...

Closing as `wontfix` for the reasons stated above.

The artifact was moved to [opentelemetry-java-contrib/noop-api](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/noop-api). There's a one week gap between the release of `opentelemetry-java` and `opentelemetry-java-contrib`. The noop-api will be first published this coming Friday, Sept 16th with...

All items except `opentelemetry-extension-aws` have been addressed. Moving that conversation to #4831 and closing this issue.

Closing in favor of [open-telemetry/opentelemetry-java-contrib#394](https://github.com/open-telemetry/opentelemetry-java-contrib/issues/394).