> I was rather referring to the inability to give the same name to distinct
> things:...  Backed by a stronger
> validation formalism, though, they can have the same GI.

Wonderful, now parsers will not be confused, only people.
.
I have never fought too hard against the "explicit-name for
explicit-model" restriction, because I have watched too many
newbies (technical newbies, they knew their content) finally
realize, because of an XML restriction, that they had, sometimes
for years, conflated several different nouns/meanings and caused
themselves confusion.

> The practice of the XML community has been overwhelmingly to grant the
> GI fundamental importance: fulminating against this sociological fact
> will not make it go away.

And the harm in requiring more precision in an XML document than
I need in casual conversation is what exactly?

--Debbie

-- 
======================================================================
Deborah Aleyne Lapeyre               mailto:dalapeyre@[...].com
Mulberry Technologies, Inc.                http://www.mulberrytech.com
17 West Jefferson Street                    Direct Phone: 301/315-9633
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
----------------------------------------------------------------------
   Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================

-----------------------------------------------------------------
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 subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>