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

RE: How to use DTDs, or not to (was: RE: ACL and lockdiscovery)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 17 Oct 2003 20:35:15 +0200
To: "Lisa Dusseault" <lisa@xythos.com>, <dennis.hamilton@acm.org>, "'Julian Reschke'" <julian.reschke@gmx.de>, "'Geoffrey M Clemm'" <geoffrey.clemm@us.ibm.com>, <w3c-dist-auth@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCMEHCINAA.julian.reschke@gmx.de>

> From: Lisa Dusseault [mailto:lisa@xythos.com]
> Sent: Saturday, October 18, 2003 8:15 AM
> To: dennis.hamilton@acm.org; 'Julian Reschke'; 'Geoffrey M Clemm';
> w3c-dist-auth@w3.org
> Subject: RE: How to use DTDs, or not to (was: RE: ACL and lockdiscovery)
>
>
> > > ...
> > > 	(a) the ANY case in an element markup declaration means
> > any element
> > > that is declared in the DTD, not some undeclared or unspecified
> > > element. ...
> >
> > Thanks for the reminder. I had forgotten about that. It
> > basically means that by definition you can't express the
> > content model of <prop> using a DTD.
>
> So does this mean we should simply remove the DTD-style definition of
> the 'prop' element (as well as 'owner' and 'resourcetype') from the
> spec?  I believe the natural-language specification should be
> sufficient to define these anyway.

The drawback would be that this would break the DTD's syntax. An alternative
is to keep ANY, and make sure that the description says what this actually
means.

> The 'owner' element could maybe be defined as MIXED but 'prop' and
> 'resourcetype' cannot be mixed.

Yes.

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 17 October 2003 14:35:56 GMT

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