2021 - W3C CCG Charter Changes

gistfile1.txt

W3C Credentials Community Group Charter (2020)


This charter was ratified by group consensus on [Date]. The previous revision of the Credentials Community Group Charter is also available for archival and auditing purposes.


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.
Scope of Work
In general, topics that are “in scope” include anything related to enabling interoperable credentials on the Web. These topics include the following:
* Storage formats for digital credentials.
* Protocols for the storage and transmission of digital credentials.
* Low-stakes (non-traditional, community-based education, badges, gamification of social events) and high-stakes (P-12, high school or high school equivalent, university degrees, professional licensure, government-issued IDs, security documents) credentials.
* Identity as it relates to an entity that claims ownership over a set of digital credentials. The credentials must be capable of identifying an entity and proving that the entity is capable, authorized, or qualified to perform a particular task or operation.
* Identity and privacy technologies as they relate to ensuring the proper identification and protection of parties engaging in the exchange of credentials.
* Security as it relates to ensuring the proper end-to-end protection and authenticity of the exchange of credentials as well as the use of these credentials to login, or get authorization to access, a particular web service.
* Base technologies (digital signatures, secure messaging, etc.) that are vital for the proper operation of the solutions deemed in-scope for the Credentials CG. If the technology is not being incubated elsewhere, it may be incubated in the Credentials CG.
* Legal, regulatory, and policy concerns that affect the successful deployment of any of the use cases or technology concepts.


In general, topics that are “out of scope” involve anything not directly related to enabling interoperable credentials on the Web. Some examples of these “out of scope” topics are listed here:
* The relative merits of various economic, political, or sociological theories. (i.e. The focus of this Community Group is on Web-based credentialing methods under any economic, political or sociological scenario.)
* Marketing or evangelizing of technologies not intended to be released under a license compatible with W3C specifications. Discussion of out-of-scope solutions should be limited to elaborating upon technological advantages/disadvantages.
Work Items
In general, all documents related to credentialing are welcome. If there are individuals who will commit to being editors for a document, the group should agree to accept it as a work item even if it conflicts with previous work adopted by the community. Newly-accepted work items that extend beyond the scope of this Community Group Charter will lead to a reconsideration of the Charter. The Community Group may vote to revise the Charter in order to include new work, or to determine that the proposed work is unrelated to credentialing.
The CCG work item process is outlined here.
The Credentials Community Group current work items are available at this location.
Dependencies or Liaisons
The group will make good faith efforts to include the following communities in the progress of our work.
* Decentralized Identifiers Working Group
* Web Payments Community Group (and future Web Payments Interest and Working Groups)
* IETF HTTPbis and HTTPauth Working Groups
* IETF GNAP Working Group 
* W3C Web Crypto Working Group
* Mozilla Persona / FirefoxID Community
* W3C Web Security Interest Group
* W3C Web Apps Working Group
* W3C Web and Mobile Interest Group
* W3C Web and TV Interest Group
* W3C Web and Broadcasting Business Group
* W3C The Web Schemas Task Force of the W3C Semantic Web Interest Group
* IMS Global, including the Caliper work
* Seede/ExPRESS
* School Interoperability Framework
* Post-Secondary Electronic Standards Council
* Research Institutions contributing to the field of digital credentials (Academic, Industry, Governmental)


Community Group Process
Anything in this charter that conflicts with requirements of the Community and Business Group Process is void.


Membership and Voting Rights
* A general non-voting member of the Community Group can be an individual or a member on behalf of an organization. Consistent with W3C rules, in order to formally join the Community Group, a member must have a W3C account and push the “Join” button for the Community Group. However, W3C membership is not required to have a W3C account nor to join the Community Group.
* A voting member of the Community Group is an individual member of the Community Group who has attended at least 25% of the Community Group public teleconference calls over the 6 months prior to the date of the announcement of the election, which will also be the record date on which voting membership is determined. Attendance is counted through the list of attendees present on meeting transcripts through the “present+” function on the public teleconference calls. A single meeting tally may be substituted by each instance of the following evidence of meaningful CCG contributions: (a) per each role served as owner for active work items or (b) three messages of substance, as determined by the chairs, within 30 days on the CCG mailing list, not to be recounted.
* The Chairs will determine the list of eligible voting members as of the record date. The Chairs will make the list available to the Community Group two weeks before every election that requires voting members to be carefully identified, and the list will be verified by a third party such as a member of W3C staff or a neutral community member for which there are no strong objections. If the voting list is not ready, then the election date will be moved until two weeks after it is ready.  If the third party has reasonable objections, the election will be delayed until two weeks after such objections are resolved.
Choosing a Chair
* A Chair’s duties include:
   * Driving inclusivity, identifying consensus within the group, recording, and distributing decisions.
   * Ensuring compliance with all W3C rules applicable to the group.
   * Being a liaison between the group and all groups with which the group is coordinating.
   * Organizing the smooth operation of the group.
   * Engaging with media, performing outreach, and ensuring the transparent operation of the group.
   * Being accountable to both the W3C and to Community Group members to ensure that all deliberation and decision processes are fair, respectful, aligned with these guidelines, and neither favouring or discriminating against any participant or their associates (incl. employer).
* At any given time there may be up to three co-chairs, each holding one of three seats. Each seat defines a three-year cycle of service. That is, chairs are elected to hold a given seat with a nominal term of three years.
* Seat A’s initial term will be from 2020-2021
* Seat B’s initial term will be from 2020-2022
* Seat C’s initial term will be from 2020-2023
* In the first election after ratification of this charter, all seats will be up for election. Thereafter, in each year, a single election will be held to fill any vacant seats.
* In the case of interim vacancy, the remaining chairs may appoint a co-chair for each open seat, hold an election for the same, or wait until the next election, at their discretion. If the chairs do not take any action, the seat will automatically be up for election in any cycle. Any such interim appointments or elections shall hold the seat until the end of its natural cycle.
* There may be up to three Chairs at any given time. There are no limits to how often chairs can be re-elected by the group.
* In an election year, current chairs will select a date for elections, which will set a nomination period of two weeks, starting 4 weeks prior to the election.
* For an individual to run for election, they must self-nominate and make a statement regarding their background and why they are running, on the group mailing list.
* The current chairs will host a conference call during the nomination period, during which candidates may make a statement and answer questions from the community.
* If, at the end of nominations, any given seat only has a single candidate, that candidate immediately wins that seat. For any seats with multiple nominees, there will be an election for those seats.
* If, after nominations, any given seat has no candidates, the remaining chairs after any election (if necessary for other seats), will address the vacancy as an interim vacancy, described above.
* To elect one of multiple candidates, a vote will be held by the election mechanism of ranked choice voting, in which voters rank candidates by preference on their ballots. The candidate with the majority (more than 50%) of first-choice votes wins outright. If no candidate gets a majority of first-choice votes, the candidate who ranked the worst is eliminated, and that candidate’s voters’ ballots are redistributed to their second-choice pick. If the vote results in a tie, an immediate runoff of the top two candidates shall be held. If the vote remains tied, the winner shall be the candidate whose nomination was first recorded publicly on the group email list.
Removing a chair
* Chairs may be removed from their duties through a no-confidence vote.
* If a member of the community group wishes to call for the recall of a chair–for any reason–that member must first privately communicate with the other chairs their desire and reason for doing so. Those chairs must give the member an opportunity to discuss their concerns with a goal of resolving them. If, after 30 days, the member feels their issues are not addressed, they may then escalate to a public call for a no confidence vote. If after 60 days, the member has not made that call for a no confidence vote, the matter is dropped; any further attempts to remove the chair in question must begin with a new round of private communication.
* A public call for no confidence must be announced to the group email list stating the name of the chair subject to the recall and the names and emails of at least 3 members of the group who thereby call for a recall. This announcement must come from the member who initiated the private communication with the chairs to discuss their concerns. The other two supporting members MUST reply to that email on the public list within 48 hours to confirm their support for a no-confidence vote of the chair in question.
* The other chairs must acknowledge the call for no confidence within 7 days of all three members declaring their support.
* Within 30 days of a call for no confidence, the other chairs must hold a conference call at which the parties seeking no confidence will have an opportunity to present their case and members of the group will be able to ask clarifying questions. The chair in question shall not moderate this call. They will, however, have equal time to respond during that same call to the case made against them.
* During the week following this conference call, members may cast votes in favor or against the recall by posting to the email list. If yea votes cast that week (in favor of recall) comprise greater than two-thirds of the total votes cast, then the chair in question is removed and the seat shall be treated as an interim vacancy.
* Members are not required to vote. Abstentions may be recorded; such abstentions shall not count towards the total number of votes when calculating the two-thirds majority.
* A Chair who has been removed may stand for re-election.
* Only one call for no-confidence, for one chair, may be in process at any given time. Priority shall be given to the first such vote to be publicly called. Any subsequent public calls must wait until any previous recalls are resolved, then must start with private communication as described above.
Transparency
* The group will conduct all of its work on its public code repositories, public mailing list and the public regular teleconference.
* Any decisions reached at any face to face meeting are tentative and must be confirmed on the mailing list.
Amendments to this Charter
* Chairs may propose amendments to the charter by asking for a call for principled objections to the new charter. If, after a period of two weeks, no principled objections have been presented by a current member of the group, the new charter is approved.
* If a principled objection is posted to the mailing list or expressed in a regular call, then the chairs may either drop the amendment or proceed with a public vote.
* A public vote for a new charter must be called by the chairs within two weeks of the principled objection.
* Such a vote will be open for two weeks, with ballots cast via the group's public mailing list. Each member of the group may cast one ballot, “yea” or “nay”. A new charter must receive "yea" on two-thirds of the votes cast in the ranked choice vote, and the total votes cast must represent 5% or greater of the group membership, to pass.
* The group will use the amendment process for any substantive changes to the goals, scope, deliverables, decision process or rules for amending the charter.
* Changes to the Dependencies and Liaisons list does not constitute an amendment to the charter that requires a rechartering vote.