Digital Bazaar founder, Manu Sporney, proposed the W3C Credentials Community Group in 2014. “to forge a path for a secure, decentralized system of credentials that would empower both individual people and organizations on the Web to store, transmit, and receive digitally verifiable proof of qualifications and achievements.”
proofs: https://w3c-ccg.github.io/ld-proofs, cryptosuite: https://w3c-ccg.github.io/ld-cryptosuite-registry, #GnuPG: signatures https://gpg.jsld.org/contexts
resolve:dids - Grants permission to resolve DIDsissue:credentials - Grants permission issue Verifiable Credentialsverify:credentials - Grants permission verify Verifiable Credentialsread:credentials - Grants permission to get Verifiable Credentialsupdate:credentials - Grants permission to update the status of Verifiable Credentialsprove:presentations - Grants permission to prove Verifiable Presentationsverify:presentations - Grants permission verify Verifiable Presentationssubmit:presentations - Grants permission to submit Verifiable Presentations
Just a reminder that these “politics” and “other-ing” isn’t some weird by product of the “identity community”, or DIF, or CCG, or OpenID… it’s endemic in any long-lived community composed of human beings.
It’s not something you’re ever rid of… it’s something you manage over time;
Harrison Tang, CEO of Spokeo, is the new co-chair of the CCG
W3C CCG (World Wide Web Consortium’s Credentials Community Group) aims to explore the creation, storage, presentation, verification, and user control of credentials (i.e. a set of claims made about someone, or a person record).
Dmitri Zagidulin: “with invisi edu here we’ve got two pressing problems […] verifiable credentials that are going to be displayed in wallets but we also would like to bind them to more traditional display artifacts such as PDFs and that’s what James is going to be talking about and the second one is [..] we want issuers to […] at least advise to wallets, verifiers, and other software how to display the credential”
Self-sovereign identity, or SSI, is basically an identity owned by you - the user. In self-sovereign identity, you control and manage the access to your information
https://github.com/w3c-ccg/ - GitHub
https://www.w3.org/community/credentials/ - W3C Community Page
https://lists.w3.org/Archives/Public/public-credentials/ - Mailing List Arcives
https://w3c-ccg.github.io/ - GItHub Pages Site
CCG 101 - Help us know what is needed! Victor Syntez (Tuesday, 25 May)
I’ve invited you to fill out the following form:
CCG 101 - Help us know what’s needed!
To fill it out, visit:
CCG updates to cgbot and scribe-tool Manu Sporny (Sunday, 30 May)
New CCG infrastructure features:
The Fellow Jitser Invisibility Decloaker Feature - If you join the meeting with a new browser, or in Incognito mode, and you change your name from “Fellow Jister” to your preferred name, you never show up in the attendee list. People that change their names now show up in the attendee list. If you want to stay pseudonymous just give yourself an unrecognizable name… like “Robot Overlord”.
These are baby steps towards an attempt at auto-transcription and auto-publication of minutes. There are a few things that aren’t automated yet (like auto-detecting the meeting name)… ETA on those upgrades is unknown since all these upgrades are on a best effort basis.
IRC mailing list bridge Charles E. Lehner (Saturday, 23 April)
Notifications of messages to this mailing list (public-credentials) are now sent to our IRC channel (#ccg).
re: How to contribute to new standards work? (was:Re: RDF Dataset Canonicalization - Formal Proof) Manu Sporny (Tuesday, 10 August)
This process is open to anyone – no W3C Membership dues, fees, etc. required to participate.
This is a friendly reminder that anyone in the community that is doing something interesting that you think the community should know about whether that work is done here in the CCG or elsewhere, can email the chairs with what you want to share and we can get you on the calendar. It’s best if you email all 3 chairs.
there are statements like: “Buy our products! We’re the best!” (with nothing else that we can learn from) that is frowned upon… but, in general, even if it is a feature in one of your products, chances are that we want to hear about it if it has relevance to how we might interoperate on that feature (or use it to meet a goal of the community).