RE: [xml-dev] What is the rule for parsing XML in a namespace inside HTML?

["Bullard, Claude L (Len)" <len.bullard@intergraph.com>]

All good.  How about this:

<?Mapping XmlNamespace="stat" ClrNamespace="WiseOwl.Statistics"
                              Assembly="WiseOwl.Statistics.Library" ?>
<Window xmlns="http://schemas.microsoft.com/2003/xaml"; Visible="true">
    <SimpleText Foreground="DarkRed" FontSize="14">Hello World!</SimpleText>
    <stat:PoissonDeviate Mean="5.0" />
</Window>

I would still expect a namespace declaration for the stat namespace. 
I've no objection to the mapping PI given that it has to tie 
together three pieces of information.  I realize that the colon 
isn't doing that much, but again, expectations are set.  Care 
to comment on the implications of the above with respect to 
interoperability (yes, the example is a user extension, so 
interoperability is dicey at best).

len



From: Joshua Allen [mailto:joshuaa@microsoft.com]

... going with whatever works best for
the user and can get consensus among browser vendors, rather than doing
user-hostile things in the name of purity to some random irrelevant
spec.  In fact, the Hyatt discussion has morphed in a sense into a
discussion about namespaces in HTML [1], and the remarkable thing is
that *none* of these people are suggesting the facist route of "force
the whole world to use XHTML and only then will it work!".  That's a
good sign, IMO.