<?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/"
	
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Moseycode, a new chapter in mobile barcoding</title>
	<atom:link href="http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/feed/" rel="self" type="application/rss+xml" />
	<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/</link>
	<description>International technology news, business &#38; culture</description>
	<lastBuildDate>Wed, 15 Feb 2012 05:25:16 +0100</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: John</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359681</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 13 Jul 2008 11:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359681</guid>
		<description>There&#039;s new moseycode reader called iCode Reader found on this site: http://blog.bryton.hu
It works on iPhone!</description>
		<content:encoded><![CDATA[<p>There&#8217;s new moseycode reader called iCode Reader found on this site: <a href="http://blog.bryton.hu" rel="nofollow">http://blog.bryton.hu</a><br />
It works on iPhone!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Whitney</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359680</link>
		<dc:creator>Robert Whitney</dc:creator>
		<pubDate>Tue, 19 Feb 2008 04:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359680</guid>
		<description>haha.  I&#039;m all pipe dreams...</description>
		<content:encoded><![CDATA[<p>haha.  I&#8217;m all pipe dreams&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Collins</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359679</link>
		<dc:creator>Dean Collins</dc:creator>
		<pubDate>Mon, 18 Feb 2008 23:34:41 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359679</guid>
		<description>then the answer is good-luck.

QR is the only real open standard out there - if you want to reccomend this go right ahead thats the great thing about open standards.

cheers,
Dean</description>
		<content:encoded><![CDATA[<p>then the answer is good-luck.</p>
<p>QR is the only real open standard out there &#8211; if you want to reccomend this go right ahead thats the great thing about open standards.</p>
<p>cheers,<br />
Dean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Whitney</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359678</link>
		<dc:creator>Robert Whitney</dc:creator>
		<pubDate>Mon, 18 Feb 2008 23:32:14 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359678</guid>
		<description>I mean a 2D barcode forum.  Is semacode still open?  I am proposing the intervention of the open source community to sway the growing number of commercial developers from exercising significant control over the way in which this stuff can grow/ the market.  A movement of sorts.</description>
		<content:encoded><![CDATA[<p>I mean a 2D barcode forum.  Is semacode still open?  I am proposing the intervention of the open source community to sway the growing number of commercial developers from exercising significant control over the way in which this stuff can grow/ the market.  A movement of sorts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Collins</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359677</link>
		<dc:creator>Dean Collins</dc:creator>
		<pubDate>Mon, 18 Feb 2008 22:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359677</guid>
		<description>do you mean a forum for moseycode or for all 2d barcodes.

if you mean moseycode - cool.

if you mean all 2d codes...forget about it, there are numerous groups trying to work things out and it&#039;s just not happening.

the difference is moseycode and wr are open standards...the rest are commercial and trying to enforce patents.


Cheers,
Dean Collins
www.Cognation.net</description>
		<content:encoded><![CDATA[<p>do you mean a forum for moseycode or for all 2d barcodes.</p>
<p>if you mean moseycode &#8211; cool.</p>
<p>if you mean all 2d codes&#8230;forget about it, there are numerous groups trying to work things out and it&#8217;s just not happening.</p>
<p>the difference is moseycode and wr are open standards&#8230;the rest are commercial and trying to enforce patents.</p>
<p>Cheers,<br />
Dean Collins<br />
<a href="http://www.Cognation.net" rel="nofollow">http://www.Cognation.net</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert Whitney</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359676</link>
		<dc:creator>Robert Whitney</dc:creator>
		<pubDate>Mon, 18 Feb 2008 22:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359676</guid>
		<description>I see a need to start talking about establishing a forum out of which the standardization of these semantics can be created.  At the very least something needs to be created which will allow for a more open dialogue can take place than what is currently going on right now (a wiki even?).  The implications are amazing, but the implementations right now are very vast and sometimes confusing.  I think it&#039;s good to let these things grow as they are, but these &quot;camps&quot; that are forming could all benefit from  an open discussion. I propose the formation of a standard set of resources for everyone from developers, to implementation, to the end consumer would be extremely beneficial for all.  This stuff is very exciting already, but getting some heads together could unlock even more potential than we currently conceive.  I feel this should be an obvious step.</description>
		<content:encoded><![CDATA[<p>I see a need to start talking about establishing a forum out of which the standardization of these semantics can be created.  At the very least something needs to be created which will allow for a more open dialogue can take place than what is currently going on right now (a wiki even?).  The implications are amazing, but the implementations right now are very vast and sometimes confusing.  I think it&#8217;s good to let these things grow as they are, but these &#8220;camps&#8221; that are forming could all benefit from  an open discussion. I propose the formation of a standard set of resources for everyone from developers, to implementation, to the end consumer would be extremely beneficial for all.  This stuff is very exciting already, but getting some heads together could unlock even more potential than we currently conceive.  I feel this should be an obvious step.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Petter</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359675</link>
		<dc:creator>Petter</dc:creator>
		<pubDate>Wed, 16 Jan 2008 04:13:26 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359675</guid>
		<description>Hi Peter,
I had the exact same user experience as you did. For each type of barcode I had to find the corresponding barcode reader. Often it wasn&#039;t available for my specific phone model and when it was I had to figure out how to install it on my phone. It&#039;s quite unlikely that the average user will make the effort necessary to install such applications.
That&#039;s the reason ZapLinks (www.zaplinks.com) was created. ZapLinks is a service which allows users to create and track images for free (for personal use). Once created, users simply take a picture of the ZapLinks image and send it to: go@zaplinks.com (using MMS or E-mail)
The colored circular images are decoded on a server and a link to the corresponding content is returned to the requester. As such, ZapLinks are supported on any mobile phone with a camera and an internet connection &quot;right off the bat&quot;, including the iPhone.

Thanks, Petter.</description>
		<content:encoded><![CDATA[<p>Hi Peter,<br />
I had the exact same user experience as you did. For each type of barcode I had to find the corresponding barcode reader. Often it wasn&#8217;t available for my specific phone model and when it was I had to figure out how to install it on my phone. It&#8217;s quite unlikely that the average user will make the effort necessary to install such applications.<br />
That&#8217;s the reason ZapLinks (www.zaplinks.com) was created. ZapLinks is a service which allows users to create and track images for free (for personal use). Once created, users simply take a picture of the ZapLinks image and send it to: <a href="mailto:go@zaplinks.com">go@zaplinks.com</a> (using MMS or E-mail)<br />
The colored circular images are decoded on a server and a link to the corresponding content is returned to the requester. As such, ZapLinks are supported on any mobile phone with a camera and an internet connection &#8220;right off the bat&#8221;, including the iPhone.</p>
<p>Thanks, Petter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Good Old Trend &#187; Blog Archive &#187; Enter, Moseycode</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359674</link>
		<dc:creator>Good Old Trend &#187; Blog Archive &#187; Enter, Moseycode</dc:creator>
		<pubDate>Tue, 08 Jan 2008 15:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359674</guid>
		<description>[...] An interesting post from the newly launched blog The Next Web: A Moseycode holds much more information than any other mobile barcode. When photographing a Moseycode, your mobile telephone will reveal information like 3D pictures, locations and even allows you to add your own media to the repository/portal you’ve found. The content of the code isn’t static. The Moseycode barcoding system is specifically developed for Android. [...]</description>
		<content:encoded><![CDATA[<p>[...] An interesting post from the newly launched blog The Next Web: A Moseycode holds much more information than any other mobile barcode. When photographing a Moseycode, your mobile telephone will reveal information like 3D pictures, locations and even allows you to add your own media to the repository/portal you’ve found. The content of the code isn’t static. The Moseycode barcoding system is specifically developed for Android. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cloudy Thinking &#187; Blog Archive &#187; Tom Gibara&#8217;s Moseycode: a new mobile barcode, supports a z-axis</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359673</link>
		<dc:creator>Cloudy Thinking &#187; Blog Archive &#187; Tom Gibara&#8217;s Moseycode: a new mobile barcode, supports a z-axis</dc:creator>
		<pubDate>Sun, 06 Jan 2008 18:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359673</guid>
		<description>[...] Peter Evers writes about Tom Gibara&#8217;s Moseycode a new mobile barcode that supports a z-axis. Watch the video (which relies on Google&#8217;s Android&#8230;) [...]</description>
		<content:encoded><![CDATA[<p>[...] Peter Evers writes about Tom Gibara&#8217;s Moseycode a new mobile barcode that supports a z-axis. Watch the video (which relies on Google&#8217;s Android&#8230;) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Gibara</title>
		<link>http://thenextweb.com/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359672</link>
		<dc:creator>Tom Gibara</dc:creator>
		<pubDate>Sun, 06 Jan 2008 01:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://thenextweb.org/2008/01/05/moseycode-a-new-chapter-in-mobile-barcoding/#comment-359672</guid>
		<description>First I&#039;d like to say thank you for taking the time to write about Moseycode. I&#039;d like to respond to some of your comments and to those of Dean.

On the point of barcode standardization: If a barcode exists that is entirely free (in the sense of being unfettered by intellectual property), well designed (in an engineering sense) and versatile (meaning broadly applicable to a wide range of situations), then I wholly agree that many industries would benefit from standardization on that barcode. I personally think that QR-Code might be such a barcode but I&#039;m not in a proper position to judge.

So why take the time to design and employ any other symbologies? Because no symbology is best suited to all purposes. For example, the Moseycode barcode was designed, among other things, to allow for faster detection and accurate spatial localization. It&#039;s very new, and time will tell if my design is superior in these (or other) regards.

With the caveat above, I think you are right about the importance of barcode standardization. In fact, it&#039;s plausible that the Moseycode software could in the future recognize a variety of different types of barcode for the same purposes.

Dean&#039;s comments are also quite accurate in almost every regard. Where I perhaps diverge is in the following analysis:

&quot;2d codes are often about providing information ‘on the spot’ in a self contained situation without needing to go ‘out elsewhere’ to gather information.&quot;

I think that this may be true now, but will become less important over time. Always-on internet connections (through which any subsidiary information is available) will undoubtedly become ever more prevalent (Shotcode is an example of this approach). Coupled with the advance of RFID tags, where does this leave barcodes?

Barcodes do have something unique, that existing scanners take no advantage of: their visible geometry. This is one thing that sets Moseycode apart from other systems and that molds its principles of user interaction. Internet connections and RFID tags don&#039;t give you the same opportunity to &#039;augment reality&#039;.

In response to Dean&#039;s query about its applicability for less capable mobile devices; a still photo is all that&#039;s needed to capture the necessary barcode information and one slow speed Internet access suffices to obtain a manifest of the barcode&#039;s contents. At this stage (depending largely on the care barcode author has taken) multiple layers of functionality may have been added, from the most complex (say an interactive 3D product demo) down to the simplest (a web link, or even just a number); most relevant devices should be capable of supporting Moseycode barcodes.

This touches on what I have personally concluded is the most damaging area of fragmentation in the current proliferation of barcodes. It&#039;s not the lack of a standard symbology, it&#039;s the lack of standard semantics for what to do with the data once the barcode is read. It is this problem that I would love to see Moseycode go some way to mending. A simple and extensible registry of barcode data that anyone can use to register and update their own barcodes would be a great leap forward; different readers could operate on the same information combined with their own symbologies and proprietary extensions.

It&#039;s very early days and it&#039;s a distant possibility that Moseycode could morph into such a repository, but all projects have to start somewhere, and I&#039;m encouraged by the number of people who have shown an interest.

Thanks, Tom.</description>
		<content:encoded><![CDATA[<p>First I&#8217;d like to say thank you for taking the time to write about Moseycode. I&#8217;d like to respond to some of your comments and to those of Dean.</p>
<p>On the point of barcode standardization: If a barcode exists that is entirely free (in the sense of being unfettered by intellectual property), well designed (in an engineering sense) and versatile (meaning broadly applicable to a wide range of situations), then I wholly agree that many industries would benefit from standardization on that barcode. I personally think that QR-Code might be such a barcode but I&#8217;m not in a proper position to judge.</p>
<p>So why take the time to design and employ any other symbologies? Because no symbology is best suited to all purposes. For example, the Moseycode barcode was designed, among other things, to allow for faster detection and accurate spatial localization. It&#8217;s very new, and time will tell if my design is superior in these (or other) regards.</p>
<p>With the caveat above, I think you are right about the importance of barcode standardization. In fact, it&#8217;s plausible that the Moseycode software could in the future recognize a variety of different types of barcode for the same purposes.</p>
<p>Dean&#8217;s comments are also quite accurate in almost every regard. Where I perhaps diverge is in the following analysis:</p>
<p>&#8220;2d codes are often about providing information ‘on the spot’ in a self contained situation without needing to go ‘out elsewhere’ to gather information.&#8221;</p>
<p>I think that this may be true now, but will become less important over time. Always-on internet connections (through which any subsidiary information is available) will undoubtedly become ever more prevalent (Shotcode is an example of this approach). Coupled with the advance of RFID tags, where does this leave barcodes?</p>
<p>Barcodes do have something unique, that existing scanners take no advantage of: their visible geometry. This is one thing that sets Moseycode apart from other systems and that molds its principles of user interaction. Internet connections and RFID tags don&#8217;t give you the same opportunity to &#8216;augment reality&#8217;.</p>
<p>In response to Dean&#8217;s query about its applicability for less capable mobile devices; a still photo is all that&#8217;s needed to capture the necessary barcode information and one slow speed Internet access suffices to obtain a manifest of the barcode&#8217;s contents. At this stage (depending largely on the care barcode author has taken) multiple layers of functionality may have been added, from the most complex (say an interactive 3D product demo) down to the simplest (a web link, or even just a number); most relevant devices should be capable of supporting Moseycode barcodes.</p>
<p>This touches on what I have personally concluded is the most damaging area of fragmentation in the current proliferation of barcodes. It&#8217;s not the lack of a standard symbology, it&#8217;s the lack of standard semantics for what to do with the data once the barcode is read. It is this problem that I would love to see Moseycode go some way to mending. A simple and extensible registry of barcode data that anyone can use to register and update their own barcodes would be a great leap forward; different readers could operate on the same information combined with their own symbologies and proprietary extensions.</p>
<p>It&#8217;s very early days and it&#8217;s a distant possibility that Moseycode could morph into such a repository, but all projects have to start somewhere, and I&#8217;m encouraged by the number of people who have shown an interest.</p>
<p>Thanks, Tom.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

