- From: Manu Sporny <msporny@digitalbazaar.com>
- Date: Fri, 3 Jan 2020 11:33:24 -0500
- To: W3C Credentials CG <public-credentials@w3.org>
Recently, a number of people note that W3C doesn't do protocol/HTTP APIs, even though there are examples at W3C to the contrary. This W3C proposed standard (the very last step before global standard) just came across my inbox and is an interesting data point that argues against the premise that "W3C doesn't work on [successful] protocol/HTTP APIs": https://www.w3.org/TR/trace-context/ The specification is particularly interesting because it 1) is a distributed systems specification, 2) is a collaboration between Microsoft and Google, 3) focuses on an HTTP protocol/API, and 4) reinforces the notion that W3C *does* work on this sort of stuff. Here are a few other W3C specifications that define protocols, HTTP APIs, and distributed systems: https://www.w3.org/TR/wot-thing-description/#http-binding-assertions https://www.w3.org/TR/webrtc/ https://www.w3.org/TR/activitypub/ https://www.w3.org/TR/ldp/ It's one of a number of data points that folks should be aware of when contemplating where to do future protocol / HTTP API work that this group (and others) incubate. -- manu -- Manu Sporny (skype: msporny, twitter: manusporny) Founder/CEO - Digital Bazaar, Inc. blog: Veres One Decentralized Identifier Blockchain Launches https://tinyurl.com/veres-one-launches
Received on Friday, 3 January 2020 16:33:29 UTC