Re: [VCARDDAV] vCard format and lack of interoperability

Non standard properties are not for interoperability. They are so that a 
vendor can put their own extension into an object (vCard or iCal) and 
provide what they see as a value added reason to use their product. By 
allowing these non-standard properties and parameters into both iCal and 
vCard it provides a standard way to add vendor value added data that 
will not crash other vendors. The fact it does not crash them, is a 
great sign for vCard and iCal.

And yes - there is always room for improvement.

Doug Royer
DouglasRoyer@gmail.com
714-989-6135
http://SoftwareAndServices.NET

On 11/16/2012 11:19 AM, Alessandro Rossini wrote:
> Dear all,
>
> I performed an empirical study of the interoperability of the vCard format:
>
> http://alessandrorossini.org/2012/11/15/the-sad-story-of-the-vcard-format-and-its-lack-of-interoperability/
>
> This study shows that common contact information is often represented by grouped properties and non-standard properties. These properties are not interoperable and make the import/export of vCard files as well as the synchronisation via CardDAV unreliable.
>
> In my opinion, the IETF should remove grouped properties and non-standard properties from the specification, even if this would break backward compatibility. Moreover, the IETF should add social networking properties to the specification. Finally, the IETF should provide an official validator for vCard files.
>
> Any comments?
>
> Best regards,
> --
> Alessandro Rossini
> http://alessandrorossini.org
> http://twitter.com/alerossini
>
> _______________________________________________
> VCARDDAV mailing list
> VCARDDAV@ietf.org
> https://www.ietf.org/mailman/listinfo/vcarddav
>
>