Re: [xml2rfc] <country> in v3

[Brian E Carpenter <[e-mail]>]

On 03-Jan-20 20:36, Julian Reschke wrote:
> On 02.01.2020 20:58, Brian E Carpenter wrote:
>> For some reason, it appears that <country>P.R. China</country> causes problems in v3, but <country>China</country> is OK.
>>
>> The problem I see is that <country> is simply ignored, and <code> is also ignored,
>> when the "P.R" was included.
>>
>> I think there is a similar issue with commas included in <street>.
>>
>> For both, RFC7991 says "Content model: only text content." I don't see that this
>> should exclude punctuation marks.
>>
>> Regards
>>     Brian Carpenter
> 
> xml2rfc wants an "ISO short name" here (see
> <https://www.iso.org/obp/ui#search> for a lookup UI).

I really hope it doesn't "want" an ISO code, since RFC7991 says nothing about
that. It's very convenient that they are available, though.

It takes some cheating to produce:

Dilbert Engineer
Pointy Haired Products LLC
42 Deepinit Street
Mudgrad 7991
Elbonia
Email: [e-mail]

> Another issue here is that it has unintended consequences with respect
> to Taiwanese users, as they would have to use "Taiwan (Province of China)".

That's a serious problem. But they can simply omit <country>.

> IMHO the changes with respect to postal formatting (see
> <https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation-notes-10#section-3.1.13>)
> are overly complex and should be backed out. And yes, I'm saying this
> after having it reverse engineered and partly implemented in my XSLT code.

Fortunately <street> isn't picky, so one can do anything:

    <author fullname="Dilbert Engineer" initials="D." surname="Engineer">
      <organization abbrev="Pointy LLC"/>
      <address>
        <postal>
          <street>Pointy Haired Products LLC</street>
          <street>42 Deepinit Street</street>
          <street>Mudgrad 7991</street>
          <street>Elbonia</street>
          <country/>
        </postal>
        <email>[e-mail]</email>
      </address>
    </author>

Regards
   Brian