<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: One web and universal access: a bridge too far?</title>
	<atom:link href="http://scrollmagazine.com/number-2/universal-access/feed" rel="self" type="application/rss+xml" />
	<link>http://scrollmagazine.com/number-2/universal-access</link>
	<description>Founded by long time web industry figures Maxine Sherrin and John Allsopp in 2008, Scroll is a print, PDF and online magazine for web professionals.</description>
	<lastBuildDate>Sun, 25 Jul 2010 21:05:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dwight Vietzke</title>
		<link>http://scrollmagazine.com/number-2/universal-access/comment-page-1#comment-26622</link>
		<dc:creator>Dwight Vietzke</dc:creator>
		<pubDate>Sun, 16 May 2010 19:34:23 +0000</pubDate>
		<guid isPermaLink="false">http://scrollmagazine.com/?p=458#comment-26622</guid>
		<description>Great article. I couldn&#039;t agree more.

An interesting bi-product of my own development work has been the realization that content must be stored in a database and served to specific devices and not just served from simple pages. Some sort of server scripting or programming is necessary to negotiate the current field of browsers and devices trying to access a website, for many reasons.

If browsers strictly followed some sort of web standard, it might be possible to create a page driven website which could adapt to different devices via media negotiation, view-port specification, etc. Yet this is improbable given the current trend for browsers (especially IE) to still do their own thing. So a &#039;one web&#039; dynamic website is a worthwhile goal, but does require significant effort to create a workable solution.

The good news is, the latest smartphones and iPhone are now able to process css, javascript and xhtml (when being xhtml MP compliant) reasonably well. So there actually may be future for the &#039;one web&#039; website.</description>
		<content:encoded><![CDATA[<p>Great article. I couldn’t agree more.</p>
<p>An interesting bi-product of my own development work has been the realization that content must be stored in a database and served to specific devices and not just served from simple pages. Some sort of server scripting or programming is necessary to negotiate the current field of browsers and devices trying to access a website, for many reasons.</p>
<p>If browsers strictly followed some sort of web standard, it might be possible to create a page driven website which could adapt to different devices via media negotiation, view-port specification, etc. Yet this is improbable given the current trend for browsers (especially IE) to still do their own thing. So a ‘one web’ dynamic website is a worthwhile goal, but does require significant effort to create a workable solution.</p>
<p>The good news is, the latest smartphones and iPhone are now able to process css, javascript and xhtml (when being xhtml MP compliant) reasonably well. So there actually may be future for the ‘one web’ website.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced) (user agent is rejected)
Database Caching 1/6 queries in 0.023 seconds using disk
Object Caching 380/388 objects using disk

Served from: scrollmagazine.com @ 2010-09-07 18:11:42 -->