Re: dateTime.iso8601 format

>  <int></int> is not valid. Conforming libs should refuse it.

There's a bit of a philosophical question here.  I don't see it being
really important for an XML-RPC communicant to reject incorrect
XML-RPC.  I.e. an XML-RPC recipient should not be the XML-RPC police.
It would not be a disaster if an XML-RPC recipient were to interpret
<int></int> as zero (which I use as an example because it's something
naive code might do).  What's _really_ required is that an XML-RPC
sender never send <int></int>.  And that where an <int> element does
conform, the recipient interpret it as the correct number.

So I consider the standard to be that recipient behavior is undefined
when you send invalid XML-RPC.

-- 
Bryan Henderson                                   San Jose, California

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xml-rpc/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/xml-rpc/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/