The   Distributed Tracing Working Group   invites implementations of the   Trace Context Level 2   Candidate Recommendation Snapshot. This specification defines standard HTTP headers and a value format to propagate context information that enables distributed tracing scenarios. The specification standardizes how context information is sent and modified between services. Context information uniquely identifies individual requests in a distributed system and also defines a means to add and propagate provider-specific context information.

  29 September 2022 The  Distributed Tracing Working Group  has published a First Public Working Draft of  Trace Context Level 2 . This specification defines standard HTTP headers and a value format to propagate context information that enables distributed tracing scenarios. The specification standardizes how context information is sent and modified between services. Context information uniquely identifies individual requests in a distributed system and also defines a means to add and propagate provider-specific context information.

The  Distributed Tracing Working Group  has published  Trace Context  as a W3C Recommendation. This specification defines standard HTTP headers and a value format to propagate context information that enables distributed tracing scenarios. The specification standardizes how context information is sent and modified between services. Context information uniquely identifies individual requests in a distributed system and also defines a means to add and propagate provider-specific context information.

24 June 2014 The Web Performance Working Group has published a Last Call Working Draft of Beacon . This specification defines an interoperable means for site developers to asynchronously transfer small HTTP data from the User Agent to a web server. Comments are welcome through 29 July 2014 . The Web Performance Working Group also updated the Candidate Recommendation of Resource Timing . This specification defines an interface for web applications to access the complete timing information for resources in a document. Learn more about the Rich Web Client Activity .

13 March 2014 The Linked Data Platform (LDP) Working Group has published a Group Note of Linked Data Platform Use Cases and Requirements . To foster the development of the Linked Data Platform specification, this document includes a set of user stories, use cases, scenarios and requirements that motivate a simple read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF. The aim throughout has been to avoid details of protocol (specifically the HTTP protocol), and use of any specific vocabulary that might be introduced by the LDP specification. Learn more about the Data Activity .

28 January 2014 The Tracking Protection Working Group has published two documents today. A Working Draft Tracking Preference Expression (DNT) . This specification defines the DNT request header field as an HTTP mechanism for expressing the user’s preference regarding tracking, an HTML DOM property to make that expression readable by scripts, and APIs that allow scripts to register site-specific exceptions granted by the user. It also defines mechanisms for sites to communicate whether and how they honor a received preference through use of the Tk response header field and well-known resources that provide a machine-readable tracking status. A Working Draft of Tracking Compliance and Scope . This specification defines the meaning of a Do Not Track (DNT) preference and sets out practices for websites to comply with this preference. Learn more about the Privacy Activity .

13 September 2013 The Tracking Protection Working Group has updated two Working Drafts: Tracking Preference Expression (DNT) . This specification defines the technical mechanisms for expressing a tracking preference via the DNT request header field in HTTP, via an HTML DOM property readable by embedded scripts, and via properties accessible to various user agent plug-in or extension APIs. It also defines mechanisms for sites to signal whether and how they honor this preference, both in the form of a machine-readable tracking status resource at a well-known location and via a "Tk" response header field, and a mechanism for allowing the user to approve exceptions to DNT as desired. Tracking Compliance and Scope . This specification defines the meaning of a Do Not Track (DNT) preference and sets out practices for websites to comply with this preference. Learn more about the Privacy Activity .

31 January 2013 The Linked Data Platform (LDP) Working Group has published the First Public Working Draft of Linked Data Platform Use Cases and Requirements . A set of user stories, use cases, scenarios and requirements that motivate a simple read-write Linked Data architecture, based on HTTP access to web resources that describe their state using RDF. Learn more about the Semantic Web Activity .