<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ashley Bowers Blog &#187; W3C</title>
	<atom:link href="http://ashleybowers.com/blog/category/w3c/feed/" rel="self" type="application/rss+xml" />
	<link>http://ashleybowers.com/blog</link>
	<description>Web standards, programming, operating systems, browsers, and more!</description>
	<lastBuildDate>Mon, 15 Nov 2010 01:28:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Accessible Search by Google</title>
		<link>http://ashleybowers.com/blog/2006/08/03/accessible-search-by-google/</link>
		<comments>http://ashleybowers.com/blog/2006/08/03/accessible-search-by-google/#comments</comments>
		<pubDate>Fri, 04 Aug 2006 04:02:20 +0000</pubDate>
		<dc:creator>Ashley</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[Web Standards]]></category>

		<guid isPermaLink="false">http://ashleybowers.com/blog/?p=89</guid>
		<description><![CDATA[Accessible Search is a new thing in Google labs that puts websites that are standards friendly to the top of the results. This is very interesting because it seems Google is getting into other Page Rank and that I heard they are also working on a Trust Rank and I wonder if the toolbar will [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://labs.google.com/accessible/">Accessible Search</a> is a new thing in Google labs that puts websites that are standards friendly to the top of the results. This is very interesting because it seems Google is getting into other Page Rank and that I heard they are also working on a Trust Rank and I wonder if the toolbar will start to reflect other ways Google ranks the site. Having a disabled  family member it makes me happy that Google has made a way for her to search for websites that are more friendly to her disablity. Congratulations to Google Team and I hope this makes it out of the Labs real soon. Also if you want to do a side by side search comparing the two seaches  <a href="http://blog.outer-court.com/accessible/?q=standards">click here</a></p>
]]></content:encoded>
			<wfw:commentRss>http://ashleybowers.com/blog/2006/08/03/accessible-search-by-google/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Update of the Best Practices document and Scope document</title>
		<link>http://ashleybowers.com/blog/2005/12/21/update-of-the-best-practices-document-and-scope-document/</link>
		<comments>http://ashleybowers.com/blog/2005/12/21/update-of-the-best-practices-document-and-scope-document/#comments</comments>
		<pubDate>Wed, 21 Dec 2005 12:14:11 +0000</pubDate>
		<dc:creator>Ashley</dc:creator>
				<category><![CDATA[Blogs]]></category>
		<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://ashleybowers.com/blog/?p=47</guid>
		<description><![CDATA[Dominique Hazael-Massieux from the W3C writes After a very productive face to face meeting in Cambridge, Massachussets, hosted by France Telecom, the Working Group has made enough progress in its main document to publish an updated Working Draft of the Mobile Web Best Practices, featuring quite a few changes: * a clean up of the [...]]]></description>
			<content:encoded><![CDATA[<p>Dominique Hazael-Massieux from the <a href="http://www.w3.org/blog/BPWG/2005/12/19/update_of_the_best_practices_document">W3C </a>writes</p>
<p>After a very productive face to face meeting in Cambridge, Massachussets, hosted by France Telecom, the Working Group has made enough progress in its main document to publish an updated Working Draft of the Mobile Web Best Practices, featuring quite a few changes:</p>
<p>    * a clean up of the Best Practices that didn&#8217;t fit well in the mobile-specific context</p>
<p>    * the association of a test assertion to each testable best practices, the other ones having been marked as informative</p>
<p>    * a clearer model of how content adaptation fits into the general conformance to the document</p>
<p>    * a definition of a default delivery context (replacing the notion of a &#8220;baseline device&#8221; in the previous draft), serving as a point of reference for cases where the content is not or cannot be adapted for a particular device</p>
<p>    * a general editorial clean up of the content</p>
<p>This results of a lot of collective work over the past few weeks, and the group is now hoping to reach consensus for a Last Call publication very soon! As a result of this, the group is not actually seeking direct feedback on this document, since it is expected to be updated in a few weeks at most.</p>
<p>They are asking everyone out there to take a look at this and send them any comments please help spread the word.</p>
]]></content:encoded>
			<wfw:commentRss>http://ashleybowers.com/blog/2005/12/21/update-of-the-best-practices-document-and-scope-document/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>First draft of Mobile Web Best Practices</title>
		<link>http://ashleybowers.com/blog/2005/12/16/first-draft-of-mobile-web-best-practices/</link>
		<comments>http://ashleybowers.com/blog/2005/12/16/first-draft-of-mobile-web-best-practices/#comments</comments>
		<pubDate>Fri, 16 Dec 2005 05:16:28 +0000</pubDate>
		<dc:creator>Ashley</dc:creator>
				<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://ashleybowers.com/blog/?p=38</guid>
		<description><![CDATA[W3C Mobile Web Best Practices Working Group asking for feedback!]]></description>
			<content:encoded><![CDATA[<p>From W3C Mobile Web Best Practices Working Group <a href="http://www.w3.org/blog/BPWG/2005/10/25/first_draft_of_mobile_web_best_practices">Blog</a></p>
<p>The Mobile Web Best Practices Working Group has released last week the first version of Mobile Web Best Practices 1.0, the core document the group is working on.</p>
<p>While the document is not complete and doesn&#8217;t reflect completely the group consensus, it is a very important achievement for us to show where we&#8217;re heading; it also invites comments on some specific issues on which the group would like to hear about&#8230; Don&#8217;t wait any second: go read it, and send comments</p>
]]></content:encoded>
			<wfw:commentRss>http://ashleybowers.com/blog/2005/12/16/first-draft-of-mobile-web-best-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>W3C Atom Feed Validator</title>
		<link>http://ashleybowers.com/blog/2005/12/15/w3c-atom-feed-validator/</link>
		<comments>http://ashleybowers.com/blog/2005/12/15/w3c-atom-feed-validator/#comments</comments>
		<pubDate>Thu, 15 Dec 2005 14:33:00 +0000</pubDate>
		<dc:creator>Ashley</dc:creator>
				<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://ashleybowers.com/blog/?p=37</guid>
		<description><![CDATA[W3C Atom Feed Validator]]></description>
			<content:encoded><![CDATA[<p>W3C Atom Feed Validator</p>
<p>Warning</p>
<p>This feed is valid, but may cause problems for some users. We recommend fixing these problems.</p>
<p>    *line 1, column 38: This feed is an obsolete version [help]</p>
<p>     line 128, column 279: summary should not contain HTML unless declared in the type attribute (8 occurrences) [help]</p>
<p>Source: http://ashleybowers.com/blog/?feed%3Datom</p>
<p>Does anyone know how to fix this problem?</p>
]]></content:encoded>
			<wfw:commentRss>http://ashleybowers.com/blog/2005/12/15/w3c-atom-feed-validator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>W3C RSS Feed Validator</title>
		<link>http://ashleybowers.com/blog/2005/12/15/w3c-rss-feed-validator/</link>
		<comments>http://ashleybowers.com/blog/2005/12/15/w3c-rss-feed-validator/#comments</comments>
		<pubDate>Thu, 15 Dec 2005 14:30:53 +0000</pubDate>
		<dc:creator>Ashley</dc:creator>
				<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://ashleybowers.com/blog/?p=36</guid>
		<description><![CDATA[W3C RSS Feed Validator]]></description>
			<content:encoded><![CDATA[<p>W3C RSS Feed Validator</p>
<p>Congratulations!</p>
<p>[Valid RSS] This is a valid RSS feed.</p>
<p>If you would like to create a banner that links to this page (i.e. this validation result), do the following:</p>
<p>   1. Download the &#8220;valid RSS&#8221; banner.<br />
   2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)<br />
   3. Add this HTML to your page (change the image src attribute if necessary):</p>
]]></content:encoded>
			<wfw:commentRss>http://ashleybowers.com/blog/2005/12/15/w3c-rss-feed-validator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>W3C CSS Validator</title>
		<link>http://ashleybowers.com/blog/2005/12/15/w3c-css-validator/</link>
		<comments>http://ashleybowers.com/blog/2005/12/15/w3c-css-validator/#comments</comments>
		<pubDate>Thu, 15 Dec 2005 14:29:28 +0000</pubDate>
		<dc:creator>Ashley</dc:creator>
				<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://ashleybowers.com/blog/?p=35</guid>
		<description><![CDATA[W3C CSS Validator]]></description>
			<content:encoded><![CDATA[<p>W3C CSS Validator Results for http://ashleybowers.com/blog/<br />
Congratulations!</p>
<p>Valid CSS! This document validates as CSS!</p>
<p>To show your readers that you&#8217;ve taken the care to create an interoperable Web page, you may display this icon on any page that validates. Here is the XHTML you could use to add this icon to your Web page</p>
]]></content:encoded>
			<wfw:commentRss>http://ashleybowers.com/blog/2005/12/15/w3c-css-validator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>W3C Markup Validation Service</title>
		<link>http://ashleybowers.com/blog/2005/12/15/w3c-markup-validation-service/</link>
		<comments>http://ashleybowers.com/blog/2005/12/15/w3c-markup-validation-service/#comments</comments>
		<pubDate>Thu, 15 Dec 2005 14:23:04 +0000</pubDate>
		<dc:creator>Ashley</dc:creator>
				<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://ashleybowers.com/blog/?p=34</guid>
		<description><![CDATA[W3C Markup Validator]]></description>
			<content:encoded><![CDATA[<p> The document located at http ://ashleybowers.com/blog/  was checked and found to be valid XHTML 1.0 Transitional. This means that the resource in question identified itself as &#8220;XHTML 1.0 Transitional&#8221; and that we successfully performed a formal validation using an SGML or XML Parser (depending on the markup language used).</p>
<p>Valid XHTML 1.0 Transitional To show your readers that you have taken the care to create an interoperable Web page, you may display this icon on any page that validates. Here is the HTML you could use to add this icon to your Web page</p>
<p>If you like, you can download a copy of this image (in PNG or GIF format) to keep in your local web directory, and change the HTML fragment above to reference your local image rather than the one on this server.</p>
<p>If you use CSS in your document, you should also check it for validity using the W3C CSS Validation Service.</p>
]]></content:encoded>
			<wfw:commentRss>http://ashleybowers.com/blog/2005/12/15/w3c-markup-validation-service/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>W3C Moves Forward on New Extensions for Voice Technologies and the Web</title>
		<link>http://ashleybowers.com/blog/2005/12/10/w3c-moves-forward-on-new-extensions-for-voice-technologies-and-the-web/</link>
		<comments>http://ashleybowers.com/blog/2005/12/10/w3c-moves-forward-on-new-extensions-for-voice-technologies-and-the-web/#comments</comments>
		<pubDate>Sat, 10 Dec 2005 06:00:14 +0000</pubDate>
		<dc:creator>Ashley</dc:creator>
				<category><![CDATA[W3C]]></category>

		<guid isPermaLink="false">http://ashleybowers.com/blog/?p=21</guid>
		<description><![CDATA[W3C Moves Forward on New Extensions for Voice Technologies and the Web Wednesday, December 07 2005 @ 04:21 PM CST Contributed by: ByteEnable The World Wide Web Consortium (W3C) announced new work on extensions to components of the Speech Interface Framework which will both extend Speech Synthesis Markup Language functionality to Asian and other languages, [...]]]></description>
			<content:encoded><![CDATA[<p>W3C Moves Forward on New Extensions for Voice Technologies and the Web  </p>
<p>Wednesday, December 07 2005 @ 04:21 PM CST<br />
Contributed by: ByteEnable</p>
<p>The World Wide Web Consortium (W3C) announced new work on extensions to components of the Speech Interface Framework which will both extend Speech Synthesis Markup Language functionality to Asian and other languages, and include speaker verification features into the next version of VoiceXML, version 3.0. Addressing both areas expands both the reach and functionality of the framework.</p>
<p>Working Group Internationalizing SSML</p>
<p>The Speech Synthesis Markup Language (SSML), a W3C Recommendation since 2004, is designed to provide a rich, XML-based markup language for assisting the generation of synthetic speech in Web and other applications. The essential role of the markup language is to provide authors of synthesizable content a standard way to control aspects of speech such as pronunciation, volume, pitch, rate, etc. across different synthesis-capable platforms.</p>
<p>While these attributes are critical, additional attributes may be even more important to specific languages. For example, Mandarin Chinese, the most widely spoken language in the world today, also has the notion of tones &#8211; the same written character can have multiple pronunciations and meanings based on the tone used. Given the profusion of cellphones in China &#8211; some estimate as high as over one billion &#8211; the case for extending SSML for Mandarin is clear in terms of sheer market forces. Including extensions for Japanese, Korean and other languages will ensure that a fuller participation possible of the world on the Web.</p>
<p>Speaker Verification Extension to Be Included in VoiceXML 3.0</p>
<p>Another feature users are demanding of telephony services and the Web is speaker verification.</p>
<p>&#8220;Identity theft, fraud, phishing, terrorism, and even the high cost of resetting passwords have heightened interest in deploying biometric security for all communication channels, including the telephone,â€ said Ken Rehor of Vocalocity, newly elected Chairman of the VoiceXML Forum and participant in the W3C Voice Browser Working Group. â€œSpeaker verification and identification is not only the best biometric for securing telephone transactions and communications, it can work seamlessly with speech recognition and speech synthesis in VoiceXML deployments.&#8221;</p>
<p>Until now, most vendors have compensated for this missing feature by making a custom fix for their services. The result has been a set of divergent technologies that do not interoperate. Thanks to requirements contributions from the VoiceXML Forum&#8217;s Speaker Biometrics Committee, the W3C Voice Browser Working Group has been able to identify the features needed for a standardized speech verification module. The Working Group is now beginning to address these requirements.</p>
<p>Timing Perfect for New Participants</p>
<p>Given the depth and breadth of the announced new work, as well as plans for additional features for VoiceXML 3.0, this is a perfect time for new companies, researchers and other interested parties to join W3C and participate in the latest developments for voice technologies and the Web. Among potential critical contributors are those from the research and industrial sectors throughout Asia in the areas of Asian languages and speaker verification, to allow for the best possible expertise in the development of standards that truly serve the needs of Web users worldwide. More information on the W3C Voice Browser Activity and on joining W3C is on the W3C Web site. </p>
]]></content:encoded>
			<wfw:commentRss>http://ashleybowers.com/blog/2005/12/10/w3c-moves-forward-on-new-extensions-for-voice-technologies-and-the-web/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

