tms@ansa.co.uk said:
] Having the NS declaration as an attribute of the topmost element to
] use it may help applications which process a tree extracting subtrees
] of a particular namespace.
No, we clearly need to make a distinction between the NS declaration and the
NS itself.
We could also put the Element declaration (content model, attribute list
declaration) as a set of "ghost" attributes within the element itself :
<P xml:cm="#PCDATA A ACRONYM APPLET B BASEFONT BDO BIG BR BUTTON CITE CODE DFN
EM FONT I IFRAME IMG INPUT KBD LABEL MAP OBJECT Q S SAMP SCRIPT SELECT SMALL
SPAN STRIKE STRONG SUB SUP TEXTAREA TT U VAR" xml:attlist="ID ID #IMPLIED;
LANG NAME #IMPLIED; etc..."> ... Funny, no ?
This attibute-based definition for XML namespaces is really bothering me.
Pat.
-- ============================================================== bonhomme@loria.fr | Office : B.228 http://www.loria.fr/~bonhomme | Phone : 03 83 59 30 52 -------------------------------------------------------------- * Serveur Silfide : http://www.loria.fr/projets/Silfide * Projet Aquarelle : http://aqua.inria.fr ==============================================================