The content of the Specification snapshot at that URL must not change other than for minor editorial changes.

Type	Annual fee (USD)	Annual fee (JPY)	Annual fee (EUR)	Annual fee (CNY)
Large non-Member Organization	10,000	1,100,000	8900	68,000
Small non-Member Organization	2000	220,000	1500	13,500
Unaffiliated individual	300	32,000	225	2000
W3C Member	0	0	0	0

3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35 | 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 | 109 | 110 | 111 | 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | 134 |

135 | Note: A previous version of this table included Incubator Groups, but W3C closed the Incubator Activity in 2012. 136 | 137 |

Goals of the Policies

General Overview

Patent Licensing Summary

Transition to W3C Standards Track

Additional Resources

3 |

1. The Purpose of this Agreement. 5 | This Agreement sets forth the terms under which I make certain copyright and patent rights available to you for your implementation of the Specification. Any other capitalized terms not specifically defined herein have the same meaning as those terms have in the W3C Patent Policy, and if not defined there, in the W3C Process Document.
2. Copyrights. 7 |
1. 2.1. Copyright Grant. I grant to you a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license, without any obligation for accounting to me, to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement the Specification to the full extent of my copyright interest in the Specification.
2. 2.2. Attribution. As a condition of the copyright grant, you must include an attribution to the Specification in any derivative work you make based on the Specification. That attribution must include, at minimum, the Specification name and version number.
11 |
3. Patents. 13 |
1. 3.1. Patent Licensing Commitment. I agree to license my Essential Claims under the W3C Community RF Licensing Requirements. This requirement includes Essential Claims that I own and any that I have the right to license without obligation of payment or other consideration to an unrelated third party. W3C Community RF Licensing Requirements obligations made concerning the Specification and described in this policy are binding on me for the life of the patents in question and encumber the patents containing Essential Claims, regardless of changes in participation status or W3C Membership. I also agree to license my Essential Claims under the W3C Community RF Licensing Requirements in derivative works of the Specification so long as all normative portions of the Specification are maintained and that this licensing commitment does not extend to any portion of the derivative work that was not included in the Specification.
2. 3.2. Optional, Additional Patent Grant. In addition to the provisions of Section 3.1, I may also, at my option, make certain intellectual property rights infringed by implementations of the Specification, including Essential Claims, available by providing those terms via the W3C Web site.
17 |
4. No Other Rights. Except as specifically set forth in this Agreement, no other express or implied patent, trademark, copyright, or other property rights are granted under this Agreement, including by implication, waiver, or estoppel.
5. Antitrust Compliance. I acknowledge that I may compete with other participants, that I am under no obligation to implement the Specification, that each participant is free to develop competing technologies and standards, and that each party is free to license its patent rights to third parties, including for the purpose of enabling competing technologies and standards.
6. Non-Circumvention. I agree that I will not intentionally take or willfully assist any third party to take any action for the purpose of circumventing my obligations under this Agreement.
7. Transition to W3C Recommendation Track. The Specification developed by the Project may transition to the W3C Recommendation Track. The W3C Team is responsible for notifying me that a Corresponding Working Group has been chartered. I have no obligation to join the Corresponding Working Group. If the Specification developed by the Project transitions to the W3C Recommendation Track, the following terms apply: 22 |
1. 7.1. If I join the Corresponding Working Group. If I join the Corresponding Working Group, I will be subject to all W3C rules, obligations, licensing commitments, and policies that govern that Corresponding Working Group.
2. 7.2. If I Do Not Join the Corresponding Working Group. 25 |
  1. 7.2.1. Licensing Obligations to Resulting Specification. If I do not join the Corresponding Working Group, I agree to offer patent licenses according to the W3C Royalty-Free licensing requirements described in Section 5 of the W3C Patent Policy for the portions of the Specification included in the resulting Recommendation. This licensing commitment does not extend to any portion of an implementation of the Recommendation that was not included in the Specification. This licensing commitment may not be revoked but may be modified through the exclusion process defined in Section 4 of the W3C Patent Policy. I am not required to join the Corresponding Working Group to exclude patents from the W3C Royalty-Free licensing commitment, but must otherwise follow the normal exclusion procedures defined by the W3C Patent Policy. The W3C Team will notify me of any Call for Exclusion in the Corresponding Working Group as set forth in Section 4.5 of the W3C Patent Policy.
  2. 7.2.2. No Disclosure Obligation. If I do not join the Corresponding Working Group, I have no patent disclosure obligations outside of those set forth in Section 6 of the W3C Patent Policy.
  29 |
31 |
8. Conflict of Interest. I will disclose significant relationships when those relationships might reasonably be perceived as creating a conflict of interest with my role. I will notify W3C of any change in my affiliation using W3C-provided mechanisms.
9. Representations, Warranties and Disclaimers. I represent and warrant that I am legally entitled to grant the rights and promises set forth in this Agreement. IN ALL OTHER RESPECTS THE SPECIFICATION IS PROVIDED “AS IS.” The entire risk as to implementing or otherwise using the Specification is assumed by the implementer and user. Except as stated herein, I expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the Specification. IN NO EVENT WILL ANY PARTY BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THIS AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. All of my obligations under Section 3 regarding the transfer, successors in interest, or assignment of Granted Claims will be satisfied if I notify the transferee or assignee of any patent that I know contains Granted Claims of the obligations under Section 3. Nothing in this Agreement requires me to undertake a patent search.
10. Definitions. 35 |
1. 10.1. Agreement. “Agreement” means this W3C Community Final Specification Agreement.
2. 10.2. Corresponding Working Group. “Corresponding Working Group” is a W3C Working Group that is chartered to develop a Recommendation, as defined in the W3C Process Document, that takes the Specification as an input.
3. 10.3. Essential Claims. “Essential Claims” shall mean all claims in any patent or patent application in any jurisdiction in the world that would necessarily be infringed by implementation of the Specification. A claim is necessarily infringed hereunder only when it is not possible to avoid infringing it because there is no non-infringing alternative for implementing the normative portions of the Specification. Existence of a non-infringing alternative shall be judged based on the state of the art at the time of the publication of the Specification. The following are expressly excluded from and shall not be deemed to constitute Essential Claims: 39 |
  1. 10.3.1. any claims other than as set forth above even if contained in the same patent as Essential Claims; and
  2. 10.3.2. claims which would be infringed only by: 42 |
    - portions of an implementation that are not specified in the normative portions of the Specification, or
    - enabling technologies that may be necessary to make or use any product or portion thereof that complies with the Specification and are not themselves expressly set forth in the Specification (e.g., semiconductor manufacturing technology, compiler technology, object-oriented technology, basic operating system technology, and the like); or
    - the implementation of technology developed elsewhere and merely incorporated by reference in the body of the Specification.
    47 |
  3. 10.3.3. design patents and design registrations.
  50 | For purposes of this definition, the normative portions of the Specification shall be deemed to include only architectural and interoperability requirements. Optional features in the RFC 2119 sense are considered normative unless they are specifically identified as informative. Implementation examples or any other material that merely illustrate the requirements of the Specification are informative, rather than normative.
4. 10.4. I, Me, or My. “I,” “me,” or “my” refers to the signatory.
5. 10.5 Project. “Project” means the W3C Community Group or Business Group for which I executed this Agreement.
6. 10.6. Specification. “Specification” means the Specification identified by the Project as the target of this agreement in a call for Final Specification Commitments. W3C shall provide the authoritative mechanisms for the identification of this Specification.
7. 10.7. W3C Community RF Licensing Requirements. “W3C Community RF Licensing Requirements” license shall mean a non-assignable, non-sublicensable license to make, have made, use, sell, have sold, offer to sell, import, and distribute and dispose of implementations of the Specification that: 55 |
  1. 10.7.1. shall be available to all, worldwide, whether or not they are W3C Members;
  2. 10.7.2. shall extend to all Essential Claims owned or controlled by me;
  3. 10.7.3. may be limited to implementations of the Specification, and to what is required by the Specification;
  4. 10.7.4. may be conditioned on a grant of a reciprocal RF license (as defined in this policy) to all Essential Claims owned or controlled by the licensee. A reciprocal license may be required to be available to all, and a reciprocal license may itself be conditioned on a further reciprocal license from all.
  5. 10.7.5. may not be conditioned on payment of royalties, fees or other consideration;
  6. 10.7.6. may be suspended with respect to any licensee when licensor is sued by licensee for infringement of claims essential to implement the Specification or any W3C Recommendation;
  7. 10.7.7. may not impose any further conditions or restrictions on the use of any technology, intellectual property rights, or other restrictions on behavior of the licensee, but may include reasonable, customary terms relating to operation or maintenance of the license relationship such as the following: choice of law and dispute resolution;
  8. 10.7.8. shall not be considered accepted by an implementer who manifests an intent not to accept the terms of the W3C Community RF Licensing Requirements license as offered by the licensor.
  9. 10.7.9. The RF license conforming to the requirements in this policy shall be made available by the licensor as long as the Specification is in effect. The term of such license shall be for the life of the patents in question.
  66 | I am encouraged to provide a contact from which licensing information can be obtained and other relevant licensing information. Any such information will be made publicly available.
8. 10.8. You or Your. “You,” “you,” or “your” means any person or entity who exercises copyright or patent rights granted under this Agreement, and any person that person or entity controls.
69 |

71 |

3 |

1. The Purpose and General Terms of this Contributor License Agreement (CLA). This CLA sets forth the terms under which I will participate in and contribute to the development of the Specification, if any, created by the Project. Any other capitalized terms not specifically defined herein have the same meaning as those terms have in the W3C Patent Policy, and if not defined there, in the W3C Process Document. Any source code outside the Specification created by the Project is not subject to this CLA, but rather subject to separate licensing terms for that source code. The W3C Community and Business Group Process governs the operations of the Project. The Community and Business Group Process delegates some rights to the participants of the Project to establish operational agreements. Those operational agreements must not conflict with or modify this Community and Business Group Process, the Community Contributor License Agreement (CLA), or the Final Specification Agreement. Except for the limited definitions specifically referenced herein, this CLA and the Final Specification Agreement, if I sign it, set forth my entire licensing obligations for Specifications created by the Project and supersede all prior negotiations, agreements, understandings, and obligations with respect thereto.
2. Copyrights. 6 |
1. 2.1. Copyright Grant. I grant to you a perpetual (for the duration of the applicable copyright), worldwide, non-exclusive, no-charge, royalty-free, copyright license, without any obligation for accounting to me, to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, distribute, and implement any Contribution to the full extent of my copyright interest in the Contribution.
2. 2.2. Attribution. As a condition of the copyright grant, you must include an attribution to the Specification in any derivative work you make based on the Specification. That attribution must include, at minimum, the Specification name and version number.
10 |
3. Patents. 12 |
1. 3.1. Patent Licensing Commitment. I agree to license my Essential Claims under the W3C CLA RF Licensing Requirements. This requirement includes Essential Claims that I own and any that I have the right to license without obligation of payment or other consideration to an unrelated third party. With the exception of the provisions of Section 5 below, W3C CLA RF Licensing Requirements obligations made concerning the Specification and described in this CLA are binding on me for the life of the patents in question and encumber the patents containing Essential Claims, regardless of changes in participation status or W3C Membership. I also agree to license my Essential Claims under the W3C CLA RF Licensing Requirements in derivative works of the Specification developed by the Project, provided that my Contribution remains intact in those derivative works. However, no additional claims are made Essential Claims in the combination of my Contribution with derivative works of the Specification.
2. 3.2. Optional, Additional Patent Grant. In addition to the provisions of Section 3.1, I may also, at my option, make certain intellectual property rights infringed by implementations of the Specification, including Essential Claims, available by providing those terms via the W3C Web site.
16 |
4. No Other Rights. Except as specifically set forth in this CLA, no other express or implied patent, trademark, copyright, or other property rights are granted under this CLA, including by implication, waiver, or estoppel.
5. Limited Opt-Out. I, in my sole discretion, may withdraw my Contribution, for any reason, by providing written notice of that withdrawal no later than 45 days after the date of my Contribution. Notice of withdrawal of a Contribution must be made in writing using the Project's communications mechanisms for that purpose and must describe the exact material of the particular Contribution being withdrawn. Upon providing that notice, the identified Contribution will be deemed null and void, and, not withstanding anything to the contrary herein, I will not be deemed to have incurred any obligation with respect to that Contribution. In addition, any particular Contribution will be null and void, and I will not incur any obligation as a result of it, if that Contribution is not included in the Specification within 150 days of the date of that Contribution.
6. W3C Community Contributor License Agreement Execution. I acknowledge that the goal of this CLA is to provide coverage for Contributions to the Specification, if any, created by the Project. The Final Specification itself, if any, will be subject to the W3C Community Final Specification Agreement. While I have no legal obligation to execute the W3C Community Final Specification Agreement for any version of the Specification being developed under this CLA, I agree that the selection and terms of the then current W3C Community Final Specification Agreement will not be subject to negotiation.
7. Antitrust Compliance. I acknowledge that I may compete with other participants, that I am under no obligation to implement the Specification, that each participant is free to develop competing technologies and standards, and that each party is free to license its patent rights to third parties, including for the purpose of enabling competing technologies and standards.
8. Non-Circumvention. I agree that I will not intentionally take or willfully assist any third party to take any action for the purpose of circumventing my obligations under this CLA.
9. Transition to W3C Recommendation Track. Specifications developed by the Project may transition to the W3C Recommendation Track. The W3C Team is responsible for notifying me that a Corresponding Working Group has been chartered. I have no obligation to join the Corresponding Working Group. If the Specification developed under the Project transitions to the W3C Recommendation Track, the following terms apply: 23 |
1. 9.1. If I join the Corresponding Working Group. If I join the Corresponding Working Group, I will be subject to all W3C rules, obligations, licensing commitments, and policies that govern that Corresponding Working Group.
2. 9.2. If I Do Not Join the Corresponding Working Group. 26 |
  1. 9.2.1. Licensing Obligations to Resulting Specification. If I do not join the Corresponding Working Group, I agree to offer patent licenses according to the W3C Royalty-Free licensing requirements described in Section 5 of the W3C Patent Policy for my Contributions included in the resulting Recommendation. This licensing commitment may not be revoked but may be modified through the exclusion process defined in Section 4 of the W3C Patent Policy. I am not required to join a Working Group to exclude patents from the W3C Royalty-Free licensing commitment, but must otherwise follow the normal exclusion procedures defined by the W3C Patent Policy. The W3C Team will notify me of any Call for Exclusion in the Corresponding Working Group as set forth in Section 4.5 of the W3C Patent Policy.
  2. 9.2.2. No Disclosure Obligation. If I do not join the Corresponding Working Group, I have no patent disclosure obligations outside of those set forth in Section 6 of the W3C Patent Policy.
  30 |
32 |
10. Conflict of Interest. I will disclose significant relationships when those relationships might reasonably be perceived as creating a conflict of interest with my role. I will notify W3C of any change in my affiliation using W3C-provided mechanisms.
11. Representations, Warranties and Disclaimers. I represent and warrant that 1) I am legally entitled to grant the rights and promises set forth in this CLA and 2) I will not intentionally include any third party materials in any Contribution unless those materials are available under terms that do not conflict with this CLA and I identify any such third party materials. IN ALL OTHER RESPECTS MY CONTRIBUTIONS ARE PROVIDED “AS IS.” The entire risk as to implementing or otherwise using the Contribution or the Specification is assumed by the implementer and user. Except as stated herein, I expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the Contribution or the Specification. IN NO EVENT WILL ANY PARTY BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THIS CLA, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
12. Definitions. 36 |
1. 12.1. CLA. “CLA” means this Contributor Licensing Agreement.
2. 12.2. Contribution. “Contribution” means any original work of authorship, including any modifications or additions to an existing work, that I intentionally submit for inclusion in the Specification, and which Contribution is actually included in the Specification. For the purposes of this definition, the method by which I “submit” a Contribution means any form of electronic, oral, or written communication for the purpose of discussing and improving the Specification, but excludes any such communication that I conspicuously designate in writing as not a Contribution to one or more of the Specifications developed by the Project.
3. 12.3. Corresponding Working Group. “Corresponding Working Group” is a W3C Working Group that is chartered to develop a Recommendation that takes the Specification as an input.
4. 12.4. Essential Claims. “Essential Claims” shall mean all claims in any patent or patent application in any jurisdiction in the world that would necessarily be infringed by implementation of my Contributions in an implementation of the Specification. A claim is necessarily infringed hereunder only when it is not possible to avoid infringing it because there is no non-infringing alternative for implementing the normative portions of the Specification. Existence of a non-infringing alternative shall be judged based on the state of the art at the time my Contribution is included in the Specification. The following are expressly excluded from and shall not be deemed to constitute Essential Claims: 41 |
  1. 12.4.1. any claims other than as set forth above even if contained in the same patent as Essential Claims; and
  2. 12.4.2. claims which would be infringed only by: 44 |
    - portions of an implementation that are not specified in the normative portions of the Specification, or
    - enabling technologies that may be necessary to make or use any product or portion thereof that complies with the Specification and are not themselves expressly set forth in the Specification (e.g., semiconductor manufacturing technology, compiler technology, object-oriented technology, basic operating system technology, and the like); or
    - the implementation of technology developed elsewhere and merely incorporated by reference in the body of the Specification.
    49 |
  3. 12.4.3. design patents and design registrations.
  52 | For purposes of this definition, the normative portions of the Specification shall be deemed to include only architectural and interoperability requirements. Optional features in the RFC 2119 sense are considered normative unless they are specifically identified as informative. Implementation examples or any other material that merely illustrate the requirements of the Specification are informative, rather than normative.
5. 12.5. I, Me, or My. “I,” “me,” or “my” refers to the signatory.
6. 12.6. Project. “Project” means the W3C Community Group or Business Group for which I executed this CLA.
7. 12.7. Specification. “Specification” means any specification developed by the Project, as of the date my Contribution is first included in that specification. W3C shall provide the authoritative mechanisms for the identification of Specifications created by the Project.
8. 12.8. W3C CLA RF Licensing Requirements. Subject to Section 5, with respect to my Contributions to the Specification, “W3C CLA RF Licensing Requirements” license shall mean a non-assignable, non-sublicensable license to make, have made, use, sell, have sold, offer to sell, import, and distribute and dispose of implementations of my Contributions in the Specification that: 57 |
  1. 12.8.1. shall be available to all, worldwide, whether or not they are W3C Members;
  2. 12.8.2. shall extend to all Essential Claims owned or controlled by me;
  3. 12.8.3. may be limited to implementations of the Specification, and to what is required by the Specification;
  4. 12.8.4. may be conditioned on a grant of a reciprocal RF license (as defined in this policy) to all Essential Claims owned or controlled by the licensee. A reciprocal license may be required to be available to all, and a reciprocal license may itself be conditioned on a further reciprocal license from all.
  5. 12.8.5. may not be conditioned on payment of royalties, fees or other consideration;
  6. 12.8.6. may be suspended with respect to any licensee when licensor is sued by licensee for infringement of claims essential to implement the Specification or any W3C Recommendation;
  7. 12.8.7. may not impose any further conditions or restrictions on the use of any technology, intellectual property rights, or other restrictions on behavior of the licensee, but may include reasonable, customary terms relating to operation or maintenance of the license relationship such as the following: choice of law and dispute resolution;
  8. 12.8.8. shall not be considered accepted by an implementer who manifests an intent not to accept the terms of the W3C CLA RF Licensing Requirements license as offered by the licensor.
  9. 12.8.9. The RF license conforming to the requirements in this policy shall be made available by the licensor as long as the Specification is in effect. The term of such license shall be for the life of the patents in question.
  68 | I am encouraged to provide a contact from which licensing information can be obtained and other relevant licensing information. Any such information will be made publicly available.
9. 12.9. You or Your. “You,” “you,” or “your” means any person or entity who exercises copyright or patent rights granted under this CLA, and any person or entity that person or entity controls.
71 |

73 |

2 |

International World Wide Web Consortium ("W3C")

3 | 4 |

BUSINESS GROUP PARTICIPATION AGREEMENT (the "Agreement") effective as of <{$date}> ("Effective Date"), by and between the Massachusetts Institute of Technology, having an office at 32 Vassar Street, 32-G519, Cambridge, Massachusetts 02139 ("MIT"); the European Research Consortium for Informatics and Mathematics, having an office at 2004, Route des Lucioles, BP 93, F-06902 Sophia Antipolis, France ("ERCIM"); Keio University having an office at 5322 Endo, Fujisawa, Kanagawa 252-0882, Japan ("KEIO"); Beihang University, having an office at No 37 Xueyuan Road, Haidian District, Beijing, China (collectively, "Hosts"); and <{$orgname}>, having an office at <{$orgaddr}> (the "Participant").

5 | 6 |

WHEREAS, the Participant wishes to participate in the <{$bgname}> Business Group ("Business Group") of the International World Wide Web Consortium (the "Consortium"), the purposes of which are more fully set forth in the Business Group proposal and in the then-current Community and Business Group Process, which is hereby incorporated by reference.

7 | 8 |

WHEREAS, the Hosts have agreed to the Participant's participation in the Business Group, subject to said terms and conditions; and

9 | 10 |

WHEREAS, the Participant's participation and cooperation with Members and Hosts under this Agreement will further the instruction and research objectives of Hosts in a manner consistent with their status as non-profit, tax-exempt institutions.

11 | 12 |

NOW, THEREFORE, MIT, ERCIM, KEIO, BEIHANG, AND THE PARTICIPANT AGREE AS FOLLOWS:

13 | 14 |

1. Participation and Fees.

15 | 16 |

17 | a. Business Groups include Consortium Members and non-Members ("Consortium Members" are those parties who have signed the International World Wide Web Consortium Member Agreement). The annual fee for Business Group participation, by Participants who are not Consortium Members ("Fee"), shall be as described on the Business Group Fees table. Participant agrees to pay a separate Fee, and to enter a separate Participation Agreement, for each Group, in which Participant agrees to participate.

18 | 19 |

20 | b. All Participants will be assigned for administrative purposes to a Consortium Host (the "Participant's Host"). Participants with a primary domicile in Europe, Africa and the Middle East, as defined by separate Agreements between the Hosts, shall be Participants with the ERCIM Host ("ERCIM Participants"). Participants with a primary domicile in Japan or Korea shall be Participants with the KEIO Host ("KEIO Participants"). Participants with a primary domicile in the People's Republic of China ("PRC") shall be Participants with the Beihang Host ("BEIHANG Participants"). All other Participants shall be Participants with the MIT Host ("MIT Participants"). 21 |

22 | 23 |

24 | c. The Participant hereby agrees to pay the applicable Fee. The initial Fee of <{$fee}> is due upon signature of this Agreement. For each year in which the Participant renews this Agreement according to Section 2 below, the then-current Fee listed according to Article 1.a shall be due on the anniversary of the first day of the month after W3C announced the creation of the Business Group (the "Anniversary Date"). The Business Group Participant Fee is due annually thereafter on the Anniversary Date for as long as the Business Group continues. Except as provided for in this Agreement, the Fee is non-refundable and shall be payable to the Participant's Host, in the currency stated. 25 |

26 | 27 |

d. The Participant's initial Fee shall be discounted by 50% for the initial year if Participant joins an in-progress Business Group six months or more after the Anniversary Date. 28 |

29 | 30 |

e. If Participant has subsidiaries, the rights and privileges granted under this Agreement shall extend to all subsidiaries the voting stock of which is directly or indirectly at least fifty percent (50%) owned or controlled by Participant.

31 | 32 |

f. For a Participant that is itself a consortium, user society, or otherwise has members or sponsors, the rights and privileges granted under this Agreement shall extend to any number of paid employees of the Participant who are appointed by Participant and to one other individual not employed by the Participant. Additional non-employee participants may be permitted at the discretion of the Consortium.

33 | 34 |

2. Term and Termination.

35 | 36 |

a. The Term shall start on the Effective Date as indicated above. This Agreement shall automatically renew each year on the Anniversary Date for successive one-year terms ("Renewal Terms") beginning on the Anniversary Date unless terminated as described below. 37 |

38 | 39 |

b. The Participant may terminate this Agrement by written notice to the Participant's Host no later than sixty (60) days prior to the Anniversary Date. If the Consortium receives termination notices such that the number of Organizations in the group drops below the threshold required by the Hosts for a Business Group, the Consortium may terminate the group and this Agreement by written notice to the Participant, effective as of the next Anniversary Date.

40 | 41 | 42 |

3. Intellectual Property Rights.

43 | 44 |

Contributions to and outputs from the Business Group shall be governed by the W3C Community Contributor License Agreement (CLA) and W3C Community Final Specification Agreement, both of which are hereby incorporated by reference.

45 | 46 |

Per the Process, participants may choose to license Business Group outputs under the W3C Document License. If the Group chooses the W3C Document License for its output, Participant shall assign the copyrights in its contributions to the Hosts, who shall license the resulting document to the public under the terms of the W3C Document License.

47 | 48 |

4. Use of Names.

49 | 50 |

The Participant will not use the name of MIT, ERCIM, KEIO, or BEIHANG and Hosts will not use the name of Participant in any form of publicity without written permission, which in the case of MIT shall be obtainable from the MIT Technology Licensing Office; in the case of ERCIM, from the Director of Promotion; in the case of KEIO, from the Administrative Director of The Keio Research Institute at SFC; in the case of BEIHANG, from the Institute of Science and Technology of Beihang University; and in the case of the Participant, from __________________________ .

51 | 52 | 53 |

5. Notices.

54 | 55 |

All notices or other communications to or upon either party shall be in writing delivered by first class, air mail or facsimile, dispatched to or given at the following addresses:

56 | 57 |

For MIT:

58 |

                         Susan Westhaver
 59 |                          MIT/CSAIL
 60 |                          32 Vassar Street
 61 |                          Room 32-G514
 62 |                          Cambridge, MA  02139
 63 |                          UNITED STATES

64 | 65 |

For ERCIM:

66 |

                         Philipp Hoschka
 67 |                          GEIE ERCIM Manager
 68 |                          2004, Route des Lucioles
 69 |                          Sophia Antipolis
 70 |                          F-06410 Biot
 71 |                          FRANCE

72 | 73 | 74 |

For KEIO:

75 |

                         Hitoshi Takano, Administrative Director
 76 |                          Keio Research Institute at SFC
 77 |                          Keio University/SFC
 78 |                          5322 Endo
 79 |                          Fujisawa, Kanagawa 252-0882
 80 |                          JAPAN

81 | 82 |

For BEIHANG:

83 |

                         Institute of Science and Technology of Beihang University                         
 84 |                          Room 1121, G Tower of New Main Building Beihang University
 85 |                          No 37 Xueyuan Road
 86 | 			 Haidian District
 87 | 			 Beijing
 88 | 			 CHINA

89 | 90 |

For the Participant:

91 |

 92 |                          __________________________________________
 93 |                          __________________________________________
 94 |                          __________________________________________
 95 |                          __________________________________________
 96 |                          __________________________________________
 97 |                          __________________________________________

98 | 99 |

In the event notices and statements required under this Agreement are sent by certified or registered mail by one party to the party entitled thereto at its above address, they shall be deemed to have been given or made as of the date received.

100 | 101 |

6. Relationship of Parties.

102 | 103 |

The relationship of the parties under this Agreement shall be that of a voluntary association. The Consortium is not a separate legal entity, and this Agreement does not create a partnership or joint venture. Neither MIT, ERCIM, KEIO, BEIHANG, nor the Participant can bind the other or create any relationship of principal or agent.

104 | 105 |

7. Limitation of Liability.

106 | 107 |

In the event of termination of this Agreement by MIT, ERCIM, KEIO, and BEIHANG pursuant to Section 2 hereof, the Participant shall be entitled to receive, as its sole and exclusive remedy, a refund of any portion of the Participant's duly paid and as-yet uncommitted Fee, and upon such refund, any further liability of MIT, ERCIM, KEIO, and/or BEIHANG to the Participant shall be extinguished. This remedy is in lieu of all other remedies, whether oral or written, express or implied. MIT's liability to the Participant in the event of any other claim by Participant shall be limited to the amount of the Participant's duly paid Fee. In no event shall MIT, ERCIM, KEIO, and/or BEIHANG be liable for any indirect, incidental, consequential, or special damages, including lost profits, sustained or incurred by the Participant in connection with or as a result of its participation in the Business Group or under this Agreement.

108 | 109 |

8. Force Majeure.

110 | 111 |

If the performance of any obligation by MIT, ERCIM, KEIO and BEIHANG under this Agreement is prevented, restricted or interfered with by reason of natural disaster, war, revolution, civil commotion, acts of public enemies, blockade, embargo, strikes, any law, order, proclamation, regulation, ordinance, demand or requirement having a legal effect of any government or any judicial authority or representative of any such government, or any other act or event which is beyond the reasonable control of the party affected, then MIT, ERCIM, KEIO and BEIHANG shall be excused from such performance to the extent of such prevention, restriction, or interference, provided that MIT, ERCIM, KEIO, and BEIHANG shall use reasonable commercial efforts to avoid or remove such causes of nonperformance, and shall continue performance hereunder with reasonable dispatch whenever such causes are removed.

112 | 113 |

9. Export Controls.

114 | 115 |

The Participant acknowledges that export and/or re-export from the United States, France, or Japan of technical data, computer software, laboratory prototypes and other commodities ("Controlled Commodities") may be subject to the export control laws and regulation of the United States (including the Arms Export Control Act, as amended, and the Export Administration Act of 1979 revised in 1985), of France, and of Japan, and that such laws and regulations could preclude or delay export of such Controlled Commodities. MIT 's, ERCIM's, KEIO's, and BEIHANG'S obligation hereunder are contingent on compliance with such applicable laws and regulations. Neither party will directly or indirectly export across any national boundary, or communicate or transfer to any third party, any Controlled Commodities without first obtaining any and all licenses that may be required from a cognizant agency of the United States government or the French or Japanese authorities, and/or any and all written assurances from the Participant that it will not re-export or transfer such Controlled Commodities to certain foreign countries or third parties without prior approval of the cognizant government agency. While MIT, ERCIM, KEIO, and BEIHANG agree to cooperate in securing any license which the cognizant agency deems necessary in connection with the export, re-export, transfer or communication of any Controlled Commodities, MIT, ERCIM, KEIO, and BEIHANG cannot guarantee that such licenses will be granted.

116 | 117 |

10. Assignment.

118 | 119 |

Neither this Agreement nor any rights hereunder, in whole or in part, are assignable by the Participant without the prior written consent of the Hosts. Any attempt to assign the rights, duties or obligations under this Agreement by the Participant without such consent shall be a breach of this Agreement and shall be null and void.

120 | 121 |

11. Entire Agreement.

122 | 123 |

This Agreement, together with the process and license documents incorporated by reference, embodies the entire understanding between MIT, ERCIM, KEIO, BEIHANG and the Participant for Participant's participation in the Business Group, and cancels and supersedes any other agreements, oral or written, entered into by the parties hereto as to its subject matter.

124 | 125 |

12. No Modifications.

126 | 127 |

This Agreement may be amended only by a writing signed by MIT, ERCIM, KEIO, BEIHANG and the Participant.

128 | 129 |

13. Governing Law.

130 | 131 |

The venue and governing law of this Agreement shall be that of the Participant's Host, namely: For ERCIM Participants, this Agreement shall be deemed to have been entered into and shall be interpreted and governed in all respects by the laws of France. For KEIO Participants, this Agreement shall be deemed to have been entered into and shall be interpreted and governed in all respects by the laws of Japan. For Beihang Participants, this Agreement shall be deemed to have been entered into and shall be interpreted and governed in all respects by the laws of PRC. For MIT Participants, this Agreement shall be deemed to have been entered into and shall be interpreted and governed in all respects by the laws of The Commonwealth of Massachusetts and the United States of America. 132 |

133 | 134 |

14. Survivability.

135 | 136 |

The obligations of MIT, ERCIM, KEIO, BEIHANG, and Participant under Sections 3-13 of this Agreement shall survive expiration or termination hereof, and shall continue hereafter in full force and effect.

137 | 138 | 139 | 140 |

IN WITNESS WHEREOF, the parties hereto have caused this Agreement to be signed by their duly authorized representatives, effective as of the day and year first above written.

141 | 142 | 143 | 144 | 145 | 146 | 158 | 182 | 183 | 184 |


For the four W3C hosts ____________________, 147 \| Participant's Host 148 \| 149 \| 150 \| By:___________________________ 151 \| 152 \| 153 \| Title: 154 \| 155 \| 156 \| Date:_________________________ 157 \|	Participant 159 \| 160 \| 161 \| By:____________________________ 162 \| 163 \| 164 \| 165 \| 166 \| 167 \| Title:___________________________ 168 \| 169 \| 170 \| 171 \| Address: _________________________ 172 \| 173 \| 174 \| _________________________ 175 \| 176 \| 177 \| Email:___________________________ 178 \| 179 \| 180 \| Date:__________________________ 181 \|

185 |

This document governs participation in W3C Community and Business Groups. For information about other types of groups in W3C, please see the W3C Process Document.

Summary

12 |

14 |
W3C Forum
15 |
17 |
Community Groups
18 |
20 |
Business groups
21 |
23 |
Participation Policies
24 |
26 |
Glossary
27 |

29 |

30 |

System Update: As of 16 July 2015, the W3C Forum is no longer used. Instead, people may discuss proposed Community Groups via comments on the main Community and Business Group blog. 31 |

The W3C Forum is a venue for discussion of Web-related topics including development of specifications. People submit material (a “Community Submission”) to the Forum that they wish to be developed by a Community or Business Group. W3C reserves the right to refuse publication of a Community Submission, for instance if the material is likely to cause offense or confusion.

32 | Individuals who wish to participate in the W3C Forum — enter into discussion or submit proposals — agree to the general communications policies. Participants are responsible for making clear the copyright and patent terms of their submissions. 33 | 34 |

35 |

36 |

Community Submission Publication Policies

37 | Community Submissions must not use a style that will cause them to be confused with W3C Technical Reports. W3C may publish additional policies to govern publication of Community Submissions. 38 | 39 |

40 |

41 |

Community Groups are open to all with no fee. They are designed in particular to provide developers with a place to meet. 42 | 43 |

44 |

45 |

Creation of a Community Group

46 |

Anyone may propose the creation of a Community Group. A proposal is “complete” when:

47 | 48 |

It includes a name for the group (not already taken by a Community Group) and a scope description. The scope should be different than that of any other Community Group (but it may be the same, such as when two communities wish to explore two solutions to the same set of problems).
Five individuals support the creation of the group. The W3C Forum may be used to build this support.

52 | Once a proposal is complete, W3C announces the creation of the group (which includes its software infrastructure). This date is called the “launch date.” 53 | 54 | The Community Development Lead does not formally approve proposals but may reject a proposal for a Community Group when the scope is likely to cause offense or confusion, appears primarily intended for commercial purposes, is frivolous, or is overly broad. 55 | 56 |

57 |

58 |

Community Group Operational Agreements

59 | A Community Group may adopt operational agreements (recorded, for example, in the form of a charter) that establish the group's scope of work, decision-making processes, communications preferences, and other operations. For example, the agreement could establish fair and reasonable criteria for accepting contributions in a specification, or set the group's scope of work (e.g., development of educational materials or discussions about future standards work at W3C). 60 | 61 | The following rules govern Community Group operational agreements: 62 |

They must be publicly documented.
They must be fair and must not unreasonably favor or discriminate against any group participant or their employer.
They must not conflict with or modify this Community and Business Group Process, the Community Contributor License Agreement (CLA), or the Final Specification Agreement.

67 | The person who first proposes a group may establish the group's initial operational agreements. Thereafter, the Chair determines the means by which the group adopts and modifies operational agreements. The Chair must give actual notice to the participants of any material changes to the agreements. Participants may resign from the group if they do not wish to participate under the new agreements. 68 | 69 | Note: W3C encourages groups adopt decision-making policies that promote consensus. 70 | 71 |

72 |

73 |

Joining a Community Group

74 | Anyone may join any Community Group. There are no participation fees. 75 | 76 |

77 |

78 |

Resigning from a Community Group

79 | W3C will provide a mechanism for Participants to resign from a Community Group. Participants that resign from a Community Group incur no new or further obligations after the date of resignation and maintain only those obligations already incurred, and that survive resignation from the Community Group, as provided in the Community Contributor License Agreement (CLA) and, when applicable, the Final Specification Agreement. 80 | 81 |

82 |

83 |

Community Group Chair(s)

84 | Each Community Group must have at least one Chair who is responsible for ensuring the group fulfills the requirements of this document as well as the group's operational agreements. The participants of the Group choose their Chair(s). The Chair(s) are also the primary contacts for the Community Development Lead. 85 | 86 |

87 |

88 |

Duration and Closure of a Community Group

89 | Once a Community Group has been launched, participants may continue to work indefinitely, until the Community Development Lead closes the group; see the grounds for closure. 90 | 91 | No less than ten business days before closing a group, the Community Development Lead must alert the participants. Once closed, no individuals may join, and discussions stop. However, W3C makes available information about closed Community Groups and archives of their communications. 92 | 93 | Closed Community Groups are re-opened following the creation process. 94 | 95 |

96 |

97 |

Grounds for Closure of a Community Group

98 | The Community Development Lead may close a Community Group in any of following circumstances: 99 |

Chair Request. The Group Chair requests that the group be closed (e.g., as the result of a group decision, or on a certain date selected in advance by the group).
Inactivity. The number of participants drops below 3 for an extended period, or because participant activity (e.g., as measured by communications among participants) ceases for an extended period.
Agreement Violations. When, in the judgment of the Community Development Lead, the group has committed a serious violation of this policy, for instance exceeding its scope.

104 | The Community Development Lead and Chair should discuss the group’s status before the Community Development Lead initiates closure. 105 | 106 |

107 |

108 |

Community Group Communications

109 | Each Community Group will have both public and non-public communications mechanisms. The former are for work, the latter for administrative matters (e.g., personal information used in meeting planning). 110 | 111 | To help Community Group participants adhere to the general communications policies, all participants (including the Chair) should help moderate discussion (for instance, to keep the group focused on relevant topics). 112 | 113 | In order to help the community track process, each Community Group is encouraged to summarize accomplishments, barriers to progress, or other challenges from time to time. 114 | 115 | All communications must be archived. 116 | 117 |

118 |

119 |

Community Group Branding

120 | Any Community Group branding (e.g., use of W3C name or logo in ways that may confuse the state of standardization, or technology-specific logo development) is subject to review and approval by the Head of W3C Marketing and Communications. 121 | 122 |

123 |

124 |

Community Group Meeting Policies

125 | A Community Group is not required to hold meetings. However, if it does, then the Chair must ensure that the following happens: 126 |

the meeting is announced to the group in a timely fashion so that people can schedule attendance;
an agenda is posted;
meeting minutes are published, including topics discussions and decisions.

131 |

132 |

133 |

Community Group Deliverables

134 | Community Group deliverables may be anything, including documents, test suites, tutorials, demos, code, discussion, etc. W3C will provide infrastructure to host discussions, code, specifications, test suites, and so on. 135 | 136 | The label "Community Group Report" refers to any document produced by a Group. Some Community Group Reports are Specifications. The following rules apply to Specifications: 137 |

they must be publicly available.
drafts are governed by Community Contributor License Agreement (CLA). W3C will provide a template for including copyright information.
they must include the name the group that published the deliverables and link to a public page about the group.
they must include a publication date.
the history of Contributions (as defined under the CLA) must be archived permanently on the W3C Web site.
They must include boilerplate language required by W3C (e.g., notice that Contributions are made under the CLA and that certain conditions apply).
When published on the W3C site, they must not violate the W3C Privacy Policy.
The content and style of the Specification must not cause confusion about its status, in particular with respect to W3C Technical Reports.

147 | The following rules apply to Final Specifications: 148 |

when they are published, W3C issues a call for participants to sign the Final Specification Agreement.
they must be available in English.
they must be published on the W3C Web site.
Once a Final Specification has been published at a given URI, the Specification must not change.

154 | Other types of deliverables must be publicly available and must be archived permanently. 155 | 156 | W3C reserves the right to refuse publication of deliverables, for instance if the material is likely to cause offense or confusion. W3C may publish additional policies to govern Community Group Specifications. W3C will provide style guides (and style sheets) for Specifications. 157 | 158 |

159 |

160 |

Community Council

161 | The Community Development Lead organizes a Community Council whose mission is: 162 |

to promote the program and ensure that it functions smoothly, and
to help the Community Development Lead fulfill the duties described in this document.

166 | Initially the Community Development Lead selects the Council participants, with an emphasis on representation of diverse interests (public, W3C Membership, staff, other standards organizations, etc.). The Community Development Lead may develop other mechanisms for participant selection. 167 | 168 |

169 |

170 |

Inreach

171 | The Community Council works with existing groups in a variety of ways, including: 172 |

Education of Community Group participants about doing work at W3C. This might involve creation of documentation, videos, or other tools. It might also involve chair training or providing good practice information to Chairs.
Education of the broader community about the work done by Community Groups.
Connections among groups that have shared interests. This might involve organizing joint meetings.

177 |

178 |

179 |

Outreach

180 | The Council promotes broad inclusion and participation by newcomers in a variety of ways, including: 181 |

Promotion of the program in online fora, at events, and in new communities.
Encouraging the creation of language-specific groups, international participation, and online meetings.
Efforts that help avoid confusion with W3C’s standardization process (e.g., through videos or other materials that help explain how to do work at W3C).

186 |

187 |

188 |

Transition to W3C Standards Track

189 | Some (but not all) Community Group and Business Group Specifications are expected to serve as input to a Working Group. When a Community Group or Business Group wishes for a Working Group to adopt one of its Specifications, W3C facilitates the transition to the W3C Standards Track in a number of ways: 190 |

Continuity of IPR commitments. The W3C Community Final Specification Agreement is designed to ensure smooth transition of IPR commitments from Community Groups or Business Groups to Working Groups.
Continuity of participation. When a Working Group takes up a Community Group or Business Group Specification, non-Member employees may continue their participation in the Working Group for a limited duration while their employer makes the transition to Membership. The individual’s employer must have fulfilled the organizational patent requirements of the W3C Community Final Specification Agreement.
Adoption by an Existing Working Group. If W3C has chartered a Working Group with a scope that encompasses the deliverable of a Community Group, the Working Group may adopt it without needing to recharter. Working Group charters created to standardize a Community Group or Business Group Specifications are be reviewed by the Membership following the usual process.

195 | See How to transition work from a Community Group to a Working Group for more information. 196 | 197 |

198 |

199 |

Parallel Activities between a Community Group and a Working Group

200 | A Community Group may continue to exist after a Working Group has been chartered. The Community Group may wish to start experimenting with new ideas for a technology while the Working Group builds consensus and focuses on implementation of a stable set of agreed upon features. 201 | 202 | W3C recommends that once a Working Group has taken up a Community Group or Business Group Specification, the Community or Business Group should no longer develop the same material in parallel. Working Group licensing commitments are limited to the deliverables of the Working Group, so commitments do not follow text that is taken up by other groups (Community Groups or Working Groups). 203 | 204 |

205 |

206 |

207 |

Business Groups are open to all (including companies, non-profits, government agencies, research institutes, individuals), but parties that are not W3C Members pay a fee to participate. That fee is less than W3C Membership and grants fewer benefits. Business Groups are designed to provide stakeholders in particular industries with a forum to develop industry-specific applications of Web technology, to create a strong liaison between a particular industry and the Web community, or to solve an industry-specific issue without an initial assumption of which Web technologies apply.

208 | Business Group policies are the same as Community Groups except where noted below. 209 | 210 |

211 |

212 |

Proposing a Business Group

213 | Business Groups are proposed in the same manner as Community Groups, except that a proposal is not complete until at least five Organizations support creation of the group and the W3C staff has confirmed the expected staff resources will be available. Because goal of Business Groups is to grow the W3C community, we expect Business Groups to have a mix of Member and non-Member Organizations and individuals. 214 | 215 | Note: Business Groups are typically proposed by W3C 216 | staff after extensive discussion about strategic planning, budgeting, 217 | and resource allocation. For this reason, non-staff should not propose 218 | a Business Group without prior discussion with the Community 219 | Development Lead (who will coordinate staff discussion). Without 220 | sufficient discussion and coordination, the Community Development Lead 221 | may choose not to approve a proposed Business Group. 222 | 223 |

224 |

225 |

Joining a Business Group

226 | Joining a Business Group is the same as for a Community Group, except that: 227 |

there is a participation fee (for organizations and individuals), and
participants must also agree to the Business Group Agreement.

231 |

232 |

233 |

Business Group Communications

234 | Each Business Group will have both public and non-public communications mechanisms. The participants decide which channel they use to conduct their work. If the group chooses to conduct its work on non-public channels, the group must maintain a public home page on the W3C site and must provide a public communication about their work at least every six months. This may take the form of a publication, a summary of work, or other form most suitable to keep the community informed of its progress. 235 | 236 |

237 |

238 |

Business Group Deliverables

239 | Deliverables are the same as for Community Groups, except the published documents are called “Business Group Reports”. 240 | 241 |

242 |

243 |

Staff Involvement in Business Groups

244 | Business Groups do not automatically receive staff contacts. W3C management may choose to allocate a small percentage of staff time to consult with Business Groups, facilitate cross-group communication, and help them accomplish their goals. The nature and degree of staff support may vary from group to group. 245 | 246 |

247 |

248 |

These policies are designed to encourage constructive participation and to balance IPR considerations with ease of participation. 249 | 250 | Community Group participants agree to abide by the terms and spirit of the W3C Code of Conduct. 251 | 252 | Violations of Community and Business Group policies should be brought to the attention of the Community Development Lead. The Community Development Lead is authorized to ban participants for violations of this policy or the signed Agreements, and also to reinstate them. Banned participants may appeal to the W3C CEO. 253 | 254 |

255 |

256 |

Summary of Copyright and Patent Policies for Community Groups

257 | The legal policies designed for Community Groups seek to balance the concerns of both implementers and intellectual property (IPR) holders. Please see the Patent and Copyright Policy Summary, which covers the W3C Community Contributor License Agreement (CLA) and the W3C Community Final Specification Agreement. 258 | 259 | W3C has a preference for organizational, rather than individual commitments. Requests to participate in an individual capacity without a corresponding organizational commitment will be subject to approval by the W3C staff; such approval to be granted or denied in the W3C Staff’s sole discretion. See the Guidelines for Evaluating Individual Requests to Participate in a Group. 260 |

261 |

262 |

General Communications Policies

263 | All Participants agree to the following general communications policies: 264 |

Participants must have an identity within the community.
Communications must not be disruptive. Participants must refrain from defaming, harassing or otherwise offending other participants or their organizations.
Participants must not send unsolicited commercial messages or other promotional activities for personal matters or for third parties.
Participants must respect confidentiality levels of communications.

270 |

271 |

272 |

273 |

Community Development Lead

The individual responsible for the Community Group program. The Community Development Lead, appointed by the W3C Management, is responsible for: 276 |

Monitoring the W3C Forum
Managing escalation of issues
Managing the composition and operations of the Community Council
Serving as liaison to the W3C Staff (e.g., for outreach opportunities)

282 |

Community Council

This task force assists existing community groups (e.g., in how the standards process works, accessibility input early in the development of the specification) and proactively seeks opportunities to engage with communities outside W3C, to find and communicate opportunities for liaisons.

Community Submission

Community Submissions are proposals made in the W3C Forum.

Community Group or Business Group Report

A Community or Business Group Report is a document (specification or other type) produced by a Community or Business Group.

W3C Forum

A single global public forum where anyone may begin to generate interest around new ideas.

292 |

293 |

	Working	Interest	Community	Business
Scope	Determined by Charter	Determined by Charter	Determined by scope statement	Application of technology to business context; requirements and use cases; input to standards process
Creation process	Team proposes charter to Membership	Team proposes charter to Membership	Proposal is complete	Proposal is complete and management approves resource allocation
Duration	Limited by charter, may be extended	Limited by charter, may be extended	Unlimited	Unlimited
Primary Deliverable	Standards-track and supporting	Note (which may become a Statement)	Community Group Report (e.g., a technology innovation from a small set of developers). Community Groups Reports are not standards-track documents.	Business Group Report (e.g., use cases or requirements of a particular industry to be provided as input to a Working Group). Business Groups Reports are not standards-track documents.
Staff Contact	Yes	Yes	Not generally; but see W3C Team support for W3C Community Groups	Consulting role (e.g., share expertise, but not likely to attend meetings regularly). But determined by W3C Management on a case-by-case basis.
Other Staff Interactions	Background support and coordination	Background support and coordination (for some)	Monitoring, Outreach	55 \| 56 \| One project review with Team annually 57 \| Light Monitoring by staff 58 \| Liaison role as needed 59 \| Communications of final reports through W3C news channels and to W3C Membership 60 \| 61 \|
Fee to participate or organize	Membership or Invited Expert (no fee)	Membership or Invited Expert (no fee)	None	Annual fees for non-Members
Confidentiality of activities	Public	Generally Public	Public	Public or non-Public
Patent Licensing Commitment for this Group's Deliverables	Defined in Section 3 of W3C Patent Policy	No	Defined in section 3 of W3C Community Contributor License Agreement (CLA) or Final Specification Agreement	Defined in section 3 of W3C Community Contributor License Agreement (CLA) or Final Specification Agreement
Patent Disclosure Obligation	Defined in Section 6 of W3C Patent Policy	Defined in Section 6 of W3C Patent Policy	Defined in Section 6 of W3C Patent Policy; no new obligations under CLA/FSA	Defined in Section 6 of W3C Patent Policy; no new obligations under CLA/FSA
Copyright for documents	Specified in charter	Specified in charter	W3C Community Contributor License Agreement (CLA), Final Specification Agreement	W3C Community Contributor License Agreement (CLA), Final Specification Agreement or W3C Document License
Copyright for software	W3C Software License generally	W3C Software License generally	Group determines, but expectation is compatibility with Open Source Software Licenses.	Group determines, but expectation is compatibility with Open Source Software Licenses.
Chair selection	Appointed by Team	Appointed by Team	Group determines	Group determines
Access to Member site	For IEs depends on charter	For IEs Depends on charter	No	No
Decision-making based on consensus	Required	Required where applicable	Recommended where applicable	Recommended where applicable
Expectations regarding scope overlap with other groups	Actively avoided	Actively avoided	Acceptable but not recommended	Acceptable but not recommended

Summary of Key License Terms

What Signers Give under the Final Specification Agreement (FSA)

What the Community Gets

Use of Trademark

Representations, Warranties and Disclaimers

Summary of Key License Terms

What Contributors Give under the CLA

What the Community Gets

Use of Trademark

Representations, Warranties and Disclaimers

Considerations

Formal Identification

Style Sheets

Logos

Name and Date

Relation to Standards Track

Copyright

Boilerplate

Patent Licensing Commitments

Privacy Policy

Additional Requirements for Final Reports

Goals of the Policies

General Overview

Copyright Summary

Patent Licensing Summary

Transition to W3C Standards Track

Additional Resources

International World Wide Web Consortium ("W3C")

1. Participation and Fees.

2. Term and Termination.

3. Intellectual Property Rights.

4. Use of Names.

5. Notices.

6. Relationship of Parties.

7. Limitation of Liability.

8. Force Majeure.

9. Export Controls.

10. Assignment.

11. Entire Agreement.

12. No Modifications.

13. Governing Law.

14. Survivability.

Summary

W3C Forum

Community Groups

Business groups

Participation Policies

Glossary

Community Submission Publication Policies

Creation of a Community Group

Community Group Operational Agreements

Joining a Community Group

Resigning from a Community Group

Community Group Chair(s)

Duration and Closure of a Community Group

Grounds for Closure of a Community Group

Community Group Communications

Community Group Branding

Community Group Meeting Policies

Community Group Deliverables

Community Council

Inreach

Outreach

Transition to W3C Standards Track

Parallel Activities between a Community Group and a Working Group

Proposing a Business Group

Joining a Business Group

Business Group Communications

Business Group Deliverables

Staff Involvement in Business Groups

Summary of Copyright and Patent Policies for Community Groups

General Communications Policies