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

VCard 4.0 TEL is always set as text #2

Open
pcarana opened this issue Nov 7, 2017 · 1 comment
Open

VCard 4.0 TEL is always set as text #2

pcarana opened this issue Nov 7, 2017 · 1 comment

Comments

@pcarana
Copy link
Contributor

pcarana commented Nov 7, 2017

Migrated from NICMx/rdap-server#41:

This issue is merely an observation based on the RFC 6350 section 6.4.1. It's stated that for the TEL property "Value type: By default, it is a single free-form text value (for backward compatibility with vCard 3), but it SHOULD be reset to a URI value. It is expected that the URI scheme will be "tel", as specified in [RFC3966], but other schemes MAY be used". The server uses this property for the distinct phones that a VCard could have (cellphone, voice, fax) as seen at mx.nic.rdap.server.renderer.json.VCardJsonWriter functions getVoice(String), getCellphone(String), getFax(String).

The functions use "text" as value type, this isn't incorrect just as is mentioned in the RFC to allow backward compatibility, but the same text states that version 4.0 SHOULD use a URI value not a TEXT value. So, taking this to an example (based from RFC 7095 appendix B.1, if I have this number:
+1.1234567x890

I SHOULD expect that VCard v4.0 will display it as:
tel:+1-1234567;ext=890

@pcarana
Copy link
Contributor Author

pcarana commented Nov 7, 2017

The recommendation is to set VCard objects using ez-vcard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant