- From: Marcos Cáceres <notifications@github.com>
- Date: Mon, 30 Apr 2018 00:18:52 -0700
- To: w3c/payment-request <payment-request@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/payment-request/pull/690/review/116209955@github.com>
marcoscaceres commented on this pull request. > + <li>Two <a>code points</a> that match an [[!ISO3166-1]] + alpha-2 country code. + </li> + <li>A single U+002D (-) <a>code point</a>. + </li> + <li>One, two, or three <a data-cite= + "INFRA#ascii-alphanumeric">ASCII alphanumeric</a> code + points, in any order. + </li> + </ul> + </div> + </li> + <li>Set <var>address</var>.<a>[[\regionCode]]</a> to + <var>regionCode</var>. + </li> + <li>Let <var>region</var> be the corresponding <a>country > As a web developer I would expect regionCode to be "CA" for California, not "US-CA" With the information I have at the moment, I'm leaning towards just returning the ISO3166-2 format. It might save us from having to deal with special cases where there is ambiguity, but I also don't know if there are any. I'll try to do a bit more reading. > I'm not sure if there are exceptions to cutting off the first 3 characters in order to get the region code specific to the country. I don't think there are, from my reading of the ISO3166-2 spec. But I'll take a closer look as it's been a few weeks. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/payment-request/pull/690#discussion_r184922398
Received on Monday, 30 April 2018 07:19:19 UTC