index.html
37.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
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
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Web Architecture - W3C Blog - Category Archives</title>
<style type="text/css" media="all">
@import "/QA/2006/01/blogstyle.css";
</style>
<meta name="keywords" content="W3C, QA, weblog, blog" />
<meta name="description" content="Archives for the W3C Questions and Answers Weblog - Category Web Architecture" />
<meta name="revision" content="$Id: index.html,v 1.270 2011/12/24 18:51:07 mirror Exp $" />
<link rel="alternate" type="application/atom+xml" title="Atom" href="http://www.w3.org/QA/atom.xml" />
<link rel="alternate" type="application/rss+xml" title="RSS 1.0" href="http://www.w3.org/QA/news.rss" />
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://www.w3.org/QA/rsd.xml" />
</head>
<body>
<div id="banner">
<h1 id="title">
<a href="http://www.w3.org/"><img height="48" alt="W3C" id="logo" src="http://www.w3.org/Icons/WWW/w3c_home_nb" /></a>
W3C Blog - Archives
</h1>
</div>
<ul class="navbar" id="menu">
<li><strong><a href="/QA/" title="W3C Blog Home">[ W3C Blog ]</a></strong></li>
<li><a href="/QA/Library/" title="Documents and Publications on Web and Quality">Documents</a></li>
<li><a href="/QA/Tools/" accesskey="3" title="Validators and other Tools">Tools</a></li>
<li><a href="/2007/12/qa-blog-help/index#feedback">Feedback</a></li>
</ul>
<div id="searchbox">
<form method="get" action="http://www.google.com/custom" enctype="application/x-www-form-urlencoded">
<p id="formbox"><input type="text" size="15" class="textfield" name="q" accesskey="E" maxlength="255" /> <input type="submit" class="submitfield" value="Search" id="goButton" name="sa" accesskey="G" /> <input type="hidden" name="cof" value="T:black;LW:72;ALC:#ff3300;L:http://www.w3.org/Icons/w3c_home;LC:#000099;LH:48;BGC:white;AH:left;VLC:#660066;GL:0;AWFID:0b9847e42caf283e;" /><input type="hidden" id="searchW3C" name="sitesearch" checked="checked" value="www.w3.org/QA" /><input type="hidden" name="domains" value="www.w3.org/QA" /></p>
</form>
</div>
<div id="main"><!-- This DIV encapsulates everything in this page - necessary for the positioning -->
<h2>Archives for Category: Web Architecture</h2>
<h3><a href="http://www.w3.org/QA/2011/12/w3c_tag_publishes_finding_on_i.html">W3C TAG Publishes Finding on Identifying Application State</a></h3>
<p><p>The W3C TAG has published a finding on Identifying Application State. See <a href="http://www.w3.org/2001/tag/doc/IdentifyingApplicationState">http://www.w3.org/2001/tag/doc/IdentifyingApplicationState</a></p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2011/12/w3c_tag_publishes_finding_on_i.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Ashok Malhotra</a> on December 24, 2011 4:53 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/12/w3c_tag_publishes_finding_on_i.html">Permalink</a>
| <a href="http://www.w3.org/QA/2011/12/w3c_tag_publishes_finding_on_i.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2011/12/w3c_tag_publishes_finding_on_i.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2011/05/hash_uris.html">Hash URIs</a></h3>
<p><p>There's been quite a bit of discussion recently about the use of hash-bang URIs following their adoption by Gawker, and the ensuing downtime of that site. The TAG at the W3C have also been drafting a document on Repurposing the Hash Sign for the New Web which takes a rather wider view than just the hash-bang issue, and on which they are seeking comments.</p>
<p>All matters of design involve weighing different choices against some criteria that you decide on implicitly or explicitly: there is no single right way of doing things on the web. Here, I explore the choices that are available to web developers around hash URIs and discuss how to mitigate the negative aspects of adopting the hash-bang pattern.<br />
</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2011/05/hash_uris.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Jeni Tennison</a> on May 12, 2011 6:17 PM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2011/05/hash_uris.html">Permalink</a>
| <a href="http://www.w3.org/QA/2011/05/hash_uris.html#comments">Comments (4)</a>
| <a href="http://www.w3.org/QA/2011/05/hash_uris.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2010/07/new_opportunities_for_linked_d.html">New opportunities for linked data nose-following</a></h3>
<p><p> For those of you interested in deploying RDF on the Web, I'd like to draw your attention to three new proposed standards from IETF, "Web Linking", "Defining Well-Known URIs", and "Web Host Metadata", that create new follow-your-nose tricks that...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2010/07/new_opportunities_for_linked_d.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Jonathan Rees</a> on July 6, 2010 6:12 PM in <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/07/new_opportunities_for_linked_d.html">Permalink</a>
| <a href="http://www.w3.org/QA/2010/07/new_opportunities_for_linked_d.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2010/07/new_opportunities_for_linked_d.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2010/06/thanks_for_a_great_15_years_at.html">Thanks for a great 15 years at W3C</a></h3>
<p><p>After 15 years working with all of you all around the world on Web technologies and standards, I'm taking a position as a Biomedical Informatics Software Engineer in the department of biostatistics at the University of Kansas Medical center. The...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2010/06/thanks_for_a_great_15_years_at.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on June 2, 2010 7:04 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/w3c_life/">W3C Life</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/06/thanks_for_a_great_15_years_at.html">Permalink</a>
| <a href="http://www.w3.org/QA/2010/06/thanks_for_a_great_15_years_at.html#comments">Comments (30)</a>
| <a href="http://www.w3.org/QA/2010/06/thanks_for_a_great_15_years_at.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html">The Mission of W3C</a></h3>
<p><p>I've now been with W3C for almost three months. My first priority was to meet with the global stakeholders of the organization. I began with W3C membership. Through meetings, phone calls, technical conferences, and informal sessions I've met upwards of...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Jeff/">Jeff Jaffe</a> on June 1, 2010 2:20 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/ceo/">CEO</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html">Permalink</a>
| <a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2010/06/the_mission_of_w3c.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2010/04/why_does_the_address_bar_show.html">Why does the address bar show the tempolink instead of the permalink?</a></h3>
<p><p>An important feature of HTTP is the temporary redirect, where a resource can have a "permanent" URI while its content moves from place to place over time. For example, http://purl.org/syndication/history/1.0 remains a constant name for that resource even though its...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2010/04/why_does_the_address_bar_show.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Jonathan Rees</a> on April 19, 2010 1:59 PM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2010/04/why_does_the_address_bar_show.html">Permalink</a>
| <a href="http://www.w3.org/QA/2010/04/why_does_the_address_bar_show.html#comments">Comments (4)</a>
| <a href="http://www.w3.org/QA/2010/04/why_does_the_address_bar_show.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/11/default_prefix_declaration.html">Default Prefix Declaration</a></h3>
<p><p>In this posting, my intention is to provide a concise statement of an idea which is neither<br />
particularly new nor particularly mine, but which needs a place that can be referenced in the context of the current debate about distributed extensibility and HTML5. It's a very simple proposal to provide an out-of-band, defaultable, document-scoped means to declare namespace prefix bindings.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/11/default_prefix_declaration.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Henry S. Thompson</a> on November 18, 2009 2:23 PM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/11/default_prefix_declaration.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/11/default_prefix_declaration.html#comments">Comments (10)</a>
| <a href="http://www.w3.org/QA/2009/11/default_prefix_declaration.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/07/tag_status_report_july_2009.html">TAG Status Report: July, 2009</a></h3>
<p><p>The latest status report to the W3C membership from the TAG is available at http://www.w3.org/2001/tag/2009/sum07. Noah...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/07/tag_status_report_july_2009.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Noah Mendelsohn</a> on July 31, 2009 2:55 PM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/07/tag_status_report_july_2009.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/07/tag_status_report_july_2009.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2009/07/tag_status_report_july_2009.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/06/orthogonality_of_specification.html"> Orthogonality of Specifications</a></h3>
<p><p>HTTP,HTML,URI The general principle of platform design is that platforms consist of a set of standard interfaces. Standard interfaces allow substitution of components across the interface boundary, while independence of interfaces allow evolution of the interfaces themselves. In a PC,...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/06/orthogonality_of_specification.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://larry.masinter.net">Larry Masinter</a> on June 24, 2009 1:03 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/06/orthogonality_of_specification.html">Permalink</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/05/language_semantics_and_operati.html">Language semantics and operational meaning</a></h3>
<p><p> W3C and other standards organizations are in the business of defining languages -- conventions that organizations can choose to follow -- and not in mandating operational behavior -- telling organizations and participants in the network how they are supposed...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/05/language_semantics_and_operati.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://larry.masinter.net">Larry Masinter</a> on May 19, 2009 6:45 PM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/05/language_semantics_and_operati.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/05/language_semantics_and_operati.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2009/05/language_semantics_and_operati.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/05/structured_data_and_search_eng.html">Search Engines take on Structured Data</a></h3>
<p><p>Structured data on the web got a boost this week, with Google's announcement of Rich Snippets and Rich Snippets in Custom Search. Structured data at such a large scale raises at least three issues:SyntaxVocabularyPolicyGoogle's documentation shows support for both microformats...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/05/structured_data_and_search_eng.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on May 13, 2009 4:18 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a>, <a href="http://www.w3.org/QA/archive/technology/egov/">eGov</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/05/structured_data_and_search_eng.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/05/structured_data_and_search_eng.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2009/05/structured_data_and_search_eng.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/05/data_interchange_problems_come.html">Data interchange problems come in all sizes</a></h3>
<p><p> I had a pretty small data interchange problem the other day: I just wanted to archive some play lists that I had compiled using various music player daemon (mpd) clients. The mpd server stores playlists as simple m3u files,...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/05/data_interchange_problems_come.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on May 8, 2009 9:10 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/05/data_interchange_problems_come.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/05/data_interchange_problems_come.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2009/05/data_interchange_problems_come.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/05/once_more_into_versioning_--_t.html">Once more into Versioning -- this time with HTML</a></h3>
<p><p>The W3C TAG has worked on the general issue of "versioning" for many years, and many TAG members may be worn out on the issue. However, undeterred by past history, I'm taking another run at it, this time trying to...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/05/once_more_into_versioning_--_t.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://larry.masinter.net">Larry Masinter</a> on May 4, 2009 5:39 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/05/once_more_into_versioning_--_t.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/05/once_more_into_versioning_--_t.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2009/05/once_more_into_versioning_--_t.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/02/palm_webos_approach_to_html_ex.html">Palm webOS approach to HTML extensibility: x-mojo-*</a></h3>
<p><p> I got pretty excited about the iPhone, and even more about the openness of Android and the G1, and then I learn that the Palm Pre developer platform is basically just the open web platform: HTML, CSS, and JavaScript....</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/02/palm_webos_approach_to_html_ex.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on February 16, 2009 5:04 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/mobile/">Mobile</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/02/palm_webos_approach_to_html_ex.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/02/palm_webos_approach_to_html_ex.html#comments">Comments (3)</a>
| <a href="http://www.w3.org/QA/2009/02/palm_webos_approach_to_html_ex.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html">JavaScript required for basic textual info? TRY AGAIN</a></h3>
<p><p>Sam says he's Online and Airborne. "Needless to say, this is seriously cool." I'll say! But when I follow the link to details from the service provider, I get:Sorry. You must have JavaScript enabled to view this page. Click the...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on January 27, 2009 10:01 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/security/">Security</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html">Permalink</a>
| <a href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html#comments">Comments (8)</a>
| <a href="http://www.w3.org/QA/2009/01/javascript_required_for_basic.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/12/web_applications_security_requ.html">How to evaluate Web Applications security designs?</a></h3>
<p><p> I could use some help getting my head around security for Web Applications and mashups. The first time someone told me W3C should be working on specs help the browser prevent sensitive data from leaking out of enterprises, I...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/12/web_applications_security_requ.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on December 3, 2008 5:00 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/12/web_applications_security_requ.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/12/web_applications_security_requ.html#comments">Comments (3)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/09/caching_xml_data_at_install_ti.html">Caching XML data at install time</a></h3>
<p><p>The W3C web server is spending most of its time serving DTDs to various bits of XML processing software. While XSLT processors such as xsltproc and Xalan have no technical dependency on the XHTML DTDs, I suspect they're used with XHTML enough that shipping copies of the DTDs along with the XSLT processing software is a win all around.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/09/caching_xml_data_at_install_ti.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on September 4, 2008 9:29 PM in <a href="http://www.w3.org/QA/archive/technology/http/">HTTP</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/09/caching_xml_data_at_install_ti.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/09/caching_xml_data_at_install_ti.html#comments">Comments (4)</a>
| <a href="http://www.w3.org/QA/2008/09/caching_xml_data_at_install_ti.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/08/the_details_of_data_in_documen.html">The details of data in documents: GRDDL, profiles, and HTML5</a></h3>
<p><p>GRDDL, a mechanism for putting RDF data in XML/XHTML documents, is specified mostly at the XPath data model level. Some GRDDL software goes beyond XML and supports HTML as she are spoke, aka tag soup. HTML 5 is intended to...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/08/the_details_of_data_in_documen.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on August 22, 2008 7:45 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a>, <a href="http://www.w3.org/QA/archive/technology/xml/">XML</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/08/the_details_of_data_in_documen.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/08/the_details_of_data_in_documen.html#comments">Comments (2)</a>
| <a href="http://www.w3.org/QA/2008/08/the_details_of_data_in_documen.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/07/life_without_mime_type_sniffin.html">life without MIME type sniffing?</a></h3>
<p><p> In a recent item on IE8 Security, Eric Lawrence, Security Program Manager for Internet Explorer, introduced a work-around to the security risks associated with content-type sniffing: an authoritative=true parameter on the Content-Type header in HTTP. This re-started discussion of...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/07/life_without_mime_type_sniffin.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on July 7, 2008 5:19 PM in <a href="http://www.w3.org/QA/archive/w3cqa_news/bugs_life/">Bugs Life</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/07/life_without_mime_type_sniffin.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/07/life_without_mime_type_sniffin.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2008/07/life_without_mime_type_sniffin.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/05/syntax_for_aria_costbenefit_an.html">Syntax for ARIA: Cost-benefit analysis</a></h3>
<p><p>The ARIA spec. defines roles, states and properties to manage the interface<br />
between rich web documents and assistive technologies. The primary expression<br />
of roles, states and properties in markup languages is via attributes. ARIA has to specify how its vocabulary of attributes and values can be<br />
integrated into both existing and future languages. This analysis assesses alternative approaches to ARIA syntax.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/05/syntax_for_aria_costbenefit_an.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Henry S. Thompson</a> on May 7, 2008 4:15 PM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/05/syntax_for_aria_costbenefit_an.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/05/syntax_for_aria_costbenefit_an.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2008/05/syntax_for_aria_costbenefit_an.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html">Proposed Activity for Video on the Web</a></h3>
<p><p>W3C organized a workshop on Video on the Web in December 2007 in order<br />
to share current experiences and examine the technologies (see <a href='http://www.w3.org/2007/08/video/report.html'>report</a>) and is now following up with a proposal for a Video on the Web activity.</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/LeHegaret/">Philippe Le Hégaret</a> on April 15, 2008 3:29 PM in <a href="http://www.w3.org/QA/archive/technology/accessibility/">Accessibility</a>, <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/technology/http/">HTTP</a>, <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a>, <a href="http://www.w3.org/QA/archive/technology/">Technology</a>, <a href="http://www.w3.org/QA/archive/technology/video/">Video</a>, <a href="http://www.w3.org/QA/archive/w3cqa_news/">W3C・QA News</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2008/04/proposed_activity_for_video_on.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2008/01/modularity.html">Simple things make firm foundations</a></h3>
<p><p>You can look at the development of web technology in many ways, but one way is as a major software project. In software projects, the independence of specs, has always been really important, I have felt. A classic example is...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2008/01/modularity.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Berners-Lee/">Tim Berners-Lee</a> on January 18, 2008 3:39 PM in <a href="http://www.w3.org/QA/archive/technology/html/">HTML</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2008/01/modularity.html">Permalink</a>
| <a href="http://www.w3.org/QA/2008/01/modularity.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2008/01/modularity.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2007/12/version_identifiers_reconsider.html">Version Identifiers Reconsidered</a></h3>
<p><p>The <a href="http://www.w3.org/TR/webarch/">Architecture of the World Wide Web</a> includes a <a href="http://www.w3.org/TR/webarch/#ext-version">section</a> on extensibility and versioning of languages and data formats. The TAG is having second thoughts about the suggestion that all data formats SHOULD provide for version identification. Sometimes it is a good thing to do, but sometimes not. </p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2007/12/version_identifiers_reconsider.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Noah Mendelsohn</a> on December 18, 2007 6:10 PM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/12/version_identifiers_reconsider.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/12/version_identifiers_reconsider.html#comments">Comments (4)</a>
| <a href="http://www.w3.org/QA/2007/12/version_identifiers_reconsider.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2007/11/what_comes_after_web_20_tv_ram.html">What comes after Web 2.0? TV Raman says: 2^W</a></h3>
<p><p>TPAC talk molly's item wish for mathml in HTML...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2007/11/what_comes_after_web_20_tv_ram.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on November 15, 2007 12:53 PM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/11/what_comes_after_web_20_tv_ram.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/11/what_comes_after_web_20_tv_ram.html#comments">Comments (0)</a>
| <a href="http://www.w3.org/QA/2007/11/what_comes_after_web_20_tv_ram.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2007/11/a_story_about_namespaces_mime.html">A story about namespaces, MIME types, and URIs</a></h3>
<p><p>Noone seems to know where the story begins; Ian Jacobs reminded me about magic namespaces as I enjoyed breakfast on Thursday; Steven Pemberton and Bert Bos had told it to him, perhaps prompted by Ian Hickson's question in the URI-based...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2007/11/a_story_about_namespaces_mime.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on November 13, 2007 2:59 AM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/11/a_story_about_namespaces_mime.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/11/a_story_about_namespaces_mime.html#comments">Comments (2)</a>
</p>
<h3><a href="http://www.w3.org/QA/2007/10/the_impact_of_javascript_and_x.html">The impact of Javascript and XMLHttpRequest on web architecture</a></h3>
<p><p>This issue was raised briefly on the TAG telcon of 11 October 2007, but I think we dismissed it too quickly.The basic WebArch story about URIs, resources and representations makes sense to people because they can see the relationship between...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2007/10/the_impact_of_javascript_and_x.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="">Henry S. Thompson</a> on October 18, 2007 11:26 AM in <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/10/the_impact_of_javascript_and_x.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/10/the_impact_of_javascript_and_x.html#comments">Comments (6)</a>
| <a href="http://www.w3.org/QA/2007/10/the_impact_of_javascript_and_x.html#trackback">TrackBacks (0)</a>
</p>
<h3><a href="http://www.w3.org/QA/2007/03/orthogonal_specifications_is_good.html">When to standardize, especially an RDF API</a></h3>
<p><p>The HTML 4.01 specification has an IMG element, but there is no normative dependency on the PNG or GIF or JPEG specifications. "What good is an HTML user agent that doesn't support GIFs?!?" you might ask. And you wouldn't be...</p></p>
<p class="readmore"><a href="http://www.w3.org/QA/2007/03/orthogonal_specifications_is_good.html">» Read on...</a></p>
<p class="postinfo">Filed by <a href="http://www.w3.org/People/Connolly/">Dan Connolly</a> on March 2, 2007 12:47 AM in <a href="http://www.w3.org/QA/archive/web_spotting/opinions_editorial/">Opinions & Editorial</a>, <a href="http://www.w3.org/QA/archive/technology/semantic_web/">Semantic Web</a>, <a href="http://www.w3.org/QA/archive/web_architecture/">Web Architecture</a><br />
<span class="separator">|</span> <a class="permalink" href="http://www.w3.org/QA/2007/03/orthogonal_specifications_is_good.html">Permalink</a>
| <a href="http://www.w3.org/QA/2007/03/orthogonal_specifications_is_good.html#comments">Comments (1)</a>
| <a href="http://www.w3.org/QA/2007/03/orthogonal_specifications_is_good.html#trackback">TrackBacks (0)</a>
</p>
<p id="gentime">This page was last generated on $Date: 2011/12/24 18:51:07 $</p>
</div><!-- End of "main" DIV. -->
<address>
This blog is written by W3C staff and working group participants,<br />
and maintained by <a href="/People/CMercier/">Coralie Mercier</a>.<br />
Authorized parties may <a href="/QA/new">log in</a> to create a new entry.<br/>
<span id="poweredby">Powered by Movable Type, magpierss and a lot of Web Technology</span>
</address>
<p class="copyright">
<a rel="Copyright" href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 1994-2011
<a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a>®
(<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>,
<a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>,
<a href="http://www.keio.ac.jp/">Keio</a>),
All Rights Reserved.
W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>,
<a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
and <a rel="Copyright" href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
rules apply. Your interactions with this site are in accordance
with our <a href="http://www.w3.org/Consortium/Legal/privacy-statement#Public">public</a> and
<a href="http://www.w3.org/Consortium/Legal/privacy-statement#Members">Member</a> privacy
statements.
</p>
</body>
</html>