Browse Prior Art Database

Parameterized XSL Style Sheets

IP.com Disclosure Number: IPCOM000123938D
Original Publication Date: 1999-Jul-01
Included in the Prior Art Database: 2005-Apr-05
Document File: 5 page(s) / 190K

Publishing Venue

IBM

Related People

Wesley, AA: AUTHOR [+2]

Abstract

The Text Transformation Engine, modifies web content to accommodate device, browser and network bandwidth limitations as well as user preferences. The Transformation Engine is a sub component of the Text Transformation Engine and focuses on applying transforms to XML documents to yield a well formed document which is optimized with respect to the above mentioned limitations and preferences. The Transformation Engine manages Transform Beans who directly modify documents to apply transformations. Transform Beans currently come in 3 flavors: Tag Handler Element Handler Parameterized Style Sheet

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 30% of the total text.

Parameterized XSL Style Sheets

   The Text Transformation Engine, modifies web content to
accommodate device, browser and network bandwidth limitations as
well as user preferences.  The Transformation Engine is a sub
component of the Text Transformation Engine and focuses on applying
transforms to XML documents to yield a well formed document which is
optimized with respect to the above mentioned limitations and
preferences.  The Transformation Engine manages Transform Beans who
directly modify documents to apply transformations.  Transform Beans
currently come in 3 flavors:
    Tag Handler
    Element Handler
    Parameterized Style Sheet

A Java XML parser (i.e. XML4J) is used to process input documents.
The XML processor parses XML documents and invokes objects registered
to process specific tags.  The objects implement either an Element
Handler Java Interface or a Tag Handler Interface.  TransformBeans
which implement either the Tag Handler or Element Handler interface,
register with the parser to process a specific set of tags.  Thus the
Handler interfaces require Transformation writers to develop
transforms that focus on the processing of specific tags.

   To facilitate efficient processing of XML documents
with a large number of elements it is desirable to use style sheets.
XSL Style Sheets applied to XML documents are capable of converting
one document object model to another.  XSL templates define patterns
and result tree fragments.  When patterns are matched against an XML
document the XML elements which match the template pattern are
replaced by a result tree.  The XML document is parsed recursively,
and the resulting trees are aggregated to yield a complete document.
XSL is often used to define formatting semantics for XML documents,
however style sheets lend themselves  as transformation scripts as
well.  With the support of XSL/XML processors, the task of defining
and invoking "static" transformations on XML documents becomes
trivial, when applying XSL style sheets.

   The Transformation Engine applies transformations based on
a set of persistent preferences.  Thus the set of transformations
which are to be invoked against a source document are resolved at
run-time.  XSL style sheets do not support a concept of input
parameters, and are thus limited in use for such dynamic scenarios.
The ability to parameterize XSL style sheets is desired such that an
aggregation of transformations may be customized at run-time and
applied to an entire XML document.

   To facilitate a notion of dynamic style sheets
the Transformation Engine acts as a XSL Style Sheet Preprocessor.
The Transformation Engine will resolve preferences at run-time and
supply the Parameterized Style Sheet with parameters.  XSL
processors, process XSL templates recursively, and XSL itself
supports conditionals as well as data storage (i.e. constants).  The
lack of input parameter support, limits XSL Style Sheets from being
leveraged as a t...