canmove, Confirmed users
2,887
edits
VCard4: Difference between revisions
Jump to navigation
Jump to search
reviewed thru section 6.7.9
(reviewed thru section 6.6.6) |
(reviewed thru section 6.7.9) |
||
| Line 520: | Line 520: | ||
http://microformats.org/wiki/xfn-brainstorming | http://microformats.org/wiki/xfn-brainstorming | ||
=== section 6.7. Explanatory Properties === | |||
Sounds more like a miscellaneous section. | |||
Organizationally I'm not sure this makes much sense. Most of these apply to the vCard object as a whole and are perhaps identity related and could be grouped into section 6.2. | |||
=== section 6.7.1. CATEGORIES === | |||
6.7.1. CATEGORIES | |||
Nice to see this section/semantic upgraded to mention tags. | |||
Suggestion: explicitly allow URIs as text values to represent specifically scoped tags, with the last path segment of the URI representing the "keyword" of the tag, as specified by the rel-tag specification http://microformats.org/wiki/rel-tag | |||
=== section 6.7.2. NOTE === | |||
Seems fine, compatible with vCard3. | |||
=== section 6.7.3. PRODID === | |||
This seems fine. In practice this is not used much. | |||
=== section 6.7.4. REV === | |||
6.7.4. REV | |||
Seems fine, compatible with vCard3. | |||
Would be nice to allow whole dates as well (without time). | |||
=== section 6.7.5. SOUND === | |||
6.7.5. SOUND | |||
Seems fine, compatible with vCard3. | |||
=== section 6.7.6. UID === | |||
6.7.6. UID | |||
Seems fine, compatible with vCard3. Nice improvement to use URI. | |||
=== section 6.7.7. CLIENTPIDMAP === | |||
6.7.7. CLIENTPIDMAP | |||
Lacking an example with a use-case, this property should be dropped. | |||
=== section 6.7.8. URL === | |||
6.7.8. URL | |||
Seems fine, compatible with vCard3. | |||
=== section 6.7.9. VERSION === | |||
6.7.9. VERSION | |||
Seems fine, compatible with vCard3. Not used much in practice. | |||