sure... but it`s better to use custom elements with your own namespace
to avoid interferention

also i am usually perform 2 xslt transformations:

first is any xml to academic xhtml
second is xhtml from first stage to result xhtml (to separate logic
layer from design layer)

On Tue, Sep 1, 2009 at 10:19 PM, max toro q<maxtoroq@g...> wrote:
> Hello list,
> Lately I've been using a different pattern that helps me separate the
> HTML from XSLT.
>
> The simplest example would be:
>
> *** content.html
> <div xmlns="http://www.w3.org/1999/xhtml">
>  <span id="current-dateTime"></span>
> </div>
>
> *** content.xsl
> <stylesheet ...>
>
>  <template name="main">
>    <apply-templates select="doc('content.html')"/>
>  </template>
>
>  <template match="@*|node()">
>    <copy>
>       <apply-templates select="@*|node()"/>
>    </copy>
>  </template>
>
>  <template match="html:*[@id='current-dateTime']">
>    <copy>
>      <apply-templates select="@*"/>
>      <value-of select="current-dateTime()"/>
>    </copy>
>  </template>
>
> </stylesheet>
>
> Anyone use this pattern?
> --
> Max
>
> --~------------------------------------------------------------------
> XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
> or e-mail: <mailto:xsl-list-unsubscribe@l...>
> --~--
>
>

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe@l...>
--~--