System and method for generating XSL transformation documents

• US 6,996,781 B1
• Filed: 10/31/2001
• Issued: 02/07/2006
• Est. Priority Date: 10/31/2001
• Status: Active Grant

• Current Assignee: Badger I, LLC
• Original Assignee: WhiteFence, Inc. (Red Ventures LLC)
• Inventors: Myers, Kenneth L., Modi, Maulik A.
• Primary Examiner(s): Luu, Sy D.
• Application Number:
  US09/999,822
• Time in Patent Office: 1,560 Days
• Field of Search: 715/763, 715/762, 715/760, 715/700, 715/764, 715780-781, 715803-804, 715/808, 715853-855, 715/961, 715/967, 715/523, 715/501.1, 715/513, 715/517, 715/530
• US Class Current: 715/763
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/154 Tree transformation for tree-structured or markup documents, e.g. XSLT, XSL-FO or stylesheets

Abstract

A system and method is disclosed for generating XSL transformation documents. A software wizard presents a series of screens to lead the user through the authoring process. The screens include a load screen, a select screen, a new entity screen, a conditional screen, and a view screen. The load screen prompts the user for an input document name. The wizard then retrieves XML entities from the input document and presents them to the user in tree form on the select screen. The user selects entities from the tree for inclusion in the output document. The new entity screen allows the user to create new entities for inclusion in the output document. These entities are accumulated in an output list. The conditional screen allows the user to make entities from the output list conditional. The view screen allows review of a tentative transformation document that will accomplish the user'"'"'s purpose.

Claims

1. A computer configured to create a transformation document in response to user input, the computer comprising:

a user output device;

a processor; and

a memory that includes a software application which configures the processor to display a series of screens on the user output device to gather input from the user, and further configures the processor to create a transformation document in response to said input,

wherein the series of screens includes;

a load screen that prompts the user for an input document name; and

a select screen that shows entities of the input document in tree form and allows the user to select input document entities for inclusion in the transformation document;

wherein the software application constructs the transformation document according to the following pattern;

+21 +48 xml version+32 +37 1.0+38 +48 +22 +21 xsl;

stylesheet PREDETERMINED ATTRIBUTES PROVIDED HERE+22 +21 xsl;

include href+32 +37 IncludeFile.xsl+38 +0 /+22 +21 xsl;

strip-space elements+32 +37 *+38 +0 /+22 +21 xsl;

output method+32 +37 text+38 +0 encoding+32 +37 utf-8+38 +0 /+22 GLOBAL VARIABLES (IF ANY) DEFINED HERE+32 xsl;

template match+32 +37 /+38 +22 +21 xsl;

apply-templates select+32 +37 TemplateName1+38 /+22 +21 xsl;

apply-templates select+32 +37 TemplateName2+38 /+22 . . .+21 xsl;

apply-templates select+32 +37 TemplateNameN+38 /+22 /xsl;

template+22 +21 xsl;

template match+32 +37 TemplateName1+38 +22 ENTITY 1 ACTION DEFINED HERE+21 /xsl;

template+22 +21 xsl;

template match+32 +37 TemplateName2+38 +22 ENTITY 2 ACTION DEFINED HERE+21 /xsl;

template+22 . . .+21 xsl;

template match+32 +37 TemplateNameN+38 +22 ENTITY N ACTION DEFINED HERE+21 /xsl;

template+22 +21 /xsl;

stylesheet+22

wherein “

IncludeFile.xsl”

is a filename for a library of standardized routines, and wherein “

TemplateNamex”

is a name for a template that specifies an action for a corresponding entity,

wherein the software application allows the user to specify an output document format, and wherein the transformation document, when applied to an input document, configures a transformation engine to generate an output document having the specified output document format,

wherein the specified output document format is fixed-length, and wherein the software application constructs non-conditional entity templates according to the following pattern;

+21 xsl;

template match+32 +37 TemplateNamex+38 +22 LOCAL VARIABLE (IF ANY) DEFINED HERE+21 xsl;

call-template name+32 +37 strextractor+38 +22 +21 xsl;

with-param name+32 +37 str+38 +22 +21 xsl;

value-of select+32 +37 VariableNamex+38 /+22 +21 /xsl;

with-param+22 +21 xsl;

with-param name+32 +37 fixlength+38 +0 select+32 +37 Length+38 +0 /+22 +21 xsl;

with-param name+32 +37 padside+38 +0 select+32 +37 Side+38 +0 /+22 +21 xsl;

with-param name+32 +37 padchar+38 +0 select+32 +37 Char+38 +0 /+22 +21 xsl;

call-template+22 +21 xsl;

template+22

wherein “

strextractor”

is a name of a library routine that produces a fixed length field, wherein “

VariableNamex”

is a name of a variable that stores a value for the fixed length field, “

Length”

is a field size, “

Side”

is an indicator of which side of the value to add pad characters on, and “

Char”

is a character to use for padding the value.

2. The computer of claim 1, wherein the software application constructs conditional entity templates according to the following pattern:

+32 xsl;

template match+32 +37 TemplateNamex+38 +22 +21 xsl;

call-template name+32 +37 strextractor+38 +22 +21 xsl;

with-param name+32 +37 str+38 +22 +21 xsl;

choose+22 +21 xsl;

when test+32 +37 Test1+38 +22 RESULT 1 DEFiNED HERE+21 /xsl;

when+22 +21 xsl;

when test+32 +37 Test2+38 +22 RESULT 2 DEFINED HERE+21 /xsl;

when+22 +21 xsl;

otherwise+22 OTHERWISE RESULT (IF ANY) DEFINED HERE+21 /xsl;

otherwise+22 +21 /xsl;

choose+22 +21 /xsl;

with-param+22 +21 xsl;

with-param name+32 +37 fixlength+38 +0 select+32 +37 Length+38 +0 /+22 +21 xsl;

with-param name+32 +37 padside+38 +0 select+32 +37 Side+38 +0 /+22 +21 xsl;

with-param name+32 +37 padchar+38 +0 select+32 +37 Char+38 +0 /+22 +21 /xsl;

call-template+22 +21 /xsl;

template+22

wherein “

Testx”

is a user specified test.