commit 836c45bca54e00d1c8386e4be233a4d83854ffb0
parent 8c84af83b2dcea19061ad3022856d61dec48dcc6
Author: Christian Grothoff <christian@grothoff.org>
Date: Thu, 6 Nov 2025 17:47:03 +0100
remove upper-case variants, pointless given that with query paramters we need ? and & which are not in the alphanumeric set
Diffstat:
1 file changed, 19 insertions(+), 14 deletions(-)
diff --git a/draft-donau.xml b/draft-donau.xml
@@ -173,7 +173,7 @@
<figure>
<artwork type="abnf"><![CDATA[
; Scheme and high-level structure
- scheme = "donau" / "DONAU" / "donau+http" / "DONAU+HTTP"
+ scheme = "donau" / "donau+http"
donau-URI = scheme "://" base "?" year-param "&"
taxid-param "&" salt-param
("&" total-param "&" sig-param)?
@@ -183,15 +183,15 @@
; three path segments (year, taxid-enc, salt) is part of the base.
base = 1*( ALPHA / DIGIT / "-" / "." / ":" / "/" / "_" )
- year-param = [ "year" / "YEAR" ] "=" year
+ year-param = [ "year" ] "=" year
- tax-id-param = [ "id" / "ID" ] "=" tax-id-enc
+ tax-id-param = [ "id" ] "=" tax-id-enc
- salt-param = [ "salt" / "SALT" ] "=" salt
+ salt-param = [ "salt" ] "=" salt
- total-param = [ "total" / "TOTAL" ] "=" amount
+ total-param = [ "total" ] "=" amount
- signature-param = [ "sig" / "SIG" ] "=" algo ":" signature
+ signature-param = [ "sig" ] "=" algo ":" signature
; Path parameters
year = DIGIT DIGIT DIGIT DIGIT
@@ -221,13 +221,6 @@
<section anchor="semantics">
<name>Semantics</name>
<t>
- Even if RFC3986 <xref target="RFC3986"/> explicitly writes that scheme names
- are case-insensitive, lower and upper case variations are presented here to
- emphasize this possibility. The applications encoding URI in a QR-code can
- benefit from the possibility to encode the URI using only uppercase letters
- which should result in a more compact encoding.
- </t>
- <t>
The base of a Donau URI refers to the base URL of the Donau REST API.
It consists of the network location (host name or IP address) and <bcp14>MAY</bcp14> include
additional path segments (for example, <tt>https://admin.ch/taxes/donau/</tt>)
@@ -809,6 +802,8 @@ Value Encoding Value Encoding Value Encoding Value Encoding
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3986.xml"/>
+ <xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4343.xml"/>
+
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/>
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.5234.xml"/>
@@ -821,7 +816,16 @@ Value Encoding Value Encoding Value Encoding Value Encoding
<xi:include href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8905.xml"/>
-
+ <reference anchor="ISO18004" target="https://www.iso.org/standard/83389.html" quoteTitle="true" derivedAnchor="ISO18004">
+ <front>
+ <title>Information technology - Automatic identification and data capture techniques - QR Code bar code symbology specification</title>
+ <author>
+ <organization showOnFrontPage="true">ISO/IEC</organization>
+ </author>
+ <date month="August" year="2024"/>
+ </front>
+ <seriesInfo name="ISO/IEC" value="18004:2024"/>
+ </reference>
</references>
<references>
@@ -951,6 +955,7 @@ W5WY4SASZQ4CRS427F4WJZJFZMQ5Y4HZNXGY30</tt></li>
<!-- Change Log
v00 2025-10-17 CG Initial version
v01 2025-10-21 EB Including first reviews (motivations + change in URI structure)
+v02 2025-11-XX CG Removed all-caps versions from syntax, pointless since we now need "?" and "&" which are not in the alphanumeric set for QR codes
-->
</back>
</rfc>