Weekly github digest (Distributed Tracing WG specs)

Issues
------
* w3c/trace-context (+0/-1/💬1)
  1 issues received 1 new comments:
  - #119 Clarify the HTTP header name choice for trace (1 by ioquatix)
    https://github.com/w3c/trace-context/issues/119 

  1 issues closed:
  - Clarify how tracestate can or cannot be used by application developers https://github.com/w3c/trace-context/issues/439 

* w3c/correlation-context (+1/-0/💬0)
  1 issues created:
  - Baggage value clarification for parsing (by lonewolf3739)
    https://github.com/w3c/baggage/issues/77 



Pull requests
-------------
* w3c/trace-context (+2/-2/💬1)
  2 pull requests submitted:
  - fix(#459): remove confusing vendor/tenant wording (by dyladan)
    https://github.com/w3c/trace-context/pull/465 [Editorial] 
  - fix: Backport #432 invalid ABNF (by dyladan)
    https://github.com/w3c/trace-context/pull/464 

  1 pull requests received 1 new comments:
  - #465 fix(#459): remove confusing vendor/tenant wording (1 by dyladan)
    https://github.com/w3c/trace-context/pull/465 [Editorial] 

  2 pull requests merged:
  - Updated tracestate to specify that it should not be used for application level properties
    https://github.com/w3c/trace-context/pull/458 
  - fix: Backport #432 invalid ABNF
    https://github.com/w3c/trace-context/pull/464 [bug] [Editorial] 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/trace-context
* https://github.com/w3c/correlation-context
* https://github.com/w3c/distributed-tracing-wg


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config