[transition] CR Request for W3C Baggage

This is a transition request for a Candidate Recommendation
CR Request for W3C Baggage
from https://github.com/w3c/transitions/issues/609

# Document title, URLs, estimated publication date
Title: Propagation Format for Distributed Context: Baggage
URL: https://www.w3.org/TR/baggage/

# Abstract
[Link to the editor's draft](https://www.w3.org/TR/baggage/)

# Status
Here are the tentative dates we are targeting:
Deadline for comments: Jul 30
File for transition to recommendation: Aug 15

# Link to group's decision to request transition
This is captured in the minutes of the Apr 23 2024 meeting: https://docs.google.com/document/d/1EaY1zhmlOut4qZzpFue4vLc96_GrRWMtmzXYLfd1Ehc/edit

# Changes
The changes since the wide review are captured in the three issues below. 

# Requirements satisfied
N/A

# Dependencies met (or not)
N/A

# Wide Review
Yes, this was completed. https://github.com/w3c/baggage/issues/91

# Issues addressed
- https://github.com/w3c/baggage/issues/128
- https://github.com/w3c/baggage/issues/55
- https://github.com/w3c/baggage/issues/124

# Formal Objections
None

# Implementation
This specification is implemented by OpenTelemetry SDKs. OpenTelemetry supports this in 13 languages. 

Minimum CR duration: 90 days

Exit Criteria:
1) We will audit the OpenTelemetry implementation of Baggage to make sure they are following the W3C Baggage spec. 
2) We will also audit a sample of OpenTelemetry's baggage test suites to verify they are testing the standard.

# Patent disclosures
https://www.w3.org/groups/wg/distributed-tracing/ipr/


-- 
This email was generated automatically using https://github.com/w3c/transition-issues-bot

Received on Saturday, 27 April 2024 18:15:11 UTC