Paul Prescod paul at
Tue May 11 19:45:00 BST 1999

John Cowan wrote:
> I remain unreconstructed.
> If we are to have validatable ENTITY/ENTITIES attributes, then
> we must have unparsed entity declarations as well.  Either
> lose both or keep both, say I.


Well, I am perfectly happy to lose ENTITY/ENTITIES and while we're at it
ID/IDREF. URLs and XPointers can do both jobs better. Let's keep our
layers clean and separate!


Even so, I don't follow your argument. The schema needs to validate that
there is a unparsed entity with a particular name. Why does the
declaration have to be done in the schema?

It makes perfect sense to me that a *document* should declare what
external resources it needs (through a URL or entity declaration) and that
the *schema* would verify that an element that is supposed to reference a
resource actually does (whether through a URL or entity).

Your argument seems analgous to arguing that IDs should indirect through
an "ID object" in the schema. Entities and IDs are a type of object that
are tied to a document. Constraints on them apply to a class of documents.
The former should go in a document and the latter in a schema.

 Paul Prescod  - ISOGEN Consulting Engineer speaking for only himself

And so, in one of history's little ironies, the global triumph of bad
software in the age of the PC was reversed by a surprising combination
of forces: the social transformation initiated by the network, a
long-discarded European theory of political economy, and a small band
of programmers throughout the world mobilized by a single simple idea. 

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list