Fixes for editorial issues

Hi,

the attachment fixes many editorial issues: 30, 41, 57, 63, 68, 88, 89, 
168, 174, 180, 182, 185, 187.

Hopefully this is useful in reducing the number of open issues, and 
concentrating on non-editorial ones.

Best regards, Julian

Index: draft-ietf-webdav-rfc2518bis-latest.xml
===================================================================
RCS file: /var/cvsroot/xml2rfc/draft-ietf-webdav-rfc2518bis-latest.xml,v
retrieving revision 1.8
diff -r1.8 draft-ietf-webdav-rfc2518bis-latest.xml
21a22,24
> <!-- BZ 168 -->
> <?rfc symrefs="yes"?>
> <?rfc sortrefs="yes"?>
23c26,28
< <rfc ipr="full3978" docName="draft-ietf-webdav-rfc2518bis-08">
---
> <!-- changes for BZ89 all over the place -->
> 
> <rfc ipr="full3978" docName="draft-ietf-webdav-rfc2518bis-latest">
99,100c104,105
<    companion document, <xref target="RFC2291">"Requirements for a Distributed Authoring and 
<    Versioning Protocol for the World Wide Web" (RFC2291)</xref>. 
---
>    companion document, "Requirements for a Distributed Authoring and 
>    Versioning Protocol for the World Wide Web" <xref target="RFC2291"/>. 
104,105c109,110
<    by <xref target="RFC2291">RFC2291</xref>. That work was done in a separate document, 
<    <xref target="RFC3253">"Versioning Extensions to WebDAV" (RFC3253)</xref>. 
---
>    by <xref target="RFC2291"/>. That work was done in a separate document, 
>    "Versioning Extensions to WebDAV" <xref target="RFC3253"/>. 
128c133
<    WebDAV uses <xref target="W3C.REC-xml-20001006">XML</xref> to marshal complicated 
---
>    WebDAV uses <xref target="XML"/> to marshal complicated 
149c154
<    <xref target="RFC2616">RFC2616</xref>, including the rules about 
---
>    <xref target="RFC2616"/>, including the rules about 
152c157
<    section 2.2 of <xref target="RFC2616">RFC2616</xref>, these rules apply to this document as 
---
>    section 2.2 of <xref target="RFC2616"/>, these rules apply to this document as 
158c163
<    this document are to be interpreted as described in <xref target="RFC2119">RFC2119</xref>. 
---
>    this document are to be interpreted as described in <xref target="RFC2119"/>. 
173c178
<    them) are defined in <xref target="RFC3986">RFC3986</xref>. 
---
>    them) are defined in <xref target="RFC3986"/>. 
236,237c241,242
<    properties include cases where a) the value of a property is read-
<    only, maintained by the server, and b) the value of the property is 
---
>    properties include cases where a) the value of a property is read-only,
>    maintained by the server, and b) the value of the property is 
263c268
<    information either in an <xref target="W3C.REC-xml-20001006">XML</xref> 
---
>    information either in an <xref target="XML"/> 
303,304c308,309
<    because of its support for multiple character sets.  XML's self-
<    describing nature allows any property's value to be extended by 
---
>    because of its support for multiple character sets.  XML's self-describing
>    nature allows any property's value to be extended by 
324a330
>   <!-- BZ 174 -->
329c335
<    further XML elements, namespace names that are in scope for that part of 
---
>    further XML elements, namespace declarations that are in scope for that part of 
364c370
<    The XML namespace mechanism, which is based on <xref target="RFC3986">URIs</xref>, is 
---
>    The XML namespace mechanism, which is based on URIs (<xref target="RFC3986"/>), is 
413c419
<   <section title="HTTP URL Namespace Model">
---
>   <section title="HTTP URL Namespace Model" anchor="http.url.namespace.model">
436,437c442,443
<    Although implicit in <xref target="RFC2616">RFC2616</xref> and 
<    <xref target="RFC3986">RFC3986</xref>, any resource, 
---
>    Although implicit in <xref target="RFC2616"/> and 
>    <xref target="RFC3986"/>, any resource, 
451,452c457,458
<    containing collection's URL plus an additional segment for non-
<    collection resources, or additional segment plus trailing slash "/" 
---
>    containing collection's URL plus an additional segment for non-collection
>    resources, or additional segment plus trailing slash "/" 
454c460
<    <xref target="RFC3986">RFC3986</xref>.  
---
>    <xref target="RFC3986"/>.  
569,570c575,576
<    band communication channel to coordinate their work (e.g., face-to-
<    face interaction, written notes, post-it notes on the screen, 
---
>    band communication channel to coordinate their work (e.g., face-to-face
>    interaction, written notes, post-it notes on the screen, 
643,644c649,650
<       and to use the URI form defined by <xref target="RFC4122">A Universally Unique 
<    Identifier (UUID) URN  Namespace</xref>.  However 
---
>       and to use the URI form defined by "A Universally Unique 
>    Identifier (UUID) URN  Namespace" (<xref target="RFC4122"/>).  However 
906,907c912,913
<    a Content-Type if any is known.  If the client supplies a Content-
<    Type value the server MUST set that value (this requirement actually 
---
>    a Content-Type if any is known.  If the client supplies a Content-Type
>    value the server MUST set that value (this requirement actually 
943,944c949,950
<       <t>MOVE a member into the collection, unless it overwrites a pre-
<       existing member </t>
---
>       <t>MOVE a member into the collection, unless it overwrites a pre-existing
>       member </t>
946,947c952,953
<       <t>COPY a member into a collection, unless it overwrites a pre-
<       existing member </t>
---
>       <t>COPY a member into a collection, unless it overwrites a pre-existing
>       member </t>
1111c1117
<    XML parsers that are compliant with <xref target="W3C.REC-xml-20001006">XML</xref> 
---
>    XML parsers that are compliant with <xref target="XML"/> 
1114,1115c1120,1121
<    formed and use namespaces correctly.  If a server receives non-
<    wellformed XML in a request it MUST reject the entire request with a 
---
>    formed and use namespaces correctly.  If a server receives non-wellformed
>    XML in a request it MUST reject the entire request with a 
1185c1191
<    (section 1.6 of <xref target="RFC3253">RFC3253</xref>). The mechanism is appropriate to use with 
---
>    (section 1.6 of <xref target="RFC3253"/>). The mechanism is appropriate to use with 
1277,1278c1283,1284
<    properties (see <xref target="RFC3253">RFC3253</xref> and 
<    <xref target="RFC3744">RFC3744</xref>) 
---
>    properties (see <xref target="RFC3253"/> and 
>    <xref target="RFC3744"/>) 
1582,1583c1588,1589
<    403 (Forbidden): The client has attempted to set a read-
<    only property, such as getetag.  If returning this error, the server
---
>    403 (Forbidden): The client has attempted to set a read-only
>    property, such as getetag.  If returning this error, the server
1707,1708c1713,1714
<    Responses from a MKCOL request MUST NOT be cached as MKCOL has non-
<    idempotent semantics. 
---
>    Responses from a MKCOL request MUST NOT be cached as MKCOL has non-idempotent
>    semantics. 
1840,1841c1846,1847
<    The server MAY return a 4xx status response, rather than a Multi-
<    Status, if the request failed. 
---
>    The server MAY return a 4xx status response, rather than a Multi-Status,
>    if the request failed. 
1844,1845c1850,1851
<    424 (Failed Dependency) errors SHOULD NOT be in the 207 (Multi-
<    Status) response for DELETE.  They can be safely left out because the client will know 
---
>    424 (Failed Dependency) errors SHOULD NOT be in the 207 (Multi-Status)
>    response for DELETE.  They can be safely left out because the client will know 
1848,1849c1854,1855
<    204 (No Content) errors SHOULD NOT be returned in the 207 (Multi-
<    Status).  The reason for this prohibition is that 204 (No Content) 
---
>    204 (No Content) errors SHOULD NOT be returned in the 207 (Multi-Status).  The
>    reason for this prohibition is that 204 (No Content) 
1914c1920
<    As defined in <xref target="RFC2616">RFC2616</xref>, the "PUT method requests that the enclosed 
---
>    As defined in <xref target="RFC2616"/>, the "PUT method requests that the enclosed 
2015a2022
>    <!-- BZ 57 -->
2018c2025
<    consistent namespace at the destination (see <xref target="delete-collections"/>for the 
---
>    consistent namespace at the destination (see <xref target="http.url.namespace.model"/> for the 
2032,2033c2039,2040
<    /a/c/. Similarly, after encountering an error copying a non-
<    collection resource as part of an infinite depth copy, the server 
---
>    /a/c/. Similarly, after encountering an error copying a non-collection
>    resource as part of an infinite depth copy, the server 
2087,2088c2094,2095
<    of the source and destination URLs, appear in the body of the multi-
<    status response. E.g. if a destination resource was locked and could 
---
>    of the source and destination URLs, appear in the body of the multi-status
>    response. E.g. if a destination resource was locked and could 
2298,2299c2305,2306
<    moving /a/c/. Similarly, after encountering an error moving a non-
<    collection resource as part of an infinite depth move, the server 
---
>    moving /a/c/. Similarly, after encountering an error moving a non-collection
>    resource as part of an infinite depth move, the server 
2344,2345c2351,2352
<    of the source and destination URLs, appear in the body of the multi-
<    status response. E.g. if a source resource was locked and could not 
---
>    of the source and destination URLs, appear in the body of the multi-status
>    response. E.g. if a source resource was locked and could not 
2483c2490
<       <t><list style="symbol">
---
>       <t><list style="symbols"><!-- BZ89 -->
2613c2620,2621
<       <t>h
---
>       <!-- BZ88 -->
>       <t>
2630a2639
>       <!-- BZ 30 -->
2674,2675c2683,2684
<           <D:href>urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4<
<           /D:href> 
---
>           <D:href
> >urn:uuid:e71d4fae-5dec-22d6-fea5-00a0c91e6be4</D:href> 
2948,2949c2957,2958
<    IETF RFC process are tokens, but other identifiers SHOULD be Coded-
<    URLs to encourage uniqueness. 
---
>    IETF RFC process are tokens, but other identifiers SHOULD be Coded-URLs
>    to encourage uniqueness. 
3059c3068
<    defined in <xref target="RFC3986">RFC3986</xref>.   
---
>    defined in <xref target="RFC3986"/>.   
3102c3111
<     header defined in section 14.24 of <xref target="RFC2616">RFC2616</xref>.  However the If 
---
>     header defined in section 14.24 of <xref target="RFC2616"/>.  However the If 
3125,3126c3134
<    Note that the absolute-URI production is defined in 
<       <xref target="RFC3986">RFC3986</xref>. 
---
>    Note that the absolute-URI production is defined in <xref target="RFC3986"/>. 
3294,3295c3302,3303
<    its cache.  When dealing with HTTP/1.0 proxies the "Pragma: no-
<    cache" request header MUST be used for the same reason. 
---
>    its cache.  When dealing with HTTP/1.0 proxies the "Pragma: no-cache"
>    request header MUST be used for the same reason. 
3406c3414
<    <xref target="RFC2616">RFC2616</xref>. 
---
>    <xref target="RFC2616"/>. 
3640,3641c3648,3649
<    wire. For example, it is illegal to use a space character or double-
<    quote in a <xref target="RFC3986">URI</xref>.  URIs appearing in PROPFIND or PROPPATCH 
---
>    wire. For example, it is illegal to use a space character or double-quote
>    in a URI.  URIs appearing in PROPFIND or PROPPATCH 
3664c3672
<    <xref target="W3C.REC-xml-20001006">XML</xref>. The 
---
>    <xref target="XML"/>. The 
3675c3683,3684
<   
---
> 
>   <!-- BZ41 -->  
3688d3696
<   </section>
3735a3744
>   </section>
3776c3785
<       <t hangText="Value: ">URI (See section 3.2.1 of <xref target="RFC2616">RFC2616</xref>) </t>
---
>       <t hangText="Value: ">URI (See section 3.2.1 of <xref target="RFC2616"/>) </t>
3811a3821
>   <!-- BZ41 -->
3826d3835
<   </section>
3859a3869
>   </section>
3860a3871
>   <!-- BZ41 -->
3875d3885
<   </section>
3891a3902
>   </section>
3892a3904
>   <!-- BZ41 -->
3911d3922
<   </section>
3915c3926,3927
<       <t hangText="Name: ">locktype</t>
---
>       <!-- BZ63 -->
>       <t hangText="Name: ">response</t>
3936,3937d3947
<   </section>
<   
3961c3971,3972
<    <t hangText="Value: "> status-line (status-line defined in <xref target="RFC2616">RFC2616</xref>
---
>    <!-- BZ 180 -->
>    <t hangText="Value: "> status-line (status-line defined in Section 6.1 of <xref target="RFC2616"/>)
3970a3982,3983
>   </section>
>   
3985a3999
>   </section>
4032a4047
>   <!-- BZ41 -->
4047d4061
<   </section>
4089a4104
>   </section>
4090a4106
>   <!-- BZ41 -->
4107d4122
<   </section>
4153a4169
>   </section>
4179c4195
<    declaration using the format defined in <xref target="W3C.REC-xml-20001006">XML</xref>. 
---
>    declaration using the format defined in <xref target="XML"/>. 
4205c4221
<    <t hangText="Value: ">  date-time (defined in <xref target="RFC3339">RFC3339</xref>, see the ABNF in section 
---
>    <t hangText="Value: ">  date-time (defined in <xref target="RFC3339"/>, see the ABNF in section 
4263c4279
<             <xref target="RFC2616">RFC2616</xref>) </t>
---
>             <xref target="RFC2616"/>) </t>
4287c4303
<    <t hangText="Value: ">content-length (see section 14.14 of <xref target="RFC2616">RFC2616</xref>) </t>
---
>    <t hangText="Value: ">content-length (see section 14.14 of <xref target="RFC2616"/>) </t>
4312c4328
<    <t hangText="Value: ">media-type (defined in section 3.7 of <xref target="RFC2616">RFC2616</xref>) </t>
---
>    <t hangText="Value: ">media-type (defined in section 3.7 of <xref target="RFC2616"/>) </t>
4336c4352
<    <t hangText="Value: ">entity-tag  (defined in section 3.11 of <xref target="RFC2616">RFC2616</xref>) </t>
---
>    <t hangText="Value: ">entity-tag  (defined in section 3.11 of <xref target="RFC2616"/>) </t>
4362c4378
<    <t hangText="Value: ">rfc1123-date  (defined in section 3.3.1 of <xref target="RFC2616">RFC2616</xref>) </t>
---
>    <t hangText="Value: ">rfc1123-date  (defined in section 3.3.1 of <xref target="RFC2616"/>) </t>
4380,4381c4396,4397
<             on any DAV compliant resource that returns the Last-
<             Modified header in response to a GET.  </t>
---
>             on any DAV compliant resource that returns the Last-Modified
>             header in response to a GET.  </t>
4419a4436
>       <!-- BZ 182 -->
4454,4455c4471,4472
<                 <D:href>urn:uuid:f81de2ad-7f3d-a1b2-4f3c
<                         -00a0c91a9d76</D:href> 
---
>                 <D:href
> >urn:uuid:f81de2ad-7f3d-a1b2-4f3c-00a0c91a9d76</D:href> 
4496,4497c4513,4514
<             recognized child elements it should be treated as a non-
<             collection WebDAV-compliant resource. </t>
---
>             recognized child elements it should be treated as a non-collection
>             WebDAV-compliant resource. </t>
4778c4795
<    compliant with <xref target="RFC2616">RFC2616</xref>. 
---
>    compliant with <xref target="RFC2616"/>. 
4801,4802c4818,4819
<    lockdiscovery property, the Time-Out response header and the Lock-
<    Token request header.  A class "2" compliant resource SHOULD also 
---
>    lockdiscovery property, the Time-Out response header and the Lock-Token
>    request header.  A class "2" compliant resource SHOULD also 
4843c4860
<    with the IETF Character Set Policy <xref target="RFC2616">RFC2277</xref>. In this specification, 
---
>    with the IETF Character Set Policy <xref target="RFC2277"/>. In this specification, 
4849c4866
<    encoded, at minimum, using the UTF-8 <xref target="RFC2279">RFC2279</xref> and UTF-16 encodings of 
---
>    encoded, at minimum, using the UTF-8 <xref target="RFC2279"/> and UTF-16 encodings of 
4852c4869
<    Content-Type header, as defined in <xref target="RFC2376">RFC2376</xref>, as well as the XML 
---
>    Content-Type header, as defined in <xref target="RFC2376"/>, as well as the XML 
4860c4877
<    language of its content and attributes. See <xref target="W3C.REC-xml-20001006">XML</xref> for 
---
>    language of its content and attributes. See <xref target="XML"/> for 
4867c4884
<    strongly encouraged to read "XML Media Types" <xref target="RFC2376">RFC2376</xref> for 
---
>    strongly encouraged to read "XML Media Types" <xref target="RFC2376"/> for 
4919,4920c4936,4937
<    <xref target="RFC2616">RFC2616</xref>) and XML (discussed in 
<    <xref target="RFC2376">RFC2376</xref>) also apply to WebDAV. In 
---
>    <xref target="RFC2616"/>) and XML (discussed in 
>    <xref target="RFC2376"/>) also apply to WebDAV. In 
4953c4970
<    <xref target="RFC2069">RFC2069</xref>. Since Digest authentication verifies that both parties to 
---
>    <xref target="RFC2069"/>. Since Digest authentication verifies that both parties to 
5037c5054
<    section 4.2.2 of <xref target="W3C.REC-xml-20001006">XML</xref>, which instruct an XML processor to 
---
>    section 4.2.2 of <xref target="XML"/>, which instruct an XML processor to 
5041,5045c5058,5061
<    used to include XML within the content of an XML document.  For non-
<    validating XML, such as the XML used in this specification, 
<    including an external XML entity is not required by 
<    <xref target="W3C.REC-xml-20001006">XML</xref>.   However, 
<    <xref target="W3C.REC-xml-20001006">XML</xref> does state that an XML processor may, at its 
---
>    used to include XML within the content of an XML document.  For non-validating
>    XML, such as the XML used in this specification, 
>    including an external XML entity is not required by XML.  However, 
>    XML does state that an XML processor may, at its 
5054c5070
<    XML processor to the security risks discussed in <xref target="RFC2376">RFC2376</xref>. 
---
>    XML processor to the security risks discussed in <xref target="RFC2376"/>. 
5074,5075c5090,5091
<    This specification requires the use of <xref target="RFC4122">A Universally 
<    Unique Identifier (UUID) URN Namespace</xref> for lock tokens, in order to guarantee 
---
>    This specification requires the use of "A Universally 
>    Unique Identifier (UUID) URN Namespace" (<xref target="RFC4122"/>) for lock tokens, in order to guarantee 
5129c5145
<     <list style="number">
---
>     <list style="numbers"><!-- BZ89 -->
5159,5160c5175,5176
<    Babich, Sanford Barr, Dylan Barrell, Bernard Chester, Tim Berners-
<    Lee, Dan Connolly, Jim Cunningham, Ron Daniel, Jr., Jim Davis, Keith 
---
>    Babich, Sanford Barr, Dylan Barrell, Bernard Chester, Tim Berners-Lee,
>    Dan Connolly, Jim Cunningham, Ron Daniel, Jr., Jim Davis, Keith 
5204a5221
>   <!-- BZ 185 -->
5206,5223d5222
<     <t>    
<      Editors of RFC2518 
<     </t>
<     
<     <t>
<      Y. Y. Goland 
<      Microsoft Corporation 
<      One Microsoft Way 
<      Redmond, WA 98052-6399 
<      Email: yarong@microsoft.com 
<     </t>
<     <t>
<      E. J. Whitehead, Jr. 
<      Dept. Of Information and Computer Science 
<      University of California, Irvine 
<      Irvine, CA 92697-3425 
<      Email: ejw@ics.uci.edu 
<     </t>
5225,5245c5224,5258
<      A. Faizi 
<      Netscape 
<      685 East Middlefield Road 
<      Mountain View, CA 94043 
<      Email: asad@netscape.com 
<     </t>
<     <t>
<      S. R. Carter 
<      Novell 
<      1555 N. Technology Way 
<      M/S ORM F111 
<      Orem, UT 84097-2399 
<      Email: srcarter@novell.com 
<     </t>
<     <t>
<      D. Jensen 
<      Novell 
<      1555 N. Technology Way 
<      M/S ORM F111 
<      Orem, UT 84097-2399 
<      Email: dcjensen@novell.com 
---
>      Y. Y. Goland, 
>      Microsoft Corporation, 
>      One Microsoft Way, 
>      Redmond, WA 98052-6399. 
>      Email: yarong@microsoft.com. 
>     </t>
>     <t>
>      E. J. Whitehead, Jr., 
>      Dept. Of Information and Computer Science, 
>      University of California, Irvine,
>      Irvine, CA 92697-3425.
>      Email: ejw@ics.uci.edu. 
>     </t>
>     <t>
>      A. Faizi,
>      Netscape, 
>      685 East Middlefield Road, 
>      Mountain View, CA 94043.
>      Email: asad@netscape.com. 
>     </t>
>     <t>
>      S. R. Carter, 
>      Novell, 
>      1555 N. Technology Way, 
>      M/S ORM F111, 
>      Orem, UT 84097-2399. 
>      Email: srcarter@novell.com. 
>     </t>
>     <t>
>      D. Jensen, 
>      Novell, 
>      1555 N. Technology Way, 
>      M/S ORM F111, 
>      Orem, UT 84097-2399. 
>      Email: dcjensen@novell.com. 
5267d5279
<     &w3cXML;
5268a5281,5319
> <!-- BZ68 -->
> <reference anchor="XML" target="http://www.w3.org/TR/2004/REC-xml-20040204">
>   <front>
>     <title>Extensible Markup Language (XML) 1.0 (Third Edition)</title>
>     <author initials="T." surname="Bray" fullname="Tim Bray">
>       <organization>Textuality and Netscape</organization>
>       <address>
>         <email>tbray@textuality.com</email>
>       </address>
>     </author>
>     <author initials="J." surname="Paoli" fullname="Jean Paoli">
>       <organization>Microsoft</organization>
>       <address>
>         <email>jeanpa@microsoft.com</email>
>       </address>
>     </author>
>     <author initials="C.M." surname="Sperberg-McQueen" fullname="C. M. Sperberg-McQueen">
>       <organization>University of Illinois at Chicago and Text Encoding Initiative</organization>
>       <address>
>         <email>cmsmcq@uic.edu</email>
>       </address>
>     </author>
>     <author initials="E." surname="Maler" fullname="Eve Maler">
>       <organization>Sun Microsystems</organization>
>       <address>
>         <email>eve.maler@east.sun.com</email>
>       </address>
>     </author>
>     <author initials="F." surname="Yergeau" fullname="Francois Yergeau">
>       <organization/>
>       <address>
>         <email>francois@yergeau.com</email>
>       </address>
>     </author>
>     <date day="4" month="February" year="2004"/>
>   </front>
>   <seriesInfo name="W3C" value="REC-xml-20040204"/>
> </reference>
>     
5470c5521
<   Extension = path  ; path is defined in section 3.3 of <xref target="RFC3986">RFC3986</xref> 
---
>   Extension = path  ; path is defined in section 3.3 of <xref target="RFC3986"/> 
5476,5477c5527,5528
< <section title="Changes">
<   <section title="Summary of changes from RFC2518">
---
> <!-- BZ 187 -->
> <section title="Summary of changes from RFC2518">
5527c5578
<     
---
> 
5546,5547c5597,5599
<   
<     
---
> 
> <!-- BZ 187 -->
> <section title="Change Log (to be removed by RFC Editor before publication">