US 6,480,865 B1Grant
Facility for adding dynamism to an extensible markup language
Issue Date:2002-11-12
•54 Claims
•2 Drawing Sheets
Abstract
A method for annotating eXtensible Markup Language (XML) documents with dynamic functionality. The dynamic functionality comprises invocations of Java objects. These annotations belong to a different name space, and thus a Dynamic XML-Java (DXMLJ) processor recognizes elements within the XML document that are tagged with DXMLJ prefix tags, processes each of these tags, and transforms the XML document accordingly.
Metadata
Assignee
- International Business Machines Corporation
Inventors
- Susan B. Lee
- Neelakantan Sundaresan
Application Information
Application Number:US 09/166,042
Filing Date:1998-10-05
Priority Date:1998-10-05
Art Unit:7
Classifications
IPC:
G06F 1721
Field of Search:
707513707530707523707 10707512
Patent Drawings (2 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application is related to the following co-pending and commonly-assigned patent applications:
[0003] application Ser. No. 09/166,018, entitled “A PATTERN MATCHING AND REPLACEMENT LANGUAGE FOR TRANSFORMING DOCUMENTS,” filed on Oct. 5, 1998, by Neelakantan Sundaresan, pending; and
[0004] application Ser. No. 09/166,043, entitled “CONVERTING SCHEMAS TO COMPONENT MODELS,” filed on Oct. 5, 1998, by Neelakantan Sundaresan, pending; both of which applications are incorporated by reference herein.
BACKGROUND OF THE INVENTION
[0005] 1. Field of the Invention.
[0006] This invention relates in general to transforming documents, and in particular, to a facility for adding dynamism to extensible Markup Language (XML) documents.
[0007] 2. Description of Related Art.
[0008] Since the early days of the Internet, and specifically, the World Wide Web (WWW), HyperText Markup Language (HTML) has been used by Web servers to create marked up documents or pages for display by browsers. Subsequently, a number of different techniques have been introduced to add dynamism to HTML.
[0009] For example, when a browser requests an HTML page that has one or more embedded APPLET tags, a Java program identified by the APPLET tag is downloaded from the server and executed by the browser. Similarly, when a browser requests an HTML page that has one or more embedded SERVLET tags, a Java object identified by the SERVLET tag is executed by the server to perform one or more functions before the HTML page being downloaded to the browser. These functions typically return tagged structures that are then embedded in the HTML page at the position of the SERVLET tags.
[0010] In another example, Java Server Pages (JSPs) and Active Server Pages (ASPs) are HTML pages that include embedded programming or scripts. This embedded programming or scripts is then invoked by the server and the results are embedded in the HTML page prior to the HTML page being downloaded to the browser. In addition, Cascading Style Sheets (CSS's) and Java scripts provide additional dynamism in the browser.
[0011] Notwithstanding the success of HTML, Extensible Markup Language (XML) is poised to be the next big revolution for the World Wide Web (WWW). With the realization that the Web is not about just browsing any more, XML has emerged as an enabling technology to carry the Web to the next generation of electronic commerce, Web-based workflow, and integration of databases with Web applications.
[0012] The XML language describes a class of data objects called XML documents and partially describes the behavior of computer programs that process them. XML is a restricted form of SGML, the Standard Generalized Markup Language, defined in ISO 8879. The specification for XML can be found at the URL: http://www.w3.org/TR/REC-xml.
[0013] Unlike HTML, XML is a balanced tag language, wherein every open tag has a corresponding closed tag and there are no semantics attached to the tag. The interpretation of the tags is left to the target environment using the document. Thus, XML separates a document description from its interpretation.
[0014] This is a big deviation from HTML where the set of tags are fixed. Thus, XML enables applications to communicate between themselves using specialized tags. Moreover, the XML documents may change between applications without ever being rendered.
[0015] An XML document has two parts: (1) the marked up document; and (2) the document schema. XML documents are made up of storage units called entities, which contain either parsed or unparsed data. Parsed data is made up of characters, some of which form character data, and some of which form markup. Markup encodes a description of the document's storage layout and logical structure.
[0016] XML schemas specify constraints on the structures and types of elements in an XML document. The basic schema for XML is the DTD (Document Type Definition). Other XML schema definitions are also being developed, such as DCD Document Content Definition), XSchema, etc. Information concerning DTD and DCD can be found at the URL: http://www.w3.org/.
[0017] The main difference between DTD and DCD is that DTD uses a different syntax from XML, while DCD specifies an XML schema language in XML itself. (XSchema is similar to DCD in this respect). In spite of the differences in the syntax, the goals and constraint semantics for all these XML schema languages are the same. Their commonality is that they all describe XML Schema. This means that they assume the common XML structure, and provide a description language to say how these elements are laid out and are related to each other.
[0018] There are about five basic constraints that an XML schema describe:
[0019] 1. The attributes that an element should/may contain:
[0020] a. the types of the attribute values (mainly string types), and
[0021] b. the mandatory or optional nature of occurrences of these attributes.
[0022] 2. The type and the order in which elements can be contained inside another element (the content model of the element):
[0023] a. the sub-element should of a certain name or type or that a subelement could be of any type, and
[0024] b. a regular expression system to express how these elements occur, wherein this regular expression system can be expressed by the following operators:
[0025] i. |: A|B (either element of type A or of type B can occur),
[0026] ii. ,: A, B (element of type B follows one of type A),
[0027] iii. *: A* (zero or more occurrence of element of type A),
[0028] iv. +: A+ (One or more occurrence of element of type A),
[0029] v. ?: A? (zero or one occurrence of element of type A), and
[0030] vi. ( ): ( . . . ) (grouping of expressions in this system).
[0031] Note that this system includes some convenience operators. For example, A+ is the same as A, A*.
[0032] A software module called an XML processor is used to read XML documents and provide access to their content and structure. It is assumed that an XML processor is doing its work on behalf of another module, called the application. The XML specification located at the URL noted above describes the required behavior of an XML processor in terms of how it must read XML data and the information it must provide to the application.
[0033] In a typical application that uses XML for a particular specification, there would be a DTD that specifies the XML schema and one or more XML documents that satisfy that schema. Consider the following XML document example:
[0034] <?xml version=“x1.0”?>
[0035] <!DOCTYPE test SYSTEM “foo.dtd”>
[0036] <foo>
[0037] <level1>
[0038] <nest1 id=“2”/>
[0039] <nest2 id=“3”/>
[0040] </if>
[0041] </level1>
[0042] </foo>
[0043] The corresponding DTD schema for the above example XML document would be the following:
[0044] <!ELEMENT foo (level1)>
[0045] <!ELEMENT level1 (nest1|nest2)>
[0046] <!ELEMENT nest1 EMPTY>
[0047] <!ATT LIST nest1
[0048] id CDATA #REQUIRED>
[0049] <!ELEMENT nest2 EMPTY>
[0050] <!ATTLIST nest2
[0051] id CDATA #REQUIRED>
[0052] The DTD schema indicates that the XML document “foo” has one tag “level1.” Within level1, there are two tags “nest1” and “nest2,” wherein both nest1 and nest2 have an attribute “id,” whose value is character data, and whose specification is mandatory.
[0053] As an XML document flows through the various nodes of the Internet, the XML document may be fully or partially filled in, transformed, pruned, or composed at every node. This gives rise to the notion of valid versus well-formed documents. A valid XML document is one that satisfies the restrictions of its associated DTD schema. A well-formed XML document may not have or satisfy an associated DTD schema, but it has to satisfy the syntax requirements of XML (e.g., every open tag has a matching closing tag, etc.). Often, however, it is expensive to verify the XML document against the DTD schema.
[0054] In the use of a common language like XML, sufficient dynamism is needed where XML documents can be automatically transformed, with the transformed XML document replacing the original portion of the document in-place. Such transformations may be applied to one or several parts of the document based on one or more conditions, the transformations may split one or more parts of the document into multiple parts, the transformations may invoke an arbitrary function to replace a part of the document with another, etc.
[0055] However, XML itself does not provide any mechanisms to perform such transformations, since XML documents are by themselves static in nature. There is no way to embed logic, or specify filtering, or specify transformation structures that are based upon the context in which the document is processed. Moreover, the concepts of applets and servlets as used in HTML are limited in that the APPLET and SERVLET tags occur at the leaf level of the HTML page, which means that there is no way to embed anything within an APPLET or SERVLET tag. What is needed, then, is a mechanism that seamlessly mixes programming language constructs with the constructs of XML so that one can reference and enable the other. Moreover, such mechanisms should exploit the fact that XML does not attach any specific semantics to its tags.
SUMMARY OF THE INVENTION
[0056] To overcome the limitations in the prior art described above, and to overcome other limitations that will become apparent upon reading and understanding the present specification, the present invention discloses a method for annotating XML documents with dynamic functionality. The dynamic functionality comprises invocations of Java objects. These annotations belong to a different name space, and thus a Dynamic XML-Java (DXMLJ) processor recognizes elements within the XML document that are tagged with DXMLJ prefix tags, processes each of these tags, and transforms the XML document accordingly.
BRIEF DESCRIPTION OF THE DRAWINGS
[0057] Referring now to the drawings in which like reference numbers represent corresponding parts throughout:
[0058] FIG. 1 is a block diagram that illustrates an exemplary client-server hardware environment of the preferred embodiment of the present invention; and
[0059] FIG. 2 is a flowchart that illustrates the logic performed by the preferred embodiment of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
[0060] In the following description of the preferred embodiment, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration a specific embodiment in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural and functional changes may be made without departing from the scope of the present invention.
Overview
[0061] The preferred embodiment of the present invention describes a technique to annotate XML documents with dynamic functionality. In the preferred embodiment, this dynamic functionality comprises invocations of Java objects. These annotations belong to a different name space than the original XML document, and so a Dynamic XML-Java (DXMLJ) processor recognizes elements within the XML document that are tagged with DXMLJ prefix tags, processes each of these tags, and transforms the XML document accordingly.
Hardware Environment
[0062] FIG. 1 schematically illustrates an exemplary hardware environment that could be used in the preferred embodiment of the present invention, and more particularly, illustrates a typical distributed computer system using the Internet 100 to connect client systems 102 executing Web browsers 104 to server systems 106 executing Web daemons 108. A typical combination of resources may include clients 102 that are personal computers or workstations, and servers 106 that are personal computers, workstations, minicomputers, or mainframes. These systems are coupled to one another over a network 100, which may include other networks such as LANs, WANs, SNA networks, as well as the Internet. Either or both of the Web browser 104 and Web daemon 108 may include a Java Virtual Machine (JVM) 110 that executes Java objects, applets, scripts, etc.
[0063] The preferred embodiment of the present invention is comprised of a number of different components. A Dynamic XML-Java (DXMLJ) processor 112 recognizes elements within a XML document 114 that are tagged with “dxmlj” prefix tags, processes each of these tags, and transforms the XML document 114 accordingly. This processing may include the instantiation of one or more Java class specifications 116 as Java objects 118, wherein the Java class specifications 116 and Java objects 118 comprise functions that transform the XML document 114.
[0064] In general, the DXMLJ processor 112, XML document 114, Java class specifications 116, and Java objects 118 comprise data and/or instructions which, when read, interpreted, and/or executed by the server computer 106, cause the computer 106 to perform the steps for performing and/or using the present invention. Generally, the data and/or instructions are embodied in and/or readable from a device, carrier or media, such as memory, data storage devices, and/or remote devices coupled to the computer via a data communications device.
[0065] However, those skilled in the art will recognize that the exemplary environment and components illustrated in FIGS. 1 and 2 are not intended to limit the present invention. Indeed, those skilled in the art will recognize that other alternative hardware environments may be used without departing from the scope of the present invention.
[0066] Thus, the present invention may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, hardware, firmware, or any combination thereof. In addition, the term “article of manufacture” as used herein is intended to encompass logic and/or data embodied in or accessible from any device, carrier, or media.
Operation of the Invention
[0067] Four categories of transformations are defined in the preferred embodiment of the present invention:
[0068] 1. Map functions (apply, execute),
[0069] 2. Copy functions (clone),
[0070] 3. Filter functions (select, filter), and
[0071] 4. Permutation functions (reverse, rotate, shuffle).
[0072] These four categories of transformations are represented by tags in the annotation language used by the DXMLJ processor 112. A typical structure is provided below:
[0073] <prefix TAG
[0074] prefix:id=“ . . . ”
[0075] prefix:class=“ . . . ”
[0076] prefix:arg=“ . . . ”
[0077] prefix:href=“ . . . ”
[0078] prefix:num=“ . . . ”
[0079] prefix:replace=“ . . . ”>
[0080] . . . sub-elements . . .
[0081] </prefix:TAG>
[0082] The placeholder TAG represents a convenience tag, which are described in more detail below.
[0083] The prefix is specified as a DXMLJ processor 112 instruction at the top of the subtree within the XML document 114. If not, by default, the prefix dxmlj is chosen as the annotation prefix.
[0084] The six typical prefixes have the following semantics (all the attributes are optional):
[0085] 1. The prefix:id attribute uniquely identifies the annotation element.
[0086] 2. The prefix:arg attribute is used to refer to a node identified using the prefix:id attribute.
[0087] 3. The prefix:class attribute uniquely identifies a class to instantiate and execute.
[0088] 4. The prefix:href attribute specifies a Uniform Resource Identifier (URI) from which an XML tree is to obtained and processed. The URI has to be well-formed. This attribute may also be used for referring to another subtree with a particular prefix:id within the same document. An xpointer language string may be placed here, which allows a reference to an arbitrary XML element traversal.
[0089] 5. The prefix:num attribute specifies DXMLJ processor 112 operations that require an integer argument.
[0090] 6. The prefix:replace attribute is a “true” or “false” attribute, wherein “true” indicates that the annotation is to be replaced by the result of the annotation processing and “false” indicates that the annotation remains.
[0091] The tag language is comprised of tags that permit arbitrary tree and subtree nodes within an XML document 114 to be processed and transformed. It is possible that almost all of the functionalities can be provided by a simple tag that is processed into a call to a Java object 118 that includes logic for traversing, searching, and manipulating a tree or subtree within the XML document 114.
[0092] The preferred embodiment of the present invention also provides convenience tags that enable commonly used and simple operations. These convenience tags reference class specifications 116 that represent generic operations. It is believed that all search and transformation operations can be expressed in terms of these generic operations.
[0093] In the preferred embodiment, the convenience tags are grouped into four classes:
[0094] 1. Map functions for applying a Java function object 118 to one or more elements,
[0095] 2. Clone functions for creating copies of XML subtrees,
[0096] 3. Filter functions for filtering XML subtrees from a group of candidate subtrees, and
[0097] 4. Permutation functions for performing permutation operations on a group of XML trees.
[0098] Each of these functions are described in more detail below.
[0099] Map Functions
[0100] Map functions are used to transform an XML tree or subtree by applying a Java function object 118. There are two tags in this category: apply and execute. These tags are described in more detail below.
[0101] Apply Function
[0102] The syntax of the apply tag is provided below:
[0103] <dxmlj:apply
[0104] class=“ . . . Java class name . . . ”
[0105] arg=“ . . . reference to a node with a particular dxmlj:ID . . . ”
[0106] href=“ . . . a URI or an Xpointer reference . . . ”
[0107] (only one of href or arg can occur)
[0108] replace=“true/false”>
[0109] . . . body of the apply function
[0110] </dxmlj:apply>
[0111] The Java class name identifies a Java class specification 116 for a Java unary function object 118 that accepts a TXElement object as an argument. The TXElement object is applied to each child of the annotation. If the annotation is specified with an arg or href attribute, then the annotation is applied to the node retrieved from those tags. The replace tag specifies whether the annotation should be replaced or not.
[0112] An example using the apply tag is provided below:
[0113] <dxmlj:apply
[0114] class=“DollarsToPounds”
[0115] replace=“true”>
[0116] <employee-info
[0117] name=“John”
[0118] wage=“10000”
[0119] unit=“dollars”/>
[0120] <employee-info
[0121] name=“Peter”
[0122] wage=“9000”
[0123] unit=“dollars”/>
[0124] </dxmlj:apply>
[0125] In the above example, the unary function “DollarsToPounds” is applied to each of the two employee-info elements. The apply element itself is replaced by the transformed children.
[0126] Execute Tag
[0127] The syntax of the execute tag is provided below:
[0128] <dxmlj:execute
[0129] class=“ . . . Java predicate class name . . . ”
[0130] arg=“ . . . reference to a node with a particular dxmlj:ID . . . ”
[0131] href=“ . . . a URI or an Xpointer reference . . . ”
[0132] (only one of href or arg can occur)
[0133] replace=“true/false”>
[0134] . . . body of the execute function
[0135] </dxmlj:execute>
[0136] The class attribute identifies a Java predicate class specification 116, and the corresponding Java predicate function object 118 is applied to each of the children of this annotation or the node specified in the arg or href attributes. The children (or the node) for which the predicate is true, are picked and any underlying transformation specified in the child node is applied to it.
[0137] The execute tag is related to the apply tag and the filter tag discussed below. However, it differs from the apply tag in the sense that each of the children might have a different transformation operation, whereas all children undergo the same transformation operation in the apply tag.
[0138] Clone Functions
[0139] Clone functions are used to make copies of an XML tree or subtree by applying a java function object 118. There is one tag in this category: clone. This tag is described in more detail below.
[0140] The syntax of the clone tag is provided below:
[0141] <prefix:clone
[0142] class=“ . . . ”
[0143] num=“ . . . ”
[0144] replace=“ . . . ”>
[0145] The num attribute specifies how many times the element tree under consideration has to be cloned. The class attribute specifies a Java class specification 116 that identifies a Java unary function object 118 that returns an integer. Only one of the class or num attributes can occur. When the class attribute is present, the associated Java unary function object 118 is invoked and the return value (which is an integer) is used to see how many clones of the element or elements under consideration have to be produced.
[0146] Filter Functions
[0147] Filter functions are used to select one or more XML subtrees or elements by applying a Java function object 118. There are two tags in this category: filter and select. These tags are described in more detail below.
[0148] Filter Tag
[0149] The syntax of the filter tag is provided below:
[0150] <prefix:filter
[0151] class=“ . . . ”
[0152] arg=“ . . . ”
[0153] href=“ . . . ”
[0154] replace=“ . . . ”>
[0155] The Java class specification 116 identified in the class attribute is a predicate class that is applied to all the elements under consideration, and only those for which it evaluates to “true” are selected. The filter tag can be considered as a special case of an execute tag where each of the elements selected undergo an identity transformation.
[0156] Select Tag
[0157] The syntax of the filter tag is provided below:
[0158] <prefix:select
[0159] class=“ . . . ”
[0160] num=“ . . . ”
[0161] replace=“ . . . ”>
[0162] The Java class specification 116 identified by the class attribute indicates a predicate. This is applied to each of the children until the first child that satisfies the condition is found or until all the elements are exhausted. The candidate element replaces the annotation node, if the replace flag is true. Alternatively, when the num attribute is specified, this selects the num-th element in the collection.
[0163] Permutation Functions
[0164] Permutation functions are used to permute a collection of elements by applying a Java function object 118. There are three tags in this category: permute, reverse, and rotate. These tags are described in more detail below.
[0165] Permute Tag
[0166] The syntax of the permute tag is provided below:
[0167] <prefix:permute
[0168] class=“ . . . ”
[0169] arg=“ . . . ”
[0170] href=“ . . . ”
[0171] replace=“ . . . ”>
[0172] The permute class corresponds to a Java unary function object 118 that returns an array of integers which is the permutation vector. This array is then used to permute the collection of elements under consideration.
[0173] Reverse Tag
[0174] The syntax of the reverse tag is provided below:
[0175] <prefix:reverse
[0176] arg=“ . . . ”
[0177] href=“ . . . ”
[0178] replace =“ . . . ”>
[0179] Reverse is a special case of permute, where a collection of elements in consideration are reversed in order.
[0180] Rotate Tag
[0181] The syntax of the rotate tag is provided below:
[0182] <prefix:rotate
[0183] class=“ . . . ”
[0184] num=“ . . . ”
[0185] arg=“ . . . ”
[0186] href=“ . . . ”
[0187] replace=“ . . . ”>
[0188] Rotate is a special case of permute where the elements are rotated a fixed number of times. This number is determined by the num attribute (which should be an integer) or by the class attribute which specifies a Java unary function object 118 that returns an integer.
[0189] Inline Programming
[0190] It may be useful to have inline programming within XML documents 114. In the preferred embodiment, the DXMLJ processor 112 allows users to include inline Java programming in their XML documents 114 using the dxmlj:inline elements. The content model for inline elements is PCDATA, which means that the user can have free flowing text in the body of the element. In order that the text not include characters that are XML tag characters like (<, > etc.), the user may enclose the text in CDATA tags.
[0191] The inline Java programming has two facilities to interact with the surrounding XML elements.
[0192] 1. The programming can refer to other XML elements in the document 114 which have a specified dxmlj:ID in them. The way the programming would refer to the surrounding elements would be through the $(id) tag. Since ID tags are expected to be unique this provides for unique addressing of XML elements. This address returns a TXElement object. Subelements, attributes, descendents can be accessed within the Java programming. The $( ) tag language can be extended to search for elements and attributes which satisfy particular conditions.
[0193] 2. The programming also has the facility to inject element subtrees back into the XML documents 114. This is done using a call to Java return call within the logic of the text.
[0194] An example of inline Java programming is provided below:
[0195] <employee-info>
[0196] <name> . . . </name >
[0197] <salary dxmlj:id=“salary” value=“100000”/>
[0198] <dxmlj:inline>
[0199] TXAttribute attr=$(salary).getAttribute(“value);//1
[0200] int salary=attr.getValue( );//2
[0201] float perks=salary*0.15;//3
[0202] TXElement perks=new TXElement(“perks”);//4
[0203] perks.addAttribute(“value”, String.valueOf(perks));//5
[0204] return txa;;//6
[0205] </dxmlj:inline>
[0206] </employee-info>
[0207] When the DXMLJ processor 112 processes the dxmlj:inline element, it first pre-processes the body of the inline element to replace all the $( . . . ) references. One of the ways the inline programming is handled is by having the DXMLJ processor 112 convert each inline tag occurrence in the document 114 to a method in the Java class specification 116, wherein the method name is automatically generated. All the variables declared in the inline programming are local to the method.
[0208] Following is a sample translation for the dxmlj:inline set forth above:
[0209] TXElement_generatedMethod(TXElement el)
[0210] {
[0211] TXAttribute attr= . . . get element from the document whose id is “salary”//1
[0212] int salary=attr.getValue( );//2
[0213] float perks=salary*0.15;//3
[0214] TXElement perks=new TXElement(“perks”);//4
[0215] perks.addAttribute(“value”, String.valueOf(perks));//5
[0216] return txa;//6
[0217] }
[0218] The argument that is passed to the method is the reference to the node that is specified in the href or the arg attribute of the annotation. The annotation can itself be identified using the id attribute. The id attribute applies to the element tree that corresponds to this annotation (if the annotation tree is replaced by the return value of the programming, then the id identifies the replaced node). Replacement can be turned on and off using the replace attribute.
[0219] Sometimes, inline programming occurring in two different locations in the XML document 114 need to share variables between them. Since each occurrence of dxmlj:inline is converted to a method body, there is a Java class wrapping them that can have field variables which can be set and obtained in these methods. To assist, another tag called dxmlj:decl is introduced. All declarations within dxmlj:decl are placed in the body of the class that is generated.
[0220] Following is an example of this tag:
[0221] <dxmlj:decl>
[0222] int referenceCount;
[0223] </dxmlj:decl>
[0224] The above example would result in a field called referenceCount being generated and this variable can be referenced in any of the Java programming that is enclosed in dxmlj:inline elements.
[0225] Relationship To Servlets, Java Server Pages, Etc.
[0226] As mentioned before, servlets, Java Server Pages, and Active Server Pages work only in a server-browser environment. For a general workflow environment, which is not just about viewing but about flowing application or business logic, XML documents 114 are used and the DXMLJ processor 112 enhances the use of XML documents 114.
[0227] Further, annotations processed by the DXMLJ processor 112 blend well with the document 114 tags, not just at the leaf level. Thus, document 114 tags can placed within DXMLJ processor 112 tags and vice versa. At the same time, they do not interfere with the document 114 tags, because they belong to a different name space than the DXMLJ processor 112 tag.
[0228] The DXMLJ processor 112 also allows embedding inline Java programming, sharing of state or variable information between these programmings occurring at different locations in the document 114 tree. In fact, the inline programming can be implemented any number of different programming languages, such as Java Script, VisualBasic Script, etc., so long as an interpreter for the language can be invoked. Further, the DXMLJ processor 112 tags can be embedded in HTML pages as well, since HTML is just an instance of XML.
Logic of the Invention
[0229] FIG. 2 is a flowchart that illustrates the steps performed by the preferred embodiment of the present invention.
[0230] Block 200 represents the DXMLJ processor 112 being initialized.
[0231] Block 202 represents the DXMLJ processor 112 retrieving the XML document 114.
[0232] Block 204 is a decision block that represents the DXMLJ processor 112 loop to examine all the subtrees within the XML document 114. Thereafter, Blocks 206-218 are performed.
[0233] Block 206 is a decision block that represents the DXMLJ processor 112 determining whether the subtree being examiner comprises a DXMLJ prefix tag. If so, control transfers to Block 208; otherwise, control transfers to Block 216.
[0234] Block 208 represents the DXMLJ processor 112 instantiating the Java class specification 116 associated with the DXMLJ prefix tag. This step is optional, in that the class may have already been instantiated. In addition, this step may represent the instantiation of a class that is comprised of inline programming within the XML subtree.
[0235] Block 210 represents the DXMLJ processor 112 invoking the Java object 118 instantiated from the Java class specification 116.
[0236] Block 212 represents the DXMLJ processor 112 receiving a result from the Java object 118.
[0237] Block 214 represents the DXMLJ processor 112 updating the XML subtree in the XML document 114 with the results received from the Java object 118. Thereafter, control transfers to Block 204.
[0238] Block 216 represents the DXMLJ processor 112 performing other processing. Thereafter, control transfers to Block 204.
[0239] Finally, Block 218 represents the DXMLJ processor 112 writing out the updated XML document 114.
Conclusion
[0240] This concludes the description of the preferred embodiment of the invention. The following describes some alternative embodiments for accomplishing the present invention. For example, any type of computer, such as a mainframe, minicomputer, or personal computer, could be used to implement the present invention. In addition, the present invention is not limited by specific document or programming languages, and could comprise languages other than XML and Java. For example, the present invention could also be used with HTML, SGML, NetRexx, VisualBasic Script, XML, Perl, C, C++, Cobol, etc.
[0241] In summary, the present invention discloses a method, apparatus, and article of manufacture for annotating XML documents with dynamic functionality. The dynamic functionality comprises invocations of Java objects. These annotations belong to a different name space, and thus a Dynamic XML-Java (DXMLJ) processor recognizes elements within the XML document that are tagged with DXMLJ prefix tags, processes each of these tags, and transforms the XML document accordingly.
[0242] The foregoing description of the preferred embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.
Claims
What is claimed is:
1. A computer-implemented method for transforming an eXtensible Markup Language (XML) document, comprising:
(a) identifying, in a computer, one or more annotations within the XML document, wherein:
(i) the XML document is specified in a fist namespace;
(ii) the annotations are specified in a second namespace within the XML document that is different from the fist namespace;
(iii) a dynamic processor in the computer is configured to identify the annotations as belonging to the second namespace;
(b) the dynamic processor invoking, in the computer, one or more functions associated with the identified annotations belonging to the second namespace, wherein:
(i) the functions perform one or more transformations on the XML document to produce a transformed XML document;
(ii) the transformed XML document replaces one or more portions of the XML document; and
(iii) the transformed XML document can be processed by an XML processor.
2. The method of claim 1, wherein the annotations comprise tags within the XML document.
3. The method of claim 1 above, wherein the functions are defined in Java.
4. The method of claim 1, wherein the invoking step further comprises the step of instantiating one or more class specifications corresponding to the functions as one or more objects.
5. The method of claim 4, wherein the class specifications comprise Java class specifications and the instantiated class specifications comprise Java objects.
6. The method of claim 1 above, wherein the transformations comprise one or more replacements to be made in the XML document.
7. The method of claim 1 above, wherein the transformations are performed based on an evaluation of one or more conditions.
8. The method of claim 7 above, where the conditions comprise one or more predicates.
9. The method of claim 1 above, wherein the conditions include one or more filters.
10. The method of claim 1 above, wherein the functions comprise one or more functions selected from a group comprising map functions, copy functions, filter functions, and permutation functions.
11. The method of claim 1 above, wherein the functions are represented by tags in the annotation language.
12. The method of claim 1 above, wherein the annotations include an identification attribute that uniquely identifies the annotation.
13. The method of claim 1 above, wherein the annotations include a class identifier attribute that uniquely identifies a class specification for the function.
14. The method of claim 1 above, wherein the annotations include a reference identification attribute that uniquely identifies a location of the XML document.
15. The method of claim 1 above, wherein the annotations include an integer attribute that uniquely identifies an argument for the annotation.
16. The method of claim 1 above, wherein the annotations include an replace attribute that identifies whether the annotation is to be replaced by the transformation.
17. The method of claim 1 above, wherein the annotations comprise one or more convenience tags that represent generic operations to be performed on the XML document.
18. The method of claim 1 above, wherein the annotations comprise inline programming.
19. An apparatus for transforming an eXtensible Markup Language (XML) document, comprising:
(a) a computer; and
(b) dynamic processor means, performed by the computer, for identifying one or more annotations within the XML document, wherein:
(i) the XML document is specified in a first namespace;
(ii) the annotations are specified in a second namespace within the XML document that is different from the first namespace;
(iii) the dynamic processor means is configured to identify the annotations as belonging to the second namespace; and
(iv) the dynamic processor is configured to invoke one or more functions associated with the identified annotations belonging to the second namespace, wherein:
(1) the functions perform one or more transformations on the XML document to produce a transformed XML document;
(2) the transformed document replaces one or more portions of the XML document; and
(3) the transformed document can be processed by an XML processor.
20. The apparatus of claim 19, wherein the annotations comprise tags within the XML document.
21. The apparatus of claim 19 above, wherein the functions are defined in Java.
22. The apparatus of claim 19, wherein the means for invoking comprises means for instantiating one or more class specifications corresponding to the functions as one or more objects.
23. The apparatus of claim 22, wherein the class specifications comprise Java class specifications and the instantiated class specifications comprise Java objects.
24. The apparatus of claim 19 above, wherein transformations comprise one or more replacements to be made in the XML document.
25. The apparatus of claim 19 above, wherein the transformations are performed based on an evaluation of one or more conditions.
26. The apparatus of claim 25 above, wherein the conditions comprise one or more predicates.
27. The apparatus of claim 19 above, wherein the conditions include one or more filters.
28. The apparatus of claim 19 above, wherein the functions comprise one or more functions selected from a group comprising map functions, copy functions, filter functions, and permutation functions.
29. The apparatus of claim 19 above, wherein the functions are represented by tags in the annotation language.
30. The apparatus of claim 19 above, wherein the annotations include an identification attribute that uniquely identifies the annotation.
31. The apparatus of claim 19 above, wherein the annotations include a class identifier attribute that uniquely identifies a class specification for the function.
32. The apparatus of claim 19 above, wherein the annotations include a reference identification attribute that uniquely identifies a location of the XML document.
33. The apparatus of claim 19 above, wherein the annotations include an integer attribute that uniquely identifies an argument for the annotation.
34. The apparatus of claim 19 above, wherein the annotations include an replace attribute that identifies whether the annotation is to be replaced by the transformation.
35. The apparatus of claim 19 above, wherein the annotations comprise one or more convenience tags that represent generic operations to be performed on the XML document.
36. The apparatus of claim 19 above, wherein the annotations comprise inline programming.
37. An article of manufacture embodying logic for performing a method for transforming an eXtensible Markup Language (XML) document, the method comprising:
(a) identifying, in a computer, one or more annotations within the XML document, wherein:
(i) the XML document is specified in a first namespace;
(ii) the annotations are specified in a second namespace within the XML document that is different from the first namespace;
(iii) a dynamic processor in the computer is configured to identify the annotations as belonging to the second namespace; and
(b) the dynamic processor invoking, in the computer, one or more functions associated with the identified annotations belonging to the second namespace, wherein:
(i) the functions perform one or more transformations on the XML document to produce a transformed XML document;
(ii) the transformed XML document replaces one or more portions of the XML document; and
(iii) the transformed XML document can be processed by an XML processor.
38. The article of manufacture of claim 37, wherein the annotations comprise tags within the XML document.
39. The article of manufacture of claim 37 above, wherein the functions are defined in Java.
40. The article of manufacture of claim 37, wherein the invoking step further comprises the step of instantiating one or more class specifications corresponding to the functions as one or more objects.
41. The side of manufacture of claim 40, wherein the class specifications comprise Java class specifications and the instantiated class specifications comprise Java objects.
42. The article of manufacture of claim 37 above, wherein the transformations comprise one or more replacements to be made in the XML document.
43. The article of manufacture of claim 37 above, wherein the transformations are performed based on an evaluation of one or more conditions.
44. The article of manufacture of claim 43 above, wherein the conditions comprise one or more predicates.
45. The article of manufacture of claim 37 above, wherein the conditions include one or more filters.
46. The article of manufacture of claim 37 above, wherein the functions comprise one or more functions selected from a group comprising map functions, copy functions, filter functions, and permutation functions.
47. The article of manufacture of claim 37 above, wherein the functions are represented by tags in the annotation language.
48. The article of manufacture of claim 37 above, wherein the annotations include an identification attribute that uniquely identifies the annotation.
49. The article of manufacture of claim 37 above, wherein the annotations include a class identifier attribute that uniquely identifies a class specification for the function.
50. The article of manufacture of claim 37 above, wherein the annotations include a reference identification attribute that uniquely identifies a location of the XML document.
51. The article of manufacture of claim 37 above, wherein the annotations include integer attribute that uniquely identifies an argument for the annotation.
52. The article of manufacture of claim 37 above, wherein the annotations include an replace attribute that identifies whether the annotation is to be replaced by the transformation.
53. The article of manufacture of claim 37 above, wherein the annotations comprise one or more convenience tags that represent generic operations to be performed on the XML document.
54. The article of manufacture of claim 37 above, wherein the annotations comprise inline programming.
Patent Citations (20)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4447875(A) | 1984-05-01 | Bolton et al. | Applicant |
| US4599691(A) | 1986-07-01 | Sakaki et al. | Applicant |
| US4949253(A) | 1990-08-01 | Chigira et al. | Applicant |
| US5269014(A) | 1993-12-01 | Ogino | Applicant |
| US5321606(A) | 1994-06-01 | Kuruma et al. | Applicant |
| US5530863(A) | 1996-06-01 | Hino | Examiner |
| US5548508(A) | 1996-08-01 | Nagami | Applicant |
| US5629846(A) | 1997-05-01 | Crapo | Applicant |
| US5659729(A) | 1997-08-01 | Nielsen | Examiner |
| US5715453(A) | 1998-02-01 | Stewart | Examiner |
| US5915259(A) | 1999-06-01 | Murata | Applicant |
| US5940075(A) | 1999-08-01 | Mutschler, III et al. | Examiner |
| US6014680(A) | 2000-01-01 | Sato et al. | Applicant |
| US6055522(A) | 2000-04-01 | Krishna et al. | Applicant |
| US6073143(A) | 2000-06-01 | Nishikawa et al. | Applicant |
| US6182092(B1) | 2001-01-01 | Francis et al. | Examiner |
| US6202072(B1) | 2001-03-01 | Kuwahara | Applicant |
| US6226642(B1) | 2001-05-01 | Beranek et al. | Examiner |
| US6272673(B1) | 2001-08-01 | Dale et al. | Examiner |
| US6336124(B1) | 2002-01-01 | Alam et al. | Examiner |
Non-Patent Literature (14)
- Willner, Eki. “Preparing Web data with XML: Part III” Information Today. vol. 15, Issue 7, Jul./Aug. 1998, pp. 1-6.Applicant
- Bray, Tim and Sperberg-McQueen, C.M. “Extensible Markup Language (XML):Part I. Syntax” http://www.w3.org/TR/WD-xml-970331, pp. 1-40.Applicant
- Bray, Tim. Name Spaces in XML, published Jan. 1998, pp. 1-14, http://www.w3.org/TR/1998/NOTE-xml-names-0119.Applicant
- Bray, Tim, “Document Content Description for XML” Http://www.w3.org/TR/Note-dcd, Jul. 31, 1998, pp. 1-21.Applicant
- Senna, Jeff, “XML Bridges the Gap” Info World, Jun. 1, 1998, vol. 20, Issue 22, pp. 88-90.Applicant
- Jones C., IBM, Developers: Java : Library—Papers, “BeanMachine for the Web”,http://review.software.ibm.com/developer/library/beanmachine.html, Jan. 1998, 2pp.Applicant
- “SGML Tool: One document, several formats” Computer World, Microstar Software Ltd., Sep. 9, 1996, vol. 30, Issue 37, pp. 58.Applicant
- Microsoft Corporation, “Dynamic HTML Overview,” 1998, Internet article available at http://www.microsoft.com/workshop/author/dhtml/dhtmlovw.asp (3 pages).Applicant
- Sun Microsystems, Inc., “Servlet Specification—Version 2.1,” 1995-98, Internet article available at http://java.sun.com/products/servlet/2.1/index.html (2pages).Applicant
- W3C (MIT, INRIA, Keio), “Extensible Markup Language (XML) 1.0,” 1998, Internet article available at http://www.w3.org/TR/REC-xml (41 pages).Applicant
- W3C (MIT, INRIA, Keio), “Namespaces in XML,” 1998, Internet article available at http://www.w3.org/TR/WD-xml-names (11 pages).Applicant
- Aho, Alfred V. et al., “Efficient String Matching: An Aid to Bibliographic Search,” Communications of the ACM, 1975, pp. 333-340.Applicant
- Budinsky, F.J., et al, “Automatic Code Generation from Design Patterns,” IBM Systems Journal, vol. 35, No. 2, 1996, pp. 151-171.Applicant
- Ramesh, R et al., “Non-linear Pattern Matching in Trees,” Journal of the Association for Computing Machinery, vol. 39, No. 2, Apr. 1992, pp. 295-316.Applicant