W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2001

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

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 13 Nov 2001 19:43:14 +0100
To: "Julian Reschke" <julian.reschke@gmx.de>, <acl@webdav.org>, "WebDAV" <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCOEEDDHAA.julian.reschke@gmx.de>
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
>
Received on Tuesday, 13 November 2001 13:43:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:59 GMT