All,

During the meeting yesterday I stated that I would send my notes on
jCard to this list to facilitate discussion. Your comments are
encouraged.

The following items are comments and observations I have heard from
various people, etc.

1. Requirements for contact information

  a. There is a need to represent contact information in multiple
languages. This is a separate requirement from tagging the language of
the contact. In other words, it should be possible to have the contact
given in a local language and given in another language. It is my
understanding that jCard supports this.

  b. There should be a way to clearly specify the ISO-3166-1 country
code of a contact. It is my understanding that jCard does not support
this.

2. Issues with jCard

  a. Is fn always required in jCard? There is confusion on this point.

  b. jCard allows for both structured and unstructured addresses, and
this causes quite a lot of problems with clients and leads to many
variations by servers.

  c. If we moved away from jCard, how does that transition work?

3. JSContact - based on the DISPATCH meeting on Monday, it is unclear
if JSContact will be moving forward in the IETF.

-andy

_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext

Reply via email to