Schema error for vtodo20 from evolution

View: New views
4 Messages — Rating Filter:   Alert me  

Schema error for vtodo20 from evolution

by Chris Frey-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I'm trying to sync a VTODO item, which gets converted from VTODO format
to xml inside opensync.

Here is the sample data taken from the trace logs:

VTODO, coming from evolution:

BEGIN:VCALENDAR
PRODID:-//Ximian//NONSGML Evolution Calendar//EN
VERSION:2.0
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:/softwarestudio.org/Tzfile/America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:STANDARD
TZNAME:EST
DTSTART:19701101T010000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
TZNAME:EDT
DTSTART:19700314T030000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=3SU;BYMONTH=3
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VTODO
UID:20090505T230708Z-19919-100-1-1@frontdesk
DTSTAMP:20090505T230708Z
SUMMARY:Do forms
PRIORITY:0
CREATED:20090505T230708
LAST-MODIFIED:20090505T230746
DESCRIPTION:Finish forms implementation\n
DUE;TZID=/softwarestudio.org/Tzfile/America/New_York:20090507T230000
DTSTART;TZID=/softwarestudio.org/Tzfile/America/New_York:20090505T200000
CLASS:PUBLIC
PERCENT-COMPLETE:0
SEQUENCE:1
END:VTODO
END:VCALENDAR


The XML that gives the error is:

<?xml version="1.0"?>
<todo>
  <Class>
    <Content>PUBLIC</Content>
  </Class>
  <Created>
    <Content>20090505T230708</Content>
  </Created>
  <DateCalendarCreated>
    <Content>20090505T230708Z</Content>
  </DateCalendarCreated>
  <DateStarted TimezoneID="/softwarestudio.org/Tzfile/America/New_York">
    <Content>20090505T200000</Content>
  </DateStarted>
  <Description>
    <Content>Finish forms implementation
</Content>
  </Description>
  <Due TimezoneID="/softwarestudio.org/Tzfile/America/New_York">
    <Content>20090507T230000</Content>
  </Due>
  <LastModified>
    <Content>20090505T230746</Content>
  </LastModified>
  <Method>
    <Content>PUBLISH</Content>
  </Method>
  <PercentComplete>
    <Content>0</Content>
  </PercentComplete>
  <Priority>
    <Content>0</Content>
  </Priority>
  <ProductID>
    <Content>-//Ximian//NONSGML Evolution Calendar//EN</Content>
  </ProductID>
  <Sequence>
    <Content>1</Content>
  </Sequence>
  <Summary>
    <Content>Do forms</Content>
  </Summary>
  <Timezone TimezoneID="/softwarestudio.org/Tzfile/America/New_York">
    <X-Location>America/New_York</X-Location>
  </Timezone>
  <TimezoneComponent TZComponent="Standard" TimezoneID="/softwarestudio.org/Tzfile/America/New_York">
    <DateTimeStart>19701101T010000</DateTimeStart>
    <TZName>EST</TZName>
    <TZOffsetFrom>-0400</TZOffsetFrom>
    <TZOffsetTo>-0500</TZOffsetTo>
  </TimezoneComponent>
  <TimezoneComponent TZComponent="Daylight" TimezoneID="/softwarestudio.org/Tzfile/America/New_York">
    <DateTimeStart>19700314T030000</DateTimeStart>
    <TZName>EDT</TZName>
    <TZOffsetFrom>-0500</TZOffsetFrom>
    <TZOffsetTo>-0400</TZOffsetTo>
  </TimezoneComponent>
  <TimezoneRule TZComponent="Standard" TimezoneID="/softwarestudio.org/Tzfile/America/New_York">
    <Frequency>YEARLY</Frequency>
    <Count>0</Count>
    <Interval>1</Interval>
    <ByDay>1SU</ByDay>
    <ByMonth>11</ByMonth>
  </TimezoneRule>
  <TimezoneRule TZComponent="Daylight" TimezoneID="/softwarestudio.org/Tzfile/America/New_York">
    <Frequency>YEARLY</Frequency>
    <Count>0</Count>
    <Interval>1</Interval>
    <ByDay>3SU</ByDay>
    <ByMonth>3</ByMonth>
  </TimezoneRule>
  <Uid>
    <Content>20090505T230708Z-19919-100-1-1@frontdesk</Content>
  </Uid>
</todo>


Using vconvert, I get the following error:

# ./vconvert /tmp/todo-invalid2.txt --to-vtodo20
element Timezone: Schemas validity error : Element 'Timezone': This element is not expected. Expected is one of ( Uid, Url, Version ).
ERROR: XMLFormat validation failed.
EXIT_ERROR: osync_converter_invoke: XMLFormat validation failed.
EXIT_ERROR: osync_format_env_convert: XMLFormat validation failed.
Unable to convert data
XMLFormat validation failed.


In which component is the bug? :-)

Thanks,
- Chris


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel

Re: Schema error for vtodo20 from evolution

by Ian Martin-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

> In which component is the bug? :-)
It is in the xmlformart-note schema

the timezone element is commented out and there is no mention of any
other of the Timezone* elements

        <!-- FIXME: Timezone as Root node... like trunk? TOO MANY subnodes...
        <xsd:element maxOccurs="unbounded" minOccurs="0"
name="Timezone" type="Timezone"/>
        -->

Ian

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel

Re: Schema error for vtodo20 from evolution

by Ian Martin-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Of course I meant xmlformat-todo schema

oops!

2009/5/13 Ian Martin <ianmartin@...>:

>> In which component is the bug? :-)
> It is in the xmlformart-note schema
>
> the timezone element is commented out and there is no mention of any
> other of the Timezone* elements
>
>        <!-- FIXME: Timezone as Root node... like trunk? TOO MANY subnodes...
>        <xsd:element maxOccurs="unbounded" minOccurs="0"
> name="Timezone" type="Timezone"/>
>        -->
>
> Ian
>

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel

Re: Schema error for vtodo20 from evolution

by Daniel Gollub-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Wednesday 13 May 2009 10:26:15 am Ian Martin wrote:

> > In which component is the bug? :-)
>
> It is in the xmlformart-note schema
>
> the timezone element is commented out and there is no mention of any
> other of the Timezone* elements
>
>         <!-- FIXME: Timezone as Root node... like trunk? TOO MANY
> subnodes... <xsd:element maxOccurs="unbounded" minOccurs="0"
> name="Timezone" type="Timezone"/>
>         -->

Right, xmlformat-event and xmlformat-todo are still lacking XML-Schema
definition for Timezone. Any volunteers? ;)

Best Regards,
Daniel

--
Daniel Gollub                        Geschaeftsfuehrer: Ralph Dehner
FOSS Developer                       Unternehmenssitz:  Vohburg
B1 Systems GmbH                      Amtsgericht:       Ingolstadt
Mobil: +49-(0)-160 47 73 970         Handelsregister:   HRB 3537
EMail: gollub@...          http://www.b1-systems.de

Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg
http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D

------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
Opensync-devel mailing list
Opensync-devel@...
https://lists.sourceforge.net/lists/listinfo/opensync-devel