System and Method for Dynamic XSLT Processing via XML Processing Appliance
Original Publication Date: 2008-Mar-06
Included in the Prior Art Database: 2008-Mar-06
XSLT Processing Technology is widely used in many areas, especially in Web based domain. But the XML processing performance is a bottle-neck for it. So in these years, some company implements some Embedded Hardware Accelerator for XML Message Processing. For example, is the IBM’s DataPower. In DataPower, it can accepted XSL rule files and when the request XML comes, the DataPower will return the result XML by processed with XSL rules. But the rule file still has some disadvantages. Once uploaded into the Appliance, the rule file can not or hardly be changed; another point is that the rule’s description ability is not enough for many cases. For example, if we want to change tag from the company name to the company’s website link, some company will add “.com” some will add “.com.cn”, … It’s very difficult for the only use some general rules to descript these varieties.
System and Method for Dynamic XSLT Processing via XML Processing Appliance System and Method for Dynamic XSLT Processing via XML Processing ApplianceSystem and Method for Dynamic XSLT Processing via XML Processing Appliance
Our idea is a system and method which will enable a XML processing appliance to be able to dynamically update its XSL files to achieve new xslt processing knowledge.
As the graph below, you can see:
New xslt processing capability can be given by external knowledge database. External knowledge provides three components. There are:
It defines some computing method of original data source.
2. Operation Rule set
It includes some conditions for those Operators.
3. Web2.0 Services Repository
It defines interface and related information of external service (Web 2.0) which provides target data format.
The process flow is:
1. A html/xml page is the data source for appliance.
2. Appliance will analyze the content of the data source and get the key words.
3. Operation Engine module will check whether it needs the operators for the key words according to the rules of Operation Rule Set.
4. Operation Engine finds suitable operator method and the interface and related information of external service from Service Repository.
5. Operation Engine extends rich tags for the key words to composite the Web2.0 service for the original html/xml page.
The following figure show the typical datapower processing steps:
The XSL file, such as a.xsl is loaded into Datapower. The Datapower will compile the XSL file into accelerator.
In runtime, the requestor will post a source XML into datapower. The Datapower will use XSL accelerator to process the XML file, converting it into the required format. Since the XSL transformation is carried out using the accelerator, the processing is very fast.
Then, the Datapower will return the result X...