This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: XHTML to HTML 4


[apologies for the formatting, but I'm using Outlook Web Access, and I don't
have as much control as I'd like.]

Mike, could you please elaborate on what you mean below, about the namespace
prefix not being necessary?  In this case, I think you're incorrect; if
prefixes are being used for the namespaces, then the prefix has to be on
*all* elements in the namespace.  It's only when a *default* namespace is
being used that you don't need to specify it for each element, which does
not appear to be the case below.  So the example given is the same as

<table border="0" cellpadding="0" cellspacing="5px" xmlns="whatever">
   <tr>
      <td>
         <span class="StoryHeadline">b</span>

But is NOT the same as

<html:table border="0" cellpadding="0" cellspacing="5px">
   <tr>
      <td>
         <span class="StoryHeadline">b</span>

In this case, the <table> element would be in the namespace declared for the
html: prefix, but the rest of the elements would not be in any namespace.

David Hunter
MobileQ
david.hunter@mobileq.com
http://www.mobileq.com

-----Original Message-----
From: Mike Brown
To: xsl-list@mulberrytech.com
Sent: 4/6/00 3:37 PM
Subject: Re: XHTML to HTML 4

> I've got an xhtml document similar to this fragment:
> 
>  <html:table border="0" cellpadding="0" cellspacing="5px">
>     <html:tr>
>        <html:td>
>           <html:span class="StoryHeadline">b</html:span>

Namespaces are inherited by element descendants; it shouldn't be
necessary
to use the prefix all the way down, although total disambiguation
of element types isn't harmful.


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]