-
Notifications
You must be signed in to change notification settings - Fork 12
/
Copy pathcharter.html
586 lines (524 loc) · 30.6 KB
/
charter.html
1
2
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
55
56
57
58
59
60
61
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
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>Private Advertising Technology Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
main {
max-width: 60em;
margin: 0 auto;
}
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: #900;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#background">Background</a></li>
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#success-criteria">Success Criteria</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#anti-trust">Anti-Trust</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title">PROPOSED Private Advertising Technology Working Group Charter</h1>
<!-- delete PROPOSED after AC review completed -->
<p class="mission">The <strong>mission</strong> of the <a href="">Private Advertising Technology Working Group</a>,
motivated by the <a href="https://www.w3.org/2001/tag/doc/ethical-web-principles/">W3C TAG Ethical Web Principles</a>, is to
specify web features and APIs that support advertising while
acting in the interests of users, in particular providing strong
privacy assurances using predominantly technical means. The Working Group welcomes participation from
browser vendors, OS vendors, mobile application vendors, advertisers,
publishers, ad buyers, advertising platforms and intermediaries,
privacy advocates, web application developers, and other interested
parties.
</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/groups/wg/[shortname]/join">Join the Private Web Advertising Working Group.</a></p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <a href="https://github.com/patcg/patwg-charter/">GitHub</a>.
Feel free to raise <a href="https://github.com/patcg/patwg-charter/issues">issues</a>.
</p>
<section id="details">
<table class="summary-table">
<tr id="Status">
<th>
Charter Status
</th>
<td>
<i class="todo">See the <a href="https://www.w3.org/groups/wg/[shortname]/charters">group status page</A> and <a href="#history">detailed change history</a>.</i>
</td>
</tr>
<tr id="Duration">
<th>
Start date
</th>
<td>
<i class="todo">[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)</i>
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
<i class="todo">[dd monthname yyyy]</i> (Start date + 2 years)
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
<ul>
<li>Aram Zucker-Scharff (Washington Post)</li>
<li>Sean Turner (sn3rd; Invited Expert)</li>
</ul>
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<ul>
<li>Sam Weiler (0.2 <abbr title="Full-Time Equivalent">FTE</abbr>)</li>
</ul>
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> We expect to meet every 1-3 months for longer-than-hour blocks, which might be spread over several days
<br>
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
</td>
</tr>
</table>
<section id="background" class="background">
<h2>Motivation and Background</h2>
<section id="section-background-origins">
<h3>Origins</h3>
<p>
The Private Advertising Technology Working Group arose from efforts to implement privacy-forward technology and standards which support and evolve use cases that, until this point, have been dependent on third-party cookies and other tracking mechanisms. The initial approach to this topic was at the <a href="https://www.w3.org/community/web-adv/" target="_blank">Improving Web Advertising Business Group</a> which worked to define requirements and engage with the community to understand the needs of the advertising ecosystem. The work that started there has generated work taken up by a variety of other, more focused, groups.
</p>
<p>
The groups that formed to help generate new standards and processes around privacy technologies at the W3C included the Private Advertising Technology Community Group (PATCG). This group has taken up community engagement to incubate web features and APIs that support advertising while acting in the interests of users, in particular providing strong privacy assurances using predominantly technical means. Some of the work incubated in that group has become mature enough to be taken up by a Working Group. The PATWG group was proposed to be chartered to take up work which reaches that state in PATCG. It also is prepared for work that matches our <a href="#mission">mission</a> and <a href="#scope">scope</a> and is ready to be taken up by a working group.
</p>
</section>
<section id="section-background-motivation">
<h3>Motivation</h3>
<p>
This group is motivated by our <a href="#mission">mission</a> and the need for a commercially sustainable web. We understand that such a web is accessed through user agents and those user agents should act in the interest of their users and provide strong assurances of privacy. Our concerns are focused on supporting and creating an environment where the many ad-driven stakeholders who build the web, and are interested in operating within the limitations of our <a href="#scope">scope</a>, can find usable and useful processes by which to operate.
</p>
</section>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>
The Working Group will specify new web platform features. The purpose of
these features is to support web advertising without compromising
user privacy. Here "privacy" minimally refers to appropriate
processing of personal information. Ways in which new features might
enable inappropriate processing include (but are not limited to)
enabling
of <a href="https://www.w3.org/TR/2023/DNOTE-privacy-principles-20230223/#dfn-cross-site-recognition">cross-site
or cross context recognition</a> of users or
enabling <a href="https://www.w3.org/TR/2023/DNOTE-privacy-principles-20230223/#dfn-same-site-recognition">same-site
or same-context recognition</a> of users across the clearing of
state.
</p>
<p>
The Working Group will produce specifications that are implemented by
user agents. The implementation of specifications in user agents
might interoperate with or depend on functionality provided by other
entities. In these cases, the Working Group
will <a href="#coordination">coordinate with other organizations</a>
to provide specifications for necessary functions.
</p>
<section id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>Features that support advertising but provide privacy by means that are primarily non-technical should be proposed elsewhere.</p>
</section>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p><i class="todo">Updated document status is available on the <a href="https://www.w3.org/groups/wg/[shortname]/publications">group publication status page</a>.</i></p>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval.
The Working Group intends to publish the latest state of their work as Candidate Recommendation (with Snapshots) and does not intend to advance their documents further in this charter period.</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="private-attribution" class="spec"><a href="https://github.com/patcg/private-measurement">Private Attribution Measurement</a></dt>
<dd>
<p>This specification defines how to privately measure advertisement attribution/conversion without revealing whether any individual user converts or does not.</p>
<p class="draft-status"><b>Draft state:</b> No draft</p>
<p class="milestone"><b>Expected completion:</b> Q3 2025</p>
<p>The proposal will work with concepts and take inspiration from:</p>
<ul>
<li><a href="https://github.com/patcg-individual-drafts/ipa"></a>Interoperable Private Attribution (IPA)</li>
<li><a href="https://github.com/privacycg/private-click-measurement/">Private Click Measurement</a></li>
<li><a href="https://github.com/patcg-individual-drafts/private-aggregation-api">Private Aggregation API</a></li>
<li><a href="https://github.com/wicg/attribution-reporting-api">Attribution Reporting API</a></li>
<li><a href="https://github.com/patcg-individual-drafts/private-ad-measurement">Prio-like Attribution Measurement</a></li>
</ul>
<p>
The proposal will arise from the dimensions set in the <a href="https://github.com/patcg/docs-and-reports/tree/main/design-dimensions">Design Dimensions document</a> and will be guided by the <a href="https://github.com/patcg/docs-and-reports/tree/main/threat-model">threat model</a> and <a href="https://github.com/patcg/docs-and-reports/tree/main/principles">principles documents</a> initiated by PATCG.
</p>
</dd>
</dl>
<p>
The Working Group intends to add other normative specifications as the technology becomes ready. The expectation is that those specifications will be incubated in the PATCG and then, when they are ready for standardization, transition to PATWG. Potential areas include:
</p>
<ul>
<li>Pre-campaign planning</li>
<li>Intra-campaign decisioning and optimization, such as:</li>
<ul>
<li>Interest-based ad or content decisioning;</li>
<li>User List Marketing/Remarketing;</li>
<li>Fraud detection and prevention;</li>
<li>Abuse detection and prevention;</li>
<li>Frequency and recency controls;</li>
<li>Error reporting and mitigation; and </li>
<li>Device resource management.</li>
</ul>
<li>Post-campaign reporting and attribution
</ul>
</section>
<section id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;</li>
<li>Test suite and implementation report for the specification;</li>
<li>Primer or Best Practice documents to support web developers when designing applications.</li>
</ul>
</section>
<section id="timeline">
<h3>Timeline</h3>
<ul>
<li>Sept 2023: First face-to-face at TPAC</li>
<li>October 2023: First teleconference meeting</li>
<li>March 2024: Requirements and Use Cases Established for Private Measurement</li>
<li>May 2024: First Draft for Private Measurement</li>
</ul>
</section>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<p>The WG will progress its normative specifications through the following
standardization process:
<a href="https://www.w3.org/2021/Process-20211102/#RecsWD">First Public
Working Draft</a>,
<a href="https://www.w3.org/2021/Process-20211102/#RecsWD">Working
Draft</a>,
<a href="https://www.w3.org/2021/Process-20211102/#candidate-recommendation-snapshot">Candidate
Recommendation Snapshot</a>, and <a href="https://www.w3.org/2021/Process-20211102/#candidate-recommendation-draft">Candidate
Recommendation Draft</a>. The WG does not intend to publish specifications as <a href="https://www.w3.org/2021/Process-20211102/#RecsPR">Proposed Recommendations</a>.
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>To promote interoperability, all changes made to specifications in Candidate Recommendation or to features that have deployed implementations should have tests. Testing efforts should be conducted via the Web Platform Tests project.</p>
<p>Each specification should contain sections detailing all known security and
privacy implications for implementers, Web authors, and end users.</p>
<p>Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximizing accessibility in implementations.</p>
<!-- Design principles -->
<p>This Working Group expects to follow the
TAG <a href="https://www.w3.org/TR/design-principles/">Web Platform Design Principles</a>.
</p>
<p>All new features should have expressions of interest from at least two potential implementors before being incorporated in the specification.</p>
<p>In considering features, the group will state, during the development of those features or in the text of the document, privacy implications. Proposals should clearly state privacy issues, how they intend to address those issues, and the advertising use cases addressed in each deliverable.</p>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for
accessibility, internationalization, privacy, and security with the relevant Working and
Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>.
Invitation for review must be issued during each major standards-track document transition, including
<a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>. The
Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of
each specification. The Working Group is advised to seek a review at least 3 months before first entering
<a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
to proactively notify the horizontal review groups when major changes occur in a specification following a review.
Additionally, the technologies this Working Group will be considering will be relevant for other standards development organizations
such that the group is encouraged to coordinate with the appropriate groups at IETF, and others as needed.
</p>
<p>
The WG will coordinate with the Private Advertising Technology Community Group to solicit feedback from a wider community of interest. At any time, but always when a specification is undergoing a <a href="https://www.w3.org/2021/Process-20211102/#rec-track" title="The W3C Recommendation Track">state change</a>, the WG will ask the CG for feedback. The WG will allow the CG at least 4 weeks to gather that feedback.
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://patcg.github.io/">Private Advertising Technology Community Group (PATCG)</a></dt>
<dd>
This Working Group will work closely with PATCG. The expectation is that PATCG will incubate proposals which it then hands off to this Working Group for standardization. Most proposals in this Working Group should start in PATCG.
</dd>
</dl>
<dl>
<dt><a href="https://www.w3.org/Privacy/IG/">Privacy Interest Group (PING)</a></dt>
<dd>This Working Group will coordinate with PING on the development of principles that will guide the development of advertising capabilities.</dd>
</dl>
<dl>
<dt><a href="https://www.w3.org/2011/webappsec/">Web Application Security Working Group (WebAppSec)</a></dt>
<dd>WebAppSec is both a potential venue for standardization of security-related capabilities and a source of expertise on web privacy.
</dd>
</dl>
<dl>
<dt><a href="https://privacycg.github.io/">Privacy Community Group</a></dt>
<dd>The Privacy Community Group is developing privacy-focused features. The PATWG is expected to regularly coordinate with the Privacy CG to ensure that the work of the two groups is not in conflict.</dd>
</dl>
<dl>
<dt><a href="https://www.w3.org/2001/tag/">Technical Architecture Group (TAG)</a></dt>
<dd>The TAG develops general design principles that will guide the work of this Working Group. The TAG might provide input and guidance on specific aspects of the work.</dd>
</dl>
<dl>
<dt><a href="https://www.w3.org/community/web-adv/">Improving Web Advertising Business Group (Web-Adv)</a></dt>
<dd>The Improving Web Advertising Business Group includes representation from the potential consumers of these technologies, some of whom are not members</dd>
</dl>
<dl>
<dt><a href="https://antifraudcg.github.io/">Anti-Fraud Community Group</a></dt>
<dd>The Anti-Fraud Community Group is working to identify and define fraud and abuse scenarios, then incubate countermeasures while maintaining security, privacy, and accessibility. Advertising use cases or proposals that are exposed to the potential for fraud might need to integrate with work from this group.</dd>
</dl>
</section>
<section>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="https://www.ietf.org">IETF</a></dt>
<dd>A number of IETF working groups are likely venues for standardization of protocol components that advertising features depend on and research groups are investigating issues that will feed into the designs this group will consider. The main group we will need to coordinate with is the <a href="https://datatracker.ietf.org/wg/ppm/">Privacy Preserving Measurement</a> group</a>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 or more active participants originating from more than 2 separate parties for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The Working Group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href="#communication">Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
<p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in public: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests. The meetings themselves are not open to public participation, as participation is limited to Working Group members.
</p>
<p>
Information about this Working Group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the PATWG Working Group Home Page.
</p>
<p>
Most Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
At the discretion of the Chairs and subject to a consensus call, the Working Group may designate a task force to study a particular subject and report back to the Working Group their findings and a recommendation. A task force will consist of a small group of volunteers who commit to investing significant amounts of time on the task over a short, time-bound, period.
</p>
<p>Task forces operate under the same policies as the Working Group.</p>
<p>
This Working Group primarily conducts its technical work in the PATWG GitHub repository, which is configured to send all issues and pull requests to the public mailing list: <span class='todo'>public-[email-list]@w3.org</span> (archive). The public is invited to review, discuss and contribute to this work. </p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This Working Group will seek to make decisions through
<a href="https://www.w3.org/Consortium/Process/#Consensus">consensus</a> and the documented decision making process of <a href="https://www.w3.org/Consortium/Process/#decisions" title="Decisions section of W3C Process Document">the W3C Process Document
(Section 5, Decisions)</a>. Typically, an editor or other
participant makes an initial proposal, which is then refined
in discussion with members of the Working Group and other
reviewers, and consensus emerges with little formal voting
being required.
</p>
<p>
After discussion in a GitHub issue and other informal
discussion, substantive change proposals should be submitted
as GitHub pull requests. These can come from the editors or
from WG members. Editors are responsible for “curating” the
pull requests to reject frivolous ones and substantive ones
that the Chairs have determined do not comply with the IPR
policies.
</p>
<p>
Chairs are responsible for determining whether or not there is WG
consensus for the changes contained in a pull request.
Unanimity is not required, but the Chairs should strive to
make consensus decisions where there is significant support
and few abstentions.
</p>
<p>
However, if a decision is necessary for timely progress and
consensus is not achieved after careful consideration of the
range of views presented, the Chairs may call for a Working
Group vote and record a decision along with any formal
objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any
resolution (including publication decisions) taken in a face-to-face
meeting or teleconference will be considered provisional. A call for
consensus (CfC) will be issued for all resolutions (for example, via
GitHub issue or web-based survey), with a response period from one
week to 10 working days, depending on the Chair's evaluation of the
consensus on the issue. If no objections are raised by the end of the
response period, the resolution will be considered to have consensus
as a resolution of the Working Group.
</p>
<p>
All decisions made by the Working Group should be considered resolved
unless and until new information becomes available or unless reopened
at the discretion of the Chairs.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document
(Section 5.2.3, Deciding by Vote)</a> and includes no voting procedures
beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web specifications that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/groups/wg/[shortname]/ipr">licensing information</a>.
</p>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/#GAGeneral">section 3.4</a> of the <a href="https://www.w3.org/Consortium/Process/">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<section id="history">
<h3>
Charter History
</h3>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 4.3, Advisory Committee Review of a Charter)</a>:</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a class="todo" href="">Initial Charter</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">none</i>
</td>
</tr>
</tbody>
</table>
</section>
<section id="changelog">
<h3>Change log</h3>
<!-- Use this section for changes _after_ the charter was approved by the Director. -->
<p>Changes to this document are documented in this section.</p>
<!--
<dl id='changes'>
<dt>YYYY-MM-DD</dt>
<dd>[changes]]</dd>
</dl>
-->
</section>
</section>
</main>
<hr>
<footer>
<address>
Samuel Weiler
</address>
<p class="copyright">Copyright © 2023 <a href="https://www.w3.org/">World Wide Web Consortium</a>.<br>
<abbr title="World Wide Web Consortium">W3C</abbr><sup>®</sup>
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and
<a rel="license" href="https://www.w3.org/Consortium/Legal/2015/copyright-software-and-document" title="W3C Software and Document Notice and License">permissive document license</a> rules apply.</p>
<hr>
<p><a href="https://github.com/patcg/patwg-charter/">Yes, it's on GitHub!</a>.</p>
</footer>
</body>
</html>