Top opentelemetry-specification issues

Metrics semantic convention: "up" metric

data-model semantic-conventions enhancement p2 allowed-for-ga metrics

Trace/Span ids base64 encoded when used in proto-JSON representation

miscellaneous p2 required-for-ga protocol

Add flush API to processor/exporter

Settle on linebreak style

needs discussion

Ability to name logger - GetLogger(name) and retain this information on event

api enhancement after-ga logs

Reconsider null behavior for span attributes.

api p1 required-for-ga trace

Semantic convention for database driver name needed

semantic-conventions required-for-ga trace

Allow supplying a callback for adding new attributes when spans start

api enhancement trace

Why are we using such a long name as StatusCanonicalCode?

api p1 required-for-ga trace

should StatusCanonicalCode be applied for rpc?

error-reporting semantic-conventions p2 allowed-for-ga trace