[
Lists Home |
Date Index |
Thread Index
]
On Fri, Feb 04, 2005 at 12:57:01PM -0800, Jeff Rafter wrote:
>>At present, there's no apparent activity targeted toward providing an
>>alternate entity-definition mechanism.
>
>Maybe XInclude? I guess it would depend on the use case...
I guess it would.
XInclude can't define anything like named character entities. Nothing
defined by XInclude can appear in an attribute.
This becomes significant, for instance, in working groups, where it's
relatively straightforward to define the URL of the spec as an entity, which
can then appear in attribute or text nodes.
XSLT for inclusions is ... moderate overkill, let's say. In any event, it
needs some "reserved characters" concept to operate upon, if what you're
doing can happen inside attributes as well as text nodes.
Almost all of this has to do with authoring, for folks who actually don't
mind (or even like, frightening as that may be) pointy brackets and
ampersands. If you're pipelining it and running it through all sorts of
cool transformations and in general ignoring the folks who *like* editing
XML in text editors, then entities very likely do "blow."
Amy!
--
Amelia A. Lewis amyzing {at} talsever.com
And now someone's on the telephone, desperate in his pain;
someone's on the bathroom floor, doing her cocaine;
someone's got his finger on the button in some room--
no one can convince me we aren't gluttons for our doom.
-- Indigo Girls
|
