26/5 Short Discussion of Encoding Data in QR Codes
| Category: QR Code, Data Matrix... By editor at 17:00 |
I 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
E-mail address - Example
Telephone numbers - Example
SMS - Example
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).
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.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.
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.
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.Agree 100%, also about not initiating a call automatically. Kaywa Reader works like this.
Readers should invoke the device's dialer, if applicable, and pre-fill it with the given number, but not automatically initiate a call.
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.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.
Readers should open a new SMS message, ready for the user to compose and send 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).
Comments
brian
-
brian [at] suda.co.uk
2008-05-27 10:41:12
Another format which i would love to see supported is iCalendar. Then you could import upcoming events, shop opening times, or any other time sensitive information straight into your mobile calendar.
2008-05-27 10:41:12
Another format which i would love to see supported is iCalendar. Then you could import upcoming events, shop opening times, or any other time sensitive information straight into your mobile calendar.
Roger
-
http://id.kaywa.com/roger
2008-05-27 20:54:42
Hi Brian,
Makes sense, although iCal is quite verbous, even in its simplest form:
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:19970714T170000Z
DTEND:19970715T035959Z
SUMMARY:Bastille Day Party
END:VEVENT
END:VCALENDAR
See example
Wouldn't it be easier to do this through an URL (Weblink)?
Currently for some european Java phones there is still a limitation of 70 letters. The above example is already around 134 letters.
2008-05-27 20:54:42
Hi Brian,
Makes sense, although iCal is quite verbous, even in its simplest form:
BEGIN:VCALENDAR
BEGIN:VEVENT
DTSTART:19970714T170000Z
DTEND:19970715T035959Z
SUMMARY:Bastille Day Party
END:VEVENT
END:VCALENDAR
See example
Wouldn't it be easier to do this through an URL (Weblink)?
Currently for some european Java phones there is still a limitation of 70 letters. The above example is already around 134 letters.
V
2008-06-20 18:00:43
Is there anyway Kaywa can AT LEAST support the basic N:last;first format for names in vCards? I expected that Kaywa would at least get the name right, but it doesn't.
2008-06-20 18:00:43
Is there anyway Kaywa can AT LEAST support the basic N:last;first format for names in vCards? I expected that Kaywa would at least get the name right, but it doesn't.
david harper
-
dharper [at] winksite.com
-
http://winksite.com
2008-06-28 23:53:49
@ roger
re: URL (Mobile Web address) "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."
Sean is talking about the URL opening in the reader software where you make the choice. your reader does not work like that. unless whitelisted your reader takes you to a landing page on your server where then the individual is given a choice. a BIG difference. ...you are a bottleneck/in between the code and the destination. please correct me if i'm wrong.
david
2008-06-28 23:53:49
@ roger
re: URL (Mobile Web address) "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."
Sean is talking about the URL opening in the reader software where you make the choice. your reader does not work like that. unless whitelisted your reader takes you to a landing page on your server where then the individual is given a choice. a BIG difference. ...you are a bottleneck/in between the code and the destination. please correct me if i'm wrong.
david
Roger
-
http://id.kaywa.com/roger
2008-07-09 21:21:21
Hi David,
Yep, you are right - if not whitelisted - there is an in-between page.
I explained this already to you once. There are two reasons to do this today (tomorrow it can be completely different;):
- Quality Control / Security
- Business Model
As anybody can create his QR Code with our free QR Code generator (http://qrcode.kaywa.com), we don't know what is behind unless we are contacted.
We want to provide a good user experience not one that costs 10 Euro and you get nothing because it crashes your phone. Also security is an important topic.
Second, mobile tagging needs somewhere - we have it on URL's - a business model. Whereas offline codes are completely free, we provide a management system if you want to get serious with QR Codes for mobile sites.
This ecosystem brings value to everybody - us, the casual QR Code user as well as to the commercial user.
For non-commercial projects we also do whitelisting as for example for Semapedia.
2008-07-09 21:21:21
Hi David,
Yep, you are right - if not whitelisted - there is an in-between page.
I explained this already to you once. There are two reasons to do this today (tomorrow it can be completely different;):
- Quality Control / Security
- Business Model
As anybody can create his QR Code with our free QR Code generator (http://qrcode.kaywa.com), we don't know what is behind unless we are contacted.
We want to provide a good user experience not one that costs 10 Euro and you get nothing because it crashes your phone. Also security is an important topic.
Second, mobile tagging needs somewhere - we have it on URL's - a business model. Whereas offline codes are completely free, we provide a management system if you want to get serious with QR Codes for mobile sites.
This ecosystem brings value to everybody - us, the casual QR Code user as well as to the commercial user.
For non-commercial projects we also do whitelisting as for example for Semapedia.
stan wiechers
-
stan [at] merkwelt.com
-
http://www.semapedia.org
2008-07-10 17:04:24
appreciate that you whitelist semapedia. But the in between page is confusing and giving more weight to your personal blog link then the actual qr code URL is not ideal. Imagine if I.e. Vodafone would do that to this blog pay to get whitelisted otherwise every visitor sees a in between page. Nobody wants that to happen.
2008-07-10 17:04:24
appreciate that you whitelist semapedia. But the in between page is confusing and giving more weight to your personal blog link then the actual qr code URL is not ideal. Imagine if I.e. Vodafone would do that to this blog pay to get whitelisted otherwise every visitor sees a in between page. Nobody wants that to happen.
David Harper
-
dharper [at] winksite.com
-
http://winksite.com
2008-07-13 03:26:13
"I explained this already to you once."
Yes, you did. But when you state, "Agree 100% ..." to Sean's statement you are misleading people. So I bring it up again.
Re: "we don't know what is behind unless we are contacted."
When people scan a QR Code on open readers they can see the URL and chose on their own to proceed or not.
Also, winksite located at winksite.com and winksite.mobi is non-commercial, why are we not whitelisted. Oh, that's right you are not only a bottleneck but a gatekeeper -- you get to pick and choose.
You are treating QR Codes like they are a postal stamp -- that's not an acceptibile a business model -- that's a tax.
2008-07-13 03:26:13
"I explained this already to you once."
Yes, you did. But when you state, "Agree 100% ..." to Sean's statement you are misleading people. So I bring it up again.
Re: "we don't know what is behind unless we are contacted."
When people scan a QR Code on open readers they can see the URL and chose on their own to proceed or not.
Also, winksite located at winksite.com and winksite.mobi is non-commercial, why are we not whitelisted. Oh, that's right you are not only a bottleneck but a gatekeeper -- you get to pick and choose.
You are treating QR Codes like they are a postal stamp -- that's not an acceptibile a business model -- that's a tax.
David Harper
-
dharper [at] winksite.com
-
http://winksite.com
2008-07-13 12:50:06
"that's not an acceptable business model -- that's a tax."
Not acceptable i mean when using an open format and confusing the general public with a scanning experience that places you in the middle of a freely generated code and that codes URL. Intercept codes created in your system but free the rest.
2008-07-13 12:50:06
"that's not an acceptable business model -- that's a tax."
Not acceptable i mean when using an open format and confusing the general public with a scanning experience that places you in the middle of a freely generated code and that codes URL. Intercept codes created in your system but free the rest.
Roger
-
http://id.kaywa.com/roger
2008-07-13 23:49:09
@Stan and David,
Tell me how to do this more elegantly today and we will listen. By doing this take into consideration that
a) there have to be a business model for us and others in a similar situation
and
b) there has to be a quality / security control as long as going online through 3G networks has a high price for the end user.
We don't have a NTTDocomo past, where no page could be heavier than 10KB.
***
Also, keep in mind that the current model is not set in stone and will be adapted to a constantly changing environment.
Currently however the biggest hindrance to the rapid deployment of QR Codes in the West are
a) still too many different codes
b) the lack of a sustainable business model for the telcos, advertisers etc.
c) the fear of the end user to spend too much money
If you address these points in your answers, this can become an interesting discussion.
PS: @David - last time we discussed it, you were not interested. So let us talk again.
2008-07-13 23:49:09
@Stan and David,
Tell me how to do this more elegantly today and we will listen. By doing this take into consideration that
a) there have to be a business model for us and others in a similar situation
and
b) there has to be a quality / security control as long as going online through 3G networks has a high price for the end user.
We don't have a NTTDocomo past, where no page could be heavier than 10KB.
***
Also, keep in mind that the current model is not set in stone and will be adapted to a constantly changing environment.
Currently however the biggest hindrance to the rapid deployment of QR Codes in the West are
a) still too many different codes
b) the lack of a sustainable business model for the telcos, advertisers etc.
c) the fear of the end user to spend too much money
If you address these points in your answers, this can become an interesting discussion.
PS: @David - last time we discussed it, you were not interested. So let us talk again.
Stan
-
whoisstan [at] gmail.com
-
http://www.semapedia.org
2008-07-14 21:20:22
hey
re: b) there has to be a quality / security control as long as going online through 3G networks has a high price for the end user. & c) the fear of the end user to spend too much money
yes, but the telcos have to do that, most of the traffic originates not from a QR code just yet. also i don't think that is clarified with your page as well. also i still could have large pages costing the customer $$$ once i paid the 500 euro.
re: a) there have to be a business model for us and others in a similar situation
i repeat myself, charging for access of data that you don't even own, not sure how that is a good model since everybody could do that, where would we end up of we head that way? kaywa is based on 3g vision, right? so 3g visions model makes sense, they can their software at large. but essentially taking what they provide (and i could download for free) and putting a gatekeeper page in between just seems to add no value, you argue that want to protect users from costs, but the real objective seems the business model.
no bad vibes, kaywa is great and good for the QR code eco system, but i don't think there is a business model to everything.
2008-07-14 21:20:22
hey
re: b) there has to be a quality / security control as long as going online through 3G networks has a high price for the end user. & c) the fear of the end user to spend too much money
yes, but the telcos have to do that, most of the traffic originates not from a QR code just yet. also i don't think that is clarified with your page as well. also i still could have large pages costing the customer $$$ once i paid the 500 euro.
re: a) there have to be a business model for us and others in a similar situation
i repeat myself, charging for access of data that you don't even own, not sure how that is a good model since everybody could do that, where would we end up of we head that way? kaywa is based on 3g vision, right? so 3g visions model makes sense, they can their software at large. but essentially taking what they provide (and i could download for free) and putting a gatekeeper page in between just seems to add no value, you argue that want to protect users from costs, but the real objective seems the business model.
no bad vibes, kaywa is great and good for the QR code eco system, but i don't think there is a business model to everything.
David Harper
-
dharper [at] winksite.com
-
http://winksite.com
2008-07-15 06:38:20
Re:
a) there have to be a business model for us and others in a similar situation
and
DH: Come up with one that does not include hijacking openly generated codes scanned with your reader.
b) there has to be a quality / security control as long as going online through 3G networks has a high price for the end user.
DH: So you have appointed yourself as protector to those who freely choose to browse the mobile web?
----------
Re: PS: @David - last time we discussed it, you were not interested. So let us talk again.
----------
...and re: Stan's statement: "no bad vibes, kaywa is great and good for the QR code eco system..."
Although I have disagreements with you - i agree with Stan. You are doing a great job.
I wanted out of your bottleneck and interception nightmare. You wanted to charge me.
David
2008-07-15 06:38:20
Re:
a) there have to be a business model for us and others in a similar situation
and
DH: Come up with one that does not include hijacking openly generated codes scanned with your reader.
b) there has to be a quality / security control as long as going online through 3G networks has a high price for the end user.
DH: So you have appointed yourself as protector to those who freely choose to browse the mobile web?
----------
Re: PS: @David - last time we discussed it, you were not interested. So let us talk again.
----------
...and re: Stan's statement: "no bad vibes, kaywa is great and good for the QR code eco system..."
Although I have disagreements with you - i agree with Stan. You are doing a great job.
I wanted out of your bottleneck and interception nightmare. You wanted to charge me.
David
Roger
-
roger [at] 2d-code.co.uk
-
http://2d-code.co.uk
2008-07-15 06:56:21
@DH DH: Come up with one that does not include hijacking openly generated codes scanned with your reader.
Of the millions of open QR Codes generated in Japan in the last eight years has there ever been a case of hijacking? If so I would like to hear about it.
- Roger
Editor: http://2d-code.co.uk
2008-07-15 06:56:21
@DH DH: Come up with one that does not include hijacking openly generated codes scanned with your reader.
Of the millions of open QR Codes generated in Japan in the last eight years has there ever been a case of hijacking? If so I would like to hear about it.
- Roger
Editor: http://2d-code.co.uk
Roger
2008-07-15 12:22:33
@Stan
Regarding b)
Well, checking on QR Codes made with the Online Generator, I must say, 80% of them are not mobile enabled sites being often quite heavy (500KB and more). And pricing of data traffic is one of the top issues with customers.
Since the beginning of Kaywa in 2003, we took care of this (see for example the red link here.
I don't think it's only the Telecoms job to look for this, it's the job of everybody working in the mobile field.
I don't know how this is in the US, but I think in comparison to Switzerland it has a much more PC/Mac-centric view. If customers here have suddenly CHF 10/Euro 7 bills for looking at two bad-looking pages on their mobile, we have a problem.
It's only now that we have - still expensive and therefore not for everybody - tools like N95 or the iPhone that offer Wifi and coming with it cheaper data prices, that this can start to change.
Concerning b)
We don't charge for accessing content and we don't charge the end user. With our free generator everybody can make as many open codes as he wants (on a non-commercial basis as it has a server cost).
Kaywa charge for the use of the management system which let's you create, edit your codes and gives you live statistics.
See our QR Code Guide
And again without business model for different participants (even an indirect one), this market will not take off.
And simply creating more data traffic is not the answer.
We opted for the most open of all models (standard ISO-code, URL if possible and therefore compatibility between different readers) and if the market changes, we will adapt.
What you probably do not see is, that the industry (reader companies, mgmt system companies, telcos, organizations like GS1) wants a business model to justify the investment. And of all projects and companies I know there is always more than only the reader software involved - you might just not see it yet.
We opted for transparency, that's why you see what we do.
2008-07-15 12:22:33
@Stan
Regarding b)
Well, checking on QR Codes made with the Online Generator, I must say, 80% of them are not mobile enabled sites being often quite heavy (500KB and more). And pricing of data traffic is one of the top issues with customers.
Since the beginning of Kaywa in 2003, we took care of this (see for example the red link here.
I don't think it's only the Telecoms job to look for this, it's the job of everybody working in the mobile field.
I don't know how this is in the US, but I think in comparison to Switzerland it has a much more PC/Mac-centric view. If customers here have suddenly CHF 10/Euro 7 bills for looking at two bad-looking pages on their mobile, we have a problem.
It's only now that we have - still expensive and therefore not for everybody - tools like N95 or the iPhone that offer Wifi and coming with it cheaper data prices, that this can start to change.
Concerning b)
We don't charge for accessing content and we don't charge the end user. With our free generator everybody can make as many open codes as he wants (on a non-commercial basis as it has a server cost).
Kaywa charge for the use of the management system which let's you create, edit your codes and gives you live statistics.
See our QR Code Guide
And again without business model for different participants (even an indirect one), this market will not take off.
And simply creating more data traffic is not the answer.
We opted for the most open of all models (standard ISO-code, URL if possible and therefore compatibility between different readers) and if the market changes, we will adapt.
What you probably do not see is, that the industry (reader companies, mgmt system companies, telcos, organizations like GS1) wants a business model to justify the investment. And of all projects and companies I know there is always more than only the reader software involved - you might just not see it yet.
We opted for transparency, that's why you see what we do.
David Harper
-
dharper [at] winksite.com
-
http://winksite.com
2008-07-17 04:19:34
@Roger "Of the millions of open QR Codes generated in Japan in the last eight years has there ever been a case of hijacking? If so I would like to hear about it."
Hijacking is what occurs when a QR Code that contains an embedded URL is delivered to a landing page first rather then directly to the embedded URL (by the qr code reader). This is how your reader operates (unless the QR Code is whitelisted by your discretion or payment to you.)
On the other hand the i-nigma reader used by the majority of Japanese keitai users sends people directly to the scanned URL - that's how it should work. Kudos to 3GVision.
2008-07-17 04:19:34
@Roger "Of the millions of open QR Codes generated in Japan in the last eight years has there ever been a case of hijacking? If so I would like to hear about it."
Hijacking is what occurs when a QR Code that contains an embedded URL is delivered to a landing page first rather then directly to the embedded URL (by the qr code reader). This is how your reader operates (unless the QR Code is whitelisted by your discretion or payment to you.)
On the other hand the i-nigma reader used by the majority of Japanese keitai users sends people directly to the scanned URL - that's how it should work. Kudos to 3GVision.
Roger
2008-07-17 11:32:30
@David,
No, but in Japan NTTDoCoMo has preinstalled QR Code Readers to boost data traffic on the i-mode network services. As i-mode is completely controlled by NTTDoCoMo, the revenue generated through more traffic also meant mor service charges = more benefit.
So openess of the QR Code, but controlled internet - selection of services, as well as page data at 10KB, no phone portability etc. KDDI and J-Phone had similiar walled garden strategies.
This is very important to understand and shows the big difference.
***
As I said nothing is set in stone here, all this is evolutional. What was important for us is to opt for an ISO-Standard, to opt for interoperability from the start.
***
As for 3GVision, we are bound by an NDA. So you have to find out yourself how there business model works.
PS: To come back on your discussion for whitelisting your service back in 2006. In the talks we had you opted for pushing Shotcode at that time. And we didn't ask you for money.
2008-07-17 11:32:30
@David,
No, but in Japan NTTDoCoMo has preinstalled QR Code Readers to boost data traffic on the i-mode network services. As i-mode is completely controlled by NTTDoCoMo, the revenue generated through more traffic also meant mor service charges = more benefit.
So openess of the QR Code, but controlled internet - selection of services, as well as page data at 10KB, no phone portability etc. KDDI and J-Phone had similiar walled garden strategies.
This is very important to understand and shows the big difference.
***
As I said nothing is set in stone here, all this is evolutional. What was important for us is to opt for an ISO-Standard, to opt for interoperability from the start.
***
As for 3GVision, we are bound by an NDA. So you have to find out yourself how there business model works.
PS: To come back on your discussion for whitelisting your service back in 2006. In the talks we had you opted for pushing Shotcode at that time. And we didn't ask you for money.
