Ben Sigelman

@yurishkuro I was imagining that `OT #(N)` becomes `OT #(N+1)` when some new "important" feature(set) is added, or certainly when something substantial is removed. Additions to standard tags would not...

@wu-sheng > Any version, be released, should NOT be changed in any way, including Additions to standard tags, etc. If have any changed, it will make confused to followers. If...

The point of the roman numeral thing is to make sure people realize that it's not semver... i.e., it is "intentionally weird" :) But I can tell that nobody else...

(See https://github.com/opentracing/specification/pull/20)

https://github.com/opentracing/opentracing.io/pull/178 brings things forward a bit.

@paulcleary thanks for raising this issue. Will be fun+interesting to see the various opinions. Historical context: OpenTracing began life (even before it had its current name) as an attempt to...

(cc @adriancole who is a big advocate for standardization of in- and out-of-band propagation formats)

@yurishkuro definitely, yeah... this is the N'th time it's come up :)

@cwe1ss the baggage mechanism is not intended to cross the trusted/untrusted boundary. Core tracing ids are also pretty difficult, as is the sampling bit... The workarounds I'm aware of generate...

Re the actual subject of this issue, I am fine with either option as long as we document the choice. My assumption as a library user is that the param...