exi-charter-final.html
13.7 KB
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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-us" lang="en-us">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>Charter of the Efficient XML Interchange Working Group</title>
<link href="/StyleSheets/activity.css" rel="stylesheet" type="text/css" />
<style type="text/css">
h2:before {
content: counter(h2) ". ";
display: inline;
}
h2 {
counter-increment: h2;
counter-reset: h3;
}
.sub:before {
content: counter(h2) "." counter(h3) ". ";
font-style: normal;
display: inline;
}
.sub {
counter-increment: h3;
font-style: italic;
}
</style>
</head>
<body>
<div id="Icons">
<img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"
/> <img width="212" height="48" src="http://www.w3.org/Icons/arch"
alt="Architecture Domain" /> | <a href="http://www.w3.org/XML">XML</a></div>
<div id="Contents">
<h1>Charter of the Efficient XML Interchange Working Group</h1>
<p><strong>[This charter has been extended until 31 December
2008]</strong></p>
<address>
</address>
<p><em>The Efficient XML Interchange Working Group is part of the <a
href="http://www.w3.org/XML">W3C XML Activity</a> and follows the Working
Group process described in section <a
href="http://www.w3.org/2004/02/Process-20040205/groups.html#GroupsWG">6.2
Working Groups and Interest Groups</a> of the <a
href="http://www.w3.org/Consortium/Process">W3C Process Document</a>. Except
as specified in this charter, the Working Group follows the <a
href="http://www.w3.org/2003/09/xmlap/xml-common-proc.html">Common Procedures
for XML Working Groups</a>.</em></p>
<hr />
<h3 class="toc">Table of Contents</h3>
<ol>
<li><a href="#mission">Mission</a></li>
<li><a href="#scope">Scope and Goals</a></li>
<li><a href="#out">Out of scope</a></li>
<li><a href="#success">Success criteria</a></li>
<li><a href="#deliverables">Deliverables and duration</a></li>
<li><a href="#milestones">Expected milestones</a></li>
<li><a href="#coordination">Coordination with Other Groups</a></li>
<li><a href="#participation">Working Group participation</a></li>
<li><a href="#meetings">Meetings</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#confidentiality">Confidentiality</a></li>
<li><a href="#pp">Patent Policy</a></li>
</ol>
<hr />
<h2 id="mission">Mission</h2>
<p>The main objective of the Efficient XML Interchange (<abbr
title="Efficient XML Interchange">EXI</abbr>) Working Group is to develop a
format that allows efficient interchange of the XML Information Set, based on
the <a href="http://www.w3.org/TR/xbc-characterization/#N107D4">conclusions
of the XML Binary Characterization Working Group</a>.</p>
<h2 id="scope">Scope and Goals</h2>
<p>XML has been enormously successful as a markup language for documents and
data, but is not an optimal format for all purposes. The XML Binary
Characterization Working Group established a set of use cases for which XML
employment may be problematic. The Efficient XML Interchange Working Group is
chartered to define an alternative encoding of the <cite>XML Information
Set</cite> that <strong>addresses at least the <a
href="http://www.w3.org/TR/xbc-characterization/#N102EC">minimum
requirements</a> identified by the XML Binary Characterization Working
Group</strong>. The Working Group shall also consider properties that
shouldn't be prevented, as listed in the second list of the <a
href="http://www.w3.org/TR/xbc-characterization/#N1020A">decision tree</a>.
Such support will be considered as extensions to the <cite>XML Information
Set</cite> or extensions introduced in the <cite>XML Schema 1.0
Post–Schema–Validation Infoset</cite> and in the <cite>XQuery 1.0
and XPath 2.0 data model</cite>.</p>
<p><strong>The goals of this Working Group are:</strong></p>
<ol>
<li>Fulfill the <a
href="http://www.w3.org/TR/2004/REC-xml-20040204/#sec-origin-goals">design
goals of XML</a> with the following exceptions:
<ol style="list-style-type: lower-alpha;">
<li>The interchange format must be compatible with the XML Information
Set instead of being “compatible with SGML” (XML goal 3);</li>
<li>For performance reasons, the format is not required to be
“human–legible and reasonably clear” (XML goal 6);</li>
<li>Terseness in efficient interchange is important (XML Goal 10).</li>
</ol>
</li>
<li>Address all <a
href="http://www.w3.org/TR/xbc-characterization/#N102EC">requirements</a>
and <a href="http://www.w3.org/TR/xbc-use-cases/">use cases</a> from the
XML Binary Characterization Working Group;</li>
<li>Maintaining the existing interoperability between XML applications, as
well as XML specifications;</li>
<li>Establish sufficient confidence in the proposed format, in particular
establishing confidence that the performance gains are significant, and
the potential for disruption to existing processors is small;</li>
</ol>
<p>There are several approaches to achieve the integration with XML. The
Working Group will provide at least one way for the new format to be both
recognized as XML by existing parsers and also rejected in a meaningful way,
<em>such as</em> by defining a new value for the pseudo–attribute
encoding.</p>
<p>The Working Group will start by considering existing solutions and will
evaluate each in terms of implementability and performance against the
requirements and use cases documents produced by the XML Binary
Characterization Working Group.</p>
<h2 id="out">Out of scope</h2>
<p>This Working Group is not chartered to:</p>
<ol>
<li>Introduce a new data model for XML;</li>
<li>Develop an application specific format. Like XML itself, the new format
must support a <cite>wide variety of applications</cite>.</li>
</ol>
<h2 id="success">Success criteria</h2>
<p>Two of the entrance criteria used for the Last Call phase will be:</p>
<ol>
<li>the Working Group Note on the impact of the new format on existing XML
technologies;</li>
<li>the Working Group Note analyzing the performance gains of the new
format, based on the criteria included in the <a
href="http://www.w3.org/TR/xbc-measurement/">measurement
methodologies</a> document. For example, in the case of <a
href="http://www.w3.org/TR/2005/NOTE-xbc-measurement-20050331/#c-method">compactness</a>,
the information compression is expected to be at most 20% larger than its
equivalent ASN.1 PER, when a schema optimization is in use. Some of the
analysis require to have an implementation and will be done during the
Candidate Recommendation phase, such as <em>processing
efficiency</em>.</li>
</ol>
<p>Careful review will be given to the feedback from other Groups, within and
outside the XML Activity. Findings that suggest that the proposed format has
a significant impact and disruption of existing XML technologies and
processors might dissuade W3C from advancing the format to W3C Candidate
Recommendation, or might persuade W3C to do so but without referring to the
format as a flavor of XML.</p>
<p>Two of the entrance criteria used for the Proposed Recommendation phase
will be:</p>
<ol>
<li>demonstrate the performance gains of the new format, based on the prior
analysis done as an entrance criteria of the Last Call phase. In
addition, an analysis regarding the properties that need an
implementation to be evaluated, such as <em>processing efficiency</em>,
will be conducted.</li>
<li>demonstrate at least two interoperable implementations supporting all
the features provided in the specification. One of the implementations
must be available for public use.</li>
</ol>
<!-- XML,
XML+gzip/bzip2, <a href=' http://www.w3.org/TR/soap12-mtom/'>SOAP
Message Transmission Optimization Mechanism</a> (for applicable use
cases and scenarios), Fast Infoset (ISO/IEC 24824-1), and possibly
other formats -->
<p>The Working Group may at any stage recommend the use of an already
published format, provided that it satisfies the above criteria, instead of
providing a W3C Recommendation.</p>
<h2 id="deliverables">Deliverables and duration</h2>
<h3 class="sub" id="Deliverables">Deliverables</h3>
<p>The Working Group is expected to produce:</p>
<ul>
<li>A W3C Working Group Note, providing an <strong>analysis of the
performance measurements using the <a
href="http://www.w3.org/TR/xbc-measurement/">measurement
methodologies</a> document, and performance gains</strong>. The analysis
should use a wide range of sizes and complexity in XML input documents,
representing at least each of the <a
href="http://www.w3.org/TR/xbc-use-cases/">use cases</a>. Favorable
performance results will help build community support by illustrating the
advantages that some applications may gain with this format over ordinary
XML text streams.</li>
<li>A Test Suite and corpus of measurable documents which can demonstrate
the results described in the performance measurements Note.</li>
<li>A W3C Working Group Note, providing an <strong>analysis of the new
format’s impact on existing XML technologies</strong> — in
particular XML Canonicalization, XML Signature, and XML Encryption
— and processors.</li>
<li>A <strong>W3C Recommendation for efficient XML
interchange</strong>.</li>
</ul>
<h3 class="sub" id="Duration">Duration</h3>
<p>The expiration date of this charter is 31 December 2007.</p>
<h2 id="milestones">Expected milestones</h2>
<p>The following milestones are proposed. As usual, the duration of the
review period must be negotiated with other groups, in particular the XML
Coordination Group for the Last Call phase duration.</p>
<dl>
<dt>December 2005</dt>
<dd>Working Group created</dd>
<dt>February 2006</dt>
<dd>First face–to–face meeting.</dd>
<dt>May 2006</dt>
<dd>First draft of the Working Group Note providing the analysis of the
performance measurements and of the Test Suite</dd>
<dt>September 2006</dt>
<dd>First Public Working Draft of the efficient XML interchange
format.</dd>
<dt>January 2007</dt>
<dd>Last Call Working Draft, <em>along with the analysis of its impact on
existing XML applications and specifications, and the analysis of the
performance gains</em>.</dd>
<dt>June 2007</dt>
<dd>Candidate Recommendation.</dd>
<dt>October 2007</dt>
<dd>Proposed Recommendation, <em>along with the final analysis of the
performance gains, based on implementation reports</em>.</dd>
</dl>
<h2 id="coordination">Coordination with Other Groups</h2>
<h3 class="sub" id="w3cgroups">W3C Groups</h3>
<p>The Working Group should coordinate its efforts with W3C Working Groups,
in particular in the XML Activity as well as the Technical Architecture
Group.</p>
<h3 class="sub" id="externalGroups">External Groups</h3>
<dl>
<dt>ISO/MPEG-7</dt>
<dd>MPEG-7 has an ISO standard binary infoset serialization, BiM, and is
currently working on a second version. </dd>
<dt>ISO/MPEG-4</dt>
<dd>MPEG-4 is currently re–evaluating its BIFS encoding, and may be
interested in providing input notably regarding efficient decoding on
small devices. </dd>
<dt>ISO/IEC/ITU-T</dt>
<dd>Fast Infoset (ITU-T Rec. X.891 (2005) | ISO/IEC 24824-1) is in the
process of being approved within the ISO. </dd>
<dt><a href="http://www.web3d.org/">Web3D</a></dt>
<dd>Web3D has explicitly asked the W3C about binary formats, and has
researched them itself. </dd>
</dl>
<h2 id="participation">Working Group participation</h2>
<p>Effective participation is expected to consume one workday per week for
each Working Group participant; two days per week for editors. The Chair
shall ensure that the criteria for <a
href="http://www.w3.org/2004/02/Process-20040205/groups.html#good-standing">Good
Standing</a> are understood and followed.</p>
<p>To be successful, we expect the Working Group to have 10 or more active
participants for its duration.</p>
<h3 class="sub" id="Chair">Chair</h3>
<p>The initial chairs of this Working Group are Oliver Goldman, Adobe
Systems, and Robin Berjon, Expway.</p>
<h3 class="sub" id="W3CResources">W3C Team resources</h3>
<p>The initial <a href="http://www.w3.org/Guide/staff-contact">W3C Team
contact</a> is Carine Bournez. It is expected that this Working Group will
consume about 0.5 <abbr title="Full–Time Equivalent">FTE</abbr>,
including administrative logistics.</p>
<h2 id="meetings">Meetings</h2>
<p>The Working Group will have distributed meetings, one to two hours every
week, and face–to–face meetings, every two to three months.</p>
<h2 id="communication">Communication</h2>
<p>The Working Group will utilize a W3C Member mailing list, <a
href="mailto:member-exi-wg@w3.org">member-exi-wg@w3.org</a>.</p>
<h2 id="confidentiality">Confidentiality</h2>
<p>The proceedings of this Working Group are “<a
href="http://www.w3.org/2004/02/Process-20040205/comm.html#confidentiality-levels">Member-only</a>”,
subject to exceptions made by the Chair, after consultation with the Working
Group.</p>
<h2 id="pp">Patent Policy</h2>
<p>This Working Group operates under the <a
href="http://www.w3.org/Consortium/Patent-Policy-20040205/">W3C Patent
Policy</a> (5 February 2004 Version). 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.</p>
<hr />
<address class="author">
<a href="/People/LeHegaret">Philippe Le Hégaret</a>, Architecture Domain
Leader, following comments from many individuals<br />
Last modified $ Date: 2005/09/29 19:06:49 $
</address>
</div>
</body>
</html>