Bureaucrats, canmove, Confirmed users
2,888
edits
VCard4: Difference between revisions
Jump to navigation
Jump to search
→high level proposal for improving vCard4: a bit more overview
(→high level proposal for improving vCard4: note GEDCOM as another source for genealogy properties) |
(→high level proposal for improving vCard4: a bit more overview) |
||
| Line 24: | Line 24: | ||
Based on a thorough section by section review, the changes and feedback I have for vCard4 draft 13 fall into a general outline as follows: | Based on a thorough section by section review, the changes and feedback I have for vCard4 draft 13 fall into a general outline as follows: | ||
1. Explicitly state as a goal to have vCard4 be reasonably backward compatible (i.e. with current implementations) of vCard3, both syntactically, and from a schema perspective (e.g. don't mess with structure of properties like N). This kind of practical backward compat enabled publishers to start posting vCard3 even when most consuming applications still only supported vCard2.1. | 1. Explicitly state as a goal to have vCard4 be reasonably backward compatible (i.e. with current implementations) of vCard3, both syntactically, and from a schema perspective (e.g. don't mess with structure of properties like N). This kind of practical backward compat enabled publishers to start posting vCard3 even when most consuming applications still only supported vCard2.1. The presence of vCard3 data then encouraged consuming applications over time to adopt it as well. I'd like to see the same successful adoption occur for | ||
vCard4. | |||
2. Keep the vCard4 core set of properties down to a minimum that has been well established either in: | 2. Keep the vCard4 core set of properties down to a minimum that has been well established either in: | ||
| Line 30: | Line 31: | ||
* Current well adopted mature RFCs (e.g. IMPP) | * Current well adopted mature RFCs (e.g. IMPP) | ||
* Common additions by OpenID / Portable Contacts that have seen adoption (e.g. SEX/GENDER, LANGUAGE, ACCOUNTS) | * Common additions by OpenID / Portable Contacts that have seen adoption (e.g. SEX/GENDER, LANGUAGE, ACCOUNTS) | ||
I believe this too will encourage better vCard4 adoption. | |||
3. Drop other new vCard4 properties from the core and if they seem to make sense, move them to extension specifications instead where they can prove themselves out, e.g.: | 3. Drop other new vCard4 properties from the core and if they seem to make sense, move them to extension specifications instead where they can prove themselves out, e.g.: | ||