19c19
<     <date month="August" year="2001" />
---
>     <date month="June" year="2001" />
90,91c90
<   instance of dates). Servers that support searching can also take advantage
<   of known data types when doing comparisons and sorting.
---
>   instance of dates).
115c114
<   WebDAV <xref target="RFC2518" /> and for properties of type
---
>   WebDAV <xref target="RFC2518" /> and related standards and properties of type
122,132d120
< <t>
< 	Note that a particular property can be typed for a number of reasons:
<   <list style="symbols">
<   	<t>The property is a live property with server-defined semantics and
<     value space.</t>
<     <t>The property may have been set using a non-WebDAV protocol that the
<     server understands in addition to WebDAV.</t>
<     <t>The type may have been specified in an extended PROPPATCH method
<     as defined in <xref target="METHOD_PROPPATCH" />.</t>
<   </list>  
< </t>
135c123
< <section title="Changes for PROPPATCH method" anchor="METHOD_PROPPATCH">
---
> <section title="Changes for PROPPATCH method">
169c157
<        </D:prop>
---
>         </D:prop>
216c204
<        </D:prop>
---
>         </D:prop>
234c222
<          <D:responsedescription>Does not parse as xs:boolean</D:responsedescription>
---
>          <D:responsedescription>Does not parse as xsd:boolean</D:responsedescription>
243,292d230
< <t>
< 	Note that similar error conditions can occur in the standard WebDAV protocol
<   even though no data type was specified: for instance, when a client tries to set
<   a live property for which only a certain value space is allowed.
< </t>
< </section>
< 
< <section title="Example for succesful PROPPATCH where type information was not preserved">
< <figure><preamble>
<    >>Request</preamble>
< <artwork><![CDATA[
<    PROPPATCH /bar.html HTTP/1.1
<    Host: www.foo.com
<    Content-Type: text/xml
<    Content-Length: xxxx
< 
<    <D:propertyupdate xmlns:D="DAV:"
<       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<       xmlns:Z="http://www.w3.com/standards/z39.50">
<      <D:set>
<        <D:prop>
<          <Z:released xsi:type="Z:custom">t</Z:released>
<        </D:prop>
<      </D:set>
<    </D:propertyupdate>
< ]]></artwork></figure>
< <figure><preamble>
<    >>Response</preamble>
< <artwork><![CDATA[
<    HTTP/1.1 207 Multi-Status
<    Content-Type: text/xml
<    Content-Length: xxxx
< 
<    <D:multistatus xmlns:D="DAV:"
<       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
<       xmlns:Z="http://www.w3.com/standards/z39.50">
<      <D:response>
<        <D:href>http://www.foo.com/bar.html</D:href>
<        <D:propstat>
<          <D:prop><Z:released/></D:prop>
<          <D:status>HTTP/1.1 200 OK</D:status>
<         </D:propstat>
<      </D:response>
<    </D:multistatus>
< ]]></artwork></figure>
< <t>
<   In this case the request succeeded, but the server did not know how to
<   handle the data type "Z:custom". Therefore no data type information was
<   returned in the response body.
< </t>
304c242
<     <t>The property's data type MUST not be defined in <xref target="RFC2518" />
---
>     <t>The property's data type MUST not defined in <xref target="RFC2518" />