feedvalidator 0.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/CHANGELOG +2 -0
- data/README +71 -0
- data/install.rb +30 -0
- data/lib/feed_validator.rb +164 -0
- data/lib/feed_validator/assertions.rb +91 -0
- data/rakefile +109 -0
- data/test/feeds/weblog.rubyonrails.org_rss_2_0_articles.xml +154 -0
- data/test/feeds/www.w3.org_news.rss.xml +843 -0
- data/test/responses/success_with_warnings +40 -0
- data/test/unit/feed_validator_assertions_test.rb +48 -0
- data/test/unit/feed_validator_test.rb +63 -0
- metadata +54 -0
|
@@ -0,0 +1,154 @@
|
|
|
1
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
|
2
|
+
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
|
|
3
|
+
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
|
|
4
|
+
<channel>
|
|
5
|
+
<title>Riding Rails</title>
|
|
6
|
+
<link>http://weblog.rubyonrails.com/</link>
|
|
7
|
+
<language>en-us</language>
|
|
8
|
+
<ttl>40</ttl>
|
|
9
|
+
<description></description>
|
|
10
|
+
<item>
|
|
11
|
+
<title>Secrets Behind Ruby on Rails: The Numbers</title>
|
|
12
|
+
<description><p>ITConversations has just made David&#8217;s <a href="http://conferences.oreillynet.com/os2005/">OSCON 2005</a> keynote, <a href="http://www.itconversations.com/shows/detail658.html"><em>Secrets Behind Ruby on Rails</em></a>, available for <a href="http://www.itconversations.com/audio/download/ITConversations-658.mp3">download</a>.</p>
|
|
13
|
+
|
|
14
|
+
|
|
15
|
+
<p>One of the big stories for Rails in August was the numbers behind its budding ecosystem. The conference fell right around Rails&#8217; first anniversary and the numbers one year in were promising. Today, six months down the road, they keep going up.</p>
|
|
16
|
+
|
|
17
|
+
|
|
18
|
+
<p>In the year between when Rails was released and the <span class="caps">OSCON 2005</span> keynote, it was downloaded 100,000 times. In the six months since then it&#8217;s up to 300,000.</p>
|
|
19
|
+
|
|
20
|
+
|
|
21
|
+
<p>Estimates on the Rails wiki in August indicated that there were no fewer than 250 programmers in 36 countries getting payed to work professionally with Rails. There are now <a href="http://wiki.rubyonrails.org/rails/pages/WorkingProfessionallyWithRails">over 550 Rails programmers in 50 countries</a>, including Azerbaijan!</p>
|
|
22
|
+
|
|
23
|
+
|
|
24
|
+
<p>When <a href="http://www.pragmaticprogrammer.com/titles/rails/">Agile Web Development with Rails</a> was released it sold 6 thousand books in its first run. Six months later, its sales are over 25 thousand. Rails publishing is busy, with <a href="http://weblog.rubyonrails.com/articles/2006/01/23/oreillys-first-rails-book-premieres-in-beta-form">even</a> <a href="http://weblog.rubyonrails.org/articles/2005/12/17/ruby-for-rails-ruby-techniques-for-rails-developers">more</a> <a href="http://weblog.rubyonrails.com/articles/2006/01/14/rapid-web-development-mit-ruby-on-rails">titles</a> upcoming, such as the <a href="http://www.pragmaticprogrammer.com/titles/fr_rr/">Rails Recipes</a> cookbook, which is scheduled to be available in beta sometime this February.</p>
|
|
25
|
+
|
|
26
|
+
|
|
27
|
+
<p>There are now around 400 people in the <code>#rubyonrails</code> IRC channel, about the same as <code>#php</code>. The Rails mailing list is as <a href="http://blog.inquirylabs.com/wp-content/uploads/2006/01/Rails%20and%20PHP%20mailing%20lists.png">busy as ever</a>.</p>
|
|
28
|
+
|
|
29
|
+
|
|
30
|
+
<p>Six months from now? The first annual <a href="http://railsconf.org">Rails Conference</a>. The next half year promises to be interesting. See you there.</p></description>
|
|
31
|
+
<pubDate>Wed, 01 Feb 2006 05:50:00 +0000</pubDate>
|
|
32
|
+
<guid isPermaLink="false">urn:uuid:967e9c30-7e78-4701-b9d4-bbf733495e87</guid>
|
|
33
|
+
<author></author>
|
|
34
|
+
<link>http://weblog.rubyonrails.com/articles/2006/02/01/secrets-behind-ruby-on-rails-the-numbers</link>
|
|
35
|
+
<category>Horizon</category>
|
|
36
|
+
<category>Sightings</category>
|
|
37
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3133</trackback:ping>
|
|
38
|
+
</item>
|
|
39
|
+
<item>
|
|
40
|
+
<title>Running Rails on the LiteSpeed webserver</title>
|
|
41
|
+
<description><p>The <a href="http://www.litespeedtech.com/">LiteSpeed Web Server</a> is a commercial engine made to be largely config-compatible with Apache, but promising massive speed increases. If the web server is the bottleneck in your setup, you may just want to give it a look. And what better way than to get your Rails application up and running on it. Bob Silva explains <a href="http://www.railtie.net/articles/2006/01/21/up-and-running-in-the-speed-of-light">in easy steps how</a>.</p></description>
|
|
42
|
+
<pubDate>Thu, 26 Jan 2006 15:52:05 +0000</pubDate>
|
|
43
|
+
<guid isPermaLink="false">urn:uuid:bc8abcda-7759-4f1d-92d3-e5c0cc736d7a</guid>
|
|
44
|
+
<author>David</author>
|
|
45
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/26/running-rails-on-the-litespeed-webserver</link>
|
|
46
|
+
<category>Sightings</category>
|
|
47
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3087</trackback:ping>
|
|
48
|
+
</item>
|
|
49
|
+
<item>
|
|
50
|
+
<title>Camping: A micro-version of Rails</title>
|
|
51
|
+
<description><p>why the lucky stiff is at it again with his great stuff. This time he has produced a <a href="http://camping.rubyforge.org/">microframework called Camping</a> in the spirit and feel of Rails, but clocking in at just 4kb! Sure, it won&#8217;t do what most people need most of the time. But often, there&#8217;s good value in doing a bit of what a few people need occasionally. Camping, as the framework is called, fits that description to a T.</p>
|
|
52
|
+
|
|
53
|
+
|
|
54
|
+
<p>And since it conceptually lies close to Rails, you could easily start a quick thing in Camping and then not have too much trouble porting it to be a full-grown Rails application if need be. Camping even uses ActiveRecord to make it all that much easier.</p>
|
|
55
|
+
|
|
56
|
+
|
|
57
|
+
<p>Checkout the insane and <a href="http://redhanded.hobix.com/bits/campingAMicroframework.html">too funny announcement</a> that even includes this classic description of <span class="caps">XML</span> sit-ups:</p>
|
|
58
|
+
|
|
59
|
+
|
|
60
|
+
<p><img src="http://redhanded.hobix.com/images/camping-xml-situps.png" /></p></description>
|
|
61
|
+
<pubDate>Thu, 26 Jan 2006 03:09:35 +0000</pubDate>
|
|
62
|
+
<guid isPermaLink="false">urn:uuid:677bdb11-f101-47a3-87da-9b4d7e020c7e</guid>
|
|
63
|
+
<author>David</author>
|
|
64
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/26/camping-a-micro-version-of-rails</link>
|
|
65
|
+
<category>Sightings</category>
|
|
66
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3078</trackback:ping>
|
|
67
|
+
</item>
|
|
68
|
+
<item>
|
|
69
|
+
<title>Globalize (i18n for Rails) gets new home</title>
|
|
70
|
+
<description><p><a href="http://www.globalize-rails.org">www.globalize-rails.org</a> is the new home for the Globalize plugin that brings i18n functionality to Rails. They&#8217;re tackling everything from translations of model data, to proper formating of local times, and much anything in between. Velbekommen!</p></description>
|
|
71
|
+
<pubDate>Tue, 24 Jan 2006 23:10:19 +0000</pubDate>
|
|
72
|
+
<guid isPermaLink="false">urn:uuid:40718348-d229-4eb5-8125-211a142e856f</guid>
|
|
73
|
+
<author>David</author>
|
|
74
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/24/globalize-i18n-for-rails-gets-new-home</link>
|
|
75
|
+
<category>Sightings</category>
|
|
76
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3056</trackback:ping>
|
|
77
|
+
</item>
|
|
78
|
+
<item>
|
|
79
|
+
<title>OpenLaszlo for Ruby on Rails</title>
|
|
80
|
+
<description><p><a href="http://osteele.com/projects/">Oliver Steele</a> is working on OpenLaszlo integration for Ruby on Rails. There&#8217;s a <a href="http://ropenlaszlo.rubyforge.org/">OpenLaszlo gem</a> out there now and <a href="http://laszlo-plugin.rubyforge.org/">a Rails plugin</a> to hook it all up for easy generation of OpenLaszlo applets. Check it out if <span class="caps">HTML</span> isn&#8217;t doing it for you on the view.</p></description>
|
|
81
|
+
<pubDate>Tue, 24 Jan 2006 23:00:22 +0000</pubDate>
|
|
82
|
+
<guid isPermaLink="false">urn:uuid:63154abc-8d98-40ee-8286-a59d4f207c27</guid>
|
|
83
|
+
<author>David</author>
|
|
84
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/24/openlaszlo-for-ruby-on-rails</link>
|
|
85
|
+
<category>Sightings</category>
|
|
86
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3055</trackback:ping>
|
|
87
|
+
</item>
|
|
88
|
+
<item>
|
|
89
|
+
<title>Pick a license for your Rails additions</title>
|
|
90
|
+
<description><p>Rails is released under <a href="http://dev.rubyonrails.org/browser/trunk/railties/MIT-LICENSE"><span class="caps">MIT</span></a> and only includes packages that are either directly under <span class="caps">MIT</span> or were re-licensed specifically for Rails under <span class="caps">MIT</span>. But not all plugins, generators, engines, or other types of additions are as explicitly clear as to what license they&#8217;re released under. It would be great if they were.</p>
|
|
91
|
+
|
|
92
|
+
|
|
93
|
+
<p>So, if you&#8217;re the creator of a Rails addition of any kind, please do pick a license and include it with your software. I recommend <a href="http://dev.rubyonrails.org/browser/trunk/railties/MIT-LICENSE"><span class="caps">MIT</span></a>.</p></description>
|
|
94
|
+
<pubDate>Tue, 24 Jan 2006 17:36:50 +0000</pubDate>
|
|
95
|
+
<guid isPermaLink="false">urn:uuid:3d831e55-ced8-4674-aff1-a3973ea7db54</guid>
|
|
96
|
+
<author>David</author>
|
|
97
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/24/pick-a-license-for-your-rails-additions</link>
|
|
98
|
+
<category>General</category>
|
|
99
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3032</trackback:ping>
|
|
100
|
+
</item>
|
|
101
|
+
<item>
|
|
102
|
+
<title>O'Reilly's first Rails book premieres in beta form</title>
|
|
103
|
+
<description><p><img src="http://www.oreilly.com/catalog/covers/rubyrails_rc.s.gif" border="0" align="right" style="margin-left: 10px" />O&#8217;Reilly has <a href="http://radar.oreilly.com/archives/2006/01/the_long_snout.html">launched</a> their Rough Cuts series with <a href="http://www.oreilly.com/catalog/rubyrails/">Ruby on Rails: Up and running</a> as one of the first titles leading the charge. Rough Cuts is O&#8217;Reilly&#8217;s version of <a href="http://www.pragmaticprogrammer.com/starter_kit/faqs/beta_faq.html">Beta Books</a> or <a href="http://manning.com/about/meap">Early Access</a> and gives you access to the content while it&#8217;s still being written.</p>
|
|
104
|
+
|
|
105
|
+
|
|
106
|
+
<p>Ruby on Rails: Up and running is written by Bruce Tate and Curt Hibbs. The final book is expected in May. Also of note for Railers on Rough Cut is <a href="http://www.oreilly.com/catalog/rubyckbk/">Ruby Cookbook</a> by Leonard Richardson and Lucas Carlson. That one is expected done in September. Not to be confused with the <a href="http://www.pragmaticprogrammer.com/titles/fr_rr/index.html">Rails Recipes</a> by Chad Fowler (featuring recipes and secrets from the 37signals dome) that&#8217;ll be out in February.</p>
|
|
107
|
+
|
|
108
|
+
|
|
109
|
+
<p>So that marks four books currently available in final or beta form that focuses exclusively or partly on Rails: <a href="http://www.pragmaticprogrammer.com/titles/rails/index.html">Agile Web Development with Rails</a> (the original bible), <a href="http://www.rapidwebdevelopment.de/">Rapid Web Development mit Ruby on Rails</a>, <a href="http://www.oreilly.com/catalog/rubyrails/">Ruby on Rails: Up and running</a>, and <a href="http://www.oreilly.com/catalog/rubyckbk/">Ruby Cookbook</a>. That&#8217;s quite an achievement already!</p>
|
|
110
|
+
|
|
111
|
+
|
|
112
|
+
<p>And coming soon will be Chad Fowler&#8217;s Rails Recipes and David A. Black&#8217;s Ruby for Rails, which will bring us to a total of six books. And I believe there&#8217;s at least a good handful of additional books in the works. Rails is certainly on track to be the best documented web framework for the dynamic languages. Rock on.</p></description>
|
|
113
|
+
<pubDate>Mon, 23 Jan 2006 23:27:00 +0000</pubDate>
|
|
114
|
+
<guid isPermaLink="false">urn:uuid:3b31f02e-96ff-4b67-970d-d29761bf3db6</guid>
|
|
115
|
+
<author>David</author>
|
|
116
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/23/oreillys-first-rails-book-premieres-in-beta-form</link>
|
|
117
|
+
<category>Documentation</category>
|
|
118
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3017</trackback:ping>
|
|
119
|
+
</item>
|
|
120
|
+
<item>
|
|
121
|
+
<title>Rails and the book both finalists for Jolt Awards</title>
|
|
122
|
+
<description><p><img src="http://www.sdmagazine.com/images/jolt_logo16_sm.gif" align="right" style="margin-left: 10px; border: 0"/><a href="http://www.sdmagazine.com/jolts/2005categories.html">The Jolt Awards</a> have been honoring products of excellence and high productivity for 15 years and this year both Rails 1.0 and <a href="http://www.pragmaticprogrammer.com/titles/rails/index.html">Agile Web Development with Rails</a> made the cut as finalists!</p>
|
|
123
|
+
|
|
124
|
+
|
|
125
|
+
<p>The <a href="http://www.prnewswire.com/cgi-bin/stories.pl?ACCT=104&amp;STORY=/www/story/01-20-2006/0004264613&amp;EDATE=">announcement</a> tells us that the book competes against such titles as Practical Common Lisp, Service-Oriented Architecture, and Wicked Cool Java. Rails 1.0 is going up against JBoss 4x, Coldfusion, and Zend Studio. Pretty exciting stuff. Hopefully we&#8217;ll be jolting in red shortly.</p></description>
|
|
126
|
+
<pubDate>Mon, 23 Jan 2006 05:02:16 +0000</pubDate>
|
|
127
|
+
<guid isPermaLink="false">urn:uuid:26b6880a-0b58-47f1-acb2-f3c71e893e93</guid>
|
|
128
|
+
<author>David</author>
|
|
129
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/23/rails-and-the-book-both-finalists-for-jolt-awards</link>
|
|
130
|
+
<category>Sightings</category>
|
|
131
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3009</trackback:ping>
|
|
132
|
+
</item>
|
|
133
|
+
<item>
|
|
134
|
+
<title>Rake 0.7.0 has been released</title>
|
|
135
|
+
<description><p><a href="http://ruby-talk.org/cgi-bin/scat.rb/ruby/ruby-talk/176161">Rake 0.7.0</a> has taken a great leap forward with the addition of parallel execution tasks and namespaces. Upcoming releases of Rails will surely use namespaces, so please do familiarize yourself with them today. And many thanks to Jim Weirich for his continued stellar work on this.</p></description>
|
|
136
|
+
<pubDate>Fri, 20 Jan 2006 19:07:30 +0000</pubDate>
|
|
137
|
+
<guid isPermaLink="false">urn:uuid:22b06624-5713-483f-9e96-b2d0ee402187</guid>
|
|
138
|
+
<author>David</author>
|
|
139
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/20/rake-0-7-0-has-been-released</link>
|
|
140
|
+
<category>Tools</category>
|
|
141
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3003</trackback:ping>
|
|
142
|
+
</item>
|
|
143
|
+
<item>
|
|
144
|
+
<title>Canada on Rails announces schedule</title>
|
|
145
|
+
<description><p>The <a href="http://canadaonrails.com/yvr06-schedule.html">schedule and list of speakers</a> for Canada on Rails has been announced. The conference is happening April 13-14th in Vancouver.</p></description>
|
|
146
|
+
<pubDate>Fri, 20 Jan 2006 18:23:23 +0000</pubDate>
|
|
147
|
+
<guid isPermaLink="false">urn:uuid:d1246cb1-ec09-4195-a8d2-7d577e78f891</guid>
|
|
148
|
+
<author>David</author>
|
|
149
|
+
<link>http://weblog.rubyonrails.com/articles/2006/01/20/canada-on-rails-announces-schedule</link>
|
|
150
|
+
<category>Sightings</category>
|
|
151
|
+
<trackback:ping>http://weblog.rubyonrails.com/archives/trackback/3000</trackback:ping>
|
|
152
|
+
</item>
|
|
153
|
+
</channel>
|
|
154
|
+
</rss>
|
|
@@ -0,0 +1,843 @@
|
|
|
1
|
+
<?xml version="1.0" encoding="utf-8"?>
|
|
2
|
+
|
|
3
|
+
<rdf:RDF
|
|
4
|
+
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
|
|
5
|
+
xmlns:dc="http://purl.org/dc/elements/1.1/"
|
|
6
|
+
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
|
|
7
|
+
xmlns:admin="http://webns.net/mvcb/"
|
|
8
|
+
xmlns:cc="http://web.resource.org/cc/"
|
|
9
|
+
xmlns="http://purl.org/rss/1.0/">
|
|
10
|
+
|
|
11
|
+
<channel rdf:about="http://www.w3.org/QA/">
|
|
12
|
+
<title>QA Weblog</title>
|
|
13
|
+
<link>http://www.w3.org/QA/</link>
|
|
14
|
+
<description></description>
|
|
15
|
+
<dc:language>en</dc:language>
|
|
16
|
+
<dc:creator>W3C QA Team</dc:creator>
|
|
17
|
+
|
|
18
|
+
<dc:date>2006-03-08T11:07:04+00:00</dc:date>
|
|
19
|
+
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=3.2" />
|
|
20
|
+
|
|
21
|
+
|
|
22
|
+
<items>
|
|
23
|
+
<rdf:Seq><rdf:li rdf:resource="http://www.w3.org/QA/2006/03/minutes_of_qa_ig_f2f_at_the_w3.html" />
|
|
24
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2006/02/content_negotiation.html" />
|
|
25
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2006/02/buy_standards_compliant_web_si.html" />
|
|
26
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2006/02/ruby_annotation_to_change_the.html" />
|
|
27
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2006/01/quality_assurance_interest_gro.html" />
|
|
28
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2006/01/failed_commitments.html" />
|
|
29
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/11/w3c_renews_quality_assurance_i.html" />
|
|
30
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/10/markup_validator_071.html" />
|
|
31
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/09/css_validator_updated.html" />
|
|
32
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/09/log_validator_10.html" />
|
|
33
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/09/the_qa_handbook_published_as_a.html" />
|
|
34
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/09/qa_at_w3c_continues_future_of.html" />
|
|
35
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/08/variability_in_specifications.html" />
|
|
36
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/08/qa_framework_specification_gui.html" />
|
|
37
|
+
<rdf:li rdf:resource="http://www.w3.org/QA/2005/08/w3c_markup_validator_v070_rele.html" />
|
|
38
|
+
</rdf:Seq>
|
|
39
|
+
</items>
|
|
40
|
+
|
|
41
|
+
</channel>
|
|
42
|
+
|
|
43
|
+
<item rdf:about="http://www.w3.org/QA/2006/03/minutes_of_qa_ig_f2f_at_the_w3.html">
|
|
44
|
+
<title>Minutes of QA IG F2F at the W3C Tech Plenary - February 2006</title>
|
|
45
|
+
<link>http://www.w3.org/QA/2006/03/minutes_of_qa_ig_f2f_at_the_w3.html</link>
|
|
46
|
+
<description> <![CDATA[<p>The first meeting of the <acronym title="Quality Assurance">QA</acronym> <acronym title="Interest Group">IG</acronym> has been very successful with a lot of interesting discussions and many projects for the future. <cite>Patrick Curran</cite>, participant of the QA IG, wrote <a href="http://blogs.sun.com/roller/page/pcurran/20060228">about the meeting on his weblog</a> and conclude by: <q>The Interest Group met yesterday and today to discuss how we should focus our efforts during the coming months. As always we have much more work to do than we have people to do it, so we would very much welcome assistance from people in the conformance testing community. Whether or not you're able to help, please join our mailing list and read our blog.</q></p>
|
|
47
|
+
|
|
48
|
+
<p>The <acronym title="Quality Assurance">QA</acronym> <acronym title="Interest Group">IG</acronym> <acronym title="face to face">F2F</acronym> has been held in Cannes Mandelieu, France during the W3C Technical Plenary from Monday 27th of February to Tuesday 28th of February 2006. This meeting was <strong>open to public participation</strong> in the room, as well on the phone or IRC (channel irc://irc.w3.org/#qa).</p>
|
|
49
|
+
|
|
50
|
+
<h3 id="participants">Participants</h3>
|
|
51
|
+
|
|
52
|
+
<ul>
|
|
53
|
+
<li>On site: Tim Boland (NIST), <a href="http://blogs.sun.com/roller/page/pcurran">Patrick Curran</a> (Sun Microsystems), <a href="http://www.w3.org/People/karl/">Karl Dubost</a> (W3C), Jacques Durand (Fujitsu), <a href="http://www.opera.com/company/investors/board/members/snorre/">Snorre M. Grimsby</a> (Opera), <a href="http://www.w3.org/People/Dom/">Dominique Hazaël-Massieux</a> (W3C), <a href="http://www.w3.org/People/olivier/">Olivier Théreaux</a> (W3C)</li>
|
|
54
|
+
<li>On phone: Lofton Henderson (CGM Open), Lynne Rosenthal (NIST)</li>
|
|
55
|
+
<li>On IRC: Björn Höhrmann, <a href="http://www.webstandards.org/about/bios/steph.html">Stephanie Troeth</a> (WASP), <a href="http://www.webstandards.org/about/bios/hmkoltz.html">Holly Marie Koltz</a> (WASP)</li>
|
|
56
|
+
</ul>
|
|
57
|
+
|
|
58
|
+
<p>Regrets: Mark Skall</p>
|
|
59
|
+
<ol>
|
|
60
|
+
<li><a href="#test-metadata">Test Cases Metadata</a></li>
|
|
61
|
+
<li><a href="#w3c-glossary">W3C Glossary system</a></li>
|
|
62
|
+
<li><a href="#cuap-chips">CUAP and CHIPs</a></li>
|
|
63
|
+
<li><a href="#qa-findings">QA Findings</a></li>
|
|
64
|
+
<li><a href="#qa-weblog">QA Weblog</a></li>
|
|
65
|
+
<li><a href="#ebnf">EBNF discussion</a></li>
|
|
66
|
+
<li><a href="#test-assertion">Test Assertion Guide</a></li>
|
|
67
|
+
<li><a href="#organization-qaig">Organization of QAIG</a></li>
|
|
68
|
+
<li><a href="#qa-templates">Templates of QA Handbook and
|
|
69
|
+
SpecGL</a></li>
|
|
70
|
+
<li><a href="#qa-tools">Tools</a></li>
|
|
71
|
+
<li><a href="#curriculum">Curriculum for Web
|
|
72
|
+
Standards</a></li>
|
|
73
|
+
<li><a href="#validators">Validators</a></li>
|
|
74
|
+
<li><a href="#earl">Joint session with ERT Working Group on EARL</a></li>
|
|
75
|
+
</ol>]]>
|
|
76
|
+
<![CDATA[ <h3 id="test-metadata">Test Cases Metadata</h3>
|
|
77
|
+
|
|
78
|
+
<p><a href="http://www.w3.org/TR/test-metadata/">Test Metadata</a>
|
|
79
|
+
has been published as a W3C Working Group note in September 2005. The document defines a minimal set of metadata elements that can usefully be applied to tests that are intended for publication within a test suite. We published it quickly. At the time of the publication, it was mentionned that a schema could be useful to help implementers to use it in their tools. Dominique Hazaël-Massieux has suggested that we should start an RDF or XML Schema implementation of these metadata. It should be done in coordination with one or two Working Groups and in the context of a practical use. Mobile Best Practices might be one canditate, and ERT WG with EARL might be another possible implementation of this language.</p>
|
|
80
|
+
|
|
81
|
+
<p>Snorre mentionned that it could be of interests for Opera which has already plenty of test suites that could be released in W3C venues.</p>
|
|
82
|
+
<p>We agreed that we have to be flexible, and make this schema as extensible as possible. So that people can not only use it but adapt it to their own needs. The choice of the format for the schema might be a problem in certain venues: RDF, XML Schema, RelaxNG, … We will then not recommend only one schema. We will start with one implementation and invite other people to contribute their own schema to be added to the document in appendix. </p>
|
|
83
|
+
|
|
84
|
+
<p>We could expect a republication in April 2006.</p>
|
|
85
|
+
<ul>
|
|
86
|
+
<li><a href="http://www.w3.org/QA/2005/03/joint-test-suites.html">A survey on Test Suite needs at W3C</a></li>
|
|
87
|
+
<li><a href="http://www.w3.org/2002/09/wbs/34786/qa-test/results">Survey of testing practices in W3C groups</a></li>
|
|
88
|
+
</ul>
|
|
89
|
+
|
|
90
|
+
<ul>
|
|
91
|
+
<li><strong>ACTION:</strong> Dom to propose an implementation of Test Metadata in RDF. Deadline: Mid-March</li>
|
|
92
|
+
<li><strong>ACTION:</strong> Patrick, Tim and Snorre to review Dom'simplementation of Test Metadata in RDF</li>
|
|
93
|
+
</ul>
|
|
94
|
+
|
|
95
|
+
<h3 id="w3c-glossary">W3C Glossary system</h3>
|
|
96
|
+
|
|
97
|
+
<p>The <a href="http://www.w3.org/2003/glossary/">W3C Glossary</a> is not a directly QA related topic, but it has interests with regards to the quality of specifications. it helps harmonization of vocabulary accross specifications and maintains regularity. The project has been started 3 years ago. It collects the data from W3C specifications and is RDF based. A new intern will start to work on this project in May 2006. The goals are translations of W3C Terms in different languages. This is useful for volunteers who translate W3C specifications. Optimization of the code, making the code open source and study of relationship (semantic genealogy) between terms are also goals. For example, what would be the variability of definitions of user agents accross W3C specifications.</p>
|
|
98
|
+
<p>The use of the W3C Glossary is encouraged on <a href="http://www.w3.org/2003/Editors/">W3C Editors home page</a>.</p>
|
|
99
|
+
|
|
100
|
+
<h3 id="cuap-chips">CUAP and CHIPs</h3>
|
|
101
|
+
|
|
102
|
+
<p><a href="http://www.w3.org/TR/cuap">Common User Agent Problems</a>
|
|
103
|
+
and <a href="http://www.w3.org/TR/chips/">Common HTTP Implementation Problems</a> are two Notes which have been published a few years ago. They highlight some common implementation issues in user agents and HTTP-based softwares. We discussed about updating and republishing the two notes making then one note synchronized on <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/">Web architecture</a> recommendation. Worries have been expressed about merging the two documents. They might not address exactly the same public: User agents versus servers. We will use the Wiki to collect issues from people about identified HTTP implementation problems using the Web Architecture document as a framework for collecting issues. We have to make very clear that it's not a way to collect issues about Web architecture document itself. The new draft will be posted to QA IG mailing-list for comments.</p>
|
|
104
|
+
|
|
105
|
+
|
|
106
|
+
<p><strong>ACTION:</strong> Olivier and Karl to provide an updated
|
|
107
|
+
version of CUAP and CHIPs - due by end of April</p>
|
|
108
|
+
<p><strong>ACTION:</strong> Snorre will review the document once it has been published.</p>
|
|
109
|
+
|
|
110
|
+
|
|
111
|
+
<h3 id="qa-findings">QA Findings</h3>
|
|
112
|
+
|
|
113
|
+
<p><a href="http://www.w3.org/2001/tag/findings">Tag Findings</a> are short documents dealing with issues about architecture. The format is quite interesting and gathering the knowledge about one particular topic of Web architecture. Dominique Hazaël-Massieux has suggested that it might be possible to publish QA Findings.</p>
|
|
114
|
+
<p>For example, in MWI WG, they are writing best practices, some of these practices are not testable. So, they are not normative. An requirement don't have to be testable to be normative, but life become much harder if non testable normative requirements are provided in a specification. Having a summary of all discussions which have been done for this specific topic would be very useful and could serve as a QA Findings.</p>
|
|
115
|
+
<p>When a discussion got enough momentum on the www-qa mailing-list, someone will take the responsibility about prototyping the topic on the <a href="http://esw.w3.org/topic/QA">QA wiki</a> and collect information. Once the document has reached maturity, we might publish it as a QA Finding, probably on the QA Weblog.</p>
|
|
116
|
+
|
|
117
|
+
<p><strong>ACTION:</strong> Dom to start a wiki page on
|
|
118
|
+
testability/normativity before mid-March and will report on www-qa.</p>
|
|
119
|
+
|
|
120
|
+
|
|
121
|
+
<h3 id="qa-weblog"><a href="http://www.w3.org/QA/">QA Weblog</a></h3>
|
|
122
|
+
|
|
123
|
+
<p>The QA home page was used to have only small news. After discussion in the QA Team, we thought about developing a Weblog for the QA home page. This is officially owned by the QA IG, although the policies for writing in it aren't well defined yet. We have already started to publish a few articles with open comments (but moderated). We may receive an email or read a news which raises an interesting question to be develop in a longer post. It has been decided to create the QA Weblog, because it doesn't reach necessary the same public than people reading mailing-list or using the wiki.</p>
|
|
124
|
+
<p>Entry will be edited for adding references and/or fix mistakes in the article to ensure a good level of quality. The comments being open, it also gives an opportunity to add information to the post. If we identify a discussion that would make a good contribution for the wiki, we might ask the person to prepare a contribution for the weblog. Recently, there was a discussion about EBNF.</p>
|
|
125
|
+
<p>The QA Weblog has not been marketed too much, only by word of mouth. We wanted to see how the community would react, but anyone can talk about it or advertize it. </p>
|
|
126
|
+
|
|
127
|
+
<p><strong>ACTION:</strong> karl to see if Björn is interested in
|
|
128
|
+
preparing a blog entry on the EBNF discussion.</p>
|
|
129
|
+
|
|
130
|
+
<h3 id="ebnf">EBNF discussion</h3>
|
|
131
|
+
|
|
132
|
+
<p>There are EBNF discrepancies or inconsistencies among specifications. It has been proposed by Björn Höhrmann to take existing ENBF and add XML namespaces plus errata to avoid further discrepancies - or guarantee consistency. It is definitely clear that is not the job of the QA IG to fix this document, but XML Core WG role. Karl will coordinate with Björn to contact XML Core.</p>
|
|
133
|
+
|
|
134
|
+
<h3 id="test-assertion">Test Assertion Guide</h3>
|
|
135
|
+
|
|
136
|
+
<p>Jacques Durand has worked inside OASIS on two efforts — one in scope of EBXML — markup of test assertions, other is that specs should be more testable. A simple guide to write test assertions has then been a requirement. There is an educational/PR exercise. The document developed at OASIS is right now a rough draft, but could be benefit of being reviewed by W3C and OASIS. It has been mentionned that would be possible only if the document is publicly available. The document could end up as a FAQ to write test assertions.</p>
|
|
137
|
+
|
|
138
|
+
<p>ACTION Jacques and Lynne: to find out about making the DRAFT guide on writing test assertions public</p>
|
|
139
|
+
<p><strong>ACTION:</strong> Lynne to develop document summary (review with Jacques) on DRAFT guide on writing test assertions</p>
|
|
140
|
+
|
|
141
|
+
<h3 id="organization-qaig">Organization of QAIG</h3>
|
|
142
|
+
|
|
143
|
+
<p>The only requirement to be a Member of the QA IG, a person has to be subscribed on qa ig mailing list. There are no currently regular teleconferences. We have to define ways of organizing the QA IG and support the QA IG objectives.</p>
|
|
144
|
+
<p>Lynne Rosenthal has also voiced the desire to step down from her role as a co-chair of the group. Her time is too limited. Lynne agrees to continue to participate to the work of the QA IG. Patrick Curran has proposed to take her role. We need to ask W3C Management for confirmation. </p>
|
|
145
|
+
<p>The two co-chairs will have regular teleconferences every two weeks to move the work forward, review the action items, and find volunteers (participants) to take responsibilty on work.</p>
|
|
146
|
+
|
|
147
|
+
<p><strong>ACTION:</strong> Karl to ask W3C management about change of co-chairs for QA IG</p>
|
|
148
|
+
|
|
149
|
+
<h3 id="qa-templates">Templates of QA Handbook and SpecGL</h3>
|
|
150
|
+
|
|
151
|
+
<p>There has been no more work done on conformance template, charter template and QA Process document template. Slightly related a mail has been sent about <a href="http://www.w3.org/mid/A2B7A5CC-8E66-4228-B18B-F0887221557A@w3.org">tagging the QA Handbook</a> to make an index to access the document with different views.</p>
|
|
152
|
+
|
|
153
|
+
<p><strong>ACTION:</strong> Karl to finish conformance template.</p>
|
|
154
|
+
<p><strong>ACTION:</strong> Karl to finish charter template by
|
|
155
|
+
March 16</p>
|
|
156
|
+
<p><strong>ACTION:</strong> Lofton to finish process template in
|
|
157
|
+
next six weeks</p>
|
|
158
|
+
<p><strong>ACTION:</strong> Tim to index QA Handbook to answer
|
|
159
|
+
specific questions</p>
|
|
160
|
+
|
|
161
|
+
<h3 id="qa-tools">Tools</h3>
|
|
162
|
+
|
|
163
|
+
<p>It would be beneficial for the W3C community to develop tools that would help WG members to write specifications and test them. It could be things like specifications markup process, measuring coverage, tools for tests/test harnesses needed, etc. As a first step, we decided to collect on a wiki page, <a href="http://esw.w3.org/topic/QaTools">QA Tools</a>, a list of resources and tools.</p>
|
|
164
|
+
<p><strong>ACTION:</strong> Patrick to update section QA Tools on the wiki - http://esw.w3.org/topic/QaTools</p>
|
|
165
|
+
|
|
166
|
+
|
|
167
|
+
<h3 id="curriculum">Curriculum for Web Standards</h3>
|
|
168
|
+
|
|
169
|
+
<p>Both the QA IG and the <a href="http://webstandards.org/">WASP</a> are interested by creating resources for a Curriculum for Web standards. It's a recurring discussion on W3C mailing lists. The <a href="http://www.webstandards.org/act/campaign/edutf/">WASP Education Task Force</a> has been involved in talking to universities and colleges, bringing out examples of what's been done. The public output has been in the forms of interviews. The WASP is now interested in developing a kind of curriculum framework to help lecturers into their teaching. The QA activity as large has done nothing in this direction yet, but we have taken contacts, like Ed Bilodeau at Mc Gill University, Montreal, Canada to collect materials that would be useful for such a curriculum. Ed Bilodeau has showed interests in contributing to such a work, maybe under the form of a W3C Group Note. This work could be moved forward quite quickly considering that Stephanie Troeth (WASP) and Ed Bilodeau are both in Montreal.</p>
|
|
170
|
+
<p>The audience of this framework would be lecturers, college teachers. It would include the time constraints, budget allocations, resources, etc. It has been shown that sometimes lecturers are quite positive about Web standards but they faced resistance through their department, specifically in Web design faculties. The framework will have to give hints on strategies for change. The format of the package has not yet been decided, but it has to be international then we need to understand how universities function around the world. </p>
|
|
171
|
+
<p>There is a need for balance between</p>
|
|
172
|
+
|
|
173
|
+
<ol>
|
|
174
|
+
<li>what needs to be taught</li>
|
|
175
|
+
<li>what can conceivably be taught</li>
|
|
176
|
+
</ol>
|
|
177
|
+
|
|
178
|
+
<p>There might be resources at Opera to make available for this effort. Opera has 1 full time + future resources part time and then probably full time working on the "open the web" initiative, but without precisely knowing how much of this could be contributed to QA IG. Some Web Standards User groups are forming at key Universities and Colleges to provide and advocate a method for change - WaSP Edu is providing interviews with these as they find out about them.</p>
|
|
179
|
+
|
|
180
|
+
<p>The Core EduTF at WASP has four to six people. It seems reasonnable to create a join effort with a regular IRC meetings at least, every 2 weeks. We will push the requirements interview phase and decide where to head from there.</p>
|
|
181
|
+
|
|
182
|
+
<p>The first IRC meeting is planned for March 21. Time to be defined.</p>
|
|
183
|
+
|
|
184
|
+
<h3 id="validators">Validators</h3>
|
|
185
|
+
|
|
186
|
+
<p>W3C hosts a number of free public tools that allow developers and
|
|
187
|
+
maintainers of web documents to check them for conformance.</p>
|
|
188
|
+
|
|
189
|
+
<ul>
|
|
190
|
+
<li>Markup validator (HTML and XHTML, SVG or MathML)</li>
|
|
191
|
+
<li>CSS validator</li>
|
|
192
|
+
<li>RDF validator </li>
|
|
193
|
+
<li>Feed validator (developed at Sourceforge) - hosted by W3C</li>
|
|
194
|
+
</ul>
|
|
195
|
+
|
|
196
|
+
<p>See the <a href="http://www.w3.org/QA/Tools">full list of individual tools</a>.</p>
|
|
197
|
+
|
|
198
|
+
<p>We're now running into discrepancies between the ways in which the tools work. Markup validator is based on SGML parser (doesn't handle XML very well) but the CSS validator is based on a better XML parser. (So, Markup validator might pass something that CSS validator will reject.). UIs were different. Over the past 6 months, much of the work has been done to harmonize the tools.</p>
|
|
199
|
+
|
|
200
|
+
<p>Major effort is under way to provide simple programmable (SOAP)
|
|
201
|
+
interfaces to these tools. Current status:</p>
|
|
202
|
+
|
|
203
|
+
<ul>
|
|
204
|
+
<li>CSS: in production</li>
|
|
205
|
+
<li>Feed: in production</li>
|
|
206
|
+
<li>Markup: still in development</li>
|
|
207
|
+
</ul>
|
|
208
|
+
|
|
209
|
+
<p>These SOAP interfaces have enabled, for example, the creation of a single
|
|
210
|
+
AJAX-based front-end to the both the Markup and CSS validators. In future, additional checks could be added (assuming that other tools are available with SOAP interfaces). Tools are written in different languages (PERL, Java, Python) - SOAP allows us to unify. Tools are developer by volunteers, mostly in Europe. The Markup validator mailing list has several hundred subscribers. A hard-core
|
|
211
|
+
of supporters provide help. CSS also has a mailing list too. RDF validator was not actively managed but Jeremy Carroll (HP) has now agreed to take this on.</p>
|
|
212
|
+
|
|
213
|
+
<p> There is an appeal to members for assistance with development and maintenance. We need to encourage member companies to use the W3C validators. Some packages are made available for in-house installation (sometimes through distributions like linux flavours) if there are concerns about passing internal documents to an outside instance of the validator. It's hoped that as usage increases some companies will contribute resources for development or bug-fixing.</p>
|
|
214
|
+
|
|
215
|
+
<p>Some years ago people considered the Markup validator to be the
|
|
216
|
+
"reference" for HTML rather than the HTML specifications themselves. Now people have understood that this is just a tool.</p>
|
|
217
|
+
|
|
218
|
+
<p>We might create a low traffic "announcement" list for all validators which would complement the RSS feed of the <a href="http://www.w3.org/Status">W3C Open Source software</a> page. We could also look at avenues like VersionTracker, Freshmeat, etc.</p>
|
|
219
|
+
|
|
220
|
+
<p><strong>ACTION:</strong> Olivier to investigate new avenues to advertise new releases of validators</p>
|
|
221
|
+
|
|
222
|
+
<h3 id="earl">Joint session with ERT Working Group on EARL</h3>
|
|
223
|
+
|
|
224
|
+
<p>We had a joint session with <a href="http://www.w3.org/WAI/ER/">ERT Working Group</a> about EARL on how the language is defined. The test metadata schema could be reused in part by EARL which is likely to make this effort even more urgent. (See <a href="http://www.w3.org/2006/02/28-er-minutes#item01">Minutes</a>)</p>
|
|
225
|
+
|
|
226
|
+
<p class="image"><img src="http://www.w3.org/QA/2006/03/cannes-mer" alt="Sea and Sky during the W3C Technical Plenary" /></p>]]></description>
|
|
227
|
+
<dc:subject>QAIG Life</dc:subject>
|
|
228
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
229
|
+
<dc:language>en</dc:language>
|
|
230
|
+
<dc:date>2006-03-08T11:07:04+00:00</dc:date>
|
|
231
|
+
</item>
|
|
232
|
+
|
|
233
|
+
<item rdf:about="http://www.w3.org/QA/2006/02/content_negotiation.html">
|
|
234
|
+
<title>Content Negotiation: why it is useful, and how to make it work</title>
|
|
235
|
+
<link>http://www.w3.org/QA/2006/02/content_negotiation.html</link>
|
|
236
|
+
<description> <![CDATA[<p>We recently received a puzzled message from a visitor of the W3C Web site, asking how we were serving images without file suffix in their URI. Looking around, our visitor found that <code>http://www.w3.org/StyleSheets/TR/logo-REC</code> was not one file, but two: <code>logo-REC.gif</code> and <code>logo-REC.png</code>. How do we do that?</p>
|
|
237
|
+
|
|
238
|
+
<p>The short answer is: <em>Content Negotiation</em>. </p>
|
|
239
|
+
<p>In this article, we will discuss content negotiation in depth and examine practical solutions.
|
|
240
|
+
However, to begin, we need to first understand what a URI is, and what it is not.</p>
|
|
241
|
+
]]>
|
|
242
|
+
<![CDATA[<h3>A URI is a reference</h3>
|
|
243
|
+
<p>The first thing we need to understand is that <strong>a URI is not a file name</strong>.</p>
|
|
244
|
+
|
|
245
|
+
<p>It is convenient to see a URI as the location for a file, and in most cases, the analogy works. However, as we will see soon, this analogy is too poor to describe everything a URI actually is. Let's just remember that there is a good reasons why web "pedants" insist on calling it a URI, a <em>Universal Resource Identifier</em>, not a URL: it is not a file name or location, it is an <em>identifier (or a reference) to a resource</em>. By using a proper protocol, it is possible to retrieve the actual resource, that's called <em>dereferencing a URI</em>.</p>
|
|
246
|
+
|
|
247
|
+
<p>But why all this abstraction, since in most cases the resource will happen to be stored in a file anyway, and the URI will be mapped directly to the file name?</p>
|
|
248
|
+
|
|
249
|
+
<p>Let us consider two things very similar to a URI: a bar code for a product, and an <acronym title="International Standard Book Numbering">ISBN</acronym> for a book. The former is a reference to a product, and the latter, a reference to a publication. In the case of the bar code and associated product, it is important to note that the product is not a specific box of cookies on a shelf, the referred product is actually the type of cookies of a certain brand, and all share the same bar code. Similarly, ISBNs do not refer to a flesh and bone (or, rather, paper-and-spine) book, but to the text it contains. In fact, it is not rare that several editions of a book share the same ISBN number: in the context of the ISBN, they are similar.</p>
|
|
250
|
+
|
|
251
|
+
<p>The same idea can be applied to URIs. A URI refers to a resource, but the resource is not one file on one web server. Take for example the resource "the weather in Oaxaca". A resource is just that: a piece of information on the Web. An HTML document with a text describing the weather in Oaxaca, or an image representing a map with indicators about the weather, all these files can be appropriate representations for this resource.</p>
|
|
252
|
+
|
|
253
|
+
<p>In fact, the maintainer of the Web resource could very well decide that a number of representations of this piece of information are equivalent, and think "what if I let the visitors of my Web site decide which representation they prefer?" On the Web, these equivalent representations of a resource are called <em>variants</em>, and the mechanism used to determine which of the existing representations is most appropriate for a given request is called <em><a href="http://www.w3.org/TR/webarch/#frag-coneg">Content Negotiation</a></em>.</p>
|
|
254
|
+
|
|
255
|
+
|
|
256
|
+
<p><img src="http://www.w3.org/QA/2006/02/content-negotiation-graph" alt="a URI is a pointer to a resource, which can have many equivalent variants" /></p>
|
|
257
|
+
|
|
258
|
+
<h3>Content Negotiation: figuring out the best deal for everyone</h3>
|
|
259
|
+
|
|
260
|
+
<p>Content Negotiation is a complex-sounding term for what is a rather simple mechanism.</p>
|
|
261
|
+
|
|
262
|
+
<p>Imagine yourself discussing on the phone, suggesting a date. You ask: <q cite="">We should meet soon! How about Wednesday, or Friday?</q>. your friend answers <q cite="">Excellent! I have free time on Friday!</q>. Sounds simple? Now replace the <em>date</em> with a <em>resource</em>, think of yourself as the <em>client requesting a resource</em> and your friend as the <em>Server, accepting the request based on the preferences of the client and on its own availabilities</em>: this is Content-Negotiation as it is implemented on the Web.</p>
|
|
263
|
+
|
|
264
|
+
<p>In summary, the basic idea of Content Negotiation is to serve the best variant for a resource, and to serve it based on:</p>
|
|
265
|
+
<ul>
|
|
266
|
+
<li>What variants are available, and what variants the server may prefer to serve</li>
|
|
267
|
+
<li>What the client can accept, and with which preferences: in HTTP, this is done by the client which may send, in its request, <em>Accept</em> headers (Accept, Accept-Language and Accept-Encoding), to communicate its capabilities and preferences in Format, Language and Encoding, respectively.</li>
|
|
268
|
+
</ul>
|
|
269
|
+
|
|
270
|
+
<!-- this part on server-driven vs client driven was not really useful, taking it oot
|
|
271
|
+
<p>By default, the HTTP protocol implements what is called a <em>server-driven</em> content negotiation mechanism, meaning that the Web server, upon receiving information about the Client's supported variants and preferences, as well as knowing the available variants for a resource, will be the actor of the negotiation responsible for making the final decision on which variant suits everyone best. The opposite is <em>client-driven</em> negotiation, where the server lists all variants, and asks the client: "pick one". The latter is sometimes used as a fallback mechanism when the server-driven mechanism fails.</p>
|
|
272
|
+
-->
|
|
273
|
+
|
|
274
|
+
<h3>Language Negotiation: why every multilingual site owner should know about it</h3>
|
|
275
|
+
|
|
276
|
+
<p>The mechanism that allows us to serve an image in two different file formats, which our visitor was puzzled about, is in fact one type of Content-Negotiation, called <em>Format Negotiation</em>. One other important and interesting usage of Content Negotiation is its application to representations of a resource in several languages, and how to serve them to the reader based on their preferences: <em>Language Negotiation</em>.</p>
|
|
277
|
+
|
|
278
|
+
<p>With Language Negotiation, there is no need to give a link to oaxaca.html.en for readers of English and oaxaca.html.de for readers of German, just link to oaxaca, set up your server properly (e.g <a href="http://www.w3.org/International/questions/qa-apache-lang-neg">apache</a>) and the negotiation happening between the server and the client's preference will make each reader receive the resource in the proper language.</p>
|
|
279
|
+
|
|
280
|
+
<h4>Why is Language Negotiation seldom used?</h4>
|
|
281
|
+
|
|
282
|
+
<p>How come then that language negotiation is not being widely used at all if it can be so useful in dispatching, automatically, the proper language variant of a document to its audience? Partly perhaps because it is not well known, and people building multilingual web sites think of their site as a multiplication of language-specific mini-sites, instead of thinking of it as one site, with one set of URIs, only with different versions and languages available.</p>
|
|
283
|
+
|
|
284
|
+
<p>It is not, however, the sole reason for the lack of usage of language negotiation. One other reason is that for a long time, with the most popular negotiation-enabled Web server (the ubiquitous apache), <a href="http://www.w3.org/TR/chips/#cp9.1">failed negotiation</a> (for instance, a reader of french being proposed only english and german variants of a document), resulted in a nasty "406 not acceptable" HTTP error, which, while technically conforming to HTTP, failed to follow the recommendation that a server should try to serve some resource rather than an error message, whenever possible. Fortunately, more recent versions of the server now allow the setting of a fallback, or default, variant in case the negotiation fails.</p>
|
|
285
|
+
|
|
286
|
+
<h4>Another serious issue: giving the <em>users</em>, not the <em>browser</em>, what they want</h4>
|
|
287
|
+
|
|
288
|
+
<p>There is another issue with language negotiation as it is implemented in HTTP: it implies that the client is properly configured, that is, it implies that the client (the Web browser) will send <code>Accept-Language</code> information that actually reflects the languages its user can read, and what languages are preferred among these. Unfortunately, it is often not true: although many modern browsers do allow their users to set preferred languages, not all of them do, and even when they do, there are cases when the user does not know how the set up is made (here is <a href="http://www.w3.org/International/questions/qa-lang-priorities">how</a>). In some cases, for instance on shared computers or "internet kiosks", the user is not even allowed to change the settings of the Web browser.</p>
|
|
289
|
+
|
|
290
|
+
<p>In this context, a zealous usage of language negotiation can even have effects against usability of a site. Imagine a bilingual site (in our example, English and Japanese) where negotiation between the server and browser results in the choice of the English variant. The reader actually prefers Japanese, and finds a link to the Japanese version, easily visible at the top of the English variant, and follows it. However, as the user keeps browsing… the negotiation between the browser and the server keeps returning the English version. Quite probably, the user will just get irritated, browse away, never to return: language negotiation, albeit there to help the user, can prove to be a usability liability.</p>
|
|
291
|
+
|
|
292
|
+
<h4>Toward a <em>better</em> language negotiation</h4>
|
|
293
|
+
|
|
294
|
+
<p>How can we work around this?</p>
|
|
295
|
+
<p> One possibility is to choose to provide "generic", language negotiated access to resources only at known important entry points to the site, and from there on, use only language specific links . That solution does prevent the running away of users irritated by the limitations of language negotiation, but if Bob wants to send a link to a specific resource on the site to his friend Norio in Japan, wouldn't it be nice to be able to just send the URI of the page he is browsing (in English) and have his Japanese friend automatically get the Japanese version? Wouldn't it be nice to be able to use the power of Language negotiation on the whole site, without any usability issue?</p>
|
|
296
|
+
|
|
297
|
+
<p>After all, the concept of negotiation is to try and automatically provide the best possible variant based on the ones available in the server and the preferences of the user - whether to use the preferences of the browser and the <code>Accept</code> HTTP headers it sends is only a convenient implementation in HTTP, not the <em>only</em> way to implement a negotiation system.</p>
|
|
298
|
+
<p>What if?… Negotiation could take into account the settings in the user's browsers, <em>and</em> records of past interactions with the site. And although HTTP is stateless, there is an easy way to do this: cookies. A negotiation algorithm trusting a cookie showing that the user has <em>chosen</em> a language different than the one negotiated based on its Accept-Language: header information, and defaulting to Accept-based negotiation in the absence of such a cookie, may be the best of both worlds: negotiated resources, and the guarantee of a consistent user experience regardless of potentially misconfigured browsers.</p>
|
|
299
|
+
|
|
300
|
+
<h3>A PHP implementation of the "better language negotiation"</h3>
|
|
301
|
+
|
|
302
|
+
<p>Below is a sample implementation of the idea described above, using the php language.</p>
|
|
303
|
+
|
|
304
|
+
<h4>How this php-based language-negotiation works</h4>
|
|
305
|
+
|
|
306
|
+
<ol>
|
|
307
|
+
<li><p><code>page</code> (the URI naming is just an example) is the "generic" resource. It checks for the existence of a language choice cookie first, and in the absence of it, calls <code>choose_lang.php</code>. When the negotiation algorithm ends, a variable called <code>$chosenlang</code> is set, and based on the value of this variable, either <code>page.en</code> or <code>page.ja</code> is called with an <code>include</code> mechanism</p>
|
|
308
|
+
|
|
309
|
+
<p>You can download the <a href="sample_nego/page">php source for <code>page</code></a>. Its code is actually very simple, as shown below:</p>
|
|
310
|
+
|
|
311
|
+
<pre>
|
|
312
|
+
<?php
|
|
313
|
+
include('/path/to/choose_lang.php');
|
|
314
|
+
if ($chosenlang == "en") {
|
|
315
|
+
include 'page.en';
|
|
316
|
+
}
|
|
317
|
+
else {
|
|
318
|
+
include 'page.ja';
|
|
319
|
+
}
|
|
320
|
+
?>
|
|
321
|
+
</pre>
|
|
322
|
+
</li>
|
|
323
|
+
|
|
324
|
+
<li><p> <code>choose_lang.php</code> implements a very basic HTTP language negotiation based on Accept-Language: headers. It does not take into account "quality factors", which could be used to weigh in several possible choices. As you can see in the <a href="sample_nego/choose_lang" title="see the full commented source for choose_lang">commented source</a>, its main task is to find a value for the variable <code>$chosenlang</code>, first by checking the presence of a cookie (denoting a language choice in previous interaction with the site), then by trying a content-negotiation algorithm similar to that of HTTP, and finally, if necessary, falling back to a default language choice.</p></li>
|
|
325
|
+
|
|
326
|
+
<li><p>Finally, the language specific files for our page, <code>page.en</code> and <code>page.ja</code> should have some code at the top, executed only if the variable <code>$chosenlang</code> is not set. As we saw above, this would mean that the resource was <em>not</em> called through the generic resource, but rather requested directly, so it's a fair assumption that the user followed a language-specific link to switch the language of display: therefore, we want to store a cookie recording the new choice of language.</p>
|
|
327
|
+
<p>Here is how the code at the top of <code>page.en</code> should look:</p>
|
|
328
|
+
<pre>
|
|
329
|
+
<?php if(! isset($chosenlang)) {setcookie("lang", "en", time()+60*60*24*30, "/"); $chosenlang="en";} ?>
|
|
330
|
+
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
|
|
331
|
+
…
|
|
332
|
+
</pre>
|
|
333
|
+
</li>
|
|
334
|
+
</ol>
|
|
335
|
+
|
|
336
|
+
|
|
337
|
+
<h3>Links galore</h3>
|
|
338
|
+
<ul>
|
|
339
|
+
<li><a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec12.html">HTTP1.1: Content Negotiation</a>. <em>The</em> reference. There is also an <a href="http://www.ietf.org/rfc/rfc2295.txt">RFC on Content Negotiation in HTTP</a>, but it's a little outdated, and refers to an now superseded draft of HTTP1.1</li>
|
|
340
|
+
<li>The <a href="http://www.w3.org/TR/webarch/#def-coneg">short and sweet definition of Content Negotiation</a> from the Web architecture document.</li>
|
|
341
|
+
<li>the <a href="http://www.w3.org/TR/chips/"><acronym title="Common HTTP Implementation Problems">CHIPs</acronym></a> W3C Note has a number of guidelines on how Web servers and server-side technologies can implement negotiation.</li>
|
|
342
|
+
<li>The <a href="http://www.w3.org/International/">Internationalization Activity</a> of W3C has two good FAQs on the topic of language negotiation: <a href="http://www.w3.org/International/questions/qa-when-lang-neg">When to use it</a> and <a href="http://www.w3.org/International/questions/qa-apache-lang-neg">How to set it up with Apache</a>.</li>
|
|
343
|
+
<li>The always thorough Jukka Korpela has a extensive section of his site dedicated to <a href="http://www.cs.tut.fi/~jkorpela/multi/">multilingual Web sites</a>, discussing technical as well as usability aspects.</li>
|
|
344
|
+
<li>The bilingual <a href="http://www.tokyoartbeat.com">Tokyo Art Beat</a> Web site uses the language negotiation techniques explained in this article.</li>
|
|
345
|
+
</ul>
|
|
346
|
+
|
|
347
|
+
<h3>Post Scriptum</h3>
|
|
348
|
+
<p>Many thanks to Karl Dubost, Felix Sasaki and Steph Troeth for some excellent input, suggestions and corrections to this article.</p>
|
|
349
|
+
<p>Please use the comments form below if you wish to provide feedback, or suggest other implementations to make Content Negotiation on the Web more useful and more widely used. Thank you.</p>
|
|
350
|
+
]]></description>
|
|
351
|
+
<dc:subject>Technology 101</dc:subject>
|
|
352
|
+
<dc:creator>olivier Thereaux</dc:creator>
|
|
353
|
+
<dc:language>en</dc:language>
|
|
354
|
+
<dc:date>2006-02-21T02:12:42+00:00</dc:date>
|
|
355
|
+
</item>
|
|
356
|
+
|
|
357
|
+
<item rdf:about="http://www.w3.org/QA/2006/02/buy_standards_compliant_web_si.html">
|
|
358
|
+
<title>Buy standards compliant Web sites</title>
|
|
359
|
+
<link>http://www.w3.org/QA/2006/02/buy_standards_compliant_web_si.html</link>
|
|
360
|
+
<description> <![CDATA[<p>The topic is far from being new, but it reaches the surface of Web business at regular times. The Web community often struggles between a desire of creating a professional work and the necessity of making a living of one's business.<cite><a href="http://www.molly.com/">Molly E. Hoschlag</a></cite> was writing in November 2005 about <cite><a href="http://www.molly.com/2005/11/14/web-standards-and-the-new-professionalism/">Web standards and The New Professionalism</a></cite>. She was reminding us about what does that mean to be professional for a Web developer, Web designer:</p>
|
|
361
|
+
|
|
362
|
+
<blockquote cite="http://www.molly.com/2005/11/14/web-standards-and-the-new-professionalism/"><p>The essence of this new professionalism isn’t about being perfect at what we do. It’s being able to say: Hey, I don’t know that. Let me go find out. It isn’t about knowing it all, because we surely never will. And, there will be shifts and changes. […]</p>
|
|
363
|
+
<p>[…]</p>
|
|
364
|
+
<p>Today, I want to express that I believe that this new professionalism means taking responsibility for the education of ourselves and each other, and ensuring that reversions like Disney Store UK never happen again. </p></blockquote>
|
|
365
|
+
]]>
|
|
366
|
+
<![CDATA[<p>In article published this week (February 7, 2006) on Evolt, <cite>Thomas Ashworth</cite> asked the following question <cite><a href="http://evolt.org/web_standards_should_my_business_website_be_compliant">Web Standards. Should my Business Website be Compliant?</a></cite> and concludes by </p>
|
|
367
|
+
|
|
368
|
+
<blockquote cite="http://evolt.org/web_standards_should_my_business_website_be_compliant">
|
|
369
|
+
<p>web standards bring real tangible benefits to business. Although finding a design company that will construct a standards compliant site is more difficult than just finding a web designer, the benefits speak for themselves. By moving to a standards based web site businesses can ensure they have accessible sites which are maintainable and future proofed. Increased customer exposure and search engine prominence can all improve the level of business that comes to you via your website. Web standards are the future of the internet and to ignore it could leave your business trailing behind the online competition.</p>
|
|
370
|
+
</blockquote>
|
|
371
|
+
|
|
372
|
+
<p>The issue presents two faces, can we try to coin them:</p>
|
|
373
|
+
|
|
374
|
+
<ul>
|
|
375
|
+
<li>Web Professionals</li>
|
|
376
|
+
<li>Web Site Clients</li>
|
|
377
|
+
</ul>
|
|
378
|
+
|
|
379
|
+
<h3 id="pro">Web Professionals</h3>
|
|
380
|
+
<p>It will take time to modify the habits, to teach to your colleagues and to create an ecosystem which is sustainable enough to have good quality and profit, but it is really worthwhile as it has been demonstrated by pioneers in the domain.</p>
|
|
381
|
+
|
|
382
|
+
<h3 id="client">Web Site Clients</h3>
|
|
383
|
+
|
|
384
|
+
<p> All person who is in charge of writing a requirement document for the future Web site of a company can change things. You may have to fight and find the right agency but here again the effort is worthwhile. It may even help you to select the right agency to do the job. Do not think about your Web site as something different than your core business. When you are dealing with a supplier, a provider, you need absolutely to get a product of quality.</p>
|
|
385
|
+
<p>The main issue is that often you do not know what you should ask. <cite><a href="http://people.w3.org/~dom/">Dominique Hazaël-Massieux</a></cite> has written a document a while ago about this specific topic: <cite><a href="http://www.w3.org/QA/2002/07/WebAgency-Requirements">Buy standards compliant Web sites</a></cite>. It provides a list of simple requirements that you could add to your Web site requirements document when negociating with Web agencies. Any public feedback on this document is welcome and can be send to the <a href="http://lists.w3.org/Archives/Public/public-evangelist/"><strong>publicly archived</strong></a> mailing list <a href="mailto:public-evangelist@w3.org">public-evangelist@w3.org</a>.</p>
|
|
386
|
+
|
|
387
|
+
<p>We will achieve Web standards by acting on both side: responsibility for Web professionals and quality requirements from customers.</p>
|
|
388
|
+
|
|
389
|
+
]]></description>
|
|
390
|
+
<dc:subject>Opinions & Editorial</dc:subject>
|
|
391
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
392
|
+
<dc:language>en</dc:language>
|
|
393
|
+
<dc:date>2006-02-07T23:19:05+00:00</dc:date>
|
|
394
|
+
</item>
|
|
395
|
+
|
|
396
|
+
<item rdf:about="http://www.w3.org/QA/2006/02/ruby_annotation_to_change_the.html">
|
|
397
|
+
<title>Ruby Annotation Under The Sunlight</title>
|
|
398
|
+
<link>http://www.w3.org/QA/2006/02/ruby_annotation_to_change_the.html</link>
|
|
399
|
+
<description> <![CDATA[<p>(Updated on Friday 3 February 2006 to add valuable source of information given by <cite><a href="http://www.w3.org/People/Ishida/">Richard Ishida</a></cite>)</p>
|
|
400
|
+
|
|
401
|
+
<p>In the concepts of <a href="http://microformats.org/">microformats</a>, there is a key concept which is <q cite="http://microformats.org/about/">design for humans first, machines second</q>. We have often been faced to the problem of giving a date that will be easy to read by human and will be easy to parse by a computer. Or maybe you would like to give the price of a product with values in two currencies? Or you would like to give the translation of a term in another language? How would you be able to do that in <a href="http://www.w3.org/TR/xhtml11/">XHTML</a>? Is there a <strong>simple way</strong> of associating different types of information with a simple semantic relationship.</p>
|
|
402
|
+
|
|
403
|
+
<p>There is a language for these applications which has been created in 2001 at W3C: <a href="http://www.w3.org/TR/ruby/">Ruby Annotation.</a></p>]]>
|
|
404
|
+
<![CDATA[<h3 id="about">About Ruby?</h3>
|
|
405
|
+
|
|
406
|
+
<p>Ruby on the Web these days is known to be a <a href="http://www.ruby-lang.org/" title="Web site of Ruby programming language">programming language</a>, a <a href="http://www.intertwingly.net/blog/" title="Weblog of Sam Ruby">programmer working for IBM</a> and I guess for most people, everywhere in the world, a <a href="http://en.wikipedia.org/wiki/Ruby" title="definition of the Ruby gemstone">red gemstone</a>. In the context of W3C, <a href="http://www.w3.org/TR/ruby/">Ruby</a> is a simple markup language which offers the possibility of creating inline annotations, as described in the <a href="http://www.w3.org/TR/2001/REC-ruby-20010531/#what">Ruby specification</a></p>
|
|
407
|
+
|
|
408
|
+
<blockquote cite="http://www.w3.org/TR/2001/REC-ruby-20010531/#what">
|
|
409
|
+
<p>Ruby is the term used for a run of text that is associated with another run of text, referred to as the base text. Ruby text is used to provide a short annotation of the associated base text. It is most often used to provide a reading (pronunciation guide). Ruby annotations are used frequently in Japan in many kinds of publications, including books and magazines. Ruby is also used in China, especially in schoolbooks.</p>
|
|
410
|
+
|
|
411
|
+
<p>Ruby text is usually presented alongside the base text, using a smaller typeface. The name "ruby" in fact originated from the name of the 5.5pt font size in British printing, which is about half the 10pt font size commonly used for normal text.</p>
|
|
412
|
+
</blockquote>
|
|
413
|
+
|
|
414
|
+
<p>You will find a lot of answers to your questions in the <a href="http://www.w3.org/International/questions/qa-ruby">FAQ about Ruby</a>.</p>
|
|
415
|
+
|
|
416
|
+
<h3 id="use-cases">Use Cases for Ruby Annotation</h3>
|
|
417
|
+
|
|
418
|
+
<p>We asked <a href="http://www.w3.org/People/fsasaki/">Felix Sasaki</a>, working in the W3C <a href="http://www.w3.org/International/">Internationalization Activity</a> to give us a set of use cases for Ruby Annotation. These examples are viewable with Firefox and this <a href="http://piro.sakura.ne.jp/xul/_rubysupport.html.en">XPI extension for Ruby</a>.</p>
|
|
419
|
+
|
|
420
|
+
<h4 id="date">Date</h4>
|
|
421
|
+
|
|
422
|
+
<p>You might want to represent a date and give information about the different parts of the date on a package to be sure that no mistakes will be made.</p>
|
|
423
|
+
|
|
424
|
+
<ul>
|
|
425
|
+
<li>Ruby base: Thursday 2 2 2006</li>
|
|
426
|
+
<li>Explanations: This is an expiration date with the following sequence: a day name, the day, the month and the year.</li>
|
|
427
|
+
</ul>
|
|
428
|
+
|
|
429
|
+
<p><a href="/QA/2006/02/ruby-examples.xhtml#date">See example</a></p>
|
|
430
|
+
|
|
431
|
+
<h4 id="japanese">Japanese use</h4>
|
|
432
|
+
|
|
433
|
+
<p>In Japan, when you learn the language, you may need to give the sound equivalent of the words in a specific scripting system, so readers will be able to pronounce it.</p>
|
|
434
|
+
|
|
435
|
+
<ul>
|
|
436
|
+
<li>Base text: "日本"</li>
|
|
437
|
+
<li>Ruby as pronounciation description with Hiragana "にほん", Katakana "ニホン" or Romaji "nihon"</li>
|
|
438
|
+
</ul>
|
|
439
|
+
<p>How to write it?</p>
|
|
440
|
+
<pre>
|
|
441
|
+
<p><ruby>
|
|
442
|
+
<rb>日本</rb>
|
|
443
|
+
<rt>nihon</rt>
|
|
444
|
+
</ruby></p>
|
|
445
|
+
</pre>
|
|
446
|
+
<p><a href="/QA/2006/02/ruby-examples.xhtml#japanese">See example for the rendering.</a></p>
|
|
447
|
+
|
|
448
|
+
|
|
449
|
+
<h4 id="chinese">Chinese use</h4>
|
|
450
|
+
|
|
451
|
+
<p>In a similar way for chinese language.</p>
|
|
452
|
+
<ul>
|
|
453
|
+
<li>Base text: 好</li>
|
|
454
|
+
<li>Ruby as pronunciation description with pin-yin "hao"</li>
|
|
455
|
+
</ul>
|
|
456
|
+
|
|
457
|
+
<p><a href="/QA/2006/02/ruby-examples.xhtml#chinese">See example</a></p>
|
|
458
|
+
|
|
459
|
+
<h4 id="glossing">Linguistic morphological glossing</h4>
|
|
460
|
+
<p>You might want to explain in a sentence which part is a noun and which part is a verb. For example, at school, when you teach grammar to children.</p>
|
|
461
|
+
|
|
462
|
+
|
|
463
|
+
<ul>
|
|
464
|
+
<li>Base text: "I like fish"</li>
|
|
465
|
+
<li>Ruby as morphological glossing: Noun (for "I") Verb (for "like") Noun (for "fish")</li>
|
|
466
|
+
</ul>
|
|
467
|
+
|
|
468
|
+
<p><a href="/QA/2006/02/ruby-examples.xhtml#glossing">See example</a></p>
|
|
469
|
+
|
|
470
|
+
<h4 id="invisible">Expression of "invisible" units in a text</h4>
|
|
471
|
+
|
|
472
|
+
<p>The base text contains a Japanese sentence "Yesterday I went to Shibuya". The pronoun "I" is usually omitted in the original, which makes it hard to understand for e.g. beginning Japanese language learners.</p>
|
|
473
|
+
|
|
474
|
+
<p>The ruby text above the base text explains what is omitted. The first ruby text line below the base text contains a romanized vesion. The second ruby text line below the base text contains morpho-lexical information. The abbreviations: "TM" means "topic marker", "DM" means "direction marker".</p>
|
|
475
|
+
|
|
476
|
+
<p><a href="/QA/2006/02/ruby-examples.xhtml#invisible">See example</a></p>
|
|
477
|
+
|
|
478
|
+
<h4 id="gesture">Adding information about gestures to conversation transcriptions</h4>
|
|
479
|
+
|
|
480
|
+
<ul>
|
|
481
|
+
<li>Base text: "And we bought a biiiig icecream."</li>
|
|
482
|
+
<li>Ruby can be used to mark up "biiig" and to add information about gestures. It could be for example an image of someone making the gesture and big eyes.</li>
|
|
483
|
+
</ul>
|
|
484
|
+
|
|
485
|
+
<h4 id="word-boundaries">Expressing non-segmentable word boundaries</h4>
|
|
486
|
+
|
|
487
|
+
<p>
|
|
488
|
+
This is useful for</p>
|
|
489
|
+
<ul>
|
|
490
|
+
<li>a contraction (Old High German, English, many other languages)</li>
|
|
491
|
+
<li>a compound word (Sanskrit, Avestan, many other languages)</li>
|
|
492
|
+
<li>a group of words whose forms have been affected by "euphonic" sandhi changes (Sanskrit, Breton)</li>
|
|
493
|
+
<li>a group of words in which, for orthographic or other reasons, the word junctions are not indicated (Sanskrit, Japanese)</li>
|
|
494
|
+
</ul>
|
|
495
|
+
|
|
496
|
+
<p>An example from Japanese:</p>
|
|
497
|
+
|
|
498
|
+
<ul>
|
|
499
|
+
<li>base text: yo-mu (means: "reading in the base form"; with the Japanese syllabic script, the boundaries between the morphemes "yom" and "m" cannot be expressed)</li>
|
|
500
|
+
<li>Ruby for a segmentation of morphological boundaries: contains a romanized version of "yomu" with the correct boundaries "yom-mu".</li>
|
|
501
|
+
</ul>
|
|
502
|
+
|
|
503
|
+
<h3 id="implementations">Implementations: Sunny side-up?</h3>
|
|
504
|
+
|
|
505
|
+
<p>Well not really for now. <cite><a href="http://annevankesteren.nl/">Anne Van Kesteren</a></cite> (Opera) in a recent post <cite><a href="http://annevankesteren.nl/2006/01/ruby">Ruby in HTML</a></cite> has looked at the implementation of Ruby in Internet Explorer.</p>
|
|
506
|
+
<blockquote cite="http://annevankesteren.nl/2006/01/ruby">
|
|
507
|
+
<p>Using the Live DOM Viewer I tried to figure out more or less how it works. Not everything is covered, but the basic parsing rules are here; simple research.</p>
|
|
508
|
+
</blockquote>
|
|
509
|
+
|
|
510
|
+
<p>We have not found an implementation report of Ruby in different browsers, user agents and in authoring tools (the too often forgotten ones). If someone could create an implementation report using the <a href="http://www.w3.org/People/mimasa/test/ruby/">Ruby Annotation Test Cases</a> developed by <cite><a href="http://www.w3.org/People/mimasa/" title="home page of ISHIKAWA, Masayasu">連絡先</a></cite> and also the <a href="http://www.w3.org/International/tests/#ruby">Ruby Test Cases</a> developed by Internationalization Activity, it would help to have a good picture of the implementation landscape. Simple Ruby annotations are <a href="http://www.w3.org/QA/2006/02/amaya-ruby-implementation" title="screenshot of ruby rendered in amaya browser/editor">implemented in Amaya</a>. There is also an <a href="http://piro.sakura.ne.jp/xul/_rubysupport.html.en">xpi extension for Ruby</a> which is available for Firefox and Mozilla and help to <a href="http://www.w3.org/QA/2006/02/ruby-annotation-firefox" title="screenshot of ruby rendered in firefox 1.5">visualize simple and complex ruby</a> annotation. Unfortunately it's not a native implementation in Mozilla rendering engine, which has still an <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=33339">open issue for Ruby markup</a>.</p>
|
|
511
|
+
|
|
512
|
+
<p>On the styling side, the CSS Working Group is working on a module called <cite><a href="http://www.w3.org/TR/css3-ruby/">CSS 3 Module for Ruby</a></cite> and <cite><a href="http://www.akatsukinishisu.net/itazuragaki/" title="kitamura home page">北村曉</a></cite> has published a way to style <a href="http://www.akatsukinishisu.net/itazuragaki/2001_10.html#ruby_for_Mozilla_3">ruby with CSS in Mozilla</a>.</p>
|
|
513
|
+
|
|
514
|
+
<p>So we are not there yet, but I would say that almost all the information is available for helping developers to implement in their products but there are real benefits using ruby in a page. For example, we found this page giving a table which contains the <a href="http://www.i18nguy.com/unicode/unicode-example-ruby.html">birthplaces and native names of celebrities</a> (actors, singers, sports figures, etc.) in different languages. (to see with Firefox and the XPI extension).</p>
|
|
515
|
+
|
|
516
|
+
<p>Any comments or additional information are welcome, specifically from the internationalization specialists… ;)</p>
|
|
517
|
+
|
|
518
|
+
<h3 id="information">More information / Reminder</h3>
|
|
519
|
+
|
|
520
|
+
<ul>
|
|
521
|
+
<li><a href="http://www.w3.org/International/questions/qa-ruby">FAQ: What is Ruby?</a></li>
|
|
522
|
+
<li><a href="http://www.w3.org/International/tutorials/ruby/">Tutorial: Ruby Markup and Styling</a></li>
|
|
523
|
+
<li><a href="http://www.w3.org/International/tests/#ruby">Test Materials for Ruby</a></li>
|
|
524
|
+
<li><a href="http://en.wikipedia.org/wiki/Ruby_characters">Ruby at Wikipedia</a></li>
|
|
525
|
+
<li><a href="http://www.w3.org/2003/03/Translations/OverviewRecs.html#ruby">Translations of Ruby Specification in different languages</a></li>
|
|
526
|
+
<li><a href="http://www.w3.org/QA/2006/02/ruby-annotation-firefox">Screenshot of ruby rendered in Firefox 1.5</a></li>
|
|
527
|
+
<li><a href="http://www.w3.org/QA/2006/02/amaya-ruby-implementation">Screenshot of ruby rendered in Amaya</a></li>
|
|
528
|
+
<li><a href="http://piro.sakura.ne.jp/xul/_rubysupport.html.en">XPI extension to have a rendering of ruby in Mozilla and Firefox</a></li>
|
|
529
|
+
<li><a href="http://www.w3.org/Amaya/User/BinDist.html">To download Amaya</a> which helps to visualize simple Ruby</li>
|
|
530
|
+
</ul>]]></description>
|
|
531
|
+
<dc:subject>HTML</dc:subject>
|
|
532
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
533
|
+
<dc:language>en</dc:language>
|
|
534
|
+
<dc:date>2006-02-02T10:47:04+00:00</dc:date>
|
|
535
|
+
</item>
|
|
536
|
+
|
|
537
|
+
<item rdf:about="http://www.w3.org/QA/2006/01/quality_assurance_interest_gro.html">
|
|
538
|
+
<title>Quality Assurance Interest Group meets at the W3C Technical Plenary 2006</title>
|
|
539
|
+
<link>http://www.w3.org/QA/2006/01/quality_assurance_interest_gro.html</link>
|
|
540
|
+
<description> <![CDATA[<p>Once a year, W3C hosts a five day event, the <a href="http://www.w3.org/2005/12/allgroupoverview.html">W3C Technical Plenary</a>, where Working Groups (WG) and Interest Groups (IG) hold their face to face meetings in one place and have the opportunity to meet and liaise with participants from other groups. The <acronym title="Quality Assurance">QA</acronym> Interest Group meeting during this event is open to the public. </p>
|
|
541
|
+
|
|
542
|
+
<p>You are welcome to join us in Cannes, Mandelieu (France) from 27 February to 28 February 2006. <strong>Deadline for registration: February 16, 2006</strong></p>
|
|
543
|
+
|
|
544
|
+
]]>
|
|
545
|
+
<![CDATA[<p>The <acronym title="Quality Assurance">QA</acronym> <a href="http://www.w3.org/QA/IG/">IG</a> is a group which is mainly composed of participants of the <a href="http://lists.w3.org/Archives/Public/www-qa/">www-qa</a>, <a href="http://lists.w3.org/Archives/Public/public-evangelist/">public-evangelist</a> and <a href="http://lists.w3.org/Archives/Public/public-qa-dev/">public-qa-dev</a> mailing-lists. It is a completely <strong>open group to the public</strong>. Anyone can participate and contribute to the publication of W3C IG Notes.</p>
|
|
546
|
+
|
|
547
|
+
<p>During this meeting, we will try to address some points of this following preliminary agenda and maybe open new possible topics depending on the level of participation. </p>
|
|
548
|
+
|
|
549
|
+
<h3 id="agenda">Agenda</h3>
|
|
550
|
+
|
|
551
|
+
<ul>
|
|
552
|
+
<li>Evangelization + W3C IG Notes: Plan for publication</li>
|
|
553
|
+
<li>Curriculum for Web standards</li>
|
|
554
|
+
<li>Validator*S*: Development, future, etc.</li>
|
|
555
|
+
<li><a href="http://www.w3.org/TR/chips/">CHIPs</a> and <a href="http://www.w3.org/TR/cuap/">CUAP</a> Notes</li>
|
|
556
|
+
<li>QA Findings ala <a href="http://www.w3.org/2001/tag/findings">TAG Findings</a>
|
|
557
|
+
<ul>
|
|
558
|
+
<li>Testable and non normative</li>
|
|
559
|
+
<li>Common EBNF for XML specs (See <cite><a href="http://lists.w3.org/Archives/Public/www-qa/2006Jan/0000.html">We need a EBNF spec</a></cite></li>
|
|
560
|
+
<li>etc.</li></ul></li>
|
|
561
|
+
<li><a href="http://www.w3.org/2001/03/earl/">EARL</a> update and relations to QA</li>
|
|
562
|
+
<li>Ongoing development of QA guidelines, tutorials, templates, etc.</li>
|
|
563
|
+
<li><a href="http://www.w3.org/TR/test-metadata/">Test Case Metadata</a> (Concrete Schema)</li>
|
|
564
|
+
<li><a href="http://www.w3.org/2003/glossary/">Glossary</a></li>
|
|
565
|
+
<li>WAI coordination with QA</li>
|
|
566
|
+
<li>Dummy Guide to Test Assertions</li>
|
|
567
|
+
</ul>
|
|
568
|
+
|
|
569
|
+
<p><a href="http://www.w3.org/2005/12/allgroupoverview.html#Registration">Please register now!</a> (before February 16, 2006)</p>]]></description>
|
|
570
|
+
<dc:subject>QAIG Life</dc:subject>
|
|
571
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
572
|
+
<dc:language>en</dc:language>
|
|
573
|
+
<dc:date>2006-01-31T22:21:00+00:00</dc:date>
|
|
574
|
+
</item>
|
|
575
|
+
|
|
576
|
+
<item rdf:about="http://www.w3.org/QA/2006/01/failed_commitments.html">
|
|
577
|
+
<title>Failed Commitments?</title>
|
|
578
|
+
<link>http://www.w3.org/QA/2006/01/failed_commitments.html</link>
|
|
579
|
+
<description> <![CDATA[<p>Do you remember? it was just three years ago or so. There were parades and brass bands. Many large Web sites were, at long last, making the switch to Web standards. For example, the Web designer <cite><a href="http://www.stopdesign.com/about/personnel/">Douglas Bowman</a></cite> was announcing the <a href="http://www.stopdesign.com/log/2002/10/11/finally-were-live.html">launch of the XHTML, CSS, Validated Wired News</a> Web site. That was great! That was a time of joy and feast. Groups like <a href="http://webstandards.org/">WASP</a> or <a href="http://www.maccaws.org/">MACCAWS</a>, Web professionals who believed in Web standards, who fought for them, were chanting the promises of better days, of a delightful rising sun on the horizon. </p>
|
|
580
|
+
|
|
581
|
+
<p>And where are we now?</p>]]>
|
|
582
|
+
<![CDATA[<h3 id="failed-redesign">Failed Redesign</h3>
|
|
583
|
+
|
|
584
|
+
<p>Recently, the unparagoned <cite><a href="http://blog.fawny.org/">Joe Clark</a></cite> has published an article about companies which have recently <a href="http://blog.fawny.org/2006/01/04/failed/">decided to redesign their Web sites and somehow failed</a>. </p>
|
|
585
|
+
|
|
586
|
+
<blockquote cite="http://blog.fawny.org/2006/01/04/failed/">
|
|
587
|
+
<p>A failed redesign is a Web page created from scratch, or substantially updated, during the era of Web standards that nonetheless ignores or misuses those standards. A failed redesign pretends that valid code and accessibility guidelines do not exist; it pretends that the 21st century is frozen in the amber of the year 1999. It indicates not merely unprofessional Web-development practices but outright incompetence. For if you are producing tag-soup code and using tables for layout in the 21st century, that’s what you are: Incompetent.</p>
|
|
588
|
+
</blockquote>
|
|
589
|
+
|
|
590
|
+
<p>What this reminds us, is that redesigning a Web site is not only a question of using XHTML and CSS, but using them in the appropriate way thinking about semantics, accessibility, internationalization, etc. In Jazz, you could put together the best jazz cellist and pianist together and still end in a monstruous cacophony. They have to be in harmony, they have to get their improvisation right. In Web design, you can improvise, you can create, but you have to be in harmony if you don't want to turn your blue note cave into a business catastrophe.</p>
|
|
591
|
+
|
|
592
|
+
<p>But that's not all! It's not enough to get it right once, to give one enjoyable jam for the audience... You have to give a good performance every. single. night. Oh! Of course a little quack, sometimes might not be such a problem, it will just remind that we are all humans. But a continuous sequence of quacks only shows your impressive ability to impersonate a gaggle of ducks.</p>
|
|
593
|
+
|
|
594
|
+
<h3 id="failed">Failed Commitments</h3>
|
|
595
|
+
|
|
596
|
+
<p><cite><a href="http://www.zeldman.com/">Jeffrey Zeldman</a></cite>, in his talk about <cite><a href="http://www.happycog.com/lectures/dwws/">Designing with Web Standards</a></cite>, had a list of Web sites which, a few years ago, had finally decided to go live with a new design, with an exciting redesign. They were examples of companies which had made the switch to Web standards. Trumpets in the sky, we could hear them.</p>
|
|
597
|
+
|
|
598
|
+
<table>
|
|
599
|
+
<tr>
|
|
600
|
+
<th>Web site</th> <th>Validation</th>
|
|
601
|
+
</tr>
|
|
602
|
+
<tr>
|
|
603
|
+
<td><a href="http://www.foxsearchlight.com/">Fox SearchLight</a></td> <td class="failed">Failed</td>
|
|
604
|
+
</tr>
|
|
605
|
+
<tr>
|
|
606
|
+
<td><a href="http://www.k10k.net/">K10K</a></td> <td class="failed">Failed</td>
|
|
607
|
+
</tr>
|
|
608
|
+
<tr>
|
|
609
|
+
<td><a href="http://navy.com/">Navy</a></td> <td class="valid">Valid</td>
|
|
610
|
+
</tr>
|
|
611
|
+
<tr>
|
|
612
|
+
<td><a href="http://www.inc.com/">Inc.com</a></td> <td class="failed">Failed</td>
|
|
613
|
+
</tr>
|
|
614
|
+
<tr>
|
|
615
|
+
<td><a href="http://www.espn.com/">ESPN</a></td> <td class="failed">Failed</td>
|
|
616
|
+
</tr>
|
|
617
|
+
<tr>
|
|
618
|
+
<td><a href="http://www.wired.com/">Wired</a></td> <td class="failed">Failed</td>
|
|
619
|
+
</tr>
|
|
620
|
+
<tr>
|
|
621
|
+
<td><a href="http://www.pga.com/openchampionship/">PGA</a></td> <td class="failed">Failed</td>
|
|
622
|
+
</tr>
|
|
623
|
+
<tr>
|
|
624
|
+
<td><a href="http://www.quark.com/">Quark Inc.</a></td> <td class="failed">Failed</td>
|
|
625
|
+
</tr>
|
|
626
|
+
<tr><td colspan="2" class="note">Note 1: These results have been collected during January 2006, and they may change in the future.<br/>
|
|
627
|
+
Note 2: The homepage is a poor indicator of the validity of a whole Web site.</td></tr>
|
|
628
|
+
</table>
|
|
629
|
+
|
|
630
|
+
<p>Is there hope?</p>
|
|
631
|
+
|
|
632
|
+
<h3 id="never">Never Stops The Music</h3>
|
|
633
|
+
|
|
634
|
+
<p>Making a valid, accessible Web site is only the beginning of the music. Most sites, good or bad, are living things: pages are added, content is updated, reorganized sometimes. It's unlikely that it will be kept as is, clean and polished, unless you put a continous quality process in place. Just keep the music flowing.</p>
|
|
635
|
+
|
|
636
|
+
<p>Unlike in Jazz, it doesn't really take greatness to always play Web Design right: it's okay to make mistakes, because it's always possible to come back and fix the mistakes. And with a little discipline and a few good tools, it gets really trivial.</p>
|
|
637
|
+
|
|
638
|
+
<p>The <a href="http://www.w3.org/QA/Tools/LogValidator/">LogValidator</a> is a tool which might help in this task. It's simple, it's extensible to one's own needs and it can be tweaked to meet the internal requirements of any company. How? Just read <cite><a href="http://www.w3.org/QA/2002/09/Step-by-step">Making your website valid: a step by step guide</a></cite> and <cite><a href="http://www.w3.org/QA/2003/03/web-kit">Web Standards Switch</a></cite>.</p>
|
|
639
|
+
|
|
640
|
+
<blockquote><p>There are wonderful things in real jazz, the talent for improvisation, the liveliness, the being at one with the audience.</p>
|
|
641
|
+
<p><cite><a href="http://en.wikipedia.org/wiki/Henri_Matisse">Henri Matisse</a></cite></p>
|
|
642
|
+
</blockquote>
|
|
643
|
+
<p>There are wonderful things in real Web design, the many ways to convey information, the being at one with the readers... and the fact that a failure can always be worked upon and fixed.</p>
|
|
644
|
+
|
|
645
|
+
]]></description>
|
|
646
|
+
<dc:subject>Opinions & Editorial</dc:subject>
|
|
647
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
648
|
+
<dc:language>en</dc:language>
|
|
649
|
+
<dc:date>2006-01-30T01:12:30+00:00</dc:date>
|
|
650
|
+
</item>
|
|
651
|
+
|
|
652
|
+
<item rdf:about="http://www.w3.org/QA/2005/11/w3c_renews_quality_assurance_i.html">
|
|
653
|
+
<title>W3C Renews Quality Assurance Interest Group</title>
|
|
654
|
+
<link>http://www.w3.org/QA/2005/11/w3c_renews_quality_assurance_i.html</link>
|
|
655
|
+
<description> <![CDATA[<p>W3C is pleased to announce the renewal of the <a href="/QA/">Quality Assurance Activity</a> and the <a href="/QA/IG/">QA Interest Group</a>, chaired by Karl Dubost (W3C) and Lynne Rosenthal (NIST). The main objective of the QA Interest Group (QA IG) is to provide a venue for W3C, its Membership, and the Web community to share their experiences and involvement with QA. Participation is open to <a href="/Consortium/Member/List">W3C<br />
|
|
656
|
+
Members</a> and the public.</p>]]>
|
|
657
|
+
</description>
|
|
658
|
+
<dc:subject>QAIG Life</dc:subject>
|
|
659
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
660
|
+
<dc:language>en</dc:language>
|
|
661
|
+
<dc:date>2005-11-28T00:16:25+00:00</dc:date>
|
|
662
|
+
</item>
|
|
663
|
+
|
|
664
|
+
<item rdf:about="http://www.w3.org/QA/2005/10/markup_validator_071.html">
|
|
665
|
+
<title>Markup Validator 0.7.1</title>
|
|
666
|
+
<link>http://www.w3.org/QA/2005/10/markup_validator_071.html</link>
|
|
667
|
+
<description> <![CDATA[<p>New release of the <a href="http://validator.w3.org/">W3C Markup Validator</a> (<abbr title="also known as">a.k.a</abbr> HTML Validator). Introducing performance enhancements and including minor fixes in the user interface and in the "Direct Input" validation results.<br />
|
|
668
|
+
Read the <a href="http://lists.w3.org/Archives/Public/www-validator/2005Oct/0055.html">announcement</a> for details.</p>]]>
|
|
669
|
+
</description>
|
|
670
|
+
<dc:subject>Tools</dc:subject>
|
|
671
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
672
|
+
<dc:language>en</dc:language>
|
|
673
|
+
<dc:date>2005-10-18T00:22:24+00:00</dc:date>
|
|
674
|
+
</item>
|
|
675
|
+
|
|
676
|
+
<item rdf:about="http://www.w3.org/QA/2005/09/css_validator_updated.html">
|
|
677
|
+
<title>CSS Validator updated</title>
|
|
678
|
+
<link>http://www.w3.org/QA/2005/09/css_validator_updated.html</link>
|
|
679
|
+
<description> <![CDATA[<p>The latest update of the <a href="http://jigsaw.w3.org/css-validator/">W3C CSS Validation Service</a> includes a stable SOAP access and output to the CSS validator, the addition of a profile for the CSS 2.1 specification, and a large number of bug fixes. Read the <a href="http://lists.w3.org/Archives/Public/www-validator-css/2005Sep/0014">announcement</a> for details.</p>]]>
|
|
680
|
+
</description>
|
|
681
|
+
<dc:subject>Tools</dc:subject>
|
|
682
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
683
|
+
<dc:language>en</dc:language>
|
|
684
|
+
<dc:date>2005-09-16T00:36:49+00:00</dc:date>
|
|
685
|
+
</item>
|
|
686
|
+
|
|
687
|
+
<item rdf:about="http://www.w3.org/QA/2005/09/log_validator_10.html">
|
|
688
|
+
<title>Log Validator 1.0</title>
|
|
689
|
+
<link>http://www.w3.org/QA/2005/09/log_validator_10.html</link>
|
|
690
|
+
<description> <![CDATA[<p>Release of the W3C <a href="http://www.w3.org/QA/Tools/LogValidator/">Log Validator</a> version 1.0. The Log Validator makes it easy to manage the quality of even large Web Sites,step by step, by finding the most popular documents failing Markup or CSS validation, or withbroken links. Read the <a href="http://lists.w3.org/Archives/Public/www-validator/2005Sep/0029.html">announcement</a> for details.</p>]]>
|
|
691
|
+
</description>
|
|
692
|
+
<dc:subject>Tools</dc:subject>
|
|
693
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
694
|
+
<dc:language>en</dc:language>
|
|
695
|
+
<dc:date>2005-09-09T00:38:53+00:00</dc:date>
|
|
696
|
+
</item>
|
|
697
|
+
|
|
698
|
+
<item rdf:about="http://www.w3.org/QA/2005/09/the_qa_handbook_published_as_a.html">
|
|
699
|
+
<title>The QA Handbook published as a W3C Working Group Note</title>
|
|
700
|
+
<link>http://www.w3.org/QA/2005/09/the_qa_handbook_published_as_a.html</link>
|
|
701
|
+
<description> <![CDATA[<p><cite><a href="http://www.w3.org/TR/2005/NOTE-qa-handbook-20050906/">The QA Handbook</a></cite>, designed to facilitate and accelerate the work of W3C Working Groups, has been updated and published as a W3C Working Group Note.</p>]]>
|
|
702
|
+
</description>
|
|
703
|
+
<dc:subject>Publications</dc:subject>
|
|
704
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
705
|
+
<dc:language>en</dc:language>
|
|
706
|
+
<dc:date>2005-09-06T00:42:02+00:00</dc:date>
|
|
707
|
+
</item>
|
|
708
|
+
|
|
709
|
+
<item rdf:about="http://www.w3.org/QA/2005/09/qa_at_w3c_continues_future_of.html">
|
|
710
|
+
<title>QA at W3C continues: future of the QAIG</title>
|
|
711
|
+
<link>http://www.w3.org/QA/2005/09/qa_at_w3c_continues_future_of.html</link>
|
|
712
|
+
<description> <![CDATA[<p>With a number of documents published in the past few days and more to come soon, W3C's QA Activity, and the QA Working group have reached the end of their charter. But W3C's commitment to quality continues! In a message to the <acronym title="Quality Assurance Interest Group">QAIG</acronym> mailing-list, Karl Dubost explains <a href="http://lists.w3.org/Archives/Public/www-qa/2005Sep/0001.html">what the future holds for QA at W3C in general, and the QA IG in particular</a>.</p>]]>
|
|
713
|
+
</description>
|
|
714
|
+
<dc:subject>QAIG Life</dc:subject>
|
|
715
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
716
|
+
<dc:language>en</dc:language>
|
|
717
|
+
<dc:date>2005-09-06T00:40:37+00:00</dc:date>
|
|
718
|
+
</item>
|
|
719
|
+
|
|
720
|
+
<item rdf:about="http://www.w3.org/QA/2005/08/variability_in_specifications.html">
|
|
721
|
+
<title>Variability in Specifications published as a W3C Working Group Note</title>
|
|
722
|
+
<link>http://www.w3.org/QA/2005/08/variability_in_specifications.html</link>
|
|
723
|
+
<description> <![CDATA[<p><cite><a href="http://www.w3.org/TR/2005/NOTE-spec-variability-20050831/">Variability in Specifications</a></cite>, a companion to the <cite><a href="http://www.w3.org/TR/qaframe-spec/">QA Framework: Specification Guidelines</a></cite>, has been updated and published as a W3C Working Group Note. The Note contains advanced specification design considerations and conformance-related techniques. It describes how design of a specification's conformance model affects implementability and interoperability.</p>]]>
|
|
724
|
+
</description>
|
|
725
|
+
<dc:subject>Publications</dc:subject>
|
|
726
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
727
|
+
<dc:language>en</dc:language>
|
|
728
|
+
<dc:date>2005-08-30T00:46:17+00:00</dc:date>
|
|
729
|
+
</item>
|
|
730
|
+
|
|
731
|
+
<item rdf:about="http://www.w3.org/QA/2005/08/qa_framework_specification_gui.html">
|
|
732
|
+
<title>QA Framework: Specification Guidelines is a W3C Recommendation</title>
|
|
733
|
+
<link>http://www.w3.org/QA/2005/08/qa_framework_specification_gui.html</link>
|
|
734
|
+
<description> <![CDATA[<p><cite><a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/">QA Framework: Specification Guidelines</a></cite>, the main document produced by the <a href="http://www.w3.org/QA/WG/">QA Working Group</a> has been published as a W3C Recommendation on August 17. Publication as a <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsW3C">W3C Recommendation</a> is the sign that this document has received the endorsement of W3C Members and the Director. See also the <a href="http://www.w3.org/2005/08/qa-pressrelease">related press release</a>.</p>]]>
|
|
735
|
+
</description>
|
|
736
|
+
<dc:subject>Publications</dc:subject>
|
|
737
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
738
|
+
<dc:language>en</dc:language>
|
|
739
|
+
<dc:date>2005-08-18T00:47:43+00:00</dc:date>
|
|
740
|
+
</item>
|
|
741
|
+
|
|
742
|
+
<item rdf:about="http://www.w3.org/QA/2005/08/w3c_markup_validator_v070_rele.html">
|
|
743
|
+
<title>W3C Markup Validator v0.7.0 released</title>
|
|
744
|
+
<link>http://www.w3.org/QA/2005/08/w3c_markup_validator_v070_rele.html</link>
|
|
745
|
+
<description> <![CDATA[<p>New release of the <a href="http://validator.w3.org/">W3C Markup Validator</a> (<abbr title="also known as">a.k.a</abbr> HTML Validator). Includes usability enhancements, improved <a href="http://validator.w3.org/feedback.html">feedback</a>, support for installation on Windows, and better support for both W3C and non-W3C document types.</p>]]>
|
|
746
|
+
</description>
|
|
747
|
+
<dc:subject>Tools</dc:subject>
|
|
748
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
749
|
+
<dc:language>en</dc:language>
|
|
750
|
+
<dc:date>2005-08-08T00:49:07+00:00</dc:date>
|
|
751
|
+
</item>
|
|
752
|
+
|
|
753
|
+
<item rdf:about="http://www.w3.org/QA/2005/05/wasp_asks_w3c_adding_multimedi.html">
|
|
754
|
+
<title>“WaSP asks W3C”, Adding Multimedia in Web Documents (part 2) published</title>
|
|
755
|
+
<link>http://www.w3.org/QA/2005/05/wasp_asks_w3c_adding_multimedi.html</link>
|
|
756
|
+
<description> <![CDATA[<p>Last week, in a new instance of the <a href="http://www.w3.org/QA/Library/WaW">WaSP asks W3C</a> project, the QA Team completed its answer on <cite><a href="http://webstandards.org/learn/askw3c/jun2004.html">Adding Multimedia in Web Documents</a></cite> with <a href="http://webstandards.org/learn/askw3c/may2005.html">more details on the use and implementation of the <code>object</code> tag</a> in HTML. Discussion and debate are welcome on the <a href="http://lists.w3.org/Archives/Public/public-evangelist/">public-evangelist</a> mailing list.</p>]]>
|
|
757
|
+
</description>
|
|
758
|
+
<dc:subject>Tutorials</dc:subject>
|
|
759
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
760
|
+
<dc:language>en</dc:language>
|
|
761
|
+
<dc:date>2005-05-31T00:50:41+00:00</dc:date>
|
|
762
|
+
</item>
|
|
763
|
+
|
|
764
|
+
<item rdf:about="http://www.w3.org/QA/2005/05/test_faq.html">
|
|
765
|
+
<title>Test FAQ</title>
|
|
766
|
+
<link>http://www.w3.org/QA/2005/05/test_faq.html</link>
|
|
767
|
+
<description> <![CDATA[<p>The <a href="http://www.w3.org/QA/WG/">QA Working Group</a> has released a <cite><a href="http://www.w3.org/QA/WG/2005/01/test-faq">Test <abbr title="Frequently Asked Questions">FAQ</abbr></a></cite>. The 17 questions it addresses match the different topics the QA Working Group has found particularly important for most Working Groups in W3C and incorporate examples and ideas from various existing testing efforts in W3C.</p>]]>
|
|
768
|
+
</description>
|
|
769
|
+
<dc:subject>Publications</dc:subject>
|
|
770
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
771
|
+
<dc:language>en</dc:language>
|
|
772
|
+
<dc:date>2005-05-11T01:00:34+00:00</dc:date>
|
|
773
|
+
</item>
|
|
774
|
+
|
|
775
|
+
<item rdf:about="http://www.w3.org/QA/2005/05/more_about_custom_dtd_article.html">
|
|
776
|
+
<title>“More About Custom DTD” article published in A List Apart</title>
|
|
777
|
+
<link>http://www.w3.org/QA/2005/05/more_about_custom_dtd_article.html</link>
|
|
778
|
+
<description> <![CDATA[<p>The QA Team has written an article for <a href="http://www.alistapart.com/">A List Apart</a>, entitled <cite><a href="http://www.alistapart.com/articles/customdtds2/">More About Custom DTDs</a></cite>, explaining when custom DTDs make sense, and when they don't.</p>]]>
|
|
779
|
+
</description>
|
|
780
|
+
<dc:subject>Tutorials</dc:subject>
|
|
781
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
782
|
+
<dc:language>en</dc:language>
|
|
783
|
+
<dc:date>2005-05-11T00:57:12+00:00</dc:date>
|
|
784
|
+
</item>
|
|
785
|
+
|
|
786
|
+
<item rdf:about="http://www.w3.org/QA/2005/04/link_checker_update_version_42.html">
|
|
787
|
+
<title>Link Checker update (version 4.2)</title>
|
|
788
|
+
<link>http://www.w3.org/QA/2005/04/link_checker_update_version_42.html</link>
|
|
789
|
+
<description> <![CDATA[<p>W3C's free Link Checker was updated with a new bug fix release which includes accessibility improvements for the tool's Web interface. <a href="http://validator.w3.org/checklink">Use the link checking service online</a> or check the <a href="http://www.w3.org/mid/20050428064855.GA1153@w3.mag.keio.ac.jp">release announcement</a> for download information.</p>]]>
|
|
790
|
+
</description>
|
|
791
|
+
<dc:subject>Tools</dc:subject>
|
|
792
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
793
|
+
<dc:language>en</dc:language>
|
|
794
|
+
<dc:date>2005-04-28T01:03:17+00:00</dc:date>
|
|
795
|
+
</item>
|
|
796
|
+
|
|
797
|
+
<item rdf:about="http://www.w3.org/QA/2005/04/specification_guidelines_and_v.html">
|
|
798
|
+
<title>Specification Guidelines and Variability in Specifications updated</title>
|
|
799
|
+
<link>http://www.w3.org/QA/2005/04/specification_guidelines_and_v.html</link>
|
|
800
|
+
<description> <![CDATA[<p>The <a href="http://www.w3.org/QA/WG/">QA Working Group</a> has published an update of two of its documents: <cite><a href="http://www.w3.org/TR/2005/WD-qaframe-spec-20050428/">QA Framework: Specification Guidelines</a></cite> and <cite><a href="http://www.w3.org/TR/2005/WD-spec-variability-20050428/">Variability in Specifications</a></cite>. The new version of <cite>Specification Guidelines</cite> includes the resolutions of the comments received during the Last Call period, and is the last version before the Working Group requests Proposed Recommendation status to the W3C Director.</p>]]>
|
|
801
|
+
</description>
|
|
802
|
+
<dc:subject>Publications</dc:subject>
|
|
803
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
804
|
+
<dc:language>en</dc:language>
|
|
805
|
+
<dc:date>2005-04-28T01:01:55+00:00</dc:date>
|
|
806
|
+
</item>
|
|
807
|
+
|
|
808
|
+
<item rdf:about="http://www.w3.org/QA/2005/04/new_article_ampersands_php_ses.html">
|
|
809
|
+
<title>New Article: Ampersands, PHP Sessions and Valid HTML</title>
|
|
810
|
+
<link>http://www.w3.org/QA/2005/04/new_article_ampersands_php_ses.html</link>
|
|
811
|
+
<description> <![CDATA[<p>A new technical article on the topic of <a href="http://www.w3.org/QA/2005/04/php-session">Ampersands, PHP Sessions and Valid HTML</a> was published by the QAIG, courtesy of <a href="http://dorward.me.uk/">David Dorward</a>. The QA Interest Group welcomes such contribution of material, see our <a href="http://www.w3.org/QA/2003/06/Contrib">Contribution Guidelines</a> for details.</p>]]>
|
|
812
|
+
</description>
|
|
813
|
+
<dc:subject>Publications</dc:subject>
|
|
814
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
815
|
+
<dc:language>en</dc:language>
|
|
816
|
+
<dc:date>2005-04-26T01:04:08+00:00</dc:date>
|
|
817
|
+
</item>
|
|
818
|
+
|
|
819
|
+
<item rdf:about="http://www.w3.org/QA/2005/02/qa_wg_f2f_at_the_technical_ple.html">
|
|
820
|
+
<title>QA WG F2F at the Technical Plenary 2005</title>
|
|
821
|
+
<link>http://www.w3.org/QA/2005/02/qa_wg_f2f_at_the_technical_ple.html</link>
|
|
822
|
+
<description> <![CDATA[<p>The QA WG and IG will have their face to face meeting in Boston, MA, during the W3C Technical Plenary 2005. If you have been an active participant of the QA IG, you might want to contact the QA IG chairs to be invited.</p>]]>
|
|
823
|
+
</description>
|
|
824
|
+
<dc:subject>Meetings</dc:subject>
|
|
825
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
826
|
+
<dc:language>en</dc:language>
|
|
827
|
+
<dc:date>2005-02-16T01:10:12+00:00</dc:date>
|
|
828
|
+
</item>
|
|
829
|
+
|
|
830
|
+
<item rdf:about="http://www.w3.org/QA/2005/02/css_validator_available_in_spa.html">
|
|
831
|
+
<title>CSS Validator available in Spanish</title>
|
|
832
|
+
<link>http://www.w3.org/QA/2005/02/css_validator_available_in_spa.html</link>
|
|
833
|
+
<description> <![CDATA[<p>W3C's open source <a href="http://jigsaw.w3.org/css-validator/">CSS Validator</a> is now available in Spanish language, thanks to the translation work of the <a href="http://www.w3c.es/" hreflang="es">W3C Spanish office</a>. The CSS Validator is also <a href="http://jigsaw.w3.org/css-validator/thanks.html">available in English, Chinese, French, German, Italian, Japanese and Russian</a>.</p>]]>
|
|
834
|
+
</description>
|
|
835
|
+
<dc:subject>CSS</dc:subject>
|
|
836
|
+
<dc:creator>Karl Dubost</dc:creator>
|
|
837
|
+
<dc:language>en</dc:language>
|
|
838
|
+
<dc:date>2005-02-16T01:08:54+00:00</dc:date>
|
|
839
|
+
</item>
|
|
840
|
+
|
|
841
|
+
|
|
842
|
+
|
|
843
|
+
</rdf:RDF>
|