On Wednesday 13 February 2008 12:39, Simon Josefsson wrote:
> After tracking down a phone bug (?) when mixing vcard21+vevent20, see
> [1], I now have syncing of calendar and contacts working. However,
> msynctool prints out several errors:
>
> element Count: Schemas validity error : Element 'Count': This element
> is not expected. Expected is ( Frequency ). element Count: Schemas
> validity error : Element 'Count': This element is not expected.
> Expected is ( Frequency ). element Count: Schemas validity error :
> Element 'Count': This element is not expected. Expected is (
> Frequency ). element Count: Schemas validity error : Element 'Count':
> This element is not expected. Expected is ( Frequency ). element
> Count: Schemas validity error : Element 'Count': This element is not
> expected. Expected is ( Frequency ). element Completed: Schemas
> validity error : Element 'Completed': This element is not expected.
> Expected is one of ( Comment, Contact, Created, DateCalendarCreated,
> DateEnd, DateStarted ). element Url: Schemas validity error : Element
> 'Url', attribute 'Location': The attribute 'Location' is not allowed.
>
> How important are these?
I think these warnings are caused by a wrong conversion from vcal to
xml. Can you please create tickets on opensync.org (componenet:
vformat)? I need the vevents and vcards which cause these errors.
> I understand the phone is probably not following the standards here.
> For example, the last error is caused by a vcard that looks like:
>
> BEGIN:VCARD
> VERSION:3.0
> N:Foo;Bar;;;
> REV:20080207T183307Z
> TEL:+123
> URL;TYPE=HOME:http://example.org/
> END:VCARD
>
> Should the library/tools be extended to handle these "extensions"?
As you already said your phone is not RFC2426 compatible.
<snip>
;For name="URL"
param = ""
; No parameters allowed
value = uri
<snip>
Nevertheless the conversion seems to be correct.
Best regards
Christopher
--
Christopher Stender, R&D Team Mobile Devices
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
|
