RE: inheritance and encapsulation in xslt? / xslt for

Hi,

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx [mailto:owner-xsl-
> list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Howard Stearns
> Sent: Monday, July 21, 2003 2:37 PM
> 
> So, is there a standard example or methodology for this?
> 

Perhaps I am simplifying this too much (don't see why XLink needs to be
considered), but we have a similar situation with our ASP based content
management system. We use a modified XHTML XML Schema (minus structure and
DIV/SPAN) as a base set to draw from. There is also a base set of extended
elements that we have found to be common. Then a client (well... us,
usually) can define their own elements and structure content pieces.
However, we know the namespace they will be using (you could create a simple
transform that creates the file below in the unique namespace). Since you
are using XHTML you could simply do something like:

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet 
  version="1.0" 
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
  xmlns:lsb="http://livestoryboard.com/lsb/schemas/2003/03/config" 
  xmlns:c="http://livestoryboard.com/lsb/schemas/2003/03/content" 
  exclude-result-prefixes="c lsb">

  <xsl:template match="c:*">
    <div class="{local-name()}">
      <xsl:copy-of select="@*"/>
      <xsl:apply-templates/>
    </div>
  </xsl:template>
      
</xsl:stylesheet>

This can get modified as needed, but it covers most (of our) needs. You
would then handle your unique look and feel through CSS. Of course this type
of thing just moves the problem somewhere else, but it is much easier for a
client to deal with CSS than XSL.

The above file is found in a default/common app location. We use a
URIResolver to first check a well-known client location first. If it finds
their own version of the file there the app uses it (and caches the
Template) otherwise it uses the default.

Am I being way too simplistic?

Best,
-Rob


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