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

RE: another RFC issue: value of GETETAG property

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 21 Nov 2001 00:58:26 +0100
To: "Daniel Brotsky" <dbrotsky@adobe.com>, <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEBEDIAA.julian.reschke@gmx.de>
> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Daniel Brotsky
> Sent: Tuesday, November 20, 2001 9:34 PM
> To: w3c-dist-auth@w3.org
> Subject: another RFC issue: value of GETETAG property
>
>
> The RFC says
>
> 13.6 getetag Property
>
>     Name:       getetag
>     Namespace:  DAV:
>     Purpose:    Contains the ETag header returned by a GET without
>     accept headers.
>     Description: The getetag property MUST be defined on any DAV
>     compliant resource that returns the Etag header.
>     Value:      entity-tag  ; defined in section 3.11 of [RFC2068]
>
>     <!ELEMENT getetag (#PCDATA) >
>
> Unfortunately, the example in section 8.1.1 (page 27) says
>
>                      <D:getetag>
>                           zzyzx
>                      </D:getetag>
>
> which is not a valid etag.  (Etags are quoted-strings, or
> quoted-strings preceded by the literal W/.)  But fixing this example
> raises one of those classic "XML-ification" issues: should it be
>
> <D:getetag>"zzyzx"</D:getetag>
>
> or
>
> <D:getetag>&quot;zzyzx&quot;</D:getetag>

It doesn't matter. Same XML Infoset.

> and how about
>
> <D:getetag>&quot;zzyzx"</D:getetag>

Same again.

> Can we get this issue listed and can someone (I vote for Julian :^)
> resolve it and also explain to idiots like me where &-entities are
> required to be used, where they are allowed to be used, and what

You don't need "&quot;", unless you are in the content of an attribute value
which uses double quotes.

> clients should do with them if their parser can't be told to do
> entity elimination???

My XML parser resolves them for me (Xerces). Which parser do you use?

Julian
Received on Tuesday, 20 November 2001 18:58:59 GMT

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