[time-secfrac]

   Numeric offsets are calculated as local time minus UTC (Coordinated
   Universal Time).  So the equivalent time in UTC can be determined by
   subtracting the offset from the local time.  For example, 18:50:00-
   04:00 is the same time as 22:58:00Z.

   If the time in UTC is known, but the offset to local time is unknown,
   this can be represented with an offset of "-00:00".  This differs
   from an offset of "Z" which implies that UTC is the preferred
   reference point for the specified time.
















 
RFC 2518                         WEBDAV                    February 1999


23.3 Appendix 3 - Notes on Processing XML Elements

23.3.1 Notes on Empty XML Elements

   XML supports two mechanisms for indicating that an XML element does
   not have any content.  The first is to declare an XML element of the
   form .  The second is to declare an XML element of the form
   .  The two XML elements are semantically identical.

   It is a violation of the XML specification to use the  form if
   the associated DTD declares the element to be EMPTY (e.g., <!ELEMENT
   A EMPTY>).  If such a statement is included, then the empty element
   format,  must be used.  If the element is not delcared to be
   EMPTY, then either form  or  may be used for empty
   elements.

   23.3.2 Notes on Illegal XML Processing

   XML is a flexible data format that makes it easy to submit data that
   appears legal but in fact is not.  The philosophy of "Be flexible in
   what you accept and strict in what you send" still applies, but it
   must not be applied inappropriately.  XML is extremely flexible in
   dealing with issues of white space, element ordering, inserting new
   elements, etc.  This flexibility does not require extension,
   especially not in the area of the meaning of elements.

   There is no kindness in accepting illegal combinations of XML
   elements.  At best it will cause an unwanted result and at worst it
   can cause real damage.

23.3.2.1  Example - XML Syntax Error

   The following request body for a PROPFIND method is illegal.

   <?xml version="1.0" encoding="utf-8" ?>
   <D:propfind xmlns:D="DAV:">
     
     <D:propname/>
   </D:propfind>

   The definition of the propfind element only allows for the allprop or
   the propname element, not both.  Thus the above is an error and must
   be responded to with a 400 (Bad Request).









 
RFC 2518                         WEBDAV                    February 1999


   Imagine, however, that a server wanted to be "kind" and decided to
   pick the allprop element as the true element and respond to it.  A
   client running over a bandwidth limited line who intended to execute
   a propname would be in for a big surprise if the server treated the
   command as an allprop.

   Additionally, if a server were lenient and decided to reply to this
   request, the results would vary randomly from server to server, with
   some servers executing the allprop directive, and others executing
   the propname directive. This reduces interoperability rather than
   increasing it.

23.3.2.2  Example - Unknown XML Element