Leighton Chen

@ofek If you'd like, you can bring up this topic in the weekly Python SIG meeting. Check the calendar here: https://calendar.google.com/calendar/u/0/embed?src=c_2bf73e3b6b530da4babd444e72b76a6ad893a5c3f43cf40467abc7a9a897f977@group.calendar.google.com&pli=1 We meet Thursdays 9am PST.

@Ali-Alnosairi I believe @Rajamanosankari has already been assigned to this issue. Feel free to reach out to them if you'd like to collaborate or take over.

@Annosha Seeing as @Rajamanosankari has not responded in the thread I will reassign.

@rajat315315 Are you still working on this?

Given the decision to make [incubating and stable](https://github.com/open-telemetry/opentelemetry-python/pull/3586#issuecomment-1998107154) namespaces for semantic conventions, we should theoretically not have anymore breaking changes going forward for the semconv package. Would it make sense...

As a result of [this](https://github.com/open-telemetry/opentelemetry-specification/issues/3539) discussion, we have decided to remove the lowering of metric names and respect casing for instrument names. Similar to [js](https://github.com/open-telemetry/opentelemetry-js/issues/4057), we will be treating this...

@shijiadong2022 Seems like we've always recorded `http.url` for old sem conv so this change would just be removing it for `url.full` for new semconv.

@fcollonval Thanks so much for picking this up. I am not too familiar with exemplars but happy to open up a discussion about the architectural design. A couple of questions/changes...

@catherine-m-zhang Is this pr ready for review? If that's the case, feel free to mark as a PR instead of draft.

Could you add an example in [samples](https://github.com/open-telemetry/opentelemetry-python/tree/main/docs/examples/metrics) displaying how someone would specify exemplar filter through MeterProvider and `exemplar_reservoir_factory` through Views configuration?