From: Petter Reinholdtsen Date: Sun, 20 Mar 2016 12:08:35 +0000 (+0100) Subject: Generated. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/9e0b8ef3ce62050c1f3609c328309fa9fcc76010 Generated. --- diff --git a/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html b/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html index 9b5128f196..16fe63ec6e 100644 --- a/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html +++ b/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html @@ -97,6 +97,27 @@ evaluate the way forward if the format proved to be popular. I hope they conclude that using an open standard organisation like IETF is the correct place to maintain such specification.

+ +

Update 2016-03-20: Via Twitter I became aware of +some comments +about this blog post that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +Short +Payment Descriptor. And I Germany, there is a system named +BezahlCode, +(specification +v1.8 2013-12-05 available as PDF), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +ZUGFeRD +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.

Tags: english, standard.
diff --git a/blog/archive/2016/03/03.rss b/blog/archive/2016/03/03.rss index 10a7e4ab63..983a1d4016 100644 --- a/blog/archive/2016/03/03.rss +++ b/blog/archive/2016/03/03.rss @@ -86,6 +86,27 @@ evaluate the way forward if the format proved to be popular. I hope they conclude that using an open standard organisation like <a href="http://www.ietf.org/">IETF</a> is the correct place to maintain such specification.</p> + +<p><strong>Update 2016-03-20</strong>: Via Twitter I became aware of +<a href="https://news.ycombinator.com/item?id=11319492">some comments +about this blog post</a> that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +<a href="https://en.wikipedia.org/wiki/Short_Payment_Descriptor">Short +Payment Descriptor</a>. And I Germany, there is a system named +<a href="http://www.bezahlcode.de/">BezahlCode</a>, +(<a href="http://www.bezahlcode.de/wp-content/uploads/BezahlCode_TechDok.pdf">specification +v1.8 2013-12-05 available as PDF</a>), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +<a href="http://www.ferd-net.de/front_content.php?idcat=231">ZUGFeRD</a> +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.</p> diff --git a/blog/archive/2016/03/index.html b/blog/archive/2016/03/index.html index 6da191e2c0..ca512cfffc 100644 --- a/blog/archive/2016/03/index.html +++ b/blog/archive/2016/03/index.html @@ -105,6 +105,27 @@ they conclude that using an open standard organisation like IETF is the correct place to maintain such specification.

+

Update 2016-03-20: Via Twitter I became aware of +some comments +about this blog post that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +Short +Payment Descriptor. And I Germany, there is a system named +BezahlCode, +(specification +v1.8 2013-12-05 available as PDF), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +ZUGFeRD +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.

+
diff --git a/blog/index.html b/blog/index.html index f52364f708..487a3067a3 100644 --- a/blog/index.html +++ b/blog/index.html @@ -97,6 +97,27 @@ evaluate the way forward if the format proved to be popular. I hope they conclude that using an open standard organisation like IETF is the correct place to maintain such specification.

+ +

Update 2016-03-20: Via Twitter I became aware of +some comments +about this blog post that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +Short +Payment Descriptor. And I Germany, there is a system named +BezahlCode, +(specification +v1.8 2013-12-05 available as PDF), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +ZUGFeRD +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.

diff --git a/blog/index.rss b/blog/index.rss index 5be2cbecbb..e37cc2cc3b 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -86,6 +86,27 @@ evaluate the way forward if the format proved to be popular. I hope they conclude that using an open standard organisation like <a href="http://www.ietf.org/">IETF</a> is the correct place to maintain such specification.</p> + +<p><strong>Update 2016-03-20</strong>: Via Twitter I became aware of +<a href="https://news.ycombinator.com/item?id=11319492">some comments +about this blog post</a> that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +<a href="https://en.wikipedia.org/wiki/Short_Payment_Descriptor">Short +Payment Descriptor</a>. And I Germany, there is a system named +<a href="http://www.bezahlcode.de/">BezahlCode</a>, +(<a href="http://www.bezahlcode.de/wp-content/uploads/BezahlCode_TechDok.pdf">specification +v1.8 2013-12-05 available as PDF</a>), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +<a href="http://www.ferd-net.de/front_content.php?idcat=231">ZUGFeRD</a> +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.</p> diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss index 63aa56de72..9bd19b5ed2 100644 --- a/blog/tags/english/english.rss +++ b/blog/tags/english/english.rss @@ -86,6 +86,27 @@ evaluate the way forward if the format proved to be popular. I hope they conclude that using an open standard organisation like <a href="http://www.ietf.org/">IETF</a> is the correct place to maintain such specification.</p> + +<p><strong>Update 2016-03-20</strong>: Via Twitter I became aware of +<a href="https://news.ycombinator.com/item?id=11319492">some comments +about this blog post</a> that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +<a href="https://en.wikipedia.org/wiki/Short_Payment_Descriptor">Short +Payment Descriptor</a>. And I Germany, there is a system named +<a href="http://www.bezahlcode.de/">BezahlCode</a>, +(<a href="http://www.bezahlcode.de/wp-content/uploads/BezahlCode_TechDok.pdf">specification +v1.8 2013-12-05 available as PDF</a>), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +<a href="http://www.ferd-net.de/front_content.php?idcat=231">ZUGFeRD</a> +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.</p> diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html index aa23430792..1484f71b5f 100644 --- a/blog/tags/english/index.html +++ b/blog/tags/english/index.html @@ -104,6 +104,27 @@ they conclude that using an open standard organisation like IETF is the correct place to maintain such specification.

+

Update 2016-03-20: Via Twitter I became aware of +some comments +about this blog post that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +Short +Payment Descriptor. And I Germany, there is a system named +BezahlCode, +(specification +v1.8 2013-12-05 available as PDF), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +ZUGFeRD +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.

+
diff --git a/blog/tags/standard/index.html b/blog/tags/standard/index.html index 0c25644015..3c6518de81 100644 --- a/blog/tags/standard/index.html +++ b/blog/tags/standard/index.html @@ -104,6 +104,27 @@ they conclude that using an open standard organisation like IETF is the correct place to maintain such specification.

+

Update 2016-03-20: Via Twitter I became aware of +some comments +about this blog post that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +Short +Payment Descriptor. And I Germany, there is a system named +BezahlCode, +(specification +v1.8 2013-12-05 available as PDF), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +ZUGFeRD +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.

+
diff --git a/blog/tags/standard/standard.rss b/blog/tags/standard/standard.rss index 7cd04175b2..409033630a 100644 --- a/blog/tags/standard/standard.rss +++ b/blog/tags/standard/standard.rss @@ -86,6 +86,27 @@ evaluate the way forward if the format proved to be popular. I hope they conclude that using an open standard organisation like <a href="http://www.ietf.org/">IETF</a> is the correct place to maintain such specification.</p> + +<p><strong>Update 2016-03-20</strong>: Via Twitter I became aware of +<a href="https://news.ycombinator.com/item?id=11319492">some comments +about this blog post</a> that had several useful links and references to +similar systems. In the Czech republic, the Czech Banking Association +standard #26, with short name SPAYD, uses QR codes with payment +information. More information is available from the Wikipedia page on +<a href="https://en.wikipedia.org/wiki/Short_Payment_Descriptor">Short +Payment Descriptor</a>. And I Germany, there is a system named +<a href="http://www.bezahlcode.de/">BezahlCode</a>, +(<a href="http://www.bezahlcode.de/wp-content/uploads/BezahlCode_TechDok.pdf">specification +v1.8 2013-12-05 available as PDF</a>), which uses QR code with +URL-like formatting using "bank:" as the URI schema/protocol to +provide the payment information. There is also the +<a href="http://www.ferd-net.de/front_content.php?idcat=231">ZUGFeRD</a> +file format that perhaps could be transfered using QR codes, but I am +not sure if it is done already. Last, in Bolivia there are reports +that tax information since november 2014 need to be printed in QR +format on invoices. I have not been able to track down a +specification for this format, because of my limited language skill +sets.</p>