From 9bf1fd25b4c58cb0f6e74f463b00fccf831109c7 Mon Sep 17 00:00:00 2001 From: Petter Reinholdtsen Date: Tue, 12 Feb 2013 09:30:18 +0000 Subject: [PATCH] Improve language. --- blog/data/2013-02-12-qr-invoice.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/blog/data/2013-02-12-qr-invoice.txt b/blog/data/2013-02-12-qr-invoice.txt index 2dde248954..5b4e24c69c 100644 --- a/blog/data/2013-02-12-qr-invoice.txt +++ b/blog/data/2013-02-12-qr-invoice.txt @@ -2,15 +2,17 @@ Title: "Electronic" paper invoices - using vCard in a QR code Tags: english, standard Date: 2013-02-12 10:30 -Here in Norway, electronic invoices are spreading, and the solution -promoted by the Norwegian government is not really decentralised and -require that invoices are sent through one of the approved +Here in Norway, electronic invoices are spreading, and the +solution promoted +by the Norwegian government require that invoices are sent through +one of the approved facilitators, and it is not possible to send +electronic invoices without an agreement with one of these facilitators. This seem like a needless limitation to be able to transfer invoice information between buyers and sellers. My preferred solution would be to just transfer the invoice information directly between seller and buyer, for example using SMTP, or some HTTP based protocol like REST or SOAP. But this might also be overkill, as the -"electronic" information can be transfered using paper invoices too, +"electronic" information can be transferred using paper invoices too, using a simple bar code. My bar code encoding of choice would be QR codes, as this encoding can be read by any smart phone out there. The content of the code could be anything, but I would go with -- 2.47.2