Re: AND (Another Namespace Dilemma) ... DTD Validation

[Peter Piatko <piatko@research.telcordia.com>]

Suppose another DTD author also fixed the prefix and the prefix just
happened to be the same one you have chosen.  If an author of an instance
document wanted to include elements from both DTD's, he would run into a
"prefix-collision".  Having parameter entities for the prefixes allows him
to override the prefixes in the instance document and avoid the collision.

Thanks,

Peter

P.S. The next obvious question to me is how does one avoid parameter entity
name collisions?  Is this even an issue?

----- Original Message -----
From: <mrossi@csc.com>
To: <xml-dev@lists.xml.org>
Sent: Friday, August 10, 2001 10:20 AM
Subject: Re: AND (Another Namespace Dilemma) ... DTD Validation


> Thanks to all for the helpful tips on parameterization. I should have
> thought of that. :-)
>
> <commentary>Is this level of complexity justified, considering the only
> apparent benefit is the flexibility of specifying an arbitrary namespace
> prefix in an instance? Does an app developer really need such flexibility?
> Does an author? I think not.</commentary>
>
> Fortunately, I have the luxury of mandating that a given prefix be used in
> order to comply with a specification. (You might say pre-fixing the
prefix.
> :-) A luxury of which I will most certainly take advantage. I am glad to
> hear that XML Schema is (XML Schema processors are) more
> namespace-friendly. I can't wait to start developing some right away! :-)
>
> Michael A. Rossi
> Computer Sciences Corporation
> mailto:mrossi@csc.com
> 856-983-4400 x4911
>
>
> ------------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: xml-dev-request@lists.xml.org
>
>