<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Reacties op: 2d barcodes, een fysieke hyperlink hoort gewoon een URL te zijn</title>
	<link>http://www.marcathing.com/2007/06/07/2d-barcodes-een-fysieke-hyperlink-hoort-gewoon-een-url-te-zijn/</link>
	<description>"new and improved"</description>
	<pubDate>Fri, 05 Dec 2008 10:06:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>door: Marc Fonteijn</title>
		<link>http://www.marcathing.com/2007/06/07/2d-barcodes-een-fysieke-hyperlink-hoort-gewoon-een-url-te-zijn/#comment-810</link>
		<pubDate>Sat, 09 Jun 2007 10:32:02 +0000</pubDate>
		<guid>http://www.marcathing.com/2007/06/07/2d-barcodes-een-fysieke-hyperlink-hoort-gewoon-een-url-te-zijn/#comment-810</guid>
					<description>Hi Roger, thanks for you quick response and bravery to respond on a dutch article.

I'll translate the article to english:
&lt;em&gt;The bottom line is that 2d barcode are a &lt;strong&gt;simple tool&lt;/strong&gt; so that you don't have to type URL on your phone. Nothing more and nothing less.&lt;/em&gt;

There is no benefit whatsoever for the end-users in to encoding shortcode numbers. Just encode URL's. Wouldn't it be insane to print some number on your businesscard instead of http://www.kaywa.com ... ? 2d barcodes are just an tool to input http://www.kaywa.com on your phone.

I have a very strong opinion about companies who (ab)use the openness of QR Codes and create a confusing proprietary system. But we had this discussion on Tommies blog a while ago.

In my view the only way to archive standardization is to &lt;strong&gt;practice good practice yourself&lt;/strong&gt;. I can believe the temptation is big but the need for standardization is even bigger.</description>
		<content:encoded><![CDATA[<p>Hi Roger, thanks for you quick response and bravery to respond on a dutch article.</p>
<p>I&#8217;ll translate the article to english:<br />
<em>The bottom line is that 2d barcode are a <strong>simple tool</strong> so that you don&#8217;t have to type URL on your phone. Nothing more and nothing less.</em></p>
<p>There is no benefit whatsoever for the end-users in to encoding shortcode numbers. Just encode URL&#8217;s. Wouldn&#8217;t it be insane to print some number on your businesscard instead of <a href="http://www.kaywa.com" rel="nofollow">http://www.kaywa.com</a> &#8230; ? 2d barcodes are just an tool to input <a href="http://www.kaywa.com" rel="nofollow">http://www.kaywa.com</a> on your phone.</p>
<p>I have a very strong opinion about companies who (ab)use the openness of QR Codes and create a confusing proprietary system. But we had this discussion on Tommies blog a while ago.</p>
<p>In my view the only way to archive standardization is to <strong>practice good practice yourself</strong>. I can believe the temptation is big but the need for standardization is even bigger.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>door: Roger</title>
		<link>http://www.marcathing.com/2007/06/07/2d-barcodes-een-fysieke-hyperlink-hoort-gewoon-een-url-te-zijn/#comment-804</link>
		<pubDate>Thu, 07 Jun 2007 22:56:11 +0000</pubDate>
		<guid>http://www.marcathing.com/2007/06/07/2d-barcodes-een-fysieke-hyperlink-hoort-gewoon-een-url-te-zijn/#comment-804</guid>
					<description>Hi,
My dutch is very poor so I better try with english.
In fact there is a solution which does not make an open code proprietory.

First we also used (and still use) short codes, which are a proprietory solution to an open code. But then - when the Nokia barcode readers arrived - we changed more an more to the Short Code URL solution. Feed2Mobile is an example of this. You can read with the Kaywa Reader but also with the Nokia Barcode Reader.

So if size doesn't matter (short codes are much smaller) we now use Shortcode URL's instead. And I think that's the evolution every barcode reader solution should go.

First - support one of the two ISO-Standards - at least.
Second - offer the (Shortcode) URL possibility.</description>
		<content:encoded><![CDATA[<p>Hi,<br />
My dutch is very poor so I better try with english.<br />
In fact there is a solution which does not make an open code proprietory.</p>
<p>First we also used (and still use) short codes, which are a proprietory solution to an open code. But then - when the Nokia barcode readers arrived - we changed more an more to the Short Code URL solution. Feed2Mobile is an example of this. You can read with the Kaywa Reader but also with the Nokia Barcode Reader.</p>
<p>So if size doesn&#8217;t matter (short codes are much smaller) we now use Shortcode URL&#8217;s instead. And I think that&#8217;s the evolution every barcode reader solution should go.</p>
<p>First - support one of the two ISO-Standards - at least.<br />
Second - offer the (Shortcode) URL possibility.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
