This repository has been archived by the owner on May 28, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathindex.html
518 lines (440 loc) · 26.5 KB
/
index.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
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>JSON-LD 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/Guide/pubrules-style.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" />
<style type="text/css">
.warning {
box-shadow: 10px 5px 3px 0px gray;
border-top-width: thin;
border-right-width: thin;
border-bottom-width: thin;
border-left-width: thin;
border-top-style: solid;
border-right-style: solid;
border-bottom-style: solid;
border-left-style: solid;
border-radius: 3px;
width: 80%;
padding-top: 0.5em;
padding-right: 0.5em;
padding-bottom: 0.5em;
padding-left: 0.5em;
}
.warning h1 {
font-size: 120%;
font-style: italic;
font-weight: bold;
text-align: center;
}
.warning p {
font-size: 110%;
}
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;
background-color:#FFC !important;
font-style: italic;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</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="#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>
<div class="warning">
<h1>Draft</h1>
<p>
This is the charter for a JSON-LD Working Group. The canonical version is at <a href="https://www.w3.org/2018/03/jsonld-wg-charter.html">the W3C Website</a>, though the content is identical to this version.
</p>
</div>
<h1 id="title">JSON-LD Working Group Charter</h1>
<p>Since its original publication in 2014 by the RDF 1.1 Working Group,
<a href="https://www.w3.org/TR/2014/REC-json-ld-20140116/">JSON-LD 1.0</a> has become an essential
format for describing structured data on the World Wide Web. It is estimated to be used by between 10% and 18.2% of all websites. This is due largely to its adoption as a recommended format by
<a href="https://schema.org/">schema.org</a>. It has been adopted by several Recommendations including those from the Social Web, Web Annotation, and Linked Data Platform Working Groups, and current Working Groups have expressed interest in alignment of their specifications, such as the Publishing and Web of Things Working Groups. It has provided a much-needed bridge between communities that need rich semantics, and those that desire an intuitive and easily usable format (see separate <a href="https://github.com/json-ld/json-ld.org/wiki/Changes-in-Community-Group-Drafts-Targeted-for-1.1">wiki page</a> for more details).</p>
<p>Subsequently the specifications have been discussed within, and errata have been maintained by the <a href="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a>. New <a href="https://github.com/json-ld/json-ld.org/issues?utf8=✓&q=is%3Aissue+created%3A%3E2014-01-01+-label%3Awebsite+-label%3Aplayground+">issues have been raised</a>, primarily around allowing JSON-LD to be expressed using more natural JSON idioms. </p>
<p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/2018/json-ld-wg/">JSON-LD Working Group</a> is to update the JSON-LD 1.0 specifications to address specific usability or technical issues based on the community's experiences, implementer feedback, and requests for new features.</p>
<div class="noprint"> <p class="join"><a href="https://www.w3.org/2004/01/pp-impl/107714/join">Join the JSON-LD Working Group.</a></p>
</div>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
15 June 2018
</td>
</tr>
<tr id="Duration">
<th>
End date
</th>
<td>
15 June 2020
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Rob Sanderson – The J. Paul Getty Trust<br/>
Benjamin Young – Wiley
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:[email protected]">Ivan Herman</a> (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> 1-hour calls will be held weekly
<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>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>The <a href="https://www.w3.org/2018/json-ld-wg/">JSON-LD Working Group</a> will update the <a href="https://www.w3.org/TR/2014/REC-json-ld-20140116/">JSON-LD 1.0 Recommendation</a> to take into account new features and desired simplifications that have become apparent since its publication. The group will also extend the <a href="http://www.w3.org/TR/2014/REC-json-ld-api-20140116/">JSON-LD 1.0 Processing Algorithms and API Recommendation</a> to update the existing APIs corresponding to changes in the JSON-LD Recommendation. Additionally, the group will move the <a href="https://json-ld.org/spec/latest/json-ld-framing/">Framing API</a> CG specification to W3C Recommendation.</p>
<p>A summary of syntax changes proposed for inclusion by the
<a href="https://www.w3.org/community/json-ld/">JSON for Linking Data Community Group</a>
can be found on a <a href="https://github.com/json-ld/json-ld.org/wiki/Changes-in-Community-Group-Drafts-Targeted-for-1.1">wiki</a>
and in <a href="https://json-ld.org/presentations/JSON-LD-Update-TPAC-2017/assets/player/KeynoteDHTMLPlayer.html#0">slides used at TPAC 2017</a>.</p>
<p>The work must be consistent with principles expressed in the <a href="https://www.w3.org/TR/dwbp/">Data on the Web Best Practices</a> Recommendation. All changes must preserve backward compatibility for JSON-LD 1.0 documents. This means that, when processing existing JSON-LD documents, JSON-LD 1.1 processors generate the same expanded output, unless that output is subject to <a href="https://www.w3.org/2001/sw/wiki/JSON_LD_Errata">errata in JSON-LD 1.0</a> or is otherwise an unspecified implementation detail.</p>
<div id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>The following features are out of scope, and will not be addressed by this Working Group.</p>
<ul class="out-of-scope">
<li>RDF Dataset Normalization</li>
<li>Linked Data Signatures</li>
</ul>
</div>
<div>
<h3>Success Criteria</h3>
<p>In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of each of feature defined in the specification.</p>
<p>Each specification should contain a section detailing any known security or privacy implications for implementers, Web authors, and end users.</p>
<p>The group will maintain and advance the <a href="https://json-ld.org/test-suite/">Test Suite</a> allowing for continued testing of JSON-LD 1.0 implementations in addition to JSON-LD processors
operating both in 1.0 and 1.1 modes.</p>
</div>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>More detailed milestones and updated publication schedules are available on the <a href="https://www.w3.org/2018/json-ld-wg/PubStatus">group publication status page</a>.</p>
<div id="normative">
<h3>
Normative Specifications
</h3>
<p>
The JSON-LD Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="syntax" class="spec">JSON-LD 1.1</dt>
<dd>
<p>
This specification defines JSON-LD 1.1, a JSON-based format to serialize RDF 1.1 Graphs and Datasets as used for Linked Data and in Web content.
The syntax is designed to easily integrate into deployed systems that already use JSON, and provides a smooth upgrade path from JSON to JSON-LD, with as little additional cost as possible.
JSON-LD 1.1 will extend the current <a href="https://www.w3.org/TR/2014/REC-json-ld-20140116/">JSON-LD 1.0 Recommendation</a> while ensuring backwards compatibility.
</p>
<p>The Working Group will handle all the <a href="https://www.w3.org/2001/sw/wiki/JSON_LD_Errata">errata filed for JSON-LD 1.0.</a></p>
<p>
Finally, the documents will better align the JSON-LD and RDF terminologies wherever applicable and without jeopardizing backward compatibility with deployed JSON-LD 1.0 data. Detailed comparisons with other RDF serialization formats will also be included.
</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://json-ld.org/spec/latest/json-ld/">Draft Community Group Report</a></p>
<p class="milestone"><b>Expected completion:</b> Q2 2020.</p>
</dd>
<dt id="api" class="spec">JSON-LD 1.1 Processing Algorithms and API</dt>
<dd>
<p>
This specification defines a set of algorithms for programmatic transformations of JSON-LD 1.1 documents.
JSON-LD 1.1 API will extend the current <a href="https://www.w3.org/TR/2014/REC-json-ld-api-20140116/">JSON-LD 1.0 API Recommendation</a>.
The Working Group will also consider incorporating the widely used <a href="https://json-ld.org/spec/latest/json-ld-framing/">Framing</a> specification into JSON-LD 1.1 API, rather than as a separate deliverable.
</p>
<p>The Working Group will handle all the <a href="https://www.w3.org/2001/sw/wiki/JSON_LD_Errata">errata filed for JSON-LD 1.0 API.</a></p>
<p class="draft-status"><b>Draft state:</b> <a href="https://json-ld.org/spec/latest/json-ld-api/">Draft Community Group Report</a></p>
<p class="milestone"><b>Expected completion:</b> Q2 2020.</p>
</dd>
<dt id="framing" class="spec">JSON-LD 1.1 Framing</dt>
<dd>
<p>
This specification defines an extension to <a href="#api">JSON-LD 1.1 Processing Algorithms and API</a>
that allows developers to query by example and force a specific tree layout to a JSON-LD document.
</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://json-ld.org/spec/latest/json-ld-framing/">Draft Community Group Report</a></p>
<p class="milestone"><b>Expected completion:</b> Q2 2020.</p>
</dd>
</dl>
<p>
The Working Group will also address the security, privacy, and efficiency issues (e.g., preventing the needs for unnecessary dereferencing) raised by handling @context files in the current JSON-LD 1.0 version, for example by providing ways to indicate the use of common syntactic profiles so that context-fetching can be avoided. These issues (and also some editorial considerations) may affect the HTTP protocol related sections, and the WG may decide to extract those issues into a separate Recommendation and/or Working Group Note.
</p>
<p>The comparison sections on RDF serializations and related toolchains such as <a href="https://www.w3.org/TR/shacl/">SHACL</a>, <a href="http://shex.io/">Shex</a>, and <a href="http://json-schema.org/">JSON Schema</a>, may also be published as a separate Working Group Note rather than (non-normative) sections of the respective Recommendation.</p>
</div>
<div id="wg-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>JSON-LD 1.1 examples specified in <a href="http://yaml.org/spec/1.2/spec.html">YAML</a>.</li>
<li>Test suite and implementation report for the specification.</li>
</ul>
</div>
<div id="timeline">
<h3>Timeline</h3>
<ul>
<li>June 2018: First teleconference</li>
<li>September 2018: FPWD for JSON-LD 1.1 Syntax</li>
<li>September 2018: FPWD for JSON-LD 1.1 Processing Algorithms and API</li>
<li>September 2018: FPWD for JSON-LD 1.1 Framing</li>
<li>October 2018: First face-to-face meeting</li>
<li>June 2020: Recommendation for JSON-LD 1.1 Syntax</li>
<li>June 2020: Recommendation for JSON-LD 1.1 Processing Algorithms and API</li>
<li>June 2020: Recommendation for JSON-LD 1.1 Framing</li>
</ul>
</div>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">horizontal review</a> for accessibility, internationalization, performance, 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> and at least 3 months before <a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</p>
<p>
The work on JSON-LD may also reveal unnecessary complexities in the RDF 1.1 specifications. The Working Group may systematically submit <a href="http://www.w3.org/2014/rdf1.1-errata">errata</a> in such cases.
</p>
<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>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/2017/vc/WG/">Verifiable Claims Working Group</a></dt>
<dd>Coordination on named graph indexing and other concerns regarding support for normalization and digital signatures.</dd>
<dt><a href="https://www.w3.org/community/schemaorg/">Schema.org Community Group</a></dt>
<dd>The Schema.org CG will be regularly solicited for reviews and comments throughout the advancement of the JSON-LD 1.1 Recommendation.</dd>
</dl>
</div>
</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 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 group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
W3C Members are invited to <a href="https://www.w3.org/2004/01/pp-impl/107714/join">join this Working Group</a>.
Individuals who wish to participate as Invited Experts (i.e., they do not represent a W3C Member) should refer to the <a href="https://www.w3.org/2004/08/invexp.html" shape="rect">policy for approval of Invited Experts</a>.
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>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: 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 on a public repository, and may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/2018/json-ld-wg/">JSON-LD Working Group home page.</a>
</p>
<p>
Most JSON-LD Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on the public mailing list <a id="public-name" href="mailto:[email protected]">[email protected]</a> (<a href="https://lists.w3.org/Archives/Public/public-json-ld-wg/">archive</a>)
or on <a id="public-github" href="https://github.com/w3c/json-ld-wg/">GitHub issues</a> (and
specification-specific GitHub repositories and issue trackers).
The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group will publish minutes for each teleconference at <a href="https://www.w3.org/2018/json-ld-wg/Meeting/Minutes/">https://www.w3.org/2018/json-ld-wg/Meeting/Minutes/
</a>.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (section 3.3</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any 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 email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised on the mailing list 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 group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/policies#Votes">W3C Process Document (Section 3.4, Votes)</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-20170801/">W3C Patent Policy</a> (Version of 5 February 2004 updated 1 August 2017). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations 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/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.
</p>
</section>
<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 5.2</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 class="issue"><b>Note:</b>Display this table and update it when appropriate. Requirements for charter extension history are documented in the <a href="https://www.w3.org/Guide/Charter#extension">Charter Guidebook (section 4)</a>.</p>
<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 5.2.3)</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 href="https://www.w3.org/2018/03/jsonld-wg-charter.html">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>
<tr>
<th>
<a class="todo" href="">Charter Extension</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>
<tr>
<th>
<a class="todo" href="">Rechartered</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
<p class="todo">[description of change to charter, with link to new deliverable item in charter] <b>Note:</b> use the class <code>new</code> for all new deliverables, for ease of recognition.</p>
</td>
</tr>
</tbody>
</table>
</section -->
</section>
</main>
<hr />
<footer>
<address>
<a href="mailto:[email protected]">Ivan Herman</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2018
<a href="https://www.w3.org/"><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="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="http://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <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 href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
</footer>
</body>
</html>