<?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"
	>
<channel>
	<title>Comments on: Will That Be Adaptation Or Alternation?</title>
	<atom:link href="http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm</link>
	<description>The Mobile Web From A Desktop Perspective</description>
	<pubDate>Sat, 06 Sep 2008 18:18:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: admin</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9834</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 15 Apr 2007 23:17:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9834</guid>
		<description>You're right, Andy, re adaptation on this site: there's certainly no alternation here.  However  I do say this is written from a desktop perspective.  I'm sure I could do much better if I created a mobile version.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, Andy, re adaptation on this site: there&#8217;s certainly no alternation here.  However  I do say this is written from a desktop perspective.  I&#8217;m sure I could do much better if I created a mobile version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Moore</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9729</link>
		<dc:creator>Andy Moore</dc:creator>
		<pubDate>Sun, 15 Apr 2007 01:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9729</guid>
		<description>Does it matter how we do it as long as we're not punishing the user with a poor interface because they're on a mobile.

My understanding of thematic consistency is to show different formats of content on the same urls or to redirect through to the version suited for mobile. Nice in principle, not always workable in practice, sometimes separate sites are the best option.

WALL is an awesome tool, I've used &lt;a&gt; for some time on a couple of sites and as far as ready.mobi testing goes one scores 4.86 which is a lot higher than average though it fails 4 tests at the w3 mobile validator. 

Where's the adaptation on this site, alternation or whatever you want to call it? My user agent is a Nokia N7's and I see the same as FireFox.

Is it just me or is that just a little ironic?

&lt;a href="http://www.andymoore.info/wordpress-mobile-plugin/" rel="nofollow"&gt;WordPress Mobile Plugin&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Does it matter how we do it as long as we&#8217;re not punishing the user with a poor interface because they&#8217;re on a mobile.</p>
<p>My understanding of thematic consistency is to show different formats of content on the same urls or to redirect through to the version suited for mobile. Nice in principle, not always workable in practice, sometimes separate sites are the best option.</p>
<p>WALL is an awesome tool, I&#8217;ve used <a> for some time on a couple of sites and as far as ready.mobi testing goes one scores 4.86 which is a lot higher than average though it fails 4 tests at the w3 mobile validator. </p>
<p>Where&#8217;s the adaptation on this site, alternation or whatever you want to call it? My user agent is a Nokia N7&#8217;s and I see the same as FireFox.</p>
<p>Is it just me or is that just a little ironic?</p>
<p></a><a href="http://www.andymoore.info/wordpress-mobile-plugin/">WordPress Mobile Plugin</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Practicality versus Purity - Alternation versus Adaptation &#124; StayGoLinks</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9608</link>
		<dc:creator>Practicality versus Purity - Alternation versus Adaptation &#124; StayGoLinks</dc:creator>
		<pubDate>Fri, 13 Apr 2007 19:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9608</guid>
		<description>[...] Related: Will That Be Adaptation Or Alternation? [...]</description>
		<content:encoded><![CDATA[<p>[...] Related: Will That Be Adaptation Or Alternation? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Working at Home on the Internet</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9558</link>
		<dc:creator>Working at Home on the Internet</dc:creator>
		<pubDate>Fri, 13 Apr 2007 11:34:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9558</guid>
		<description>[...] Barry Welford presents Will That Be Adaptation Or Alternation? posted at StayGoLinks, saying, &#8220;Making your website viewable in mobile devices such as cellphones is a mighty challenge if you try to follow the W3C&#8217;s &#8216;One Web&#8217; Adaptation process. Better and simpler is to design specific cellphone web pages: that&#8217;s called Alternation.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] Barry Welford presents Will That Be Adaptation Or Alternation? posted at StayGoLinks, saying, &#8220;Making your website viewable in mobile devices such as cellphones is a mighty challenge if you try to follow the W3C&#8217;s &#8216;One Web&#8217; Adaptation process. Better and simpler is to design specific cellphone web pages: that&#8217;s called Alternation.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Smith</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9457</link>
		<dc:creator>Kevin Smith</dc:creator>
		<pubDate>Thu, 12 Apr 2007 15:01:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9457</guid>
		<description>Nothing worse than feature creep :) 

In DIAL you make the features yourself (i.e., the expressions which are evaluated to determine if content is delivered or not). So it's as creepy as the implementor wants it to be, or it can be nice and light too.</description>
		<content:encoded><![CDATA[<p>Nothing worse than feature creep <img src='http://www.staygolinks.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>In DIAL you make the features yourself (i.e., the expressions which are evaluated to determine if content is delivered or not). So it&#8217;s as creepy as the implementor wants it to be, or it can be nice and light too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9452</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 12 Apr 2007 14:44:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9452</guid>
		<description>That certainly will make DIAL most impressive, Kevin.  The only concern I might have is that &lt;a href="http://en.wikipedia.org/wiki/Feature_creep" rel=" nofollow"  rel="nofollow"&gt;Feature Creep&lt;/a&gt; may mean you will never get there.  Sometimes it's better to run with what can be made to work fairly quickly.</description>
		<content:encoded><![CDATA[<p>That certainly will make DIAL most impressive, Kevin.  The only concern I might have is that <a href="http://en.wikipedia.org/wiki/Feature_creep" rel=" "  rel="nofollow">Feature Creep</a> may mean you will never get there.  Sometimes it&#8217;s better to run with what can be made to work fairly quickly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Smith</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9443</link>
		<dc:creator>Kevin Smith</dc:creator>
		<pubDate>Thu, 12 Apr 2007 13:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9443</guid>
		<description>Whilst DIAL could (in theory) meet some of the use cases provided by WALL, the goals of these technologies are not the same. 

DIAL aims to allow the author to declare under which delivery contexts a given block of content/markup is rendered. Delivery context covers more than static device capabilities and wireless devices: the decision to include content can be based on user state (pre-pay or post-pay, age, preferences), device state (current battery life, screen orientation, ambient light, current connection speed) as well. Both fixed and wireless devices are in scope. 

The expressions of interest so far in DIAL have included intranets (single authoring for PC and mobile use) and mobile portals (where age suitability checks, current 3G or GPRS connection speed and roaming state etc. unfortunately add complexity beyond device capability). As Luca says, it's theory so far, and we are working on evolving the specification and test implementation.

Cheers,
Kevin</description>
		<content:encoded><![CDATA[<p>Whilst DIAL could (in theory) meet some of the use cases provided by WALL, the goals of these technologies are not the same. </p>
<p>DIAL aims to allow the author to declare under which delivery contexts a given block of content/markup is rendered. Delivery context covers more than static device capabilities and wireless devices: the decision to include content can be based on user state (pre-pay or post-pay, age, preferences), device state (current battery life, screen orientation, ambient light, current connection speed) as well. Both fixed and wireless devices are in scope. </p>
<p>The expressions of interest so far in DIAL have included intranets (single authoring for PC and mobile use) and mobile portals (where age suitability checks, current 3G or GPRS connection speed and roaming state etc. unfortunately add complexity beyond device capability). As Luca says, it&#8217;s theory so far, and we are working on evolving the specification and test implementation.</p>
<p>Cheers,<br />
Kevin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9430</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 12 Apr 2007 09:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9430</guid>
		<description>Thanks, Luca.  Link is fixed.</description>
		<content:encoded><![CDATA[<p>Thanks, Luca.  Link is fixed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luca Passani</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9419</link>
		<dc:creator>Luca Passani</dc:creator>
		<pubDate>Thu, 12 Apr 2007 08:51:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9419</guid>
		<description>Brian Fling did a good job with that document (BTW, you may want to fix the link above. It's broken). One of the shortcomings is that it is based on W3C MWIBP. Admittedly, the dotMobi guys are smart enough to give more importance to reasonable practices and less (much less) the BP practices that happen to be wrong or useless, so the Design Guide is overall very good.
For the record, one of the BP practices I dislike the most is the one which forbids the usage of tables. Tables are a devlopers best chance to place a picture and text/links side by side. CSS cannot deliver this, while tables can deliver this effect pretty consistently across devices.

Luca</description>
		<content:encoded><![CDATA[<p>Brian Fling did a good job with that document (BTW, you may want to fix the link above. It&#8217;s broken). One of the shortcomings is that it is based on W3C MWIBP. Admittedly, the dotMobi guys are smart enough to give more importance to reasonable practices and less (much less) the BP practices that happen to be wrong or useless, so the Design Guide is overall very good.<br />
For the record, one of the BP practices I dislike the most is the one which forbids the usage of tables. Tables are a devlopers best chance to place a picture and text/links side by side. CSS cannot deliver this, while tables can deliver this effect pretty consistently across devices.</p>
<p>Luca</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9380</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 11 Apr 2007 23:31:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.staygolinks.com/will-that-be-adaptation-or-alternation.htm#comment-9380</guid>
		<description>Thank you, Luca, for that reference.  Perhaps I could add to your Simple, Fast and Cheap criteria, the objective that every device should also not merely receive a viewable content but rather receive a content that delivers a &lt;strong&gt;satisfactory user experience&lt;/strong&gt;.  I do not believe that can always be achieved by taking a single content package and then treating it to make it acceptable to the target devices.

I am not sure that I like that Multiple Authoring concept, but at least it conveys the sense that different devices may require a design process specific to that device in order to deliver a satisfactory user experience.  That I think is what is implied by such efforts as the &lt;a href="http://pc.dev.mobi/files/dotMobi%20Mobile%20Web%20Developers%20Guide.pdf" rel="nofollow"&gt;Design Guide specifically for dotMobi websites&lt;/a&gt; (PDF).</description>
		<content:encoded><![CDATA[<p>Thank you, Luca, for that reference.  Perhaps I could add to your Simple, Fast and Cheap criteria, the objective that every device should also not merely receive a viewable content but rather receive a content that delivers a <strong>satisfactory user experience</strong>.  I do not believe that can always be achieved by taking a single content package and then treating it to make it acceptable to the target devices.</p>
<p>I am not sure that I like that Multiple Authoring concept, but at least it conveys the sense that different devices may require a design process specific to that device in order to deliver a satisfactory user experience.  That I think is what is implied by such efforts as the <a href="http://pc.dev.mobi/files/dotMobi%20Mobile%20Web%20Developers%20Guide.pdf">Design Guide specifically for dotMobi websites</a> (PDF).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
