xml-dev - RE: new Infoset

["Bullard, Claude L (Len)" <clbullar@ingr.com>]

It will be prudent to close the gaping hole in 
the XML 1.0 spec quickly.  This course of choosing 
"losers" makes it possible for some agency to 
implement an alternative to the namespace that 
is non-interoperable with existing 
APIs that depend on it, thus collapsing a 
rather fragile framework of interlocking 
specifications without abandoning XML legally 
or otherwise.   Loss becomes opportunity.

Ick.

Len Bullard

http://fly.hiwaay.net/~cbullard/lensongs.ram

Ekam sat.h, Vipraah bahudhaa vadanti.
Daamyata. Datta. Dayadhvam.h


-----Original Message-----
From: John Cowan [mailto:cowan@locke.ccil.org]
Sent: Friday, July 28, 2000 8:16 AM
To: Bullard, Claude L (Len)
Cc: xml-dev@xml.org
Subject: RE: new Infoset


On Fri, 28 Jul 2000, Bullard, Claude L (Len) wrote:

> I sense a circularity in which I can have a compliant 
> XML document that does not have a conforming information set.

That is correct.  For example, the document:

	<foo::bar/>

is well-formed but does not have an infoset.

> This ties up
> specifications that normatively reference XML 1.0 and can orphan XML 1.0.

We considered that this behavior is licensed by the following language
in the XML Rec:

# Note: The colon character within XML names is reserved for
# experimentation with name spaces. Its meaning is expected to be
# standardized at some future point, at which point those documents
# using the colon for experimental purposes may need to be updated. 

In the WG's view, the meaning of colon has now been standardized, and
documents using it in non-Namespace-conformant ways deserve to lose.

-- 
John Cowan                                   cowan@ccil.org
C'est la` pourtant que se livre le sens du dire, de ce que, s'y conjuguant
le nyania qui bruit des sexes en compagnie, il supplee a ce qu'entre eux,
de rapport nyait pas.               -- Jacques Lacan, "L'Etourdit"