Difference between revisions of "WebID Comparison"

From MgmtWiki
Jump to: navigation, search
(Trust Token)
Line 16: Line 16:
 
==Trust Token==
 
==Trust Token==
 
* The [https://groups.google.com/a/chromium.org/g/blink-dev/c/UIvia1WwIhk/m/DuXLKdF7AgAJ?pli=1 Trust Token explainer]
 
* The [https://groups.google.com/a/chromium.org/g/blink-dev/c/UIvia1WwIhk/m/DuXLKdF7AgAJ?pli=1 Trust Token explainer]
 +
* a new API for propagating a notion of user authenticity across sites, without using cross-site persistent identifiers like third party cookies. Trust Token is built on Privacy Pass for anonymous tokens that can't be tracked between issuance and redemption.
  
 
==References==
 
==References==

Revision as of 17:48, 22 September 2020

Full Title

Comparison between various proposals for Web ID.

Context

Several proposals existing starting from Tim Berners-Lee in 2020-03-05 to rescent version from the browser folk and the decerntalized ID folk, all in the W3.

WebID 1.0

  • The first proposal from Sambra, Story and Berners-Lee sought to deal with a distributed Social Web.
  • A WebID is an HTTP URI which refers to an Agent (Person, Organization, Group, Device, etc.). A description of the WebID can be found in the Profile Document.
  • A WebID Profile Document is a Web resource that MUST be available as text/turtle [link broken], but MAY be available in other RDF formats.
  • WebIDs can be used to build a Web of trust using vocabularies such as FOAF [FOAF] by allowing people to link together their profiles in a public or protected manner.
  • URI fragments (#me) support sub sets or offshoots of the profile doc which is available at the base URI.

DIF Web ID

WICG Web ID

Trust Token

  • The Trust Token explainer
  • a new API for propagating a notion of user authenticity across sites, without using cross-site persistent identifiers like third party cookies. Trust Token is built on Privacy Pass for anonymous tokens that can't be tracked between issuance and redemption.

References