charles@97: charles@97: charles@96: charles@97: charles@97: charles@96: charles@96: 2 Members, Advisory Committee, Team, Advisory Board, Technical charles@96: Architecture Group charles@97: charles@97: charles@97: charles@99: charles@99: charles@96: charles@96: charles@96:
charles@96: charles@96:
charles@101:

Editor's draft proposed new W3C Process Document

charles@96:

2 Members, Advisory Committee, charles@96: Team, Advisory Board, Technical Architecture Group

charles@96:
charles@96: charles@96:
charles@96: charles@96: charles@96:

W3C's mission is to lead the Web to its full potential. W3C Member organizations provide resources to this end, and the W3C charles@96: Team provides the technical leadership and organization to charles@96: coordinate the effort.

charles@96:

2.1 Members

charles@96:

W3C Members are primarily represented in W3C processes as follows:

charles@96:
    charles@96:
  1. The Advisory Committee is composed of one representative charles@96: from each Member organization (refer to the Member-only list of current Advisory Committee charles@96: representatives [MEM1]). The charles@96: Advisory Committee: charles@96: charles@96: Advisory Committee representatives have appeal powers for some processes described in this charles@96: document.
  2. charles@96:
  3. Representatives of Member organizations participate in Working Groups, Interest Groups, and Coordination charles@96: Groups and author and review technical reports.
  4. charles@96:
charles@96:

W3C membership is charles@96: open to all entities, as described in "How to Join W3C" [PUB5]; (refer to the public list of current W3C Members [PUB8]). Organizations subscribe according to charles@96: the Membership charles@96: Agreement [PUB6]. The Team MUST ensure that Member charles@96: participation agreements remain Team-only and charles@96: that no Member receives preferential treatment within W3C.

charles@96:

W3C does not charles@96: have a class of membership tailored to, or priced for individuals. However, charles@96: an individual MAY join W3C as an Affiliate Member. charles@96: In this case the same restrictions pertaining to related Members apply when the individual also represents another W3C Member.

charles@96:

2.1.1 Rights of charles@96: Members

charles@96:

Each Member organization enjoys the following rights and benefits:

charles@96: charles@96:

Furthermore, representatives of Member organizations participate in W3C as charles@96: follows:

charles@96: charles@96:

In the case (described in paragraph 5g of the Membership charles@96: Agreement), where a Member organization is itself a consortium, user charles@96: society, or otherwise has members or sponsors, the organization's paid staff charles@96: and Advisory Committee representative exercise all the rights and privileges of charles@96: W3C membership. In addition, the Advisory Committee representative MAY designate up to four (or more at the Team's discretion) charles@96: individuals who, though not employed by the organization, MAY exercise the rights of Member representatives. These individuals charles@96: MUST disclose their employment affiliation when charles@96: participating in W3C work. Provisions for related charles@96: Members apply. Furthermore, these individuals are expected to represent the charles@96: broad interests of the W3C Member organization and not the parochial interests charles@96: of their employers.

charles@96:

The rights and benefits of W3C membership are contingent upon conformance to charles@96: the processes described in this document. The vast majority of W3C Members charles@96: faithfully follow the spirit as well as the letter of these processes. When charles@96: serious and/or repeated violations do occur, and repeated attempts to address charles@96: these violations have not resolved the situation, the Director MAY take disciplinary action. Arbitration in the case of charles@96: further disagreement is governed by paragraph 19 of the Membership Agreement. charles@96: Refer to the Guidelines for charles@96: Disciplinary Action [MEM14].

charles@96:

2.1.2 Related Members

charles@96:

In the interest of ensuring the integrity of the consensus process, Member charles@96: involvement in some of the processes in this document is affected by related charles@96: Member status. As used herein, two Members are related if:

charles@96:
    charles@96:
  1. Either Member is a subsidiary of the other, or
  2. charles@96:
  3. Both Members are subsidiaries of a common entity, or
  4. charles@96:
  5. The Members have an employment contract or consulting contract that affects charles@96: W3C participation.
  6. charles@96:
charles@96:

A subsidiary is an organization of which effective control and/or charles@96: majority ownership rests with another, single organization.

charles@96:

Related Members MUST disclose these charles@96: relationships according to the mechanisms described in the New Member Orientation [MEM4].

charles@96:

2.1.3 Advisory Committee (AC)

charles@96:

When an organization joins W3C (see "How to Join W3C" [PUB5]), it MUST name charles@96: its Advisory Committee representative as part of the Membership Agreement. The charles@96: New Member Orientation explains charles@96: how to subscribe or unsubscribe to Advisory Committee mailing lists, provides charles@96: information about Advisory Committee meetings, explains how to name a new charles@96: Advisory Committee representative, and more. Advisory Committee representatives charles@96: MUST follow the conflict of interest policy by disclosing information charles@96: according to the mechanisms described in the New Member Orientation. See also charles@96: the additional roles of Advisory Committee representatives described in the charles@96: W3C Patent Policy charles@96: [PUB33].

charles@96:

Additional information for Members is available at the Member Web site [MEM6].

charles@96:
2.1.3.1 Advisory Committee charles@96: Mailing Lists
charles@96:

The Team MUST provide two mailing lists for use charles@96: by the Advisory Committee:

charles@96:
    charles@96:
  1. One for official announcements (e.g., those required by this document) from charles@96: the Team to the Advisory Committee. This list is read-only for Advisory charles@96: Committee representatives.
  2. charles@96:
  3. One for discussion among Advisory Committee representatives. Though this charles@96: list is primarily for Advisory Committee representatives, the Team MUST monitor discussion and SHOULD participate in discussion when appropriate. Ongoing charles@96: detailed discussions SHOULD be moved to other charles@96: appropriate lists (new or existing, such as a mailing list created for a charles@96: Workshop).
  4. charles@96:
charles@96:

An Advisory Committee representative MAY charles@96: request that additional individuals from their organization be subscribed to charles@96: these lists. Failure to contain distribution internally MAY result in suspension of additional email addresses, at the charles@96: discretion of the Team.

charles@96:
2.1.3.2 Advisory Committee charles@96: Meetings
charles@96:

The Team organizes a face-to-face charles@96: meeting for the Advisory Committee twice a charles@96: year. The Team appoints the Chair of these meetings (generally the charles@96: W3C Chair or Chief Operating charles@96: Officer). At each Advisory Committee meeting, the Team SHOULD provide an update to the Advisory Committee about:

charles@96:
charles@96:
Resources
charles@96:
charles@96: charles@96:
charles@96:
Allocations
charles@96:
charles@96: charles@96:
charles@96:
charles@96:

Each Member organization SHOULD send one charles@96: representative to each Advisory charles@96: Committee meeting. In exceptional circumstances (e.g., during a period of charles@96: transition between representatives from an organization), the meeting Chair charles@96: MAY allow a Member organization to send two charles@96: representatives to a meeting.

charles@96:

The Team MUST announce the date and location of charles@96: each Advisory Committee meeting no later than at the end of the previous charles@96: meeting; one year's notice is preferred. The charles@96: Team MUST announce the region of each Advisory charles@96: Committee meeting at least one year in charles@96: advance.

charles@96:

More information about Advisory charles@96: Committee meetings [MEM5] is charles@96: available at the Member Web site.

charles@96:

2.2 The W3C Team

charles@96:

The Team consists of the W3C paid staff, unpaid interns, and W3C Fellows. charles@96: W3C Fellows are Member employees working as charles@96: part of the Team; see the W3C Fellows Program charles@96: [PUB32]. The Team provides technical charles@96: leadership about Web technologies, organizes and manages W3C Activities to charles@96: reach goals within practical constraints (such as resources available), and charles@96: communicates with the Members and the public about the Web and W3C charles@96: technologies.

charles@96:

The Team is led by the Director, W3C Chair, and Chief Operating Officer. charles@96: These individuals MAY delegate responsibility charles@96: (generally to other individuals in the Team) for any of their roles described charles@96: in this document.

charles@96:

The Director is the lead charles@96: technical architect at W3C and as such, is responsible for assessing consensus within W3C for architectural choices, charles@96: publication of technical reports, and new charles@96: Activities. The Director appoints charles@96: group Chairs and has the role of charles@96: "tie-breaker" for questions of Good charles@96: Standing in a Working Group or appeal of charles@96: a Working Group decision. The Director is generally Chair of the TAG.

charles@96:

The W3C Chair leads Member charles@96: relations, and liaisons with other charles@96: organizations, governments, and the public.

charles@96:

The Chief Operating Officer charles@96: (COO) leads the operation of W3C as an organization: a charles@96: collection of people, Host institutions, and charles@96: processes.

charles@96:

Team administrative information such as Team salaries, detailed budgeting, charles@96: and other business decisions are Team-only, charles@96: subject to oversight by the Host institutions.

charles@96:

Note: W3C is not currently incorporated. For legal charles@96: contracts, W3C is represented by three "Host" charles@96: institutions: the European Research Consortium for Informatics and charles@96: Mathematics (ERCIM), Keio University, and the Massachusetts charles@96: Institute of Technology (MIT). Within W3C, the Host charles@96: institutions are governed by joint sponsorship contracts; the Hosts themselves charles@96: are not W3C Members.

charles@96:

2.2.1 Team charles@96: Submissions

charles@96:

Team members MAY request that the Director charles@96: publish information at the W3C Web site. At the Director's discretion, these charles@96: documents are published as "Team Submissions". These documents are analogous to charles@96: Member Submissions (e.g., in expected scope). However, there is no charles@96: additional Team comment. The document status charles@96: section of a Team Submission indicates the level of Team consensus about charles@96: the published material.

charles@96:

Team Submissions are not part of the technical report development process.

charles@96:

The list of published Team charles@96: Submissions [PUB16] is charles@96: available at the W3C Web site.

charles@96:

2.3 Advisory Board (AB)

charles@96:

Created in March 1998, the Advisory Board provides ongoing guidance to the charles@96: Team on issues of strategy, management, legal matters, process, and conflict charles@96: resolution. The Advisory Board also serves the Members by tracking issues charles@96: raised between Advisory Committee meetings, soliciting Member comments on such charles@96: issues, and proposing actions to resolve these issues. The Advisory Board charles@96: manages the evolution of the Process charles@96: Document. The Advisory Board hears appeals of Member Submission requests that are rejected charles@96: for reasons unrelated to Web architecture; see also the TAG.

charles@96:

The Advisory Board is not a board of directors and has no charles@96: decision-making authority within W3C; its role is strictly advisory.

charles@96:

The Team MUST make available a mailing list for charles@96: the Advisory Board to use for its communication, confidential to the Advisory charles@96: Board and Team.

charles@96:

The Advisory Board SHOULD send a summary of charles@96: each of its meetings to the Advisory Committee and other group Chairs. The charles@96: Advisory Board SHOULD also report on its charles@96: activities at each Advisory Committee meeting.

charles@96:

Details about the Advisory Board (e.g., the list of Advisory Board charles@96: participants, mailing list information, and summaries of Advisory Board charles@96: meetings) are available at the Advisory charles@96: Board home page [PUB30].

charles@96:

2.3.1 Advisory Board charles@96: Participation

charles@96:

The Advisory Board consists of nine elected participants and a Chair. The charles@96: Team appoints the Chair of the Advisory Board, who is charles@96: generally the W3C Chair.

charles@96:

The remaining nine Advisory Board participants are elected by the W3C charles@96: Advisory Committee following the AB/TAG nomination charles@96: and election process.

charles@96:

With the exception of the Chair, the terms of all Advisory Board charles@96: participants are for two years. Terms are charles@96: staggered so that each year, either four or five terms expire. If an individual charles@96: is elected to fill an incomplete term, that individual's term ends at the charles@96: normal expiration date of that term. Regular Advisory Board terms begin on 1 charles@96: July and end on 30 June.

charles@96:

2.4 Technical Architecture Group (TAG)

charles@96:

Created in February 2001, the mission of the TAG is stewardship of the Web charles@96: architecture. There are three aspects to this mission:

charles@96:
    charles@96:
  1. to document and build consensus around principles of Web architecture and charles@96: to interpret and clarify these principles when necessary;
  2. charles@96:
  3. to resolve issues involving general Web architecture brought to the charles@96: TAG;
  4. charles@96:
  5. to help coordinate cross-technology architecture developments inside and charles@96: outside W3C.
  6. charles@96:
charles@96:

The TAG hears appeals of Member charles@96: Submission requests that are rejected for reasons related to Web charles@96: architecture; see also the Advisory Board.

charles@96:

The TAG's scope is limited to technical issues about Web architecture. The charles@96: TAG SHOULD NOT consider administrative, process, charles@96: or organizational policy issues of W3C, which are generally addressed by the charles@96: W3C Advisory Committee, Advisory Board, and Team. Please refer to the TAG charter [PUB25] for more information about the charles@96: background and scope of the TAG, and the expected qualifications of TAG charles@96: participants.

charles@96:

The Team MUST make available two mailing lists charles@96: for the TAG:

charles@96: charles@96:

The TAG MAY also request the creation of charles@96: additional topic-specific, public mailing lists. For some TAG discussions charles@96: (e.g., an appeal of a rejected Member charles@96: Submission request), the TAG MAY use a list charles@96: that will be Member-only.

charles@96:

The TAG SHOULD send a summary of each of its charles@96: meetings to the Advisory Committee charles@96: and other group Chairs. The TAG SHOULD also report charles@96: on its activities at each Advisory Committee charles@96: meeting.

charles@96:

When the TAG votes to resolve an issue, each TAG participant (whether charles@96: appointed, elected, or the Chair) has one vote; see also the section on charles@96: voting in the TAG charter charles@96: [PUB25] and the general section on charles@96: votes in this Process Document.

charles@96:

Details about the TAG (e.g., the list of TAG participants, mailing list charles@96: information, and summaries of TAG meetings) are available at the TAG home page [PUB26].

charles@96:

2.4.1 Technical charles@96: Architecture Group Participation

charles@96:

The TAG consists of eight elected or appointed participants and a Chair. The charles@96: Team appoints the Chair of the TAG, who is generally the Director.

charles@96:

Three TAG participants are appointed by the Director. Appointees are charles@96: NOT REQUIRED to be on the W3C Team. The Director charles@96: MAY appoint W3C Fellows to charles@96: the TAG.

charles@96:

The remaining five TAG participants are elected by the W3C Advisory charles@96: Committee following the AB/TAG nomination and charles@96: election process.

charles@96:

With the exception of the Chair, the terms of all TAG participants are for charles@96: two years. Terms are staggered so that each charles@96: year, either two or three elected terms, and either one or two appointed terms charles@96: expire. If an individual is appointed or elected to fill an incomplete term, charles@96: that individual's term ends at the normal expiration date of that term. Regular charles@96: TAG terms begin on 1 February and end on 31 January.

charles@96:

2.5 Advisory Board charles@96: and Technical Architecture Group Participation

charles@96:

Advisory Board and TAG participants have a special role within W3C: they are charles@96: elected by the Membership and appointed by the Director with the expectation charles@96: that they will use their best judgment to find the best solutions for the Web, charles@96: not just for any particular network, technology, vendor, or user. Advisory charles@96: Board and TAG participants are expected to participate regularly and fully. charles@96: Good Standing rules as defined for charles@96: Working Group participants also apply to Advisory Board and TAG participants. charles@96: Advisory Board and TAG participants SHOULD attend charles@96: Advisory Committee meetings.

charles@96:

An individual participates on the Advisory Board or TAG from the moment the charles@96: individual's term begins until the term ends or the seat is vacated. Although Advisory Board and TAG participants do charles@96: not advocate for the commercial interests of their employers, their charles@96: participation does carry the responsibilities associated with Member charles@96: representation, Invited Expert status, or Team representation (as described in charles@96: the section on the AB/TAG nomination and election charles@96: process). See also the licensing obligations on TAG participants in charles@96: section charles@96: 3 of the W3C Patent charles@96: Policy [PUB33], and the claim charles@96: exclusion process of section 4.

charles@96:

2.5.1 Advisory Board charles@96: and Technical Architecture Group Participation Constraints

charles@96:

Given the few seats available on the Advisory Board and the TAG, and in charles@96: order to ensure that the diversity of W3C Members is represented:

charles@96: charles@96:

If, for whatever reason, these constraints are not satisfied (e.g., because charles@96: a TAG or AB participant changes jobs), one participant MUST cease TAG or AB participation until the situation has charles@96: been resolved. If after 30 days the charles@96: situation has not been resolved, the Chair will declare one participant's seat charles@96: to be vacant. When more than one individual is involved, the verifiable random selection procedure described below will be charles@96: used to choose one person for continued participation.

charles@96:

2.5.2 Advisory Board and charles@96: Technical Architecture Group Elections

charles@96:

The Advisory Board and a portion of the Technical Architecture Group are charles@96: elected by the Advisory Committee. An election begins when the Team sends a charles@96: Call for Nominations to the Advisory Committee. Any Call for Nominations charles@96: specifies the number of available seats, the deadline for nominations, and the charles@96: address where nominations are sent. The Director SHOULD announce appointments no later than the start of a charles@96: nomination period, and generally as part of the Call for Nominations.

charles@96:

Each Member (or group of related Members) charles@96: MAY nominate one individual. A nomination charles@96: MUST be made with the consent of the nominee. In charles@96: order for an individual to be nominated as a Member representative, the charles@96: individual MUST qualify for Member representation and the Member's Advisory charles@96: Committee representative MUST include in the charles@96: nomination the (same) information charles@96: required for a Member representative in a Working Group. In order for an charles@96: individual to be nominated as an Invited Expert, the individual MUST provide the (same) information required for an Invited Expert in a charles@96: Working Group and the nominating Advisory Committee representative charles@96: MUST include that information in the nomination. charles@96: In order for an individual to be nominated as a Team representative, the charles@96: nominating Advisory Committee representative MUST charles@96: first secure approval from Team management. A nominee is NOT REQUIRED to be an employee of a Member organization, and charles@96: MAY be a W3C Fellow. Each charles@96: nomination SHOULD include a few informative charles@96: paragraphs about the nominee.

charles@96:

If, after the deadline for nominations, the number of nominees is:

charles@96: charles@96:

When there is a vote, each Member (or group of related Members) MAY vote for charles@96: as many candidates as there are available seats; see the section on Advisory Committee votes. Once the deadline for charles@96: votes has passed, the Team announces the results to the Advisory Committee. The charles@96: candidates with the most votes are elected to the available seats. In case of a charles@96: tie where there are more apparent winners than available seats (e.g., three charles@96: candidates receive 10 votes each for two seats), the verifiable random selection procedure described below will be charles@96: used to fill the available seats.

charles@96:

The shortest term is assigned to the elected individual who charles@96: received the fewest votes, the next shortest to the elected individual who charles@96: received the next fewest, and so on. In the case of a tie among those eligible charles@96: for a short term, the verifiable random selection charles@96: procedure described below will be used to assign the short term.

charles@96:

Refer to How to Organize charles@96: an Advisory Board or TAG election [MEM15] for more details.

charles@96:
2.5.2.1 Verifiable Random Selection charles@96: Procedure
charles@96:

When it is necessary to use a verifiable random selection process (e.g., in charles@96: an AB or TAG election, to "draw straws" in case of a tie or to fill a short charles@96: term), W3C uses the random and verifiable procedure defined in RFC 2777 [RFC2777]. The procedure orders an input list of charles@96: names (listed in alphabetical order by family name unless otherwise specified) charles@96: into a "result order."

charles@96:

W3C applies this procedure as follows:

charles@96:
    charles@96:
  1. When N people have tied for M (less than N) seats. In this case, only the charles@96: names of the N individuals who tied are provided as input to the procedure. The charles@96: M seats are assigned in result order.
  2. charles@96:
  3. After all elected individuals have been identified, when N people are charles@96: eligible for M (less than N) short terms. In this case, only the names of those charles@96: N individuals are provided as input to the procedure. The short terms are charles@96: assigned in result order.
  4. charles@96:
charles@96:

2.5.3 Advisory Board and charles@96: Technical Architecture Group Vacated Seats

charles@96:

An Advisory Board or TAG participant's seat is vacated when either of the charles@96: following occurs:

charles@96: charles@96:

When an Advisory Board or TAG participant changes affiliations, as long as charles@96: Advisory Board and TAG participation charles@96: constraints are respected, the individual MAY charles@96: continue to participate until the next regularly scheduled election for that charles@96: group. Otherwise, the seat is vacated.

charles@96:

Vacated seats are filled according to this schedule:

charles@96: charles@96:
charles@96: charles@96:
charles@96: charles@96: