mirror of
https://github.com/Decentralized-ID/decentralized-id.github.io.git
synced 2024-12-25 23:29:26 -05:00
add\sort ccg
This commit is contained in:
parent
b8af33de1b
commit
74a47941bf
@ -8,7 +8,7 @@ excerpt: >
|
|||||||
permalink: companies/digital-bazaar/
|
permalink: companies/digital-bazaar/
|
||||||
canonical_url: 'https://decentralized-id.com/companies/digital-bazaar/'
|
canonical_url: 'https://decentralized-id.com/companies/digital-bazaar/'
|
||||||
categories: ["Companies"]
|
categories: ["Companies"]
|
||||||
tags: ["IETF","Web Payments IG","VCTF","CCG","DHS","Veres One","W3C","GS1","SecureKey","TradeLens","Sovrin Steward","Founding Sovrin Steward","USC&B","Payments","XHTML+RDFa","HTML5+RDFa","Semantic Web","OpenID Connect","WebID","JSON-LD","RDFa","Encrypted Data Vaults","Linked Data"]
|
tags: ["IETF","Web Payments IG","VCTF","Credentials Community Group","DHS","Veres One","W3C","GS1","SecureKey","TradeLens","Sovrin Steward","Founding Sovrin Steward","USC&B","Payments","XHTML+RDFa","HTML5+RDFa","Semantic Web","OpenID Connect","WebID","JSON-LD","RDFa","Encrypted Data Vaults","Linked Data"]
|
||||||
last_modified_at: 2023-02-20
|
last_modified_at: 2023-02-20
|
||||||
toc: true
|
toc: true
|
||||||
header:
|
header:
|
||||||
|
@ -89,6 +89,22 @@ last_modified_at: 2023-07-01
|
|||||||
> Alternative ways include adding VC’s into NFC chips and adding the NFC identifier as a claim to the VC preventing duplication. There is a cost overhead to this compared to paper but is a cost potentially worth occurring.
|
> Alternative ways include adding VC’s into NFC chips and adding the NFC identifier as a claim to the VC preventing duplication. There is a cost overhead to this compared to paper but is a cost potentially worth occurring.
|
||||||
* [Indicio contributes UI messaging design for digital wallet to open source](https://indicio.tech/blog/indicio-contributes-novel-ui-messaging-design-for-digital-wallet-to-open-source-community/) 2021-03-23 Indicio
|
* [Indicio contributes UI messaging design for digital wallet to open source](https://indicio.tech/blog/indicio-contributes-novel-ui-messaging-design-for-digital-wallet-to-open-source-community/) 2021-03-23 Indicio
|
||||||
> A [finalist](https://www.dhs.gov/science-and-technology/news/2020/11/02/news-release-finalists-announced-digital-wallets-prize-challenge) in the Department of Homeland Security (DHS) Science and Technology ( S&T) Trusted User Interface (UI) Digital Wallets Challenge, the UI digital wallet design is now available in the [Indicio public Github repository](https://github.com/Indicio-tech/indicio-mobile-ux).
|
> A [finalist](https://www.dhs.gov/science-and-technology/news/2020/11/02/news-release-finalists-announced-digital-wallets-prize-challenge) in the Department of Homeland Security (DHS) Science and Technology ( S&T) Trusted User Interface (UI) Digital Wallets Challenge, the UI digital wallet design is now available in the [Indicio public Github repository](https://github.com/Indicio-tech/indicio-mobile-ux).
|
||||||
|
* [What’s in a Wallet? The recap](https://www.w3.org/community/credentials/2020/09/10/whats-in-a-wallet-the-recap/) 2020-07 Heather Vescent
|
||||||
|
> The CCG hosted two sessions where we asked people from inside and outside the community to answer the question,“What’s in a Wallet?” You can review the meeting notes and listen to the audio below:
|
||||||
|
> - [Tuesday July 7, 2020](https://w3c-ccg.github.io/meetings/2020-07-07/)
|
||||||
|
> - [Tuesday July 14, 2020](https://w3c-ccg.github.io/meetings/2020-07-14/)\
|
||||||
|
> “What’s in a Wallet?” as answered by…
|
||||||
|
> - Manu Sporny, Digital Bazaar: [Wallet Architecture Diagram](https://lists.w3.org/Archives/Public/public-credentials/2020Jul/att-0006/2020_W3C_CCG_Simple_Wallet_Architecture.pdf)
|
||||||
|
> - Christopher Allen: [Decentralized Identity Network Components](https://raw.githubusercontent.com/WebOfTrustInfo/rwot9-prague/master/topics-and-advance-readings/media/ExpandedDecentralizedIdentityNetworkComponents.png)
|
||||||
|
> - Dan Buchner: [Microsoft](https://www.microsoft.com/en-us/security/business/identity/own-your-identity) (check the minutes.)
|
||||||
|
> - Kyle Kemper, [SwissKey](https://swisskey.io/)
|
||||||
|
> - Kaliya Identity Woman Young: [CCG Glossary Group with DIF Presentation](https://docs.google.com/presentation/d/1vB50Ta7H86_PopLaDE_yhJlCLhA9TiO2zQUutKiFmTQ/edit#slide=id.g752184a474_0_4)
|
||||||
|
> - Orie Steele, Transmute: [Universal Wallet](https://github.com/transmute-industries/universal-wallet)
|
||||||
|
> - Daniel Hardman: [What goes in a Wallet?](https://docs.google.com/presentation/d/1ZoD9njc0USS6Qr3O7WXmd-3Nmxmz0pVyBFEjkM4p9C4/edit#slide=id.p)
|
||||||
|
> - Darrell O’Donnell: [The State of Digital Wallets](https://docs.google.com/presentation/d/1shW4GzjG0HE2uxLCcYdSkaG-nCRBVZrwRFpa8Gs709U/edit)
|
||||||
|
> - Charles Cunningham, Jolocom: [What’s in a Wallet?](https://jolocom.io/wp-content/uploads/2020/05/Jolocom-WhatisinaWallet-CCG-W3C.pdf)
|
||||||
|
> - Katryna Dow, [MeeCo](https://www.meeco.me/) (check the minutes.)
|
||||||
|
> - Nathan Tonani, Learning Economy.io: [What is a Wallet?](https://docs.google.com/document/u/4/d/e/2PACX-1vR6GMNrBzDuMvhHGlVeENEMZjijHTVKUueG5f6KshFlsIfcqt1QjsTGNgB8vjEGfDVFRB-dWhe5-Hxc/pub)
|
||||||
* [Dealing with private key loss or compromise in digital identity systems](https://github.com/bhaskar20/rebooting-the-web-of-trust/blob/master/topics-and-advance-readings/dealing_with_key_loss_in_digital_identity.md) 2015-10-31 Christian Lundkvist RWoT 1
|
* [Dealing with private key loss or compromise in digital identity systems](https://github.com/bhaskar20/rebooting-the-web-of-trust/blob/master/topics-and-advance-readings/dealing_with_key_loss_in_digital_identity.md) 2015-10-31 Christian Lundkvist RWoT 1
|
||||||
> If an identity is tied to a single persistent private key, then loss or compromise of the private key will mean total loss of the identity. Since key compromise and/or loss do happen there needs to be a way to recover from this in order to have a persistent digital identity. [See here for definitions used](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/topics-and-advance-readings/shared_terminology_for_digital_identity_systems.md).
|
> If an identity is tied to a single persistent private key, then loss or compromise of the private key will mean total loss of the identity. Since key compromise and/or loss do happen there needs to be a way to recover from this in order to have a persistent digital identity. [See here for definitions used](https://github.com/WebOfTrustInfo/rebooting-the-web-of-trust/blob/master/topics-and-advance-readings/shared_terminology_for_digital_identity_systems.md).
|
||||||
>
|
>
|
||||||
|
@ -38,6 +38,10 @@ last_modified_at: 2023-07-02
|
|||||||
* [Prioritizing Individual Sovereignty over Interoperability](http://web.archive.org/web/20230616014429/https://jolocom.io/blog/decentralized-identifiers-design-challenges/) 2019-04-26 Jolocom and Danube tech
|
* [Prioritizing Individual Sovereignty over Interoperability](http://web.archive.org/web/20230616014429/https://jolocom.io/blog/decentralized-identifiers-design-challenges/) 2019-04-26 Jolocom and Danube tech
|
||||||
> While we see the potential to enable interoperability with actors that do not put control in the hands of the subject of the digital identity, we must ensure that this interoperability on a technical level does not undermine the Design Goals that guided the creation of decentralized identifiers in the first place.
|
> While we see the potential to enable interoperability with actors that do not put control in the hands of the subject of the digital identity, we must ensure that this interoperability on a technical level does not undermine the Design Goals that guided the creation of decentralized identifiers in the first place.
|
||||||
|
|
||||||
|
## Development
|
||||||
|
* [Open API for Interoperable Traceability](https://w3c-ccg.github.io/traceability-interop/openapi/#overview) 2023-06-21 CCG
|
||||||
|
> `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`
|
||||||
|
|
||||||
## Interoperability Plug-fest
|
## Interoperability Plug-fest
|
||||||
* [JFF & VC-EDU Plugfest #1: Leaping Towards Interoperable Verifiable Learning & Employment Records](https://kayaelle.medium.com/jff-vc-edu-plugfest-1-892b6f2c9dfb) 2022-07-07 Kayaelle
|
* [JFF & VC-EDU Plugfest #1: Leaping Towards Interoperable Verifiable Learning & Employment Records](https://kayaelle.medium.com/jff-vc-edu-plugfest-1-892b6f2c9dfb) 2022-07-07 Kayaelle
|
||||||
> With this badge, they qualify to participate in Plugfest #2 which will focus on issuing and displaying LER VCs. Plugfest #2 will take place in November 2022 with plans to meet in person the day before the [Internet Identity Workshop](https://internetidentityworkshop.com/) on November 14 in Mountainview, CA. If vendors are interested in Plugfest #2 and didn’t participate in Plugfest #1, there is still an opportunity to do so by fulfilling the same requirements listed above including the video and earning a Plugfest #1 badge.
|
> With this badge, they qualify to participate in Plugfest #2 which will focus on issuing and displaying LER VCs. Plugfest #2 will take place in November 2022 with plans to meet in person the day before the [Internet Identity Workshop](https://internetidentityworkshop.com/) on November 14 in Mountainview, CA. If vendors are interested in Plugfest #2 and didn’t participate in Plugfest #1, there is still an opportunity to do so by fulfilling the same requirements listed above including the video and earning a Plugfest #1 badge.
|
||||||
|
@ -6,7 +6,7 @@ title: World Wide Web Consortium - W3C
|
|||||||
headings: ["Main","W3C ID History","ID in the Browser 2011"]
|
headings: ["Main","W3C ID History","ID in the Browser 2011"]
|
||||||
description: An international community that develops open standards to ensure the long-term growth of the Web.
|
description: An international community that develops open standards to ensure the long-term growth of the Web.
|
||||||
excerpt: "First started as an IETF application area at the beginning of 1990, the Web standard stack, given its foreseen volume and applicative nature on top of the Internet protocols, quickly spun off its own forum. The W3C then laid the foundations of the Web with the development of HTML 4 and XML at the end of the last century. It still works closely with IETF today, on the HTTP or URL specifications and in other areas of common interest (e.g. crypto, security, video)."
|
excerpt: "First started as an IETF application area at the beginning of 1990, the Web standard stack, given its foreseen volume and applicative nature on top of the Internet protocols, quickly spun off its own forum. The W3C then laid the foundations of the Web with the development of HTML 4 and XML at the end of the last century. It still works closely with IETF today, on the HTTP or URL specifications and in other areas of common interest (e.g. crypto, security, video)."
|
||||||
permalink: web-standards/w3c/
|
permalink: /web-standards/w3c/
|
||||||
canonical_url: 'https://decentralized-id.com/web-standards/w3c/'
|
canonical_url: 'https://decentralized-id.com/web-standards/w3c/'
|
||||||
categories: ["Web Standards","Organizations"]
|
categories: ["Web Standards","Organizations"]
|
||||||
tags: ["W3C","Credentials Community Group","JSON-LD","WebAuthN","Decentralized Identifiers","Verifiable Credentials","Veres One","BTCR","Linked Data"]
|
tags: ["W3C","Credentials Community Group","JSON-LD","WebAuthN","Decentralized Identifiers","Verifiable Credentials","Veres One","BTCR","Linked Data"]
|
||||||
|
@ -1,12 +1,58 @@
|
|||||||
---
|
---
|
||||||
title: Credentials Community Group - W3C
|
title: Credentials Community Group - W3C
|
||||||
description: "to explore the creation, storage, presentation, verification, and user control of credentials."
|
description: "Drafting and incubating Internet specifications for further standardization; prototyping and testing reference implementations."
|
||||||
excerpt: >
|
excerpt: >
|
||||||
The mission of the W3C Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.
|
explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems.
|
||||||
permalink: web-standards/w3c/cg/credentials/
|
permalink: /web-standards/sdo/w3c/credentials-community-group/
|
||||||
redirect_from:
|
canonical_url: "https://decentralized-id.com/web-standards/w3c/credentials-community-group/"
|
||||||
- web-standards/w3c/ccg/
|
categories: ["Web Standards","Organizations"]
|
||||||
categories: ["Web Standards"]
|
tags: ["Credentials Community Group","Verifiable Credentials","Decentralized Identifiers","W3C","ECDSA Cryptosuite v2019","ECDSA Cryptosuite v2020","JWS","Tracability"]
|
||||||
tags: ["Verifiable Credentials","Decentralized Identifiers","W3C"]
|
last_modified_at: 2023-07-03
|
||||||
published: false
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
## Main
|
||||||
|
[GitHub](https://github.com/w3c-ccg/) - [Mailing List Archive](https://lists.w3.org/Archives/Public/public-credentials/) - [Charter](https://www.w3.org/community/credentials/charter) - [Meetings](https://w3c-ccg.github.io/meetings/) - [Announcements](https://w3c-ccg.github.io/announcements/) - [IRC](irc://irc.w3.org/#credentials)
|
||||||
|
|
||||||
|
* [Credentials Community Group](https://www.w3.org/community/credentials/) 2014-08-08 W3C
|
||||||
|
> to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.
|
||||||
|
* [W3C Credentials Community Group](https://w3c-ccg.github.io/) Credentials Community Group
|
||||||
|
> Increasing trust on the Web, one spec at a time.
|
||||||
|
* [CCG 101 - Help us know what is needed!](https://lists.w3.org/Archives/Public/public-credentials/2021May/0150.html) 2021-05-25 Victor Syntez
|
||||||
|
> I've invited you to fill out the following form:
|
||||||
|
> [CCG 101 - Help us know what’s needed!](https://docs.google.com/forms/d/e/1FAIpQLSe3OakcEg8IfWXYALg10eiii2hiLKq2vXC-yazpPk0QVzIMzQ/viewform?vc=0&c=0&w=1&flr=0&usp=mail_form_link)
|
||||||
|
* [GDocs] [W3C-CCG Work Item Process](https://docs.google.com/document/d/1vj811aUbs8GwZUNo-LIFBHafsz4rZTSnRtPv7RQaqNc/) 2020-06-19 Credentials Community Group
|
||||||
|
> In general, any work that advances the mission is welcome for consideration as a Work Item. A Work Item requires at least one group member willing to commit to being the first editor, another group member (from a different company) willing to be a co-editor, a suggested timeline, and the expected Work Item type, e.g., Community Final Report or Ongoing Repository.
|
||||||
|
|
||||||
|
## [Meetings](https://w3c-ccg.github.io/announcements/)
|
||||||
|
|
||||||
|
* [Meeting Transcriptions and Audio Recordings (2014-today)](https://w3c-ccg.github.io/meetings/)
|
||||||
|
* [Verifiable Credentials for Education task force](https://w3c-ccg.github.io/vc-ed/)
|
||||||
|
* [Verifiable Credentials API](https://meet.w3c-ccg.org/vcapi) - how we exchange credentials over REST
|
||||||
|
* [Supply Chain Traceability with Verifiable Credentials](https://meet.w3c-ccg.org/traceability)
|
||||||
|
* [Confidential Storage](https://forms.gle/HGGiFtgASUqWRqTLA)
|
||||||
|
|
||||||
|
## About
|
||||||
|
|
||||||
|
* [IRC mailing list bridge](https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0117.html) 2022-04-23 Charles E. Lehner
|
||||||
|
> Notifications of messages to this mailing list (public-credentials) are now sent to our IRC channel (#ccg).
|
||||||
|
* [CCG updates to cgbot and scribe-tool](https://lists.w3.org/Archives/Public/public-credentials/2021May/0169.html) 2021-05-30 Manu Sporny
|
||||||
|
> 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.
|
||||||
|
* [Reminder: You can present to the CCG](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0151.html) 2022-03
|
||||||
|
> 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.
|
||||||
|
* [W3C Credentials Community Group Launch Announcement](https://www.w3.org/community/credentials/launch-pr-draft/) 2014-08-10 Manu Sporny
|
||||||
|
> The Credentials Community Group has been launched to create a common way of storing and transmitting low-stakes and high-stakes credentials both on the Web and in the physical world. The founding members of the group include Educational Testing Service (ETS), British Computer Society (BCS), Badge Alliance, Conexxus, Standard Treasury, Accreditrust, Digital Bazaar, NBREDS, COMPANY_X, COMPANY_Y, … and COMPANY_Z.
|
||||||
|
|
||||||
|
## Standards Work
|
||||||
|
* [2022-2026 Verifiable Data Standards Roadmap [DRAFT]](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0068.html) 2022-03-12 Manu Sporny
|
||||||
|
> ![](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/att-0068/2022_Verifiable_Data_Standards_Roadmap.png)
|
||||||
|
|
||||||
|
## Reports
|
||||||
|
* [RDF Dataset Canonicalization](https://www.w3.org/community/reports/credentials/CG-FINAL-rdf-dataset-canonicalization-20221009/) 2022-10-12
|
||||||
|
* [JSON Web Signature 2020](https://www.w3.org/community/reports/credentials/CG-FINAL-lds-jws2020-20220721/) 2022-07-26
|
||||||
|
* [ECDSA Cryptosuite v2019](https://www.w3.org/community/reports/credentials/CG-FINAL-di-ecdsa-2019-20220724/) 2022-07-26
|
||||||
|
* [EdDSA Cryptosuite v2020](https://www.w3.org/community/reports/credentials/CG-FINAL-di-eddsa-2020-20220724/) 2022-07-26
|
||||||
|
* [Data Integrity 1.0](https://www.w3.org/community/reports/credentials/CG-FINAL-data-integrity-20220722/) 2022-07-26
|
||||||
|
* [Decentralized Identifiers (DIDs) v0.13 Data Model and Syntaxes](https://www.w3.org/2019/08/did-20190828/) 2019-09-13
|
||||||
|
* [Verifiable Claims Use Cases 1.0](https://www.w3.org/2017/05/vc-use-cases/CGFR/2017-05-01/) 2017-05-12
|
||||||
|
* [Verifiable Claims Data Model and Representations 1.0](https://www.w3.org/2017/05/vc-data-model/CGFR/2017-05-01/) 2017-05-12
|
||||||
|
|
||||||
|
@ -8,3 +8,5 @@
|
|||||||
> Here’s an easy-to-understand analogy to help your non-technical friends and customers understand public keys and private keys, and how they relate to cryptography and digital signatures.
|
> Here’s an easy-to-understand analogy to help your non-technical friends and customers understand public keys and private keys, and how they relate to cryptography and digital signatures.
|
||||||
* [Zero Knowledge Proofs](https://www.windley.com/archives/2021/11/zero_knowledge_proofs.shtml) 2021-11 Phil Windley
|
* [Zero Knowledge Proofs](https://www.windley.com/archives/2021/11/zero_knowledge_proofs.shtml) 2021-11 Phil Windley
|
||||||
> This problem was first explored by MIT researchers Shafi Goldwasser, Silvio Micali and Charles Rackoff in the 1980s as a way of combatting information leakage. The goal is to reduce the amount of extra information the verifier, Victor, can learn about the prover, Peggy.
|
> This problem was first explored by MIT researchers Shafi Goldwasser, Silvio Micali and Charles Rackoff in the 1980s as a way of combatting information leakage. The goal is to reduce the amount of extra information the verifier, Victor, can learn about the prover, Peggy.
|
||||||
|
* [@BartHanssens shares](https://twitter.com/BartHanssens/status/1319604882068787200):
|
||||||
|
> proofs: https://w3c-ccg.github.io/ld-proofs, cryptosuite: https://w3c-ccg.github.io/ld-cryptosuite-registry, #GnuPG: signatures https://gpg.jsld.org/contexts
|
||||||
|
@ -1,93 +0,0 @@
|
|||||||
---
|
|
||||||
published: false
|
|
||||||
---
|
|
||||||
# W3C - CCG
|
|
||||||
|
|
||||||
Digital Bazaar founder, Manu Sporney, proposed the [W3C Credentials Community Group](http://web.archive.org/web/20181206060143/https://www.w3.org/community/credentials/charter-20140808/) 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."
|
|
||||||
|
|
||||||
|
|
||||||
* [@BartHanssens shares](https://twitter.com/BartHanssens/status/1319604882068787200):
|
|
||||||
> proofs: https://w3c-ccg.github.io/ld-proofs, cryptosuite: https://w3c-ccg.github.io/ld-cryptosuite-registry, #GnuPG: signatures https://gpg.jsld.org/contexts
|
|
||||||
* [Open API for Interoperable Traceability](https://w3c-ccg.github.io/traceability-interop/openapi/#overview) CCG
|
|
||||||
> `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`
|
|
||||||
|
|
||||||
* [We're not the only community with problems (Fwd: Open Letter to Debian election candidates about Debian vendettas)](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0127.html) Manu Sporny (Saturday, 19 March)
|
|
||||||
> 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;
|
|
||||||
* [CCG Highlights](https://lists.w3.org/Archives/Public/public-credentials/)
|
|
||||||
|
|
||||||
|
|
||||||
Harrison Tang, CEO of Spokeo, [is the new co-chair of the CCG](https://twitter.com/TheCEODad/status/1544884282316845057)
|
|
||||||
|
|
||||||
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).
|
|
||||||
|
|
||||||
### VC-EDU
|
|
||||||
|
|
||||||
* [VC-Educational Task Force](https://w3c-ccg.github.io/meetings/2022-04-18-vc-education/) VCEdu Mailing List
|
|
||||||
> 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”
|
|
||||||
|
|
||||||
### CCG - Credentials community group
|
|
||||||
|
|
||||||
* [Harrison new Co-Chair of the CCG and CEO of Spokeo explaining SSI](https://twitter.com/TheCEODad/status/1545907309435428864) Harrison Tang @TheCEODad
|
|
||||||
|
|
||||||
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/](https://github.com/w3c-ccg/meetings) - GitHub
|
|
||||||
|
|
||||||
* [https://www.w3.org/community/credentials/](https://www.w3.org/community/credentials/) - W3C Community Page
|
|
||||||
|
|
||||||
* [https://lists.w3.org/Archives/Public/public-credentials/](https://lists.w3.org/Archives/Public/public-credentials/) - Mailing List Arcives
|
|
||||||
|
|
||||||
* [https://w3c-ccg.github.io/](https://w3c-ccg.github.io/) - GItHub Pages Site
|
|
||||||
|
|
||||||
* [CCG 101 - Help us know what is needed!](https://lists.w3.org/Archives/Public/public-credentials/2021May/0150.html) 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:
|
|
||||||
|
|
||||||
* [https://docs.google.com/forms/d/e/1FAIpQLSe3OakcEg8IfWXYALg10eiii2hiLKq2vXC-yazpPk0QVzIMzQ/viewform?vc=0&c=0&w=1&flr=0&usp=mail_form_link](https://docs.google.com/forms/d/e/1FAIpQLSe3OakcEg8IfWXYALg10eiii2hiLKq2vXC-yazpPk0QVzIMzQ/viewform?vc=0&c=0&w=1&flr=0&usp=mail_form_link)
|
|
||||||
|
|
||||||
* [CCG updates to cgbot and scribe-tool](https://lists.w3.org/Archives/Public/public-credentials/2021May/0169.html) Manu Sporny (Sunday, 30 May)
|
|
||||||
|
|
||||||
New CCG infrastructure features:
|
|
||||||
|
|
||||||
- Auto-presence - No one is required to present+ themselves any more. The cgbot does it for us now, saving our feeble sausage fingers from being over exerted.
|
|
||||||
- The Ryan Grant, Who We All Know And Love, Would Like To Know Where The Raw Transcripts Are Feature - When the cgbot closes out the meeting, it will let everyone in IRC know where the raw transcripts, audio, and video files are so anyone can download them and/or remix them to spread CCG propaganda. This will hopefully also save Heather from having to document yet another piece of tribal CCG knowledge.
|
|
||||||
- The You Exist Even Though You're Not in people.json Feature - When someone is present+'d, which is anyone that joins the call now thanks to auto-presence, that person will show up in the attendees list. This achieves two things 1) the poor minutes publisher can update the people.json at their leisure instead of being blocked by it whenever a new person shows up to a call, and 2) we get a more accurate record of attendees.
|
|
||||||
- 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.
|
|
||||||
* [https://www.w3.org/community/credentials/](https://www.w3.org/community/credentials/)
|
|
||||||
|
|
||||||
* [https://lists.w3.org/Archives/Public/public-credentials/](https://lists.w3.org/Archives/Public/public-credentials/)
|
|
||||||
|
|
||||||
* [IRC mailing list bridge](https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0117.html) 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)](https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0172.html) Manu Sporny (Tuesday, 10 August)
|
|
||||||
|
|
||||||
* [The CCG Work Item process is outlined here](https://docs.google.com/document/d/1vj811aUbs8GwZUNo-LIFBHafsz4rZTSnRtPv7RQaqNc/):
|
|
||||||
|
|
||||||
* [Here's how you get started:](https://docs.google.com/document/d/1vj811aUbs8GwZUNo-LIFBHafsz4rZTSnRtPv7RQaqNc/edit#heading=h.f28tyzjvad8g)
|
|
||||||
|
|
||||||
This process is open to anyone -- no W3C Membership dues, fees, etc. required to participate.
|
|
||||||
|
|
||||||
* [Reminder: You can present to the CCG](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0151.html)
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
* [Clarity about the group charter](https://lists.w3.org/Archives/Public/public-credentials/2022Jun/0044.html) Manu Sporny (Wednesday, 22 June)
|
|
||||||
|
|
||||||
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).
|
|
||||||
|
|
||||||
* [2022-2026 Verifiable Data Standards Roadmap [DRAFT]](https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0068.html) Manu Sporny (Saturday, 12 March)
|
|
||||||
|
|
||||||
![https://www.notion.soimages/image1.png](https://www.notion.soimages/image1.png)
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user