VCard4: Difference between revisions

1,357 bytes added ,  17 August 2010
→‎draft 13 section by section review: section 4.1, 4.4, 5.1, 5.4, 5.5 (reviewed thru end of section 5)
(added draft 13 section by section review comments section, and 3.1 editorial comment)
(→‎draft 13 section by section review: section 4.1, 4.4, 5.1, 5.4, 5.5 (reviewed thru end of section 5))
Line 66: Line 66:
Suggestion: use "NOTE" property instead.
Suggestion: use "NOTE" property instead.


=== section 4.1 ===
4.1.  TEXT
Editorial comment:
Examples use "DESCRIPTION" property - which is not in vCard.
Suggestion: use "NOTE" property instead.
=== section 4.4 ===
4.4.  BOOLEAN
Editorial comment:
TYPO:
"boolean": The "boolean" value type is used to express boolen values.
Should be:
"boolean": The "boolean" value type is used to express boolean values.
=== section 5.1 ===
5.1.  LANGUAGE
Editorial comment:
Please provide a simple example use of the LANGUAGE property parameter, e.g.
<pre><nowiki>
ROLE;LANGUAGE=en:teacher
ROLE;LANGUAGE=tr:hoca
See below ALTID property parameter for how associate these two ROLE properties as being alternatives for the same property instance.
</nowiki></pre>
=== section 5.4 ===
5.4.  PREF
Preferred value between 1 and 100 seems a bit arbitrary.
What is the use-case for this?
Also, from a synchronization perspective, picking absolute numbers for indicating preference would seem to make little sense, as the values themselves only make sense relative to other values.
Suggestion: drop this property parameter - it seems like a bad design, and unnecessary.
=== section 5.5 ===
5.5.  ALTID
This seems like a good mechanism for publishing multilingual alternatives on a per-property basis.
I'm interested to see how implementations support this, but overall optimistic about its potential.


== related ==
== related ==
* [[Standards]]
* [[Standards]]
canmove, Confirmed users
2,675

edits