sum10.html
12 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
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>TAG work in recent months, August 2008</title>
</head>
<body>
<div>
<a href="http://www.w3.org/" title="W3C Home"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72" border="0"/></a>
*
<a href="../../">TAG</a></div>
<h1>TAG work in recent months, October 2008</h1>
<p>[This summary is a minor update of our <a href="sum8.html">previous summary</a>
published in August 2008]</p>
<p>The core technologies of the Web are HTML, HTTP, and URIs,
and the work of the W3C Technical Architecture Group (TAG)
continues to focus on the corresponding areas of formats,
protocols, and naming.
</p>
<div><h2>Formats: HTML and ARIA, Namespace Documents</h2>
<p>As design of Accessible Rich Internet Applications (<a
href="http://www.w3.org/WAI/intro/aria.php">WAI-ARIA</a>) matured in
the WAI Protocols and Formats Working Group (<a
href="http://www.w3.org/WAI/PF/">PFWG</a>) and work started on
integration with host languages, especially HTML, the TAG noted the
use of an ad-hoc namespace mechanism: an <tt>aria-</tt> prefix on a
collection of attributes. The TAG sent <a
href="http://lists.w3.org/Archives/Public/www-tag/2008May/0035.html">some
questions and suggestsions</a> on 14 May regarding the costs and
benefits of this ad-hoc mechanism versus using XML Namespaces; after
consideration of the deployment costs and benefits, the <a
href="http://lists.w3.org/Archives/Public/www-tag/2008Jun/0005.html">conclusion
of the TAG on 2 June</a> was to accept
that the most pragmatic short-term approach is indeed to use names
beginning with
<tt>aria-</tt>. URI-based distributed extensibility remains a topic
of concern which the TAG discusses under issue
<a
href="http://www.w3.org/2001/tag/group/track/issues/54"
>tagSoupIntegration-54</a>.
The TAG devoted half of its <a href="09/f2fkc-agenda.html">3-day September F2F</a>
to the topic of "<a href="09/f2fkc-agenda#HTMLandTheWeb">HTML and The Web</a>".
The TAG plans to meet with the <a href="http://www.w3.org/html/wg/">HTML WG</a>
during <a href="http://www.w3.org/2008/10/TPAC/Schedule.html#Thurs">TPAC 2008</a>
to discuss Modularisation of the HTML5 specification.</p>
<p>The TAG published a finding on <cite><a
href="http://www.w3.org/2001/tag/doc/nsDocuments-2008-06-25/">Associating
Resources with Namespaces</a></cite>, which addresses issue
namespaceDocument-8. The finding suggests conventions, from ordinary
HTML to dialects using RDDL and GRDDL to RDF, OWL, and XML Schema, for
documenting namespaces and for linking associated resources. This 25
June 2008 revision of the finding incorporates editorial work
following from our <a
href="http://www.w3.org/2001/tag/2008/02/27-minutes#item05">February
discussion in Vancouver</a>.
</p>
<p>While still in draft form, <cite><a
href="http://www.w3.org/2001/tag/doc/selfDescribingDocuments.html"
>The Self-Describing Web</a></cite> was updated
<a href="http://www.w3.org/2001/tag/doc/selfDescribingDocuments-2008-05-12.html">12 May 2008</a>
and
<a href="http://www.w3.org/2001/tag/doc/selfDescribingDocuments-2008-09-08.html">
8 September 2008</a> it
discusses features of the Web that support reliable, ad hoc discovery
of information, including formats such as Atom, RDFa, GRDDL, XML, and
RDF. </p>
<p>Work continued on <a
href="http://www.w3.org/2001/tag/group/track/issues/41">ISSUE-41</a>,
<em>What are good practices for designing extensible XML languages and
for handling versioning?</em> The 20 May 2008 draft of <cite><a
href="http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies"
>Extending and Versioning Languages: Compatibility
Strategies</a></cite> incorporates a number of reviews comments.
The TAG reviewed the
<a href="http://www.w3.org/2001/tag/doc/versioning-compatibility-strategies-20080912.html">
12 September 2008</a> during its
<a href="http://www.w3.org/2001/tag/2008/09/f2fkc-agenda">September F2F</a> and
decided to include a formalism based on
<a href="http://lists.w3.org/Archives/Public/www-tag/2008May/0155.html">work by
Jonathan Rees</a>. Finding a concise way to distill the experience from
a large history of examples continues to be a challenge.
</p>
</div>
<div><h2>Protocols: widget packaging, HTTP scalability, linking</h2>
<p>The TAG has opened a new issue, <a
href="http://www.w3.org/2001/tag/group/track/issues/61">uriBasedPackageAccess-61</a>,
in response to a <a
href="http://lists.w3.org/Archives/Public/www-tag/2008Jun/0090">request</a>
for support from the Web Applications Formats (<a
href="http://www.w3.org/2008/webapps/">WAF</a>) community to consider
URI based access and reference to items within a web accessible
package. The TAG expects to help address the requirements of not only
the WAF community in support of their current work on <a
href="http://www.w3.org/TR/widgets/">widgets</a> but also related
situations that involve reference within and into packaged
structures on the web.
The TAG plans to meet with the <a href="http://www.w3.org/2008/webapps/">WebApps
WG</a> on this topic during
<a href="http://www.w3.org/2008/10/TPAC/Schedule.html#Mon">TPAC 2008</a>
</p>
<p>In a <a
href="http://www.w3.org/2001/tag/2008/06/19-tagmem-minutes#item03">19
June discussion of issue scalabilityOfURIAccess-58</a>, the TAG
encouraged use of XML catalogs as a caching mechanism to mitigate the
load that automated access to DTDs and schemas put on the W3C web site.
</p>
<p>Protocol support for linking, e.g. from non-hypertext formats, was
in early drafts of HTTP but did not receive enough implementation
experience to be ratified in <a
href="http://www.w3.org/Protocols/rfc2616/rfc2616.html" >RFC 2616</a>
in June 1999. An <cite><a
href="http://tools.ietf.org/id/draft-nottingham-http-link-header-01.txt">HTTP
Header Linking</a></cite> draft of 14 March "clarifies the status of
the Link HTTP header and attempts to consolidate link relations in a
single registry." A <a
href="http://lists.w3.org/Archives/Public/www-tag/2008May/0022.html">9
May message from the POWDER Working Group chair</a> explains use cases
that seem to be satisfied by an HTTP Link header field. After a
lengthy <a
href="http://lists.w3.org/Archives/Public/www-tag/2008Mar/0024">Uniform
Access to Metadata</a> thread, the TAG encouraged the use of Link for
POWDER, among other scenarios in a <a
href="http://lists.w3.org/Archives/Public/www-tag/2008Jun/0082.html">13
Jun message</a> following our <a
href="http://www.w3.org/2001/tag/2008/05/20-minutes#item06">20 May
discussion of issue httpRedirections-57</a>.
</p>
<p>Also following our <a
href="http://www.w3.org/2001/tag/2008/05/19-agenda">May meeting in
Bristol</a>, we invited comment on the 2 June draft of <cite>
<a href="http://www.w3.org/2001/tag/doc/passwordsInTheClear-52-20080602.html">Passwords
in the Clear</a></cite>, especially from the HTML Working Group and the Web
Security Context Working Group. A further
<a href="http://www.w3.org/2001/tag/doc/passwordsInTheClear-52-20080912.html">
draft</a> was discussed at our
<a href="http://www.w3.org/2001/tag/2008/09/25-minutes#item01">September F2F</a>
and a TAG approved <i>
<a href="http://www.w3.org/2001/tag/doc/passwordsInTheClear-52-20081008.html">
Passwords in the Clear</a></i> finding was published on 15 October.</p>
</div>
<div><h2>Naming: XRIs</h2>
<p>The TAG is working on comparing HTTP and DNS to other approaches to
persistent naming such as <tt>info:</tt> and <tt>xri:</tt> under issue
<a href="http://www.w3.org/2001/tag/group/track/issues/50">issue
URNsAndRegistries-50</a>. While the <cite><a
href="http://www.w3.org/2001/tag/doc/URNsAndRegistries-50.html" >URNs,
Namespaces and Registries</a></cite> draft has been preempted by other
work since the last update of August 2006, the TAG discovered a 31 May
deadline on a <a
href="http://www.oasis-open.org/committees/ballot.php?id=1468">ballot
to Approve XRI Resolution v2.0 as an OASIS Standard</a> and summarized
its position: <a
href="http://lists.w3.org/Archives/Public/www-tag/2008May/0078.html"
>TAG recommends against XRI</a>. In an attempt to facilitate dialog
after this somewhat awkward step, the TAG and the <a
href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xri">OASIS
XRI TC</a> held a <a
href="http://www.w3.org/2001/tag/2008/07/03-tag-xri-minutes">3 July
joint meeting</a> and continue the discussion by email in <a
href="http://lists.w3.org/Archives/Public/www-tag/2008Aug/thread.html">www-tag</a>
with the goals of improving understanding of our respective positions and to
publically record points of agreement and if necessary irresolvable
disagreement. </p>
<p>Discussion of with the OASIS XRI TC has continued through October 2008 with
improving levels of mutual understanding and much less talking past one
another. The XRI TC are currently exploring alternate approaches to meeting their
requirements using existing URI schemes with the intention of developing an
approach aligned with the <a href="http://www.w3.org/TR/webarch">Architecture
of the World Wide Web</a>.</p>
</div>
<div>
<h2><a id="about" name="about">About the Technical Architecture Group</a></h2>
<p>The Technical Architecture Group (TAG) was created in February 2001. Three TAG participants are appointed by the
Director and five TAG participants are elected by the Advisory Committee. The
<a href="http://www.w3.org/2004/10/27-tag-charter.html">mission of the TAG</a> is stewardship of the Web architecture.
Included in this mission is building consensus around principles of Web architecture, resolving issues involving Web
architecture, and helping to coordinate cross-technology architecture developments inside and outside W3C.</p>
<p>Details on TAG activities can be found from the
<a href="http://www.w3.org/2001/tag/">TAG home page</a>. The TAG
meets weekly and sends summaries of its activity to the AC, Chairs, and public TAG mailing list (<a
href="http://lists.w3.org/Archives/Public/www-tag/">www-tag archive</a>). The TAG welcomes public discussion of open
issues, as well as proposals for new issues, on that same list.</p>
<h2><a id="tag" name="tag">TAG Participants</a></h2>
<p>Following the TAG
<a href="http://lists.w3.org/Archives/Member/w3c-ac-members/2008JanMar/0020.html">election results</a> announced in January 2008, the TAG participants are:</p>
<ul>
<li class="vcard"><span class="fn">Tim Berners-Lee</span> (<span class="org">W3C</span>)
(<span class="role">Chair</span>)</li>
<li class="vcard">Dan Connolly (W3C) staff contact</li>
<li class="vcard"><span class="fn">Ashok Malhotra</span> (<span class="org">Oracle</span>)<sup><a href="#term2">2</a></sup>
</li>
<li class="vcard"><span class="fn">Noah Mendelsohn</span> (<span class="org">IBMM</span>)<sup><a href="#term4">4</a></sup>
</li>
<li class="vcard"><span class="fn">David Orchard</span> (<span class="org">BEA</span>)<sup><a href="#term1">1</a></sup>
</li>
<li class="vcard"><span class="fn">T. V. Raman</span> (<span class="org">Google</span>)<sup><a href="#term1">1</a></sup>
</li>
<li class="vcard"><span class="fn">Jonathan Rees</span> (<span class="org">Science
Commons</span>)<sup><a href="#term4">4</a></sup> </li>
<li class="vcard"><span class="fn">Henry Thompson</span> (<span class="org">U.
of Edinburgh</span>)<sup><a href="#term2">2</a></sup> </li>
<li class="vcard"><span class="fn">Norm Walsh</span> (<span class="org">Sun</span>)<sup><a href="#term1">1</a></sup>
</li>
<li class="vcard"><span class="fn">Stuart Williams</span> (<span class="org">HP)</span><sup><a href="#term3">3</a></sup><span class="org">
co-chair</span><sup> </sup></li>
</ul>
<p>Notes:</p>
<ul>
<li><sup><a id="term1" name="term1">1</a></sup> elected through 31 Jan 2009</li>
<li><sup><a id="term2" name="term2">2</a></sup> elected through 31 Jan 2010</li>
<li><sup><a id="term3" name="term3">3</a></sup> appointed through 31 Jan 2009</li>
<li><sup><a id="term4" name="term4">4</a></sup> appointed through 31 Jan 2010</li>
</ul>
</div>
<hr />
<address>
Dan Connolly, W3C TAG team contact, August 2008<br>
Stuart Williams, TAG co-chair, October 2008<br />
<small>$Revision: 1.3 $ of $Date: 2008/10/17 12:21:47 $</small>
</address>
</body>
</html>