The spec. "Payment Request 1.1" describes an #API that allows user agents (e.g., #browsers) to facilitate the payment flow between merchant and user. This API also enables websites to take advantage of more secure payment schemes #timetogiveinput!
Day 1 of @W3CTAG face-to-face (actually face-to-face this time!). Started by reviewing DCAT 3.0, an RDF vocabulary for interoperability between data catalogs published on the Web.
w3.org/TR/2022/WD-vocab-dcat…
I’d enjoy seeing even more new faces in September in Vancouver at @w3c’s annual TPAC (and first in person since pandemic times)! Love the idea of an inclusion fund!
As one step in that direction, this inclusion fund will help cover costs for under-represented groups to participate in the upcoming TPAC meeting. If you're interested in contributing to web standards, please apply! #W3Cw3.org/2022/09/TPAC/registra…
DIDs and DID documents can be adapted to any modern blockchain, distributed ledger, or other decentralized network capable of resolving a unique key into a unique value. Check the DID method registry for a list of known DID method specifications: w3c.github.io/did-spec-regis…
Coupled with #w3c Verifiable Credentials, DIDs are being used across a number of markets (such as governments, retailers, etc.) where #identification and #data authenticity is a concern. Read the numerous testimonials from W3C members and the industry: w3.org/2022/07/pressrelease-…
DIDs are a new type of identifier that do not require a centralized registry. It empowers everyone on the Web to generate their own identifiers and take control of their own #identity and relationships while also providing greater #security and #privacy