Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostalInfo::info_type can be an enum #69

Open
nrempel opened this issue Jan 26, 2022 · 1 comment
Open

PostalInfo::info_type can be an enum #69

nrempel opened this issue Jan 26, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@nrempel
Copy link
Collaborator

nrempel commented Jan 26, 2022

https://datatracker.ietf.org/doc/html/rfc5733#section-3.2.1

One or two contact:postalInfo elements that contain postal-
address information. Two elements are provided so that address
information can be provided in both internationalized and
localized forms; a "type" attribute is used to identify the two
forms. If an internationalized form (type="int") is provided,
element content MUST be represented in a subset of UTF-8 that can
be represented in the 7-bit US-ASCII character set. If a
localized form (type="loc") is provided, element content MAY be
represented in unrestricted UTF-8. The contact:postalInfo
element contains the following child elements:

@nrempel nrempel added the enhancement New feature or request label Jan 26, 2022
@djc
Copy link
Collaborator

djc commented Jan 27, 2022

Ah, that's a a good bit more complex than what we have now. So if I understand correctly:

  • There might be two postalInfos, not just one (as we have now)
  • If type = int the content must be representable in ASCII
  • If type = loc the content may use all of UTF-8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants