Hi

I'm afraid that renaming/changing an existing standard is really bad
practise.

It isn't a safe choice,
even if you need a quick and (really!!!) dirty prototype ... :-)

I've seen examples of the modularization in a custom cms
where new tags acts as placeholders to tell the engine
where the dynamic contents need to be placed.

All the markers are replaced by the engine with the contents
in a single XSLT transformation.

So the output is XHTML Strict 1.0 compliant.

That's all.

Bye ;-)

kieranbenton ha scritto:

> monique wrote:
> > Hi,
> >
> > take a look at XHTML modularization,
> > it seems useful to extend the xhmlt specs with custom tags.
> >
> > There's something in the XHTML section on w3c official site, like this:
> >
> > http://www.w3.org/MarkUp/Guide/xhtml-m12n-tutorial/
>
> Thanks for that Monique, it does look like the right track for me. I've
> also considered the posibility of just making changes to the
> transitional xsd and renaming it / changing the namespace. I take it
> that is considered bad practice?
> 
> Cheers,
> Kieran