Skip to content

XEP-0080: Add "regioncode" element. #1442

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

Merged
merged 2 commits into from
Jul 9, 2025

Conversation

goffi-contrib
Copy link
Contributor

No description provided.

@goffi-contrib
Copy link
Contributor Author

Notes:

  • I'm not one of the author of the XEP.
  • The XEP is stable, but the new field is optional, so it's backward compatible and should be fine to add.

@goffi-contrib
Copy link
Contributor Author

@stpeter this change needs author acceptance, and you're one of them (I don't have the nickname of Joe Hildebrand to ping them too). Would you mind checking it? Thanks!

@stpeter
Copy link
Member

stpeter commented Jun 15, 2025

LGTM. It would be nice to add the mapping to other formats in Table 2. (Alternatively, we could remove the section about mappings, since I expect that some of those formats are obsolete.)

@hildjj do you have opinions?

@hildjj
Copy link

hildjj commented Jun 15, 2025

I have no objection. Are all of the formats in Table 2 obsolete now? Did vCard XML ever get traction?

@goffi-contrib
Copy link
Contributor Author

Thanks for your quick feedback.

XEP-0054 is still in use and even in compliance suite, while several clients have been moving to XEP-0292 (probably supporting both).
To be honest, I don't know how I would map this field to the formats in mapping as at least vCard-XML seems to use free form region, not something standardized such as ISO 3166-2. Maybe removing this entire section is the best thing to do indeed.

@iNPUTmice iNPUTmice merged commit c5d174d into xsf:master Jul 9, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants