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

RE: rfc2518bis DAV DTD (was Re: How to use DTDs, or not ...)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 15 Oct 2003 20:32:48 +0200
To: "Stanley Guan" <stanley.guan@oracle.com>, <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEBKINAA.julian.reschke@gmx.de>

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Stanley Guan
> Sent: Wednesday, October 15, 2003 8:05 PM
> To: w3c-dist-auth@w3.org
> Subject: Re: rfc2518bis DAV DTD (was Re: How to use DTDs, or not ...)
>
>
>
> Julian,
>
> If you're just looking for a schema language for the *formal notation*,
> then any choice will be fine with me :-).
>
> Let me try my best for these questions:
>
> > OK, so *how* do you express the following rules in XML Schema?
> >
> > - in addition to the specified child elements, *any* other element is
> > allowed (at any position!), unless it's specified in RFC2518,
>
> I think, what you need here is
>    <xs:any namespace="##other" processContents="lax"/>
> specified in a "choice" component.

Last time was dicussed I was told that this will not allow new extension
elements from the DAV: namespace.

> A question here: if the server claims that it only supports "versioning",
> but not "acl", is it an error if the user sends  a request to find the
> "DAV:acl" property?

No.

> > - arbitrary properties are allowed
>
> I think, you can collect all server supported DAV: properties in
> a single complexType using "choice" component.  Then, using
> "extension" component to extend different capabilities into the
> final set.

Sorry. I wanted to say "attributes".

> > - ordering is irrelevant
>
> "choice" is the best candidate.  "all" is somewhat limited.

Thanks,

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Wednesday, 15 October 2003 14:33:05 GMT

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