Previously the DTD defined the named version of many of these special
character references in imported .ent files, meaning that one was free
to use either the named or numeric form.
Is there any plan to implement an analog to this in the schema? IMO this
would greatly ease the process of creating/editing files containing
On Tue, 2007-06-19 at 16:34 -0500, Fox, Michael wrote:
> Be as wildly enthusiastic as you want to be. Crazy for character references, as it were.
> See section 4.1, Character and entity references, in the XML spec at
> -----Original Message-----
> From: Encoded Archival Description List [mailto:[log in to unmask]]On Behalf Of
> Michele Combs
> Sent: Tuesday, June 19, 2007 2:21 PM
> To: [log in to unmask]
> Subject: Re: special characters in EAD (+ federated search)
> I note that Michael's post says that *named* entities are discouraged
> (other than those five). May one assume then that numeric forms are
> valid in XML and may be used with abandon, or at least moderate
> Michele C.
> Fox, Michael wrote:
> > While one can do whatever one wishes in the privacy of one's own
> search engine, I believe that, other than the five specified in the
> standard, named entities such as é are not valid in XML and
> should be avoided for data interchange.
> > Michael Fox
> > -----Original Message-----
> > 1. Special characters should be encoded within XML, using either the
> > named or numeric form - e.g. é or é
> > 2. The named form as preferable when editing and proof-reading the
> > If numeric forms are required by your XML parser of choice, these can
> > substituted for the named versions in en mass prior to parsing.
> Michele R. Combs
> Manuscripts processor
> Special Collections Research Center
> Syracuse University
> Syracuse, NY 13221
John Harrison <[log in to unmask]>
University of Liverpool Library