Comments on: Ideas for Interoperability of Secure Barcode Tickets http://www.masabi.com/2008/04/13/ideas-for-interoperability-of-secure-barcode-tickets/ The ticket machine in your pocket Sat, 23 Jan 2010 20:27:25 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Anonymous http://www.masabi.com/2008/04/13/ideas-for-interoperability-of-secure-barcode-tickets/comment-page-1/#comment-47 Anonymous Fri, 29 Aug 2008 00:20:00 +0000 http://masabi.com/2008/04/ideas-for-interoperability-of-secure-barcode-tickets.html#comment-47 Great article, really helped alot! Tkoma Si?kve Great article, really helped alot! Tkoma Si?kve

]]> By: TJ Crawford http://www.masabi.com/2008/04/13/ideas-for-interoperability-of-secure-barcode-tickets/comment-page-1/#comment-36 TJ Crawford Mon, 14 Apr 2008 19:51:00 +0000 http://masabi.com/2008/04/ideas-for-interoperability-of-secure-barcode-tickets.html#comment-36 We have been working on an implementation in the US and have had several considerations regarding the barcode and surrounding technologies.<br/><br/>1. Carrier Capabilities - Not all of the carriers will deliver an MMS message that contains the barcode. Another alternative is a WAP link, however there is no way of knowing if the purchaser has a data plan to retrieve the barcode, and would not get charged a premium to do so. That leaves a failsafe of SMS, and sending a corresponding PIN/Confirmation number that can be entered into the redemption point as well.<br/><br/>2. In the large format barcodes information we have seen a few advantages. One example is that we are able to include duplicate information about a ticket in the different quadrants of the barcode. This helps when there is a print at home ticket that has been crumpled or worn from travel. Since we can grab duplicate information from separate quadrants it has reduced the scanning error rate.<br/><br/>3. Off-line as well as On-line checking doesn't have to be segregated. By using a multi-master database replication you can prevent down time by redeeming up to the last point of replication, however you have the ability to get real-time redemption if connectivity exists.<br/><br/>4. We are watching the technology but cell phones are being equipped with RFID chips and could be used in the future instead of an optical scanning technology.<br/><br/>5. We have developed a web services API into and out of our solution to facilitate 3rd party integrations and make the barcode generating and redemption extensible. We have been working on an implementation in the US and have had several considerations regarding the barcode and surrounding technologies.

1. Carrier Capabilities – Not all of the carriers will deliver an MMS message that contains the barcode. Another alternative is a WAP link, however there is no way of knowing if the purchaser has a data plan to retrieve the barcode, and would not get charged a premium to do so. That leaves a failsafe of SMS, and sending a corresponding PIN/Confirmation number that can be entered into the redemption point as well.

2. In the large format barcodes information we have seen a few advantages. One example is that we are able to include duplicate information about a ticket in the different quadrants of the barcode. This helps when there is a print at home ticket that has been crumpled or worn from travel. Since we can grab duplicate information from separate quadrants it has reduced the scanning error rate.

3. Off-line as well as On-line checking doesn’t have to be segregated. By using a multi-master database replication you can prevent down time by redeeming up to the last point of replication, however you have the ability to get real-time redemption if connectivity exists.

4. We are watching the technology but cell phones are being equipped with RFID chips and could be used in the future instead of an optical scanning technology.

5. We have developed a web services API into and out of our solution to facilitate 3rd party integrations and make the barcode generating and redemption extensible.

]]>