23/7 Mobile Barcodes: OMA and GS1 opt both for QR Codes and DatamatrixBoth OMA, the Open Mobile Alliance and GS1, responsible for the 1D Barcode Number assignment worldwide, have picked up interest in Mobile Barcodes. Both organizations have now approved QR Codes and Datamatrix as the two defacto 2D barcode standards.
Great!
Both organizations also try to define an interoperability standard especially in the field of Shortcodes aka indirect mode (number to be translated into an URL on a Server). GS1 points to the already existing EAN barcode numbers which are well established whereas OMA presents a different way of doing it (see mainly page 20).
***
GS1
Datamatrix and QR Codes as GS1 approved 2D Barcodes, June 12-13 in New York.
Mobile Commerce Whitepaper by GS1
GS1 Japan on QR Codes.
OMA
Mobile Codes, MC (V1_0)(June 2008)
OMA (October 2007)
Work to be undertaken:
The work will include recommendations of: choice of 2D barcode symbology(ies); the data stored in the barcodes; and terminal behaviours in response to reading barcodes, including behaviours with respect to some existing (1D and 2D) barcodes. The aim is to re-use as much of existing standards as possible. This way we can get a recommendation published as soon as possible, to avoid further fragmentation of the market. Prime candidates for re-use include the industrial standards for barcode symbologies QR and Datamatrix, and the NFC Forum NDEF data structure. The normative specifications to be developed shall ensure backward compatibility with relevant 2D barcode systems, so that mobile devices that are compliant to the specifications to be developed shall be able to recognize and process such existing 2D barcode print-outs or images.
The list of relevant specifications includes:
Quick Response, ISO/IEC 18004:2000
Datamatrix ISO/IEC 16022:2000
NFC Data Exchange Format (NDEF) Technical Specification
NFC Smart Poster Record Type Definition (RTD) Technical Specification
NFC URI RTD Technical Specification
NTT DoCoMo Bar Code Functions 18/7 Google Trends on QR Code, Datamatrix and others11/7 QR Codes in Switzerland (continued)07/7 Houston QR Code Fence in NYC
Image: Houston Fence Project
Houston Fence
The Houston Fence, located on the corner of Broadway and Houston, is an temporary outdoor installation inspired by QR-code patterns. These bar codes, when scanned with a mobile phone, allow pedestrians to seamlessly connect to online content such as web sites, blogs and others.
Scan the QR Code:
Via David Hartman11/6 Bidibooks, the first multilingual QR Code books series in Europe05/6 O codigo do amor (Fast Shop / Dentsu Latin America)
Emice gave me the green lights to blog this. The campaign will hit Brazil tomorrow. In her words:
This is the campaign for Valentine's for Fast Shop (www.fastshop.com.br), a retail for eletronics in Brazil. And just as a reminder: we celebrate Valentine's on June 12th here.
The campaign's name is "The Code of Love". The QR code is the main character, even though most people won't know at first what it is. Fast Shop has a strong appeal to innovation and the QR code exemplifies this perfectly. Also, Valentine's is known for the huge sale of mobiles among young people, so the QR code is pertinent.
The campaign is focused on Sao Paulo and will be starring in newspapers ads, POP materials such as window shops, alarm antennas and adhesives on the main shopping malls, catalogues that will be sent to AB class people homes. And we added a hotsite (www.fastshop.com.br/desvendeocodigo) that will be on after the campaign. The codes display messages such as present suggestions, store's solutions; they also link to the hotsite.
This is the second time Dentsu Latin America offers a QR Code campaign
for Fast Shop. First time was in 2007.
More pictures:
Poster
Poster II
FAST Shopping Bag02/6 Nike, Umbro and Adidas, where is Puma?30/5 Orbit-iEX (the Swiss IT conference) with QR Code on Poster
Our partner anthrazit used QR Codes to offer anyone a free ticket to Orbit-iEX.
26/5 Short Discussion of Encoding Data in QR CodesI refer here to Sean Owen's Barcode Contents. I made sometimes minor changes in the quotes (URL change and adding more examples for sending SMS), but remained true to the text.
URL (Mobile Web address) - Example
The most common application of barcodes is to encode the text of URL. To do so, simply encode exactly the text of the URL in the barcode: "http://anyurl.mobi". Include the protocol ("http://", here) to ensure it is recognized as an URL.
Readers should open the URL in the device's web browser when decoding a URL. It is probably desirable for a reader to display the URL and ask the user whether to proceed, so that the user may see the URL before accessing it.
Agree 100% and we think it's important that the user chooses to proceed or not. - Kaywa Reader works like this. If possible do not use capital letters for URL's.
E-mail address - Example
To encode an e-mail address like sean@example.com, one could simply encode "sean@example.com". However to ensure it is recognized as an e-mail address, it is advisable to create a proper mailto URI from the address: "mailto:sean@example.com".
Agree 100% - Kaywa Reader works like this
Telephone numbers - Example
A tel URI should be used to encode a telephone number, to ensure that the digits are understood as a telephone number. Further, it is advisable to include prefixes that make the number accessible internationally. For example, to encode the US phone number 212-555-1212, one should encode "tel:+12125551212". This tel URI includes a "+1" prefix that will make it usable outside the United States.
Readers should invoke the device's dialer, if applicable, and pre-fill it with the given number, but not automatically initiate a call.
Agree 100%, also about not initiating a call automatically. Kaywa Reader works like this.
SMS - Example
Much like an e-mail address, one can encode an SMS shortcode or number by creating an sms URI. For example to create a link to the number "12345" one would encode "sms:12345" or "sms:+12024561111?body=hello%20there" or "sms:+12024561111,+15102061079". See this draft of the SMS URI specification for details.
Readers should open a new SMS message, ready for the user to compose and send it.
Difference! The Kaywa Reader used and uses currently smsto! I think if we have mailto, smsto would make more sense. If there is a standard (right now it's a Draft) however, everybody should try to follow it.
Contact information - Example
The trickiest of all and the least standardized.
There is vCard, MECARD from NTTDoCoMo and another KDDI format.
Kaywa Reader uses vCard Standard for Name, Email and Telephone Number.
BEGIN:VCARD
N: Your name
EMAIL: Your email
TEL: Your phone number internationally
END:VCARD
For international use, I think vCard is definitely the way to go. It's a bit more verbous than MECARD, it's true, but people do not have to learn another format. The optimum would be to support both MECARD (established in Japan) and vCard (established here). | |