marketing

Marketing materials (presentations, posters, flyers)
Log | Files | Refs

commit a182d26ac517695f540fd82c638bb9a311c7f720
parent a840892b84bfaf9ac121868b022b0ff9e96ae8a5
Author: Florian Dold <florian.dold@gmail.com>
Date:   Fri, 25 Sep 2020 14:33:58 +0530

my pass

Diffstat:
Mstandards/rfc8905-in-prep.xml | 67++++++++++++++++++++++++++++++++++++++++++++++++++-----------------
1 file changed, 50 insertions(+), 17 deletions(-)

diff --git a/standards/rfc8905-in-prep.xml b/standards/rfc8905-in-prep.xml @@ -135,12 +135,17 @@ should this artwork element be tagged as <sourcecode>, <t>, or another element? Answer-CG: <t> seems fine to me. Not really source. +Answer-FD: As <t> would cause rendering in variable width font, + I've used sourcecode and moved the "annotation" of the examples above. --> -<artwork name="" type="" align="left" alt=""><![CDATA[ + <t>Valid Example:</t> +<sourcecode><![CDATA[ payto://iban/DE75512108001245126199?amount=EUR:200.0&message=hello - -INVALID (authority missing): payto:iban/12345 -]]></artwork> +]]></sourcecode> + <t>Invalid Example (authority missing):</t> +<sourcecode><![CDATA[ +payto:iban/12345 +]]></sourcecode> </section> <section anchor="generic-options" numbered="true" toc="default"> <name>Generic Options</name> @@ -279,7 +284,11 @@ INVALID (authority missing): payto:iban/12345 of the handler. Language tagging and internationalization of options are not supported.</dd> <dt>Example:</dt> - <dd>payto://ach/122000661/1234</dd> + <dd> +<sourcecode><![CDATA[ +payto://ach/122000661/1234 +]]></sourcecode> + </dd> <dt>Contact:</dt> <dd>N/A</dd> <dt>References:</dt> @@ -311,7 +320,10 @@ Answer-CG: handler. Language tagging and internationalization of options are not supported.</dd> <dt>Example:</dt> - <dd>payto://bic/SOGEDEFFXXX + <dd> +<sourcecode><![CDATA[ +payto://bic/SOGEDEFFXXX +]]></sourcecode> </dd> <dt>Contact:</dt> <dd>N/A</dd> @@ -331,7 +343,7 @@ Answer-CG: Original: Generally the IBAN allows to unambiguously derive the the associated Business Identifier Code (BIC). -Answer: +Answer-CG: Extended sentence explaining how it is done. But largely this is out of scope of the document. --> @@ -353,7 +365,11 @@ Answer: special characters, i.e., "+?/-:().,'". Language tagging and internationalization of options are not supported.</dd> <dt>Examples:</dt> -<dd><t>payto://iban/DE75512108001245126199</t><t>payto://iban/SOGEDEFFXXX/DE75512108001245126199</t> +<dd> +<sourcecode><![CDATA[ +payto://iban/DE75512108001245126199 +payto://iban/SOGEDEFFXXX/DE75512108001245126199 +]]></sourcecode> </dd> <dt>Contact:</dt> <dd>N/A</dd> @@ -373,7 +389,11 @@ Answer: are defined by the implementation of the handler. Language tags and internationalization of options are not supported.</dd> <dt>Example:</dt> - <dd>payto://upi/alice@example.com?receiver-name=Alice&amp;amount=INR:200 + <dd> +<sourcecode><![CDATA[ +payto://upi/alice@example.com?receiver-name=Alice&amount=INR:200 +]]></sourcecode> + </dd> <dt>Contact:</dt> <dd>N/A</dd> @@ -393,7 +413,10 @@ Answer: the handler. Language tags and internationalization of options are not supported.</dd> <dt>Example:</dt> - <dd>payto://bitcoin/12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu + <dd> +<sourcecode><![CDATA[ +payto://bitcoin/12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu +]]></sourcecode> </dd> <dt>Contact:</dt> <dd>N/A</dd> @@ -434,7 +457,10 @@ Answer: values are defined by the implementation of the handler. Language tags and internationalization of options are not supported.</dd> <dt>Example:</dt> - <dd>payto://void/?amount=EUR:10.5 + <dd> +<sourcecode><![CDATA[ +payto://void/?amount=EUR:10.5 +]]></sourcecode> </dd> <dt>Contact:</dt> <dd>N/A</dd> @@ -603,6 +629,7 @@ Original: [ISO4217] International Organization for Standardization, "ISO 4217 Currency Codes", August 2018. +Answer-FD: Revised the date and title. c) We have updated the date of this reference from "March 2019" to "December 2014" to correspond to the date in the URL provided. Please let us know any @@ -619,6 +646,7 @@ Updated: code (BIC)", ISO 9362, December 2014, <https://www.iso.org/standard/60390.html>. +Answer-FC: That's fine! c) We note that one ISO reference entry includes a URL while two others do not. For consistency, would you like to include URLs for all three ISO @@ -652,6 +680,9 @@ Perhaps: code (BIC)", ISO 9362, December 2014, <https://www.iso.org/standard/60390.html>. +Answer-FD: These links are not canonical links to the standard, but deep links + to the store page where they can be bought. Thus I would + prefer a more canonical link to the ISO Website. d) We note that this reference has an updated version (see https://www.nacha.org/products/2020-nacha-operating-rules-guidelines). Would @@ -663,6 +694,7 @@ Original: Perhaps: [NACHA] Nacha, "2020 NACHA Operating Rules & Guidelines", 2019. +Answer-FD: Updated. e) We see that the wiki cited in this reference was last updated in September 2019. We updated this reference entry accordingly. @@ -676,17 +708,18 @@ Perhaps: [BIP0021] Schneider, N. and M. Corallo, "BIP 0021", September 2019, <https://en.bitcoin.it/w/index.php?title=BIP_0021&oldid=66778>. +Answer-FD: That's fine! --> <reference anchor="ISO4217"> <front> - <title>Currency Codes</title> + <title>Codes for the representation of currencies</title> <author> <organization>International Organization for Standardization</organization> <address> - <uri>http://www.iso.ch</uri> + <uri>http://www.iso.org</uri> </address> </author> - <date month="August" year="2018"/> + <date month="August" year="2015"/> </front> <seriesInfo name="ISO" value="4217"/> </reference> @@ -697,7 +730,7 @@ Perhaps: <author> <organization>International Organization for Standardization</organization> <address> - <uri>http://www.iso.ch</uri> + <uri>http://www.iso.org</uri> </address> </author> <date month="May" year="2013"/> @@ -714,7 +747,7 @@ Perhaps: <uri>https://www.nacha.org/</uri> </address> </author> - <date month="January" year="2017"/> + <date year="2019"/> </front> </reference> @@ -788,7 +821,7 @@ Perhaps: </front> </reference> - <reference anchor="BIC" target="https://www.iso.org/standard/60390.html"> + <reference anchor="BIC" target="https://www.iso.org"> <front> <title>Banking - Baking telecommunication messages - Business identifier code (BIC)</title>