Issues

• Can Traceresponse enable parent-child relationship between browser and server spans?

  trace-context-level-3
  w3c/trace-context#572 · Filter by author scheler opened on Apr 30, 2024
  

• Remove all markdown includes

  tooling
  w3c/trace-context#562 · Filter by author dyladan opened on Mar 26, 2024

• Server-timing names

  trace-context-level-3
  w3c/trace-context#561 · Filter by author SergeyKanzhelev opened on Feb 27, 2024
  6

• Revisit header name -- Server-Timing vs. traceresponse

  trace-context-level-3
  w3c/trace-context#556 · Filter by author jpkrohling opened on Jan 10, 2024
  10

• Should tracing headers be included in 304 Not Modified responses?

  trace-context-level-3
  w3c/trace-context#554 · Filter by author mitar opened on Nov 13, 2023
  14

• Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service

  trace-context-level-3
  w3c/trace-context#550 · Filter by author bogdandrutu opened on Nov 1, 2023
  6

• Autopublishing level2/Level3 specs need to work with multiple markdown files

  tooling
  w3c/trace-context#545 · Filter by author kalyanaj opened on Aug 29, 2023
  2

  

• Level 3 spec: Update privacy section to include information about traceresponse headers.

  trace-context-level-3
  w3c/trace-context#542 · Filter by author kalyanaj opened on Jun 6, 2023
  

• Update tests to test Trace Context level 2 by default

  tooling
  w3c/trace-context#529 · Filter by author kalyanaj opened on Apr 11, 2023
  

• Trace Context: Apache Kafka protocol specification

  revisit-later
  w3c/trace-context#504 · Filter by author ppatierno opened on Oct 13, 2022
  5

• Request to republish level-1 spec (to publish a recent editorial change)

  tooling
  w3c/trace-context#503 · Filter by author kalyanaj opened on Oct 12, 2022
  

• Enable automatic publishing for Level 2 branch

  tooling
  w3c/trace-context#502 · Filter by author kalyanaj opened on Oct 12, 2022
  

• Inconsistent text style

  Editorial
  w3c/trace-context#485 · Filter by author dyladan opened on Apr 12, 2022
  2

• tracestate response header proposal

  trace-context-level-3
  w3c/trace-context#483 · Filter by author dyladan opened on Mar 2, 2022
  4

• Vendor information in the response from traced service

  trace-context-level-3
  w3c/trace-context#466 · Filter by author wjch-krl opened on Sep 16, 2021
  5

  

• Consider trace context support for probability sampling

  trace-context-level-3
  w3c/trace-context#463 · Filter by author jmacd opened on Aug 17, 2021
  2

  

• Add "request" to glossary

  w3c/trace-context#452 · Filter by author SergeyKanzhelev opened on Apr 6, 2021
  1

  

• Requirements for CORS safe-list

  revisit-later
  w3c/trace-context#405 · Filter by author dyladan opened on Mar 27, 2020 · 8. future-work
  3

  

• Make initial traceparent optional

  revisit-later
  w3c/trace-context#401 · Filter by author codefromthecrypt opened on Mar 26, 2020
  5

• Be consistent with normative / non-normative sections

  Editorialprivacy-needs-resolutiontodo
  w3c/trace-context#396 · Filter by author danielkhan opened on Mar 25, 2020 · 7. level-2
  2

  

• Privacy: What information may be revealed?

  privacy-needs-resolutionworkshop-fall-2020
  w3c/trace-context#393 · Filter by author danielkhan opened on Mar 25, 2020 · 7. level-2
  2

  

• Define the intended implementer

  privacy-needs-resolutionworkshop-fall-2020
  w3c/trace-context#392 · Filter by author danielkhan opened on Mar 25, 2020 · 8. future-work
  3

• Stop using vendor terminology

  Editorialworkshop-fall-2020
  w3c/trace-context#387 · Filter by author codefromthecrypt opened on Mar 18, 2020 · 7. level-2
  1

  

• Add general text format to the next version of the spec

  revisit-later
  w3c/trace-context#360 · Filter by author danielkhan opened on Nov 15, 2019 · 8. future-work
  

• Extend glossary with additional terms

  Editorialworkshop-fall-2020
  w3c/trace-context#277 · Filter by author watson opened on Apr 10, 2019 · 8. future-work