RE: content type for WebDAV request/response bodies, was: [ACL] Access Control Protocol -07 submitted

OK,

to verify my wording, I've done the following:

1) write an XSLT that extracts all XML examples from rfc2518.xml (needs an
XSLT engine with the XSLT 1.1 xsl:document function),

2) write an XSLT that implements the transformation in my proposal (XSLT
1.0).

Results (attached):

1) The RFC2518 DTD has an error in the keepalive element (at least according
to MSXML).

2) Example 8.1.1 in RFC2518 (response) isn't wellformed.

3) Several DTD validation errors were found:

3a) in ordering of lockdiscovery child elements,
3b) in the examples in appendix C (which were supposed to fail).

Question: so *do* we assume that child element ordering is relevant? In
which case, the examples in RFC2518 should be fixed.

Julian

> -----Original Message-----
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Julian Reschke
> Sent: Friday, November 16, 2001 9:42 PM
> To: acl@webdav.org; WebDAV
> Subject: RE: content type for WebDAV request/response bodies, was: [ACL]
> Access Control Protocol -07 submitted
>
>
> Below is an attempt to clarify the role of the DTD fragments:
>
> 19	APPENDICIES
> 19.1	WebDAV XML Document Type Definition Addendum
> All XML elements defined in this Document Type Definition (DTD) belong to
> the XML namespace "DAV:"DAV namespace. This DTD should be viewed as an
> addendum to the DTD provided in [RFC2518], section 23.1.
> Note that WebDAV messages must not be validated using the DTD, as
> WebDAV is
> based on XML namespaces, and the special WebDAV "element ignore" rule
> ([RFC2518], section 23.3.2) applies.
> The following transformations need to be applied to a WebDAV
> message before
> it can be validated using the DTD:
> -	removal of all elements and attributes not defined in
> RFC2518 or this
> specification,
> -	transformation of all remaining elements into elements in
> no namespace.
>
> > -----Original Message-----
> > From: acl-admin@webdav.org [mailto:acl-admin@webdav.org]On Behalf Of
> > Julian Reschke
> > Sent: Tuesday, November 13, 2001 7:43 PM
> > To: Julian Reschke; acl@webdav.org; WebDAV
> > Subject: RE: content type for WebDAV request/response bodies, was: [ACL]
> > Access Control Protocol -07 submitted
> >
> >
> > OK, here's my attempt to clarify it:
> >
> > 10	XML PROCESSING
> >
> > 10.1	Request / response marshalling
> >
> > The XML media type rules as defined in [RFC2376] apply:
> > Servers and clients MUST support the content type "text/xml". When this
> > content type is used, the character set MUST be specified in
> the "charset"
> > parameter unless the character set is "US-ASCII".
> > Servers and clients also SHOULD accept the content type
> "application/xml".
> > For this content type, the "charset" parameter is not required,
> but it is
> > STRONGLY RECOMMENDED to specify it anyway.
> > Request and response bodies MUST be encoded in one of the standard XML
> > encodings ("UTF-8" or "UTF-16") .
> >
> > 10.2	Request / response parsing
> > Implementations of this specification MUST support the XML
> element ignore
> > rule, as specified in Section 23.3.2 of [RFC2518], and the WebDAV XML
> > Namespace  interpretation convention, described in Section 23.4 of
> > [RFC2518]recommendation [REC-XML-NAMES].
> > Note that use of the DAV namespace is reserved for XML elements
> > and property
> > names defined in a standards-track or Experimental IETF RFC.
> >
> > > -----Original Message-----
> > > From: acl-admin@webdav.org [mailto:acl-admin@webdav.org]On Behalf Of
> > > Julian Reschke
> > > Sent: Tuesday, November 13, 2001 7:17 PM
> > > To: acl@webdav.org; WebDAV
> > > Subject: content type for WebDAV request/response bodies, was: [ACL]
> > > Access Control Protocol -07 submitted
> > >
> > >
> > > Hi,
> > >
> > > I'd suggest to extend section 10 to make a few statements about
> > > content type
> > > and encoding of request/responses.
> > >
> > > In particular,
> > >
> > > - MUST support text/xml,
> > >
> > > (because it's what all examples have been using since RFC2518)
> > >
> > > - SHOULD accept application/xml,
> > >
> > > (because it makes more sense than text/xml)
> > >
> > > - when text/xml is used and the encoding is not US-ASCII, the
> > charset MUST
> > > be declared in the content type
> > >
> > > (as per XML media types RFC2376),
> > >
> > > - the bodies MUST be encoded in UTF-8 or UTF-16.
> > >
> > > (because XML processors are not required to support anything else).
> > >
> > >
> > > (of course this is not really an ACL issue, but ACL would be the first
> > > WebDAV spec to clarify this).
> > >
> > > Julian
> > >
> > > > -----Original Message-----
> > > > From: acl-admin@webdav.org [mailto:acl-admin@webdav.org]On
> > Behalf Of Jim
> > > > Whitehead
> > > > Sent: Saturday, November 10, 2001 1:57 AM
> > > > To: acl@webdav.org; WebDAV
> > > > Subject: [ACL] Access Control Protocol -07 submitted
> > > >
> > > >
> > > > I have submitted draft-ietf-webdav-acl-07, the WebDAV Access Control
> > > > Protocol, to the IETF for inclusion in the Internet Drafts
> > directory. It
> > > > should appear there in a few days.
> > > >
> > > > Big thanks are due to Julian Reschke, Stefan Eissing, Keith
> > Wannamaker,
> > > > Dylan Barrell, Tim Ellison, Lisa Dusseault, Greg Stein, and Geoff
> > > > Clemm for
> > > > their review of the -06 specification, and/or comments and
> > > suggestions on
> > > > working drafts between -06 and -07.
> > > >
> > > > This specification can be found at:
> > > >
> > > > http://www.webdav.org/acl/
> > > >
> > > > Specifically:
> > > >
> > > > Text:
> > > > http://www.webdav.org/acl/protocol/draft-ietf-webdav-acl-07.txt
> > > > PDF:
> > > > http://www.webdav.org/acl/protocol/draft-ietf-webdav-acl-07.pdf
> > > > Word (change tracking active):
> > > >
> http://www.webdav.org/acl/protocol/draft-ietf-webdav-acl-07-tracked.doc
> > > HTML:
> > > http://www.webdav.org/acl/protocol/draft-ietf-webdav-acl-07.htm
> > >
> > > - Jim
> > >
> > > _______________________________________________
> > > acl mailing list
> > > acl@webdav.org
> > > http://mailman.webdav.org/mailman/listinfo/acl
> > >
> >
> > _______________________________________________
> > acl mailing list
> > acl@webdav.org
> > http://mailman.webdav.org/mailman/listinfo/acl
> >
>
> _______________________________________________
> acl mailing list
> acl@webdav.org
> http://mailman.webdav.org/mailman/listinfo/acl
>