No, and yes.
>2) Is there some standard way to declare an ENTITY that includes an array
>of values? To be specific, I'd like to include a list of values in a
>document so my parser can build a SELECT menu of OPTIONS.
No, but you could have an entity whose value was
<option value='1'>foo <option value='2'>bar etc..
>3) Does anyone have an opinion on how &entities; can best be used with a
>database application? For example, assume you declare in your DTD a list
>of &entities;, one for each database field name/value. If we are to
>expect browsers to parse an xml document with entities, how can a found
>table or hit list of values get substituted?
I'm not sure entities are the way to go for this. WHy not just generate
your HTML or XML on the fly the way any number of excellent products
do right now? -Tim