X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/91cfb945f2bebfec2e497cfa026eb5917d321538..3e8c4bf87aeaa0c186308fd80e471e22eb8dc523:/blog/archive/2016/03/03.rss
diff --git a/blog/archive/2016/03/03.rss b/blog/archive/2016/03/03.rss
index 464ab5e3c7..d84113d515 100644
--- a/blog/archive/2016/03/03.rss
+++ b/blog/archive/2016/03/03.rss
@@ -6,6 +6,89 @@
http://people.skolelinux.org/pere/blog/
+
+ UsingQR - "Electronic" paper invoices using JSON and QR codes
+ http://people.skolelinux.org/pere/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html
+ http://people.skolelinux.org/pere/blog/UsingQR____Electronic__paper_invoices_using_JSON_and_QR_codes.html
+ Sat, 19 Mar 2016 09:40:00 +0100
+ <p>Back in 2013 I proposed
+<a href="http://people.skolelinux.org/pere/blog/_Electronic__paper_invoices___using_vCard_in_a_QR_code.html">a
+way to make paper and PDF invoices easier to process electronically by
+adding a QR code with the key information about the invoice</a>. I
+suggested using vCard field definition, to get some standard format
+for name and address, but any format would work. I did not do
+anything about the proposal, but hoped someone one day would make
+something like it. It would make it possible to efficiently send
+machine readable invoices directly between seller and buyer.</p>
+
+<p>This was the background when I came across a proposal and
+specification from the web based accounting and invoicing supplier
+<a href="http://www.visma.com/">Visma</a> in Sweden called
+<a href="http://usingqr.com/">UsingQR</a>. Their PDF invoices contain
+a QR code with the key information of the invoice in JSON format.
+This is the typical content of a QR code following the UsingQR
+specification (based on a real world example, some numbers replaced to
+get a more bogus entry). I've reformatted the JSON to make it easier
+to read. Normally this is all on one long line:
+
+<p><img src="http://people.skolelinux.org/pere/blog/images/2016-03-19-qr-invoice.png" align="right"><pre>
+{
+ "vh":500.00,
+ "vm":0,
+ "vl":0,
+ "uqr":1,
+ "tp":1,
+ "nme":"Din Leverandør",
+ "cc":"NO",
+ "cid":"997912345 MVA",
+ "iref":"12300001",
+ "idt":"20151022",
+ "ddt":"20151105",
+ "due":2500.0000,
+ "cur":"NOK",
+ "pt":"BBAN",
+ "acc":"17202612345",
+ "bc":"BIENNOK1",
+ "adr":"0313 OSLO"
+}
+</pre></p>
+
+</p>The interpretation of the fields can be found in the
+<a href="http://usingqr.com/wp-content/uploads/2014/06/UsingQR_specification1.pdf">format
+specification</a> (revision 2 from june 2014). The format seem to
+have most of the information needed to handle accounting and payment
+of invoices, at least the fields I have needed so far here in
+Norway.</p>
+
+<p>Unfortunately, the site and document do not mention anything about
+the patent, trademark and copyright status of the format and the
+specification. Because of this, I asked the people behind it back in
+November to clarify. Ann-Christine Savlid (ann-christine.savlid (at)
+visma.com) replied that Visma had not applied for patent or trademark
+protection for this format, and that there were no copyright based
+usage limitations for the format. I urged her to make sure this was
+explicitly written on the web pages and in the specification, but
+unfortunately this has not happened yet. So I guess if there is
+submarine patents, hidden trademarks or a will to sue for copyright
+infringements, those starting to use the UsingQR format might be at
+risk, but if this happen there is some legal defense in the fact that
+the people behind the format claimed it was safe to do so. At least
+with patents, there is always
+<a href="http://www.paperspecs.com/paper-news/beware-the-qr-code-patent-trap/">a
+chance of getting sued...</a>
+
+<p>I also asked if they planned to maintain the format in an
+independent standard organization to give others more confidence that
+they would participate in the standardization process on equal terms
+with Visma, but they had no immediate plans for this. Their plan was
+to work with banks to try to get more users of the format, and
+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>
+
+
+
Making battery measurements a little easier in Debian
http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html