Is it 'illegal' to include a GENDER type in vCard 3.0? -


i understand vcard 4.0 introduce commonly used contact property fields (types) gender, anniversary, etc. there no standard way represent these in vcard 3.0 format.

my question should client if vcard 3.0 object contains gender type. make invalid vcard, or clients ignore fields?

some clients add x-gender property. however, since it's extended property, there's no guarantee application reading vcard detect it.

x-gender:male 

source: http://en.wikipedia.org/wiki/vcard#vcard_extensions

you go ahead , include gender property, though it's not part of 3.0 specs. specs if vcard contains property consumer not recognize, consumer must ignore property , continue parsing rest of vcard.


Comments

Popular posts from this blog

monitor web browser programmatically in Android? -

Shrink a YouTube video to responsive width -

wpf - PdfWriter.GetInstance throws System.NullReferenceException -