--- a/cover.html Mon Jul 11 00:07:25 2016 +0200
+++ b/cover.html Mon Jul 11 00:14:02 2016 +0200
@@ -17,22 +17,22 @@
</style> <!--[if lt IE 9]><script src='undefined://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
</head>
<body>
- <div class="head"><a href="http://www.w3.org/"><img alt="W3C" src="https://www.w3.org/Icons/w3c_home" height="48" width="72"></a>
+ <div class="head"><a href="https://www.w3.org/"><img alt="W3C" src="https://www.w3.org/Icons/w3c_home" height="48" width="72"></a>
<h1>W3C Draft Process Document</h1>
<h2 class="notoc">10 July 2016 Editor's Draft</h2>
<dl>
<dt>Latest Editor's version:</dt>
<dd> <a href="https://dvcs.w3.org/hg/AB/raw-file/default/cover.html">https://dvcs.w3.org/hg/AB/raw-file/default/cover.html</a></dd>
<dt>Latest operative version:</dt>
- <dd><a href="http://www.w3.org/Consortium/Process/">http://www.w3.org/Consortium/Process/</a></dd>
+ <dd><a href="https://www.w3.org/Consortium/Process/">https://www.w3.org/Consortium/Process/</a></dd>
<dt>Editor:</dt>
<dd>Charles McCathie Nevile, <a style="color:black" href="http://yandex.com"><span style="color: red;">Y</span>andex</a>—<a style="color:black"
href="http://yandex.ru"><span style="color: red;">Я</span>ндекс</a></dd>
<dt>Previous editor:</dt>
- <dd>Ian Jacobs, <a href="http://www.w3.org/">W3C</a></dd>
+ <dd>Ian Jacobs, <a href="https://www.w3.org/">W3C</a></dd>
</dl>
- <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1996-2016 <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
- (<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr
+ <p class="copyright"><a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1996-2016 <a href="/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
+ (<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="http://www.ercim.eu/"><abbr
title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>, <a href="http://www.keio.ac.jp/">Keio</a>,
<a href="http://ev.buaa.edu.cn/">Beihang</a>), All Rights Reserved. W3C <a href="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a rel="Copyright" href="/Consortium/Legal/copyright-documents">document
@@ -45,26 +45,26 @@
common protocols that promote its evolution and ensure its interoperability. The W3C Process Document describes the organizational
structure of the W3C and the processes related to the responsibilities and functions they exercise to enable W3C to accomplish its
mission. This document does not describe the internal workings of the Team or W3C's public communication mechanisms.</p>
- <p>For more information about the W3C mission and the history of W3C, please refer to <a href="http://www.w3.org/Consortium/">About W3C</a>
+ <p>For more information about the W3C mission and the history of W3C, please refer to <a href="https://www.w3.org/Consortium/">About W3C</a>
[<a href="#ref-mission">PUB15</a>].</p>
<h2 class="notoc" id="status">Status of this Document</h2>
- <p>W3C, including all existing chartered groups, follows the <a href="http://www.w3.org/Consortium/Process/">most recent operative
+ <p>W3C, including all existing chartered groups, follows the <a href="https://www.w3.org/Consortium/Process/">most recent operative
Process Document</a> announced to the Membership.</p>
- <p>This document is developed by the Advisory Board's Process Task Force (which anyone may join) working within the <a href="http://www.w3.org/community/w3process/">Revising
+ <p>This document is developed by the Advisory Board's Process Task Force (which anyone may join) working within the <a href="https://www.w3.org/community/w3process/">Revising
W3C Process Community Group</a>. This is the 10 July 2016 Editor's draft for the proposed next version of the W3C Process Document.
This document is based on the 1 September 2015 Process.</p>
<p>This draft is expected to be proposed to the Advisory Committee for a formal AC review on whether to adopt this as the new operative
Process document. Further revision to the Process is expected as needed.</p>
<p>A <a href="#changes">change history</a>
(compared to the current 1 September 2015 Process Document) forms part of this draft.</p>
- <p>Comment is invited on the draft. Please send comments to <a href="mailto:public-w3process@w3.org">public-w3process@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-w3process/">Mailing
- list archive</a>, publicly available) or to process-issues@w3.org (<a href="http://lists.w3.org/Archives/Member/process-issues">Member-only
+ <p>Comment is invited on the draft. Please send comments to <a href="mailto:public-w3process@w3.org">public-w3process@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-w3process/">Mailing
+ list archive</a>, publicly available) or to process-issues@w3.org (<a href="https://lists.w3.org/Archives/Member/process-issues">Member-only
archive</a>). A <a href="https://www.w3.org/community/w3process/track/">Public Issue Tracker</a> and <a href="https://dvcs.w3.org/hg/AB/">detailed
changelogs</a> are available online. </p>
<h2 class="notoc" id="pp">Relation of Process Document to Patent Policy</h2>
- <p>W3C Members' attention is called to the fact that provisions of the Process Document are binding on Members per the <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
- Agreement</a> [<a href="#ref-member-agreement">PUB6</a>]. The Patent Policy <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ <p>W3C Members' attention is called to the fact that provisions of the Process Document are binding on Members per the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+ Agreement</a> [<a href="#ref-member-agreement">PUB6</a>]. The Patent Policy <a href="https://www.w3.org/Consortium/Patent-Policy">W3C
Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>] is incorporated by normative reference as a part of the Process Document,
and is thus equally binding.</p>
<p>The Patent Policy places additional obligations on Members, Team, and other participants in W3C. The Process Document does not
@@ -323,7 +323,7 @@
<p>W3C Members are primarily represented in W3C processes as follows:</p>
<ol>
<li>The <a href="#AC">Advisory Committee</a> is composed of one representative from each Member organization (refer to the <a href="#Member-only">Member-only</a>
- list of <a href="http://www.w3.org/Member/ACList">current Advisory Committee representatives</a> [<a href="#ref-current-ac">MEM1</a>]).
+ list of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a> [<a href="#ref-current-ac">MEM1</a>]).
The Advisory Committee:
<ul>
<li>reviews plans for W3C at each <a href="#ACMeetings">Advisory Committee meeting</a>;</li>
@@ -336,9 +336,9 @@
<li>Representatives of Member organizations participate in <a href="#GAGeneral">Working Groups and Interest Groups</a> and author
and review <a href="#Reports">technical reports</a>.</li>
</ol>
- <p id="MemberSubscription">W3C membership is open to all entities, as described in "<a href="http://www.w3.org/Consortium/join">How to
- Join W3C</a>" [<a href="#ref-join-w3c">PUB5</a>]; (refer to the public list of <a href="http://www.w3.org/Consortium/Member/List">current
- W3C Members</a> [<a href="#ref-current-mem">PUB8</a>]). Organizations subscribe according to the <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+ <p id="MemberSubscription">W3C membership is open to all entities, as described in "<a href="https://www.w3.org/Consortium/join">How to
+ Join W3C</a>" [<a href="#ref-join-w3c">PUB5</a>]; (refer to the public list of <a href="https://www.w3.org/Consortium/Member/List">current
+ W3C Members</a> [<a href="#ref-current-mem">PUB8</a>]). Organizations subscribe according to the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
Agreement</a> [<a href="#ref-member-agreement">PUB6</a>]. The <a href="#Team">Team</a> <em class="rfc2119">must</em> ensure that
Member participation agreements remain <a href="#Team-only">Team-only</a> and that no Member receives preferential treatment within
W3C.</p>
@@ -352,7 +352,7 @@
<li>Access to <a href="#Member-only">Member-only</a> information;</li>
<li>The <a href="#Submission">Member Submission</a> process;</li>
<li>Use of the W3C Member logo on promotional material and to publicize the Member's participation in W3C. For more information,
- please refer to the Member logo usage policy described in the <a href="http://www.w3.org/Member/Intro">New Member Orientation</a>
+ please refer to the Member logo usage policy described in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a>
[<a href="#ref-new-member">MEM4</a>].</li>
</ul>
<p>Furthermore, representatives of Member organizations participate in W3C as follows:</p>
@@ -361,7 +361,7 @@
<li>In <a href="#GAEvents">Workshops and Symposia</a>;</li>
<li>On the Team, as <a href="#fellows">W3C Fellows</a>.</li>
</ul>
- <p>In the case (described in paragraph 5g of the <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
+ <p>In the case (described in paragraph 5g of the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership
Agreement</a>), where a Member organization is itself a consortium, user society, or otherwise has members or sponsors, the
organization's paid staff and Advisory Committee representative exercise all the rights and privileges of W3C membership. In
addition, the Advisory Committee representative <em class="rfc2119">may</em> designate up to four (or more at the Team's
@@ -373,7 +373,7 @@
majority of W3C Members faithfully follow the spirit as well as the letter of these processes. When serious and/or repeated
violations do occur, and repeated attempts to address these violations have not resolved the situation, the Director <em class="rfc2119">may</em>
take disciplinary action. Arbitration in the case of further disagreement is governed by paragraph 19 of the Membership Agreement.
- Refer to the <a href="http://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a> [<a href="#ref-discipline-gl">MEM14</a>].</p>
+ Refer to the <a href="https://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a> [<a href="#ref-discipline-gl">MEM14</a>].</p>
<h4 id="MemberRelated">2.1.2 Related Members</h4>
<p>In the interest of ensuring the integrity of the consensus process, Member involvement in some of the processes in this document is
affected by related Member status. As used herein, two Members are related if:</p>
@@ -384,17 +384,17 @@
</ol>
<p>A <em>subsidiary</em> is an organization of which effective control and/or majority ownership rests with another, single
organization.</p>
- <p>Related Members <em class="rfc2119">must</em> disclose these relationships according to the mechanisms described in the <a href="http://www.w3.org/Member/Intro">New
+ <p>Related Members <em class="rfc2119">must</em> disclose these relationships according to the mechanisms described in the <a href="https://www.w3.org/Member/Intro">New
Member Orientation</a> [<a href="#ref-new-member">MEM4</a>].</p>
<h4 id="AC">2.1.3 Advisory Committee (AC)</h4>
- <p>When an organization joins W3C (see "<a href="http://www.w3.org/Consortium/join">How to Join W3C</a>" [<a href="#ref-join-w3c">PUB5</a>]),
- it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement. The <a href="http://www.w3.org/Member/Intro">New
+ <p>When an organization joins W3C (see "<a href="https://www.w3.org/Consortium/join">How to Join W3C</a>" [<a href="#ref-join-w3c">PUB5</a>]),
+ it <em class="rfc2119">must</em> name its Advisory Committee representative as part of the Membership Agreement. The <a href="https://www.w3.org/Member/Intro">New
Member Orientation</a> explains how to subscribe or unsubscribe to Advisory Committee mailing lists, provides information about
Advisory Committee meetings, explains how to name a new Advisory Committee representative, and more. Advisory Committee
representatives <em class="rfc2119">must</em> follow the <a href="#coi">conflict of interest policy</a> by disclosing information
according to the mechanisms described in the New Member Orientation. See also the additional roles of Advisory Committee
- representatives described in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
- <p>Additional information for Members is available at the <a href="http://www.w3.org/Member/">Member Web site</a> [<a href="#ref-member-web">MEM6</a>].</p>
+ representatives described in the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+ <p>Additional information for Members is available at the <a href="https://www.w3.org/Member/">Member Web site</a> [<a href="#ref-member-web">MEM6</a>].</p>
<h5 id="ACCommunication">2.1.3.1 Advisory Committee Mailing Lists</h5>
<p>The Team <em class="rfc2119">must</em> provide two mailing lists for use by the Advisory Committee:</p>
<ol>
@@ -436,11 +436,11 @@
<p>The Team <em class="rfc2119">must</em> announce the date and location of each Advisory Committee meeting no later than at the end
of the previous meeting; <span class="time-interval">one year's</span> notice is preferred. The Team <em class="rfc2119">must</em>
announce the region of each Advisory Committee meeting at least <span class="time-interval">one year</span> in advance.</p>
- <p>More information about <a href="http://www.w3.org/Member/Meeting/">Advisory Committee meetings</a> [<a href="#ref-ac-meetings">MEM5</a>]
+ <p>More information about <a href="https://www.w3.org/Member/Meeting/">Advisory Committee meetings</a> [<a href="#ref-ac-meetings">MEM5</a>]
is available at the Member Web site.</p>
<h3 id="Team">2.2 The W3C Team</h3>
<p>The Team consists of the Director, CEO, W3C paid staff, unpaid interns, and W3C Fellows. <dfn id="fellows">W3C Fellows</dfn> are
- Member employees working as part of the Team; see the <a href="http://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows
+ Member employees working as part of the Team; see the <a href="https://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows
Program</a> [<a href="#ref-fellows">PUB32</a>]. The Team provides technical leadership about Web technologies, organizes and
manages W3C activities to reach goals within practical constraints (such as resources available), and communicates with the Members
and the public about the Web and W3C technologies.</p>
@@ -463,7 +463,7 @@
Submissions</a> (e.g., in <a href="#SubmissionScope">expected scope</a>). However, there is no additional Team comment. The <a href="#DocumentStatus">document
status section</a> of a Team Submission indicates the level of Team consensus about the published material.</p>
<p>Team Submissions are <strong>not</strong> part of the <a href="#Reports">technical report development process</a>.</p>
- <p>The list of <a href="http://www.w3.org/TeamSubmission/">published Team Submissions</a> [<a href="#ref-team-submission-list">PUB16</a>]
+ <p>The list of <a href="https://www.w3.org/TeamSubmission/">published Team Submissions</a> [<a href="#ref-team-submission-list">PUB16</a>]
is available at the W3C Web site.</p>
<h3 id="AB">2.3 Advisory Board (AB)</h3>
<p>Created in March 1998, the Advisory Board provides ongoing guidance to the Team on issues of strategy, management, legal matters,
@@ -479,7 +479,7 @@
group Chairs. The Advisory Board <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory
Committee meeting</a>.</p>
<p>Details about the Advisory Board (e.g., the list of Advisory Board participants, mailing list information, and summaries of
- Advisory Board meetings) are available at the <a href="http://www.w3.org/2002/ab/">Advisory Board home page</a> [<a href="#ref-ab-home">PUB30</a>].</p>
+ Advisory Board meetings) are available at the <a href="https://www.w3.org/2002/ab/">Advisory Board home page</a> [<a href="#ref-ab-home">PUB30</a>].</p>
<h4 id="ABParticipation">2.3.1 Advisory Board Participation</h4>
<p>The Advisory Board consists of nine elected participants and a Chair. The Team appoints the Chair of the <a href="#AB">Advisory
Board</a>, who is generally the <a href="#def-W3CChair">CEO</a>.</p>
@@ -501,7 +501,7 @@
architecture; see also the <a href="#AB">Advisory Board</a>.</p>
<p>The TAG's scope is limited to technical issues about Web architecture. The TAG <em class="rfc2119">should not</em> consider
administrative, process, or organizational policy issues of W3C, which are generally addressed by the W3C Advisory Committee,
- Advisory Board, and Team. Please refer to the <a href="http://www.w3.org/2001/07/19-tag">TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
+ Advisory Board, and Team. Please refer to the <a href="https://www.w3.org/2001/07/19-tag">TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
for more information about the background and scope of the TAG, and the expected qualifications of TAG participants.</p>
<p>The Team <em class="rfc2119">must</em> make available two mailing lists for the TAG:</p>
<ul>
@@ -516,10 +516,10 @@
Committee and other group Chairs. The TAG <em class="rfc2119">should</em> also report on its activities at each <a href="#ACMeetings">Advisory
Committee meeting</a>.</p>
<p>When the TAG votes to resolve an issue, each TAG participant (whether appointed, elected, or the Chair) has one vote; see also the
- section on <a href="http://www.w3.org/2001/07/19-tag#Voting">voting in the TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
+ section on <a href="https://www.w3.org/2001/07/19-tag#Voting">voting in the TAG charter</a> [<a href="#ref-tag-charter">PUB25</a>]
and the general section on <a href="#Votes">votes</a> in this Process Document.</p>
<p>Details about the TAG (e.g., the list of TAG participants, mailing list information, and summaries of TAG meetings) are available
- at the <a href="http://www.w3.org/2001/tag/">TAG home page</a> [<a href="#ref-tag-home">PUB26</a>].</p>
+ at the <a href="https://www.w3.org/2001/tag/">TAG home page</a> [<a href="#ref-tag-home">PUB26</a>].</p>
<h4 id="tag-participation">2.4.1 Technical Architecture Group Participation</h4>
<p>The TAG consists of eight elected or appointed participants and a Chair. The Team appoints the Chair of the TAG, who is generally
the <a href="#def-Director">Director</a>.</p>
@@ -541,9 +541,9 @@
seat is <a href="#AB-TAG-vacated">vacated</a>. Although Advisory Board and TAG participants do not advocate for the commercial
interests of their employers, their participation does carry the responsibilities associated with Member representation, Invited
Expert status, or Team representation (as described in the section on the <a href="#AB-TAG-elections">AB/TAG nomination and
- election process</a>). See also the licensing obligations on TAG participants in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
- 3</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
- and the claim exclusion process of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section 4</a>.</p>
+ election process</a>). See also the licensing obligations on TAG participants in <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+ 3</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
+ and the claim exclusion process of <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section 4</a>.</p>
<h4 id="AB-TAG-constraints">2.5.1 Advisory Board and Technical Architecture Group Participation Constraints</h4>
<p>Given the few seats available on the Advisory Board and the TAG, and in order to ensure that the diversity of W3C Members is
represented:</p>
@@ -606,7 +606,7 @@
a short term, the <a href="#random">verifiable random selection procedure</a> described below will be used to assign the
short term.</p>
- <p>Refer to <a href="http://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a>
+ <p>Refer to <a href="https://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a>
[<a href="#ref-election-howto">MEM15</a>] for more details.</p>
<h5 id="random">2.5.2.1 Verifiable Random Selection Procedure</h5>
@@ -653,8 +653,8 @@
</ol>
<p>Advisory Committee representatives who nominate individuals from their organization for participation in W3C activities are
responsible for assessing and attesting to the qualities of those nominees.</p>
- <p>See also the participation requirements described in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section 6</a>
- of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+ <p>See also the participation requirements described in <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section 6</a>
+ of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
<h4 id="coi">3.1.1 Conflict of Interest Policy</h4>
<p>Individuals participating materially in W3C work <em class="rfc2119">must</em> disclose significant relationships when those
relationships might reasonably be perceived as creating a conflict of interest with the individual's role at W3C. These disclosures
@@ -674,7 +674,7 @@
<li>A position on a publicly visible advisory body, even if no decision making authority is involved.</li>
</ul>
<p>Individuals seeking assistance on these matters <em class="rfc2119">should</em> contact the Team.</p>
- <p>Team members are subject to the <a href="http://www.w3.org/2000/09/06-conflictpolicy">W3C Team conflict of interest policy</a> [<a
+ <p>Team members are subject to the <a href="https://www.w3.org/2000/09/06-conflictpolicy">W3C Team conflict of interest policy</a> [<a
href="#ref-coi">PUB23</a>].</p>
<h4 id="member-rep">3.1.2 Individuals Representing a Member Organization</h4>
<p>Generally, individuals representing a Member in an official capacity within W3C are employees of the Member organization. However,
@@ -861,7 +861,7 @@
<h3 id="resignation">3.6 Resignation from a Group</h3>
<p>A W3C Member or Invited Expert <em class="rfc2119">may</em> resign from a group. On written notification from an Advisory
Committee representative or Invited Expert to the team, the Member and their representatives or the Invited Expert will be deemed to
- have resigned from the relevant group. See section 4.2. of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
+ have resigned from the relevant group. See section 4.2. of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent
Policy</a> [<a href="#ref-patentpolicy">PUB33</a>] for information about obligations remaining after resignation from certain
groups.</p>
<section id="chapterDissemination">
@@ -872,17 +872,17 @@
<p>The Team makes every effort to ensure the persistence and availability of the following public information:</p>
<ul>
<li><a href="#Reports">W3C technical reports</a> whose publication has been approved by the Director. Per the Membership
- Agreement, W3C technical reports (and software) are available free of charge to the general public; (refer to the <a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C
+ Agreement, W3C technical reports (and software) are available free of charge to the general public; (refer to the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C
Document License</a> [<a href="#ref-doc-license">PUB18</a>]).</li>
- <li>A <a href="http://www.w3.org/Consortium/mission">mission statement</a> [<a href="#ref-mission">PUB15</a>] that explains the
+ <li>A <a href="https://www.w3.org/Consortium/mission">mission statement</a> [<a href="#ref-mission">PUB15</a>] that explains the
purpose and mission of W3C, the key benefits for Members, and the organizational structure of W3C.</li>
- <li>Legal documents, including the <a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> [<a
+ <li>Legal documents, including the <a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a> [<a
href="#ref-member-agreement">PUB6</a>]) and documentation of any legal commitments W3C has with other entities.</li>
<li>The Process Document.</li>
<li>Public results of W3C activities and <a href="#GAEvents">Workshops</a>.</li>
</ul>
<p>To keep the Members abreast of W3C meetings, Workshops, and review deadlines, the Team provides them with a regular (e.g.,
- weekly) news service and maintains a <a href="http://www.w3.org/Member/Eventscal">calendar</a> [<a href="#ref-calendar">MEM3</a>]
+ weekly) news service and maintains a <a href="https://www.w3.org/Member/Eventscal">calendar</a> [<a href="#ref-calendar">MEM3</a>]
of official W3C events. Members are encouraged to send schedule and event information to the Team for inclusion on this calendar.</p>
<h3 id"confidentiality-levels"="">4.1 Confidentiality Levels</h3>
<p>There are three principal levels of access to W3C information (on the W3C Web site, in W3C meetings, etc.): public, Member-only,
@@ -906,7 +906,7 @@
representatives</a> and other individuals employed by the Member who are considered appropriate recipients. For instance, it is
the responsibility of the Advisory Committee representative and other employees and official representatives of the organization
to ensure that Member-only news announcements are distributed for internal use only within their organization. Information about
- Member mailing lists is available in the <a href="http://www.w3.org/Member/Intro">New Member Orientation</a>.</p>
+ Member mailing lists is available in the <a href="https://www.w3.org/Member/Intro">New Member Orientation</a>.</p>
<h4 id="confidentiality-change">4.1.1 Changing Confidentiality Level</h4>
<p>As a benefit of membership, W3C provides some Team-only and Member-only channels for certain types of communication. For example,
Advisory Committee representatives can send <a href="#ACReview">reviews</a> to a Team-only channel. However, for W3C processes
@@ -934,7 +934,7 @@
<ol>
<li><a href="#GroupsWG">Working Groups.</a> Working Groups typically produce deliverables (e.g., <a href="#rec-advance">Recommendation
Track technical reports</a>, software, test suites, and reviews of the deliverables of other groups). There are additional
- participation requirements described in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</li>
+ participation requirements described in the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</li>
<li><a href="#GroupsIG">Interest Groups.</a> The primary goal of an Interest Group is to bring together people who wish to
evaluate potential Web technologies and policies. An Interest Group is a forum for the exchange of ideas.</li>
</ol>
@@ -949,14 +949,14 @@
tasks. The Director appoints (and re-appoints) Chairs for all groups. The Chair is a <a href="#member-rep">Member representative</a>,
a <a href="#Team">Team representative</a>, or an <a href="#invited-expert-wg">Invited Expert</a> (invited by the Director). The
requirements of this document that apply to those types of participants apply to Chairs as well. The <a href="/Guide/chair-roles">role
- of the Chair [MEM14]</a> is described in the <a href="http://www.w3.org/Guide/">Member guide</a> [<a href="#ref-guide">MEM9</a>].</p>
+ of the Chair [MEM14]</a> is described in the <a href="https://www.w3.org/Guide/">Member guide</a> [<a href="#ref-guide">MEM9</a>].</p>
<p>Each group <em class="rfc2119">must</em> have a <dfn id="TeamContact">Team Contact</dfn>, who acts as the interface between the
Chair, group participants, and the rest of the Team. The <a href="/Guide/staff-contact">role of the Team Contact</a> is described
in the Member guide. The Chair and the Team Contact of a group <em class="rfc2119">should not</em> be the same individual.</p>
<p>Each group <em class="rfc2119">must</em> have an archived mailing list for formal group communication (e.g., for meeting
announcements and minutes, documentation of decisions, and <a href="#FormalObjection">Formal Objections</a> to decisions). It is
the responsibility of the Chair and Team Contact to ensure that new participants are subscribed to all relevant mailing lists.
- Refer to the list of <a href="http://www.w3.org/Member/Mail/">group mailing lists</a> [<a href="#ref-mailing-lists">MEM2</a>].</p>
+ Refer to the list of <a href="https://www.w3.org/Member/Mail/">group mailing lists</a> [<a href="#ref-mailing-lists">MEM2</a>].</p>
<p>A Chair <em class="rfc2119">may</em> form task forces (composed of group participants) to carry out assignments for the group.
The scope of these assignments <em class="rfc2119">must not</em> exceed the scope of the group's charter. A group <em class="rfc2119">should</em>
document the process it uses to create task forces (e.g., each task force might have an informal "charter"). Task forces do not
@@ -976,8 +976,8 @@
group; see also the <a href="#ParticipationCriteria">individual participation criteria</a>.</p>
<p>A participant <em class="rfc2119">must</em> represent at most one organization in a Working Group or Interest Group.</p>
<p>An individual <em class="rfc2119">may</em> become a Working or Interest Group participant at any time during the group's
- existence. See also relevant requirements in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-join">section 4.3</a> of the
- <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+ existence. See also relevant requirements in <a href="https://www.w3.org/Consortium/Patent-Policy#sec-join">section 4.3</a> of the
+ <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
<p>On an exceptional basis, a Working or Interest Group participant <em class="rfc2119">may</em> designate a <dfn id="mtg-substitute">substitute</dfn>
to attend a <a href="#GeneralMeetings">meeting</a> and <em class="rfc2119">should</em> inform the Chair. The substitute <em class="rfc2119">may</em>
act on behalf of the participant, including for <a href="#Votes">votes</a>. For the substitute to vote, the participant <em class="rfc2119">must</em>
@@ -988,9 +988,9 @@
area defined by the charter. In principle, Interest Groups have no limit on the number of participants. When a Working Group grows
too large to be effective, W3C <em class="rfc2119">may</em> split it into an Interest Group (a discussion forum) and a much
smaller Working Group (a core group of highly dedicated participants).</p>
- <p>See also the licensing obligations on Working Group participants in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
- 3</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
- and the patent claim exclusion process of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section 4</a>.</p>
+ <p>See also the licensing obligations on Working Group participants in <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+ 3</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
+ and the patent claim exclusion process of <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Exclusion">section 4</a>.</p>
<h5>5.2.1.1 <dfn id="member-rep-wg">Member Representative</dfn> in a Working Group</h5>
<p>An individual is a Member representative in a Working Group if all of the following conditions are satisfied:</p>
<ul>
@@ -1001,7 +1001,7 @@
<p><dfn id="member-rep-info">To designate an individual as a Member representative in a Working Group</dfn>, an Advisory Committee
representative <em class="rfc2119">must</em> provide the Chair and Team Contact with all of the following information, in
addition to any other information required by the <a href="#cfp">Call for Participation</a> and charter (including the
- participation requirements of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]):</p>
+ participation requirements of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]):</p>
<ol>
<li>The name of the W3C Member the individual represents and whether the individual is an employee of that Member organization;</li>
<li>A statement that the individual accepts the participation terms set forth in the charter (with an indication of charter date
@@ -1045,11 +1045,11 @@
do all of the following:</p>
<ul>
<li>identify the organization, if any, the individual represents as a participant in this group,</li>
- <li>agree to the terms of the <a href="http://www.w3.org/Consortium/Legal/collaborators-agreement">invited expert and
+ <li>agree to the terms of the <a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">invited expert and
collaborators agreement</a> [<a href="#ref-invited-expert">PUB17</a>],</li>
- <li>accept the participation terms set forth in the charter (including the participation requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
- 3</a> (especially 3.4) and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section 6</a> (especially
- 6.10) of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]).
+ <li>accept the participation terms set forth in the charter (including the participation requirements of <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section
+ 3</a> (especially 3.4) and <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Disclosure">section 6</a> (especially
+ 6.10) of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]).
Indicate a specific charter date or version,</li>
<li>disclose whether the individual is an employee of a W3C Member; see the <a href="#coi">conflict of interest policy</a>,</li>
<li>provide a statement of who will provide the necessary financial support for the individual's participation (e.g., for travel,
@@ -1123,8 +1123,8 @@
review comments before the Director issues a Call for Participation. </p>
<p>If a charter includes deliverables that continue work on documents which have previously had an
- Exclusion Opportunity per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the
- <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
+ Exclusion Opportunity per <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the
+ <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>],
the Director <em class="rfc2119">must not</em> issue a call for participation less
than 60 days after the beginning of Advisory Committee Review of the charter.</p>
@@ -1166,7 +1166,7 @@
<li>Any dependencies by groups within or outside of W3C on the deliverables of this group. For any dependencies,
the charter <em class="rfc2119">must</em> specify the mechanisms for communication about the deliverables;</li>
<li>Any dependencies of this group on other groups within or outside of W3C. Such dependencies include interactions
- with <a href="http://www.w3.org/Guide/Charter.html#horizontal-review">W3C Horizontal Groups</a>;</li>
+ with <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">W3C Horizontal Groups</a>;</li>
<li>The <a href="#confidentiality-levels">level of confidentiality</a> of the group's proceedings and deliverables;</li>
<li>Meeting mechanisms and expected frequency;</li>
<li>If known, the date of the first <a href="#ftf-meeting">face-to-face meeting</a>. The date of the first
@@ -1180,18 +1180,18 @@
<li>Intellectual property information. What are the intellectual property (including patents and copyright)
considerations affecting the success of the Group? In particular, is there any reason to believe that it will be
difficult to meet the Royalty-Free licensing goals of section 2 of the
- <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
+ <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
[<a href="#ref-patentpolicy">PUB33</a>]?</li>
</ul>
- <p>See also the charter requirements of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section 2</a>
- and <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section 3</a> of the
- <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+ <p>See also the charter requirements of <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section 2</a>
+ and <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Obligations">section 3</a> of the
+ <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
<p>For every Recommendation Track deliverable that continues work on a Working Draft (WD) published under any other Charter
(including a predecessor group of the same name), for which an Exclusion Opportunity per
- <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the
- <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]
+ <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the
+ <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]
has occurred, the description of that deliverable in the proposed charter of the adopting Working Group
<em class="rfc2119">must</em> provide the following information:</p>
@@ -1229,7 +1229,7 @@
<li>The group produces chartered deliverables ahead of schedule.</li>
</ul>
<p>The Director closes a Working Group or Interest Group by announcement to the Advisory Committee.</p>
- <p>Closing a Working Group has implications with respect to the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent
+ <p>Closing a Working Group has implications with respect to the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent
Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
</section>
<h2 id="Reports">6 W3C Technical Report Development Process</h2>
@@ -1244,12 +1244,12 @@
<li>facilitate royalty-free, interoperable implementations of Web Standards, and</li>
<li>earn endorsement by W3C and the broader community.</li>
</ul>
- <p>See also the licensing goals for W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section
- 2</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].
+ <p>See also the licensing goals for W3C Recommendations in <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Licensing">section
+ 2</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].
</p>
<h3 id="rec-advance">6.1 W3C Technical Reports</h3>
<p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a W3C Technical
- Report on its <a href="http://www.w3.org/TR/">Technical Reports page http://www.w3.org/TR</a>.</p>
+ Report on its <a href="https://www.w3.org/TR/">Technical Reports page https://www.w3.org/TR</a>.</p>
<p>This chapter describes the formal requirements for publishing and maintaining a W3C Recommendation or Note.</p>
<p>Typically a series of Working Drafts are published, each of which refines a document under development to complete the scope of
work envisioned by a Working Group's charter. For a technical specification, once review suggests the Working Group has met their
@@ -1276,7 +1276,7 @@
<li>Possibly, Publication as an <a href="#rec-edited">Edited Recommendation</a></li>
</ol>
<p>
- <svg xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 450 60" height="5em" width="45em">
+ <svg xlink="https://www.w3.org/1999/xlink" xmlns="https://www.w3.org/2000/svg" viewBox="0 0 450 60" height="5em" width="45em">
<g id="ToFPWD" stroke="black" fill="black">
<a xlink:href="#first-wd"><text font-size="8" font-family="Times,serif" y="38" x="66" text-anchor="start" stroke="none">First WD</text></a>
<path d="M66,40h33"></path>
@@ -1338,7 +1338,7 @@
<li>gather <a href="#implementation-experience">implementation experience</a></li>
<li>begin formal review by the Advisory Committee, who <em class="rfc2119">may</em> recommend that the document be published as
a W3C Recommendation, returned to the Working Group for further work, or abandoned.</li>
- <li>Provide an exclusion opportunity as per the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a
+ <li>Provide an exclusion opportunity as per the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a
href="#ref-patentpolicy">PUB33</a>]. A Candidate Recommendation under this process corresponds to the "Last Call Working
Draft" discussed in the Patent Policy.</li>
</ul>
@@ -1360,18 +1360,18 @@
producing a Recommendation.</dd>
<dt id="RescindedRec">Rescinded Recommendation</dt>
<dd>A Rescinded Recommendation is an entire Recommendation that W3C no longer endorses. See also clause 10 of the licensing
- requirements for W3C Recommendations in <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section 5</a> of
- the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</dd>
+ requirements for W3C Recommendations in <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section 5</a> of
+ the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</dd>
</dl>
<p>Working Groups and Interest Groups <em class="rfc2119">may</em> make available "Editor's drafts". Editor's drafts have no official
standing whatsoever, and do not necessarily imply consensus of a Working Group or Interest Group, nor are their contents endorsed in
any way by W3C.</p>
<h3 id="requirements-and-definitions">6.2 General requirements and definitions</h3>
<p>Please note that <dfn>publishing</dfn> as used in this document refers to producing a version which is listed as a W3C Technical
- Report on its <a href="http://www.w3.org/TR/">Technical Reports page http://www.w3.org/TR</a> [<a href="#rdf-doc-list">PUB11</a>].</p>
+ Report on its <a href="https://www.w3.org/TR/">Technical Reports page https://www.w3.org/TR</a> [<a href="#rdf-doc-list">PUB11</a>].</p>
<h4 id="general-requirements">6.2.1 General requirements for Technical Reports</h4>
<p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> be a public
- document. The <a href="http://www.w3.org/TR/">index of W3C technical reports</a> [<a href="#ref-doc-list">PUB11</a>] is available
+ document. The <a href="https://www.w3.org/TR/">index of W3C technical reports</a> [<a href="#ref-doc-list">PUB11</a>] is available
at the W3C Web site. W3C strives to make archival documents indefinitely available at their original address in their original form.</p>
<p>Every document published as part of the technical report development process <em class="rfc2119 old">must</em> clearly indicate
its <a href="#maturity-levels">maturity level</a>, and <em id="DocumentStatus" class="rfc2119">must</em> include information about
@@ -1389,11 +1389,11 @@
a Group Chair. It is the responsibility of these editors to ensure that the decisions of the Group are correctly reflected in
subsequent drafts of the technical report. An editor <em class="rfc2119">must</em> be a participant, as a Member representative,
Team representative, or Invited Expert in the Group responsible for the document(s) they are editing. </p>
- <p>The Team is <em class="rfc2119">not required</em> to publish a Technical Report that does not conform to the Team's <a href="http://www.w3.org/Guide/pubrules">Publication
+ <p>The Team is <em class="rfc2119">not required</em> to publish a Technical Report that does not conform to the Team's <a href="https://www.w3.org/Guide/pubrules">Publication
Rules</a> [<a href="#rdf-pubrules">PUB31</a>](e.g., for <span id="DocumentName">naming</span>, status information, style, and <span
id="document-copyright">copyright requirements</span>). These rules are subject to change by the Team from time to time. The Team
<em class="rfc2119">must</em> inform group Chairs and the Advisory Committee of any changes to these rules.</p>
- <p>The primary language for W3C Technical Reports is English. W3C encourages the translation of its Technical Reports. <a href="http://www.w3.org/Consortium/Translation/">Information
+ <p>The primary language for W3C Technical Reports is English. W3C encourages the translation of its Technical Reports. <a href="https://www.w3.org/Consortium/Translation/">Information
about translations of W3C technical reports</a> [<a href="#ref-translations">PUB18</a>] is available at the W3C Web site.</p>
<h4 id="transition-reqs">6.2.2 Advancement on the Recommendation Track</h4>
@@ -1436,8 +1436,8 @@
to actually perform reviews of and provide comments on the specification. A second objective is to encourage groups to request
reviews early enough that comments and suggested changes may still be reasonably incorporated in response to the review. Before
approving transitions, the Director will consider who has been explicitly offered a reasonable opportunity to review the document,
- who has provided comments, the record of requests to and responses from reviewers, especially <a href="http://www.w3.org/Guide/Charter.html#horizontal-review">W3C
- Horizontal Groups</a> and groups identified as dependencies in the charter or identified as <a href="http://www.w3.org/2001/11/StdLiaison.html">liaisons</a>
+ who has provided comments, the record of requests to and responses from reviewers, especially <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">W3C
+ Horizontal Groups</a> and groups identified as dependencies in the charter or identified as <a href="https://www.w3.org/2001/11/StdLiaison.html">liaisons</a>
[<a href="#rdf-liaison-list">PUB29</a>], and seek evidence of clear communication to the general public about appropriate times and
which content to review and whether such reviews actually occurred. </p>
<p>For example, inviting review of new or significantly revised sections published in Working Drafts, and tracking those comments and
@@ -1493,7 +1493,7 @@
<dd>Changes that add a new functionality, element, etc.</dd>
</dl>
<h3 id="working-draft">6.3 Working Draft</h3>
- <p>A Public Working Draft is published on the <a href="http://www.w3.org/TR/">W3C's Technical Reports page</a> [<a href="#rdf-doc-list">PUB11</a>]
+ <p>A Public Working Draft is published on the <a href="https://www.w3.org/TR/">W3C's Technical Reports page</a> [<a href="#rdf-doc-list">PUB11</a>]
for review, and for simple historical reference. For all Public Working Drafts a Working Group</p>
<ul>
<li> <em class="rfc2119">should</em> document outstanding issues, and parts of the document on which the Working Group does not
@@ -1506,8 +1506,8 @@
requirements for advancement</a>.</p>
<p>The Director <em class="rfc2119">must</em> announce the publication of a First Public Working Draft publication to other W3C
groups and to the public. </p>
- <p>Publishing the First Public Working Draft triggers a Call for Exclusions, per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
- 4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+ <p>Publishing the First Public Working Draft triggers a Call for Exclusions, per <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
+ 4</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
<h4 id="revised-wd">6.3.2 Revising Public Working Drafts</h4>
<p>A Working Group <em class="rfc2119">should</em> publish a Working Draft to the W3C Technical Reports page when there have been
significant changes to the previous published document that would benefit from review beyond the Working Group. </p>
@@ -1556,9 +1556,9 @@
<p>The Director <em class="rfc2119">must</em> announce the publication of a Candidate Recommendation to other W3C groups and to the
public, and <em class="rfc2119">must</em> begin an Advisory Committee Review on the question of whether the specification is
appropriate to publish as a W3C Recommendation.</p>
- <p> A Candidate Recommendation corresponds to a "Last Call Working Draft" as used in the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ <p> A Candidate Recommendation corresponds to a "Last Call Working Draft" as used in the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C
Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>]. Publishing a Candidate Recommendation triggers a Call for Exclusions,
- per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C
+ per <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C
Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
<p>Possible next steps:</p>
<ul>
@@ -1576,8 +1576,8 @@
<p>If there are any <a href="#substantive-change">substantive changes</a> made to a Candidate Recommendation other than to
remove features explicitly identified as "at risk", the Working Group <em class="rfc2119">must</em> obtain the Director's
approval to publish a revision of a Candidate Recommendation. This is because substantive changes will generally require a
- new Exclusion Opportunity per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the
- <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].
+ new Exclusion Opportunity per <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section 4</a> of the
+ <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].
Note that approval is <em>expected</em> to be fairly simple compared to getting approval for a transition from
Working Draft to Candidate Recommendation.</p>
@@ -1599,8 +1599,8 @@
<ul>
<li>The status information <em class="rfc2119">must</em> specify the deadline for Advisory Committee review, which <em class="rfc2119">must</em>
be <strong>at least</strong> 28 days after the publication of the Proposed Recommendation and <em class="rfc2119">should</em> be
- at least 10 days after the end of the last Exclusion Opportunity per <a href="http://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
- 4</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</li>
+ at least 10 days after the end of the last Exclusion Opportunity per <a href="https://www.w3.org/Consortium/Patent-Policy/#sec-Exclusion">section
+ 4</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</li>
</ul>
<p>A Working Group:</p>
<ul>
@@ -1655,10 +1655,10 @@
</ul>
<h3 id="rec-modify">6.7 Modifying a W3C Recommendation</h3>
- <p>This section details the management of errors in, and the process for making changes to a Recommendation. Please see also the <a href="http://www.w3.org/2003/01/republishing/">Requirements
+ <p>This section details the management of errors in, and the process for making changes to a Recommendation. Please see also the <a href="https://www.w3.org/2003/01/republishing/">Requirements
for modification of W3C Technical Reports</a> [<a href="#in-place-tr-mod">PUB35</a>].</p>
<p>
- <svg xlink="http://www.w3.org/1999/xlink" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 500 160" height="12em" width="50em">
+ <svg xlink="https://www.w3.org/1999/xlink" xmlns="https://www.w3.org/2000/svg" viewBox="0 0 500 160" height="12em" width="50em">
<g id="basicProcess" opacity=".6">
<g id="Modif-nodeWD">
<ellipse ry="18" rx="38" cy="40" cx="147" stroke="black" fill="none"></ellipse>
@@ -1769,17 +1769,17 @@
<li>A Working Group <em class="rfc2119">may</em> resume work on technical report within the scope of its charter at any time, at
the maturity level the specification had before publication as a Note</li>
</ul>
- <p>The <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>] does not
+ <p>The <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>] does not
specify any licensing requirements or commitments for Working Group Notes.</p>
<h3 id="rec-rescind">6.9 Obsoleting or Rescinding a W3C Recommendation</h3>
<p>W3C <em class="rfc2119">may</em> rescind a Recommendation, for example if the Recommendation contains many
errors that conflict with a later version, or if W3C discovers burdensome patent claims that affect implementers
- and cannot be resolved; see the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
+ and cannot be resolved; see the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a>
[<a href="#ref-patentpolicy">PUB33</a>] and in particular
- <a href="http://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section 5</a> (bullet 10) and
- <a href="http://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section 7.5</a>.</p>
+ <a href="https://www.w3.org/Consortium/Patent-Policy#sec-Requirements">section 5</a> (bullet 10) and
+ <a href="https://www.w3.org/Consortium/Patent-Policy#sec-PAG-conclude">section 7.5</a>.</p>
<p>W3C may obsolete a Recommendation, for example if the W3C Community decides that the Recommendation
no longer represents best practices, or is not adopted and is unlikely to be adopted.</p>
@@ -1839,8 +1839,8 @@
version-specific URL.</p>
<h3 id="further-reading">Further reading</h3>
- <p>Refer to <a href="http://www.w3.org/2003/05/Transitions">"How to Organize a Recommendation Track Transition"</a> in the <a href="http://www.w3.org/Guide/">Member
- guide</a> for practical information about preparing for the reviews and announcements of the various steps, and <a href="http://www.w3.org/2002/05/rec-tips">tips
+ <p>Refer to <a href="https://www.w3.org/2003/05/Transitions">"How to Organize a Recommendation Track Transition"</a> in the <a href="https://www.w3.org/Guide/">Member
+ guide</a> for practical information about preparing for the reviews and announcements of the various steps, and <a href="https://www.w3.org/2002/05/rec-tips">tips
on getting to Recommendation faster</a> [<a href="#ref-rec-tips">PUB27</a>].</p>
<h2 id="ReviewAppeal">7 Advisory Committee Reviews, Appeals, and Votes</h2>
<p>This section describes how the Advisory Committee reviews proposals from the Director and how Advisory Committee representatives
@@ -1912,7 +1912,7 @@
</ul>
<p>In all cases, an appeal <em class="rfc2119">must</em> be initiated within <span class="time-interval">three weeks</span> of the
decision.</p>
- <p>An Advisory Committee representative initiates an appeal by sending a request to the Team (explained in detail in the <a href="http://www.w3.org/Member/Intro">New
+ <p>An Advisory Committee representative initiates an appeal by sending a request to the Team (explained in detail in the <a href="https://www.w3.org/Member/Intro">New
Member Orientation</a>). The Team <em class="rfc2119">must</em> announce the appeal process to the Advisory Committee and provide
an address for comments from Advisory Committee representatives. The archive of these comments <em class="rfc2119">must</em> be
Member-visible. If, within <span class="time-interval">one week</span> of the Team's announcement, 5% or more of the Advisory
@@ -1953,7 +1953,7 @@
with another organization. Before signing the MoU, the Team <em class="rfc2119">must</em> inform the Advisory Committee of the
intent to sign and make the MoU available for Advisory Committee review; the Advisory Committee <em class="rfc2119">may</em> <a href="#ACAppeal">appeal</a>.
Once approved, a Memorandum of Understanding <em class="rfc2119">should</em> be made public.</p>
- <p>Information about <a href="http://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a> and the guidelines W3C
+ <p>Information about <a href="https://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a> and the guidelines W3C
follows when creating a liaison [<a href="#ref-liaison-list">PUB28</a>] is available on the Web.</p>
<h2 id="Submission">10 Member Submission Process</h2>
<p>The Member Submission process allows Members to propose technology or other ideas for consideration by the Team. After review, the
@@ -1983,7 +1983,7 @@
<p><strong>Note:</strong> To avoid confusion about the Member Submission process, please note that:</p>
<ul>
<li>Documents in a Member Submission are developed outside of W3C. These documents are <strong>not</strong> part of the <a href="#Reports">technical
- report development process</a> (and therefore are not included in the <a href="http://www.w3.org/TR/">index of W3C technical
+ report development process</a> (and therefore are not included in the <a href="https://www.w3.org/TR/">index of W3C technical
reports</a>). Members wishing to have documents developed outside of W3C published by W3C <em class="rfc2119">must</em> follow
the Member Submission process.</li>
<li>The Submission process is <strong>not</strong> a means by which Members ask for "ratification" of these documents as <a href="#RecsW3C">W3C
@@ -1995,7 +1995,7 @@
of a Submission request does not imply that any action will be taken by W3C. It merely records publicly that the Submission request
has been made by the Submitter. A Member Submission published by W3C <em class="rfc2119">must not</em> be referred to as "work in
progress" of the W3C.</p>
- <p>The list of <a href="http://www.w3.org/Submission/">acknowledged Member Submissions</a> [<a href="#ref-submission-list">PUB10</a>]
+ <p>The list of <a href="https://www.w3.org/Submission/">acknowledged Member Submissions</a> [<a href="#ref-submission-list">PUB10</a>]
is available at the W3C Web site.</p>
<h3 id="SubmissionRights">10.1 Submitter Rights and Obligations</h3>
<p>When more than one Member jointly participates in a Submission request, only one Member formally sends in the request. That Member
@@ -2003,7 +2003,7 @@
those Advisory Committee representatives <em class="rfc2119">must</em> confirm (by email to the Team) their participation in the
Submission request.</p>
<p>At any time prior to acknowledgment, any Submitter <em class="rfc2119">may</em> withdraw support for a Submission request
- (described in "<a href="http://www.w3.org/2000/09/submission">How to send a Submission request</a>"). A Submission request is
+ (described in "<a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a>"). A Submission request is
"withdrawn" when no Submitter(s) support it. The Team <em class="rfc2119">must not</em> make statements about withdrawn Submission
requests.</p>
<p>Prior to acknowledgment, the Submitter(s) <em class="rfc2119">must not</em>, <strong>under any circumstances</strong>, refer to a
@@ -2021,15 +2021,15 @@
Working Group Notes since Working Group Notes represent group output, not input to the group.</p>
<p>On the other hand, while W3C is in the early stages of developing a charter, Members <em class="rfc2119">should</em> use the
Submission process to build consensus around concrete proposals for new work.</p>
- <p>Members <em class="rfc2119">should not</em> submit materials covering topics well outside the scope of <a href="http://www.w3.org/Consortium/mission">W3C's
+ <p>Members <em class="rfc2119">should not</em> submit materials covering topics well outside the scope of <a href="https://www.w3.org/Consortium/mission">W3C's
mission</a> [<a href="#ref-mission">PUB15</a>].</p>
<h4 id="SubmissionReqs">10.1.2 Information Required in a Submission Request</h4>
<p>The Submitter(s) and any other authors of the submitted material <em class="rfc2119">must</em> agree that, if the request is
- acknowledged, the documents in the Member Submission will be subject to the <a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C
+ acknowledged, the documents in the Member Submission will be subject to the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C
Document License</a> [<a href="#ref-doc-license">PUB18</a>] and will include a reference to it. The Submitter(s) <em class="rfc2119">may</em>
hold the copyright for the documents in a Member Submission.</p>
- <p>The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments of <a href="http://www.w3.org/Consortium/Patent-Policy#sec-submissions">section
- 3.3</a> of the <a href="http://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
+ <p>The request <em class="rfc2119">must</em> satisfy the Member Submission licensing commitments of <a href="https://www.w3.org/Consortium/Patent-Policy#sec-submissions">section
+ 3.3</a> of the <a href="https://www.w3.org/Consortium/Patent-Policy">W3C Patent Policy</a> [<a href="#ref-patentpolicy">PUB33</a>].</p>
<p>The Submitter(s) <em class="rfc2119">must</em> include the following information:</p>
<ul>
<li>The list of all submitting Members.</li>
@@ -2037,9 +2037,9 @@
appear in a separate document.</li>
<li>Complete electronic copies of any documents submitted for consideration (e.g., a technical specification, a position paper,
etc.) If the Submission request is acknowledged, these documents will be published by W3C and therefore <em class="rfc2119">must</em>
- satisfy the Communication Team's <a href="http://www.w3.org/Guide/pubrules">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>].
+ satisfy the Communication Team's <a href="https://www.w3.org/Guide/pubrules">Publication Rules</a> [<a href="#ref-pubrules">PUB31</a>].
Submitters may hold the copyright for the material contained in these documents, but when published by W3C, these documents <em class="rfc2119">must</em>
- be subject to the provisions of the <a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> [<a
+ be subject to the provisions of the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a> [<a
href="#ref-doc-license">PUB18</a>].</li>
</ul>
<p>The request <em class="rfc2119">must</em> also answer the following questions.</p>
@@ -2052,11 +2052,11 @@
<li>What mechanisms are there to make changes to the specification being submitted? This includes, but is not limited to, stating
where change control will reside if the request is acknowledged.</li>
</ul>
- <p>For other administrative requirements related to Submission requests, see "<a href="http://www.w3.org/2000/09/submission">How to
+ <p>For other administrative requirements related to Submission requests, see "<a href="https://www.w3.org/2000/09/submission">How to
send a Submission request</a>" [<a href="#ref-member-sub">MEM8</a>].</p>
<h3 id="TeamSubmissionRights">10.2 Team Rights and Obligations</h3>
<p>Although they are not technical reports, the documents in a Member Submission <em class="rfc2119">must</em> fulfill the
- requirements established by the Team, including the Team's <a href="http://www.w3.org/Guide/pubrules">Publication Rules</a>.</p>
+ requirements established by the Team, including the Team's <a href="https://www.w3.org/Guide/pubrules">Publication Rules</a>.</p>
<p>The Team sends a <a id="validation-notice">validation notice</a> to the Submitter(s) once the Team has reviewed a Submission
request and judged it complete and correct.</p>
<p>Prior to a decision to <a href="#SubmissionYes">acknowledge</a> or <a href="#SubmissionNo">reject</a> the request, the request is
@@ -2079,10 +2079,10 @@
<ul>
<li>The ideas expressed in the request overlap in scope with the work of a chartered Working Group, and acknowledgment might
jeopardize the progress of the group.</li>
- <li>The IPR statement made by the Submitter(s) is inconsistent with the W3C's <a href="http://www.w3.org/Consortium/Patent-Policy">Patent
- Policy</a> [<a href="#ref-patentpolicy">PUB33</a>], <a href="http://www.w3.org/Consortium/Legal/copyright-documents">Document
+ <li>The IPR statement made by the Submitter(s) is inconsistent with the W3C's <a href="https://www.w3.org/Consortium/Patent-Policy">Patent
+ Policy</a> [<a href="#ref-patentpolicy">PUB33</a>], <a href="https://www.w3.org/Consortium/Legal/copyright-documents">Document
License</a> [<a href="#ref-doc-license">PUB18</a>], or other IPR policies.</li>
- <li>The ideas expressed in the request are poor, might harm the Web, or run counter to <a href="http://www.w3.org/Consortium/mission">W3C's
+ <li>The ideas expressed in the request are poor, might harm the Web, or run counter to <a href="https://www.w3.org/Consortium/mission">W3C's
mission</a>.</li>
<li>The ideas expressed in the request lie well outside the scope of W3C's mission.</li>
</ul>
@@ -2113,87 +2113,87 @@
<p>Reviews of the Process Document are not public reviews.</p>
<h2 id="references">12 References</h2>
<h3 id="public-refs">12.1 Public Resources</h3>
- <p>The following public information is available at the <a href="http://www.w3.org/">W3C Web site</a>.</p>
+ <p>The following public information is available at the <a href="https://www.w3.org/">W3C Web site</a>.</p>
<dl>
<dt id="ref-join-w3c">[PUB5]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/join">How to Join W3C</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/join">How to Join W3C</a></cite></dd>
<dt id="ref-member-agreement">[PUB6]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/Agreement/Member-Agreement">Membership Agreement</a></cite></dd>
<dt id="ref-current-mem">[PUB8]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/Member/List">The list of current W3C Members</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/Member/List">The list of current W3C Members</a></cite></dd>
<dt id="ref-activity-list">[PUB9]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/activities">The list of W3C Activities</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/activities">The list of W3C Activities</a></cite></dd>
<dt id="rdf-submission-list">[PUB10]</dt>
- <dd><cite><a href="http://www.w3.org/Submission/">The list of acknowledged Member Submissions</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Submission/">The list of acknowledged Member Submissions</a></cite></dd>
<dt id="rdf-doc-list">[PUB11]</dt>
- <dd><cite><a href="http://www.w3.org/TR/">The W3C technical reports index</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/TR/">The W3C technical reports index</a></cite></dd>
<dt id="rdf-submission-overview">[PUB13]</dt>
- <dd><cite><a href="http://www.w3.org/Submission/1996/Template/">Submission request overview</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Submission/1996/Template/">Submission request overview</a></cite></dd>
<dt id="rdf-people">[PUB14]</dt>
- <dd><cite><a href="http://www.w3.org/People/">The W3C Team</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/People/">The W3C Team</a></cite></dd>
<dt id="rdf-mission">[PUB15]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/">About the World Wide Web Consortium</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/">About the World Wide Web Consortium</a></cite></dd>
<dt id="rdf-team-submission-list">[PUB16]</dt>
- <dd><cite><a href="http://www.w3.org/TeamSubmission/">The list of published Team Submissions</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/TeamSubmission/">The list of published Team Submissions</a></cite></dd>
<dt id="rdf-invited-expert">[PUB17]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/Legal/collaborators-agreement">Invited expert and collaborators agreement</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/Legal/collaborators-agreement">Invited expert and collaborators agreement</a></cite></dd>
<dt id="rdf-doc-license">[PUB18]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document License</a></cite></dd>
<dt id="rdf-software-license">[PUB19]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/Legal/copyright-software">W3C Software Notice and License</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software Notice and License</a></cite></dd>
<dt id="rdf-translations">[PUB20]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/Translation/">Translations of W3C technical reports</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/Translation/">Translations of W3C technical reports</a></cite></dd>
<dt id="rdf-pub-mailing-lists">[PUB21]</dt>
- <dd><cite><a href="http://www.w3.org/Mail/">Public W3C mailing lists</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Mail/">Public W3C mailing lists</a></cite></dd>
<dt id="rdf-coi">[PUB23]</dt>
- <dd><cite><a href="http://www.w3.org/2000/09/06-conflictpolicy">Conflict of Interest Policy for W3C Team Members Engaged in Outside
+ <dd><cite><a href="https://www.w3.org/2000/09/06-conflictpolicy">Conflict of Interest Policy for W3C Team Members Engaged in Outside
Professional Activities</a></cite></dd>
<dt id="rdf-tag-charter">[PUB25]</dt>
- <dd><cite><a href="http://www.w3.org/2001/07/19-tag">Technical Architecture Group (TAG) Charter</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2001/07/19-tag">Technical Architecture Group (TAG) Charter</a></cite></dd>
<dt id="rdf-tag-home">[PUB26]</dt>
- <dd><cite><a href="http://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2001/tag/">The TAG home page</a></cite></dd>
<dt id="rdf-rec-tips">[PUB27]</dt>
- <dd><cite><a href="http://www.w3.org/2002/05/rec-tips">Tips for Getting to Recommendation Faster</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2002/05/rec-tips">Tips for Getting to Recommendation Faster</a></cite></dd>
<dt id="rdf-liaison-list">[PUB28]</dt>
- <dd><cite><a href="http://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2001/11/StdLiaison">W3C liaisons with other organizations</a></cite></dd>
<dt id="rdf-ab-home">[PUB30]</dt>
- <dd><cite><a href="http://www.w3.org/2002/ab/">The Advisory Board home page</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2002/ab/">The Advisory Board home page</a></cite></dd>
<dt id="rdf-pubrules">[PUB31]</dt>
- <dd><cite><a href="http://www.w3.org/Guide/pubrules">Publication Rules</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Guide/pubrules">Publication Rules</a></cite></dd>
<dt id="rdf-fellows">[PUB32]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/Recruitment/Fellows">W3C Fellows Program</a></cite></dd>
<dt id="rdf-patentpolicy">[PUB33]</dt>
- <dd><cite><a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 Feb 2004 version of the W3C Patent Policy</a></cite>. The
- <a href="http://www.w3.org/Consortium/Patent-Policy/">latest version of the W3C Patent Policy</a> is available at
- http://www.w3.org/Consortium/Patent-Policy/.</dd>
+ <dd><cite><a href="https://www.w3.org/Consortium/Patent-Policy-20040205/">5 Feb 2004 version of the W3C Patent Policy</a></cite>. The
+ <a href="https://www.w3.org/Consortium/Patent-Policy/">latest version of the W3C Patent Policy</a> is available at
+ https://www.w3.org/Consortium/Patent-Policy/.</dd>
<dt id="in-place-tr-mod">[PUB35]</dt>
- <dd><cite><a href="http://www.w3.org/2003/01/republishing/">In-place modification of W3C Technical Reports</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2003/01/republishing/">In-place modification of W3C Technical Reports</a></cite></dd>
</dl>
<h3>12.2 <a id="member-refs">Member-only Resources</a></h3>
- <p>The following <a href="#Member-only">Member-only</a> information is available at the <a href="http://www.w3.org/">W3C Web site</a>.</p>
+ <p>The following <a href="#Member-only">Member-only</a> information is available at the <a href="https://www.w3.org/">W3C Web site</a>.</p>
<dl>
<dt id="rdf-current-ac">[MEM1]</dt>
- <dd><cite><a href="http://www.w3.org/Member/ACList">Current Advisory Committee representatives</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Member/ACList">Current Advisory Committee representatives</a></cite></dd>
<dt id="rdf-mailing-lists">[MEM2]</dt>
- <dd><cite><a href="http://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Member/Mail/">Group mailing lists</a></cite></dd>
<dt id="rdf-calendar">[MEM3]</dt>
- <dd>The <cite><a href="http://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite></dd>
+ <dd>The <cite><a href="https://www.w3.org/Member/Eventscal">calendar of all scheduled official W3C events</a></cite></dd>
<dt id="rdf-new-member">[MEM4]</dt>
- <dd>The <cite><a href="http://www.w3.org/Member/Intro">New Member Orientation</a></cite>, which includes an introduction to W3C
+ <dd>The <cite><a href="https://www.w3.org/Member/Intro">New Member Orientation</a></cite>, which includes an introduction to W3C
processes from a practical standpoint, including relevant email addresses.</dd>
<dt id="rdf-ac-meetings">[MEM5]</dt>
- <dd><cite><a href="http://www.w3.org/Member/Meeting/">Advisory Committee meetings</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Member/Meeting/">Advisory Committee meetings</a></cite></dd>
<dt id="rdf-member-web">[MEM6]</dt>
- <dd><cite><a href="http://www.w3.org/Member/">Member Web site</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/Member/">Member Web site</a></cite></dd>
<dt id="rdf-member-sub">[MEM8]</dt>
- <dd><cite><a href="http://www.w3.org/2000/09/submission">How to send a Submission request</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2000/09/submission">How to send a Submission request</a></cite></dd>
<dt id="rdf-guide">[MEM9]</dt>
- <dd><cite><a href="http://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other
+ <dd><cite><a href="https://www.w3.org/Guide/">The Art of Consensus</a></cite>, a guidebook for W3C Working Group Chairs and other
collaborators</dd>
<dt id="rdf-discipline-gl">[MEM14]</dt>
- <dd><cite><a href="http://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2002/09/discipline">Guidelines for Disciplinary Action</a></cite></dd>
<dt id="rdf-election-howto">[MEM15]</dt>
- <dd><cite><a href="http://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a></cite></dd>
+ <dd><cite><a href="https://www.w3.org/2002/10/election-howto">How to Organize an Advisory Board or TAG election</a></cite></dd>
</dl>
<h3 id="other-refs">12.3 Other References</h3>
<dl>
@@ -2233,8 +2233,11 @@
David Singer (IBM), Henri Sivonen (Mozilla), Josh Soref (BlackBerry), Ralph Swick (W3C), Anne van Kesteren,
Jean-Charles Verdié (MStar), Mike West (Google), Chris Wilson (Google), Lauren Wood (unaffiliated),
and Steve Zilles (Adobe Systems).</p>
+
<h2 id="changes">14 Changes</h2>
- <p>This document is based on 1 September 2015 Process. <a href="https://dvcs.w3.org/hg/AB/">Detailed change logs</a> are available.</p>
+
+ <p>This document is based on the <a href="https://www.w3.org/2015/Process-20150901/">1 September 2015 Process. <a href="https://dvcs.w3.org/hg/AB/">Detailed change logs</a> are available.</p>
+
<p>The notable changes include:</p>
<h3>Current draft</h3>
<ul>