<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>W3C Compliant</title>
	
	<link>http://w3c-compliant.com</link>
	<description>Web Development, Web Design, Search Engine Optimization</description>
	<lastBuildDate>Wed, 28 Jul 2010 12:21:37 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/W3cCompliant" /><feedburner:info uri="w3ccompliant" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>W3cCompliant</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><item>
		<title>Privacy Workshop Participants to Study Data Usage and Handling</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/NXOGBhRTPvI/</link>
		<comments>http://w3c-compliant.com/2010/07/privacy-workshop-participants-to-study-data-usage-and-handling/#comments</comments>
		<pubDate>Wed, 28 Jul 2010 12:21:37 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Home Page Stories]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[Semantic Web]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Design and Applications]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[W3C announces organization of a Workshop on Privacy and Data Usage Control, to take place in Cambridge, MA, UA on 4-5 October 2010. Users trust enormous amounts of personal information to a large variety of online services including social network...]]></description>
			<content:encoded><![CDATA[
        
        <p>W3C announces organization of a <a href="http://www.w3.org/2010/policy-ws/">Workshop on Privacy and Data Usage Control</a>, to take place in Cambridge, MA, UA on 4-5 October 2010. Users trust enormous amounts of personal information to a large variety of online services including social network sites, search engines, photo and video sharing services, and hosted email solutions. As those services become ever more tightly integrated, it becomes increasingly difficult to control the spread of information on the Web. Participants will represent a broad set of stakeholders, including researchers, database manufacturers, CRM-system manufacturers, and Social Networking Providers. Participants will study whether there is interest in further work on policy languages and data handling/data usage work within W3C. Anyone may participate in the Workshop; all participants must submit a short <a href="http://www.w3.org/2010/policy-ws/#paper">position paper</a>. More information about the Workshop is available in the <a href="http://www.w3.org/2010/policy-ws/">Call for Participation</a>. Learn more about W3C's <a href="http://www.w3.org/Privacy/">Privacy Activity</a>.
</p>
    
<p><a href="http://feedads.g.doubleclick.net/~a/XoUzZAgSBvjLFmcoGhcjoBBZNdg/0/da"><img src="http://feedads.g.doubleclick.net/~a/XoUzZAgSBvjLFmcoGhcjoBBZNdg/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/XoUzZAgSBvjLFmcoGhcjoBBZNdg/1/da"><img src="http://feedads.g.doubleclick.net/~a/XoUzZAgSBvjLFmcoGhcjoBBZNdg/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/NXOGBhRTPvI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/privacy-workshop-participants-to-study-data-usage-and-handling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/privacy-workshop-participants-to-study-data-usage-and-handling/</feedburner:origLink></item>
		<item>
		<title>First Draft of WOFF File Format 1.0 Published</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/o8VukzVCkaM/</link>
		<comments>http://w3c-compliant.com/2010/07/first-draft-of-woff-file-format-1-0-published/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 18:01:49 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Home Page Stories]]></category>
		<category><![CDATA[Publication]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Design and Applications]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[The WebFonts Working Group has published the First Public Working Draft of WOFF File Format 1.0. This document specifies the WOFF font format. This format was designed to provide lightweight, easy-to-implement compression of the font data, suitable for use in...]]></description>
			<content:encoded><![CDATA[
        
        <p>The <a href="http://www.w3.org/Fonts/WG/">WebFonts Working Group</a> has published the First Public Working Draft of <a href="http://www.w3.org/TR/2010/WD-WOFF-20100727/">WOFF File Format 1.0</a>. This document specifies the WOFF font format. This format was designed to provide lightweight, easy-to-implement compression of the font data, suitable for use in conjunction with CSS. Any TrueType/OpenType/Open Font Format file can be losslessly converted to WOFF for Web use (subject to licensing of the font data); once decoded by a user agent, the WOFF font will display identically to the original desktop font from which it was created. Learn more about the <a href="http://www.w3.org/Fonts/">Fonts Activity</a>.</p>
    
<p><a href="http://feedads.g.doubleclick.net/~a/inhgqsC-I6kVG1G4tk3rmFQnt8Q/0/da"><img src="http://feedads.g.doubleclick.net/~a/inhgqsC-I6kVG1G4tk3rmFQnt8Q/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/inhgqsC-I6kVG1G4tk3rmFQnt8Q/1/da"><img src="http://feedads.g.doubleclick.net/~a/inhgqsC-I6kVG1G4tk3rmFQnt8Q/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/o8VukzVCkaM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/first-draft-of-woff-file-format-1-0-published/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/first-draft-of-woff-file-format-1-0-published/</feedburner:origLink></item>
		<item>
		<title>Last Call: Cascading Style Sheets (CSS) Snapshot 2007</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/HuAITIgn1Rc/</link>
		<comments>http://w3c-compliant.com/2010/07/last-call-cascading-style-sheets-css-snapshot-2007/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 18:00:00 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Home Page Stories]]></category>
		<category><![CDATA[Publication]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Design and Applications]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[The Cascading Style Sheets (CSS) Working Group has published a Last Call Working Draft of Cascading Style Sheets (CSS) Snapshot 2007. This document collects together into one definition all the specifications that together form the current state of Cascading Style...]]></description>
			<content:encoded><![CDATA[
        
        <p>The <a href="http://www.w3.org/Style/CSS/members">Cascading Style Sheets (CSS) Working Group</a> has published a Last Call Working Draft of <a href="http://www.w3.org/TR/2010/WD-css-beijing-20100727/">Cascading Style Sheets (CSS) Snapshot 2007</a>. This document collects together into one definition all the specifications that together form the current state of Cascading Style Sheets (CSS) as of 2007. The primary audience is CSS implementors, not CSS authors, as this definition includes modules by specification stability, not Web browser adoption rate. Comments are welcome through 15 August. Learn more about the <a href="http://www.w3.org/Style/">Style Activity</a>.</p>
    
<p><a href="http://feedads.g.doubleclick.net/~a/GjIjeD88niWFcW8WQr20qTIR3fA/0/da"><img src="http://feedads.g.doubleclick.net/~a/GjIjeD88niWFcW8WQr20qTIR3fA/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/GjIjeD88niWFcW8WQr20qTIR3fA/1/da"><img src="http://feedads.g.doubleclick.net/~a/GjIjeD88niWFcW8WQr20qTIR3fA/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/HuAITIgn1Rc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/last-call-cascading-style-sheets-css-snapshot-2007/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/last-call-cascading-style-sheets-css-snapshot-2007/</feedburner:origLink></item>
		<item>
		<title>Cross-Origin Resource Sharing Draft Published</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/6-_4XwQdnOA/</link>
		<comments>http://w3c-compliant.com/2010/07/cross-origin-resource-sharing-draft-published/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 17:56:43 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Home Page Stories]]></category>
		<category><![CDATA[Publication]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Design and Applications]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[The Web Applications Working Group has published a Working Draft of Cross-Origin Resource Sharing. User agents commonly apply same-origin restrictions to network requests. These restrictions prevent a client-side Web application running from one origin from obtaining data retrieved from another...]]></description>
			<content:encoded><![CDATA[
        
        <p>The <a href="http://www.w3.org/2008/webapps/">Web Applications Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2010/WD-cors-20100727/">Cross-Origin Resource Sharing</a>. User agents commonly apply same-origin restrictions to network requests. These restrictions prevent a client-side Web application running from one origin from obtaining data retrieved from another origin, and also limit unsafe HTTP requests that can be automatically launched toward destinations that differ from the running application's origin. In user agents that follow this pattern, network requests typically use ambient authentication and session management information, including HTTP authentication and cookie information. This specification extends this model in a number of ways.Learn more about the <a href="http://www.w3.org/2006/rwc/">Rich Web Client Activity</a>.</p>
    
<p><a href="http://feedads.g.doubleclick.net/~a/jtDXYIePWRy4rb86096GlV8B3zc/0/da"><img src="http://feedads.g.doubleclick.net/~a/jtDXYIePWRy4rb86096GlV8B3zc/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/jtDXYIePWRy4rb86096GlV8B3zc/1/da"><img src="http://feedads.g.doubleclick.net/~a/jtDXYIePWRy4rb86096GlV8B3zc/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/6-_4XwQdnOA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/cross-origin-resource-sharing-draft-published/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/cross-origin-resource-sharing-draft-published/</feedburner:origLink></item>
		<item>
		<title>W3C Releases Unicorn, an All-in-One Validator</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/V5VFlDmV74Y/</link>
		<comments>http://w3c-compliant.com/2010/07/w3c-releases-unicorn-an-all-in-one-validator/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 13:46:08 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Home Page Stories]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[Top Story]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Design and Applications]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[W3C is pleased to announce the release of Unicorn, a one-stop tool to help people improve the quality of their Web pages. Unicorn combines a number of popular tools in a single, easy interface, including the Markup validator, CSS validator,...]]></description>
			<content:encoded><![CDATA[
        
        <p>W3C is pleased to announce the release of <a href="http://validator.w3.org/unicorn/">Unicorn</a>, a one-stop tool to help people improve the quality of their Web pages. Unicorn combines a number of popular tools in a single, easy interface, including the <a href="http://validator.w3.org/">Markup validator</a>, <a href="http://jigsaw.w3.org/css-validator/">CSS validator</a>, <a href="http://validator.w3.org/mobile/">mobileOk checker</a>, and <a href="http://validator.w3.org/feed/">Feed validator</a>, which remain available as individual services as well. W3C invites developers to enhance the service by <a href="http://code.w3.org/unicorn/wiki/Documentation/Observer">creating new modules</a> and testing them in our <a href="http://code.w3.org/unicorn/wiki#DevelopUnicornandValidationServices">online developer space</a> (or <a href="http://code.w3.org/unicorn/wiki/Documentation/Install">installing Unicorn locally</a>). W3C looks forward to code contributions from the community as well as <a href="http://code.w3.org/unicorn/wiki#Feedback">suggestions for new features</a>. W3C would like to thank the many people whose work has led up to this first release of Unicorn. This includes developers  who started and improved the tool over the past few years, users who have provided feedback, <a href="http://code.w3.org/unicorn/wiki/Translators">translators</a> who have helped localize the interface with  <a href="http://validator.w3.org/unicorn/translations">21 translations</a> so far, and sponsors HP and Mozilla and other individual donors. W3C welcomes <a href="http://code.w3.org/unicorn/wiki#Feedback">feedback</a> and <a href="http://www.w3.org/QA/Tools/Donate">donations</a> so that W3C can continue to expand this free service to the community. Learn more about <a href="http://www.w3.org/Status">W3C open source software</a>.
</p>

    
<p><a href="http://feedads.g.doubleclick.net/~a/TwdwpiIdnmW0XUFx8oqlh1XVyzY/0/da"><img src="http://feedads.g.doubleclick.net/~a/TwdwpiIdnmW0XUFx8oqlh1XVyzY/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/TwdwpiIdnmW0XUFx8oqlh1XVyzY/1/da"><img src="http://feedads.g.doubleclick.net/~a/TwdwpiIdnmW0XUFx8oqlh1XVyzY/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/V5VFlDmV74Y" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/w3c-releases-unicorn-an-all-in-one-validator/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/w3c-releases-unicorn-an-all-in-one-validator/</feedburner:origLink></item>
		<item>
		<title>PHP 4 and MySQL 4 End of Life Announcement</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/I1njvdIGd3A/</link>
		<comments>http://w3c-compliant.com/2010/07/php-4-and-mysql-4-end-of-life-announcement/#comments</comments>
		<pubDate>Fri, 23 Jul 2010 19:01:46 +0000</pubDate>
		<dc:creator>Mark Jaquith</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Hosting]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false">http://wordpress.org/news/?p=1447</guid>
		<description><![CDATA[Our approach with WordPress has always been to make it run on common server configurations. We want users to have flexibility when choosing a host for their precious content. Because of this strategy, WordPress runs pretty much anywhere. Web hosting platforms, however, change over time, and we occasionally are able to reevaluate some of the [...]]]></description>
			<content:encoded><![CDATA[<p>Our approach with WordPress has always been to make it run on common server configurations. We want users to have flexibility when choosing a host for their precious content. Because of this strategy, WordPress runs pretty much anywhere. Web hosting platforms, however, change over time, and we occasionally are able to reevaluate some of the requirements for running WordPress. Now is one of those times. You probably guessed it from the title &#8212; we&#8217;re finally ready to announce the end of support for PHP 4 and MySQL 4!</p>
<p>First up, the announcement that developers really care about. WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4.</p>
<p>For WordPress 3.2, due in the first half of 2011, we will be raising the minimum required PHP version to 5.2. Why 5.2? Because that&#8217;s what the vast majority of WordPress users are using, and it offers substantial improvements over earlier PHP 5 releases. It is also the minimum PHP version that the <a href="http://drupal.org/">Drupal</a> and <a href="http://www.joomla.org/">Joomla</a> projects will be supporting in their next versions, both due out this year.</p>
<p>The numbers are now, <em>finally</em>, strongly in favor of this move. Only around 11 percent of WordPress installs are running on a PHP version below 5.2. Many of them are on hosts who support PHP 5.2 &#8212; users merely need to change a setting in their hosting control panel to activate it. We believe that percentage will only go down over the rest of the year as hosting providers realize that to support the newest versions of WordPress (or Drupal, or Joomla), they&#8217;re going to have to pull the trigger.</p>
<p>In less exciting news, we are also going to be dropping support for MySQL 4 after WordPress 3.1. Fewer than 6 percent of WordPress users are running MySQL 4. The new required MySQL version for WordPress 3.2 will be 5.0.15.</p>
<p>WordPress users will not be able to upgrade to WordPress 3.2 if their hosting environment does not meet these requirements (the built-in updater will prevent it). In order to determine which versions your host provides, we&#8217;ve created the <a href="http://wordpress.org/extend/plugins/health-check/">Health Check plugin</a>. You can download it manually, or use this <a href="http://coveredwebservices.com/wp-plugin-install/?plugin=health-check">handy plugin installation</a> tool I whipped up. Right now, Health Check will only tell you if you&#8217;re ready for WordPress 3.2. In a future release it will provide all sorts of useful information about your server and your WordPress install, so hang on to it!</p>
<p>In summary: WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4 and MySQL 4. WordPress 3.2, due in the first half of 2011, will require PHP 5.2 or higher, and MySQL 5.0.15 or higher. <a href="http://coveredwebservices.com/wp-plugin-install/?plugin=health-check">Install the Health Check plugin</a> to see if you&#8217;re ready!</p>

<p><a href="http://feedads.g.doubleclick.net/~a/2nzeD_eMJ-suZ7McYeJriTGL6JQ/0/da"><img src="http://feedads.g.doubleclick.net/~a/2nzeD_eMJ-suZ7McYeJriTGL6JQ/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/2nzeD_eMJ-suZ7McYeJriTGL6JQ/1/da"><img src="http://feedads.g.doubleclick.net/~a/2nzeD_eMJ-suZ7McYeJriTGL6JQ/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/I1njvdIGd3A" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/php-4-and-mysql-4-end-of-life-announcement/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/php-4-and-mysql-4-end-of-life-announcement/</feedburner:origLink></item>
		<item>
		<title>The Multilingual Web – Where Are We? Find out at the W3C Workshop</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/9pHYS71x7Kc/</link>
		<comments>http://w3c-compliant.com/2010/07/the-multilingual-web-where-are-we-find-out-at-the-w3c-workshop/#comments</comments>
		<pubDate>Thu, 22 Jul 2010 20:45:06 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Home Page Stories]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Design and Applications]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[W3C is organizing a Workshop: The Multilingual Web - Where Are We?, to take place 26-27 October 2010 in Madrid, Spain. Workshop participants will survey and introduce currently available best practices and standards that help content creators, localizers, language...]]></description>
			<content:encoded><![CDATA[
        
        <p>
<a class="imageLink" href="http://www.w3.org/International/multilingualweb/madrid/cfp">
<img width="98" height="98" src="http://www.w3.org/International/multilingualweb/madrid/mw3-small.png" alt="Multilingual Web logo"/>
</a>
W3C is organizing a Workshop: 
<a href="http://www.w3.org/International/multilingualweb/madrid/cfp">The Multilingual Web - Where Are We?</a>, to take place 26-27 October 2010 in Madrid, Spain. Workshop participants will  survey and introduce currently available best practices and standards that help content creators, localizers, language technology developers, browser makers, and others meet the challenges of the multilingual Web. The Workshop also provides opportunities for networking that span the various communities involved in enabling the multilingual Web. <a href="http://www.w3.org/International/multilingualweb/madrid/cfp#participation">Participation</a> is free and open to anyone. However, space is limited and participants must send an <a href="http://www.w3.org/International/multilingualweb/madrid/cfp#eoi">expression of interest</a> to the program committee. People wishing to speak should also submit a presentation outline as soon as possible.
</p>
<p>
This is the first of four Workshops being planned by W3C over the next two years as part of the <a href="http://www.multilingualweb.eu/">MultilingualWeb</a> European Project. The first Workshop is hosted by the Universidad Politécnica de Madrid. For more information, see the <a href="http://www.w3.org/International/multilingualweb/madrid/cfp">call for participation</a>. Learn more about W3C's <a href="http://www.w3.org/International/">Internationalization Activity</a>.</p>
    
<p><a href="http://feedads.g.doubleclick.net/~a/fB5394C8fRidezZYlhg48WPO3kg/0/da"><img src="http://feedads.g.doubleclick.net/~a/fB5394C8fRidezZYlhg48WPO3kg/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/fB5394C8fRidezZYlhg48WPO3kg/1/da"><img src="http://feedads.g.doubleclick.net/~a/fB5394C8fRidezZYlhg48WPO3kg/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/9pHYS71x7Kc" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/the-multilingual-web-where-are-we-find-out-at-the-w3c-workshop/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/the-multilingual-web-where-are-we-find-out-at-the-w3c-workshop/</feedburner:origLink></item>
		<item>
		<title>HTML Media Capture Draft Published</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/kDtP1Z5DjOw/</link>
		<comments>http://w3c-compliant.com/2010/07/html-media-capture-draft-published/#comments</comments>
		<pubDate>Tue, 20 Jul 2010 16:50:47 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Browsers and Authoring Tools]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Publication]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Design and Applications]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[The Device APIs and Policy Working Group has published a Working Draft of HTML Media Capture. This specification defines HTML form enhancements that provide access to the audio, image and video capture capabilities of the device. The title of the...]]></description>
			<content:encoded><![CDATA[
        
        <p>The <a href="http://www.w3.org/2009/dap/">Device APIs and Policy Working Group</a> has published a Working Draft of <a href="http://www.w3.org/TR/2010/WD-html-media-capture-20100720/">HTML Media Capture</a>. This specification defines HTML form enhancements that provide access to the audio, image and video capture capabilities of the device. The title of the specification changed in this draft (from "The Capture API"). Learn more about the <a href="http://www.w3.org/2007/uwa/">Ubiquitous Web Applications Activity</a>.</p>
    
<p><a href="http://feedads.g.doubleclick.net/~a/jkgtZXJly9V-8cjrDclHTpIIy88/0/da"><img src="http://feedads.g.doubleclick.net/~a/jkgtZXJly9V-8cjrDclHTpIIy88/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/jkgtZXJly9V-8cjrDclHTpIIy88/1/da"><img src="http://feedads.g.doubleclick.net/~a/jkgtZXJly9V-8cjrDclHTpIIy88/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/kDtP1Z5DjOw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/html-media-capture-draft-published/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/html-media-capture-draft-published/</feedburner:origLink></item>
		<item>
		<title>Last Call: Web Services SOAP Assertions (WS-SOAPAssertions)</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/49qqr_GuWeo/</link>
		<comments>http://w3c-compliant.com/2010/07/last-call-web-services-soap-assertions-ws-soapassertions/#comments</comments>
		<pubDate>Tue, 13 Jul 2010 19:55:57 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Publication]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[Web of Services]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[The Web Services Resource Access Working Group has published a Last Call Working Draft of Web Services SOAP Assertions (WS-SOAPAssertions). This specification defines two WS-Policy assertions that can be used to advertise the requirement to use a certain version of...]]></description>
			<content:encoded><![CDATA[
        
        <p>The <a href="http://www.w3.org/2002/ws/ra/">Web Services Resource Access Working Group</a> has published a Last Call Working Draft of <a href="http://www.w3.org/TR/2010/WD-ws-soap-assertions-20100713/">Web Services SOAP Assertions (WS-SOAPAssertions)</a>. This specification defines two WS-Policy assertions that can be used to advertise the requirement to use a certain version of SOAP in message exchanges. Comments are welcome through 27 August. The group also published <a href="http://www.w3.org/TR/2010/NOTE-ws-resource-transfer-20100713/">Web Services Resource Transfer (WS-RT)</a> as a Note today. That specification defines extensions to WS-Transfer primarily to provide fragment-based access to resources. Learn more about the <a href="http://www.w3.org/2002/ws/">Web Services Activity</a>.</p>
    
<p><a href="http://feedads.g.doubleclick.net/~a/50e5-BGumYtaV3Yi-9mp1mpIbyA/0/da"><img src="http://feedads.g.doubleclick.net/~a/50e5-BGumYtaV3Yi-9mp1mpIbyA/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/50e5-BGumYtaV3Yi-9mp1mpIbyA/1/da"><img src="http://feedads.g.doubleclick.net/~a/50e5-BGumYtaV3Yi-9mp1mpIbyA/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/49qqr_GuWeo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/last-call-web-services-soap-assertions-ws-soapassertions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/last-call-web-services-soap-assertions-ws-soapassertions/</feedburner:origLink></item>
		<item>
		<title>Last Call: Mobile Web Application Best Practices</title>
		<link>http://feedproxy.google.com/~r/W3cCompliant/~3/76JdnHRN1iU/</link>
		<comments>http://w3c-compliant.com/2010/07/last-call-mobile-web-application-best-practices/#comments</comments>
		<pubDate>Tue, 13 Jul 2010 19:46:56 +0000</pubDate>
		<dc:creator>W3C Staff</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[Publication]]></category>
		<category><![CDATA[Search Engine Optimization]]></category>
		<category><![CDATA[search engines]]></category>
		<category><![CDATA[SEO]]></category>
		<category><![CDATA[valid code]]></category>
		<category><![CDATA[valid CSS]]></category>
		<category><![CDATA[valid XHTML]]></category>
		<category><![CDATA[W3C]]></category>
		<category><![CDATA[W3C compliant]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Design and Applications]]></category>
		<category><![CDATA[Web Designer]]></category>
		<category><![CDATA[Web of Devices]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[WordPress Development]]></category>
		<category><![CDATA[XHTML]]></category>

		<guid isPermaLink="false" />
		<description><![CDATA[The Mobile Web Best Practices Working Group has published a Last Call Working Draft of Mobile Web Application Best Practices. The goal of this document is to aid the development of rich and dynamic mobile Web applications. It collects the...]]></description>
			<content:encoded><![CDATA[
        
        <p>The <a href="http://www.w3.org/2005/MWI/BPWG/">Mobile Web Best Practices Working Group</a> has published a Last Call Working Draft of <a href="http://www.w3.org/TR/2010/WD-mwabp-20100713/">Mobile Web Application Best Practices</a>. The goal of this document is to aid the development of rich and dynamic mobile Web applications. It collects the most relevant engineering practices, promoting those that enable a better user experience and warning against those that are considered harmful. The Mobile Web Best Practices Working Group does not expect more substantive changes at this point and expects to be able to transition directly to Proposed Recommendation at the end of the Last Call review period. Last call comments welcome before Comments are welcome through 06 August 2010. Learn more about the <a href="http://www.w3.org/Mobile/">Mobile Web Initiative Activity</a>.</p>
    
<p><a href="http://feedads.g.doubleclick.net/~a/AdyANLsVIGnfeNlpGatSC3SwgsM/0/da"><img src="http://feedads.g.doubleclick.net/~a/AdyANLsVIGnfeNlpGatSC3SwgsM/0/di" border="0" ismap="true"></img></a><br/>
<a href="http://feedads.g.doubleclick.net/~a/AdyANLsVIGnfeNlpGatSC3SwgsM/1/da"><img src="http://feedads.g.doubleclick.net/~a/AdyANLsVIGnfeNlpGatSC3SwgsM/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/W3cCompliant/~4/76JdnHRN1iU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://w3c-compliant.com/2010/07/last-call-mobile-web-application-best-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://w3c-compliant.com/2010/07/last-call-mobile-web-application-best-practices/</feedburner:origLink></item>
	</channel>
</rss>
