| Validator-driven architecture of an xml parsing and validating solution -> Monitor Keywords |
|
|
  Validator-driven architecture of an xml parsing and validating solutionUSPTO Application #: 20080028375Title: Validator-driven architecture of an xml parsing and validating solution Abstract: A method for parsing a document in an Extensible Markup Language (XML) format includes identifying data via the XML format, defining a tag set including a plurality of tags, defining a tokenizer that produces one token at a time, parsing the XML document via a parser, validating the XML document via a validation engine, the validation engine driving the tokenizer, the validating being an integral part of the parsing, and permitting the validation engine to be written in a recursive-descent code-driven manner. (end of abstract)
Agent: Cantor Colburn LLP-ibm Yorktown - Bloomfield, CT, US Inventors: Moshe E. Matsa, Eric Perkins USPTO Applicaton #: 20080028375 - Class: 717141 (USPTO) The Patent Description & Claims data below is from USPTO Patent Application 20080028375. Brief Patent Description - Full Patent Description - Patent Application Claims
TRADEMARKS [0001]IBM.RTM. is a registered trademark of International Business Machines Corporation, Armonk, N.Y., U.S.A. Other names used herein may be registered trademarks, trademarks or product names of International Business Machines Corporation or other companies. BACKGROUND OF THE INVENTION [0002]1. Field of the Invention [0003]This invention relates to XML parsers, and particularly to a method that treats validation engines as an integral part of parsing by allowing the validation engines to be written in a recursive-descent code-driven manner. [0004]2. Description of Background [0005]XML (Extensible Markup Language) has begun to work its way into the business computing infrastructure and underlying protocols such as the Simple Object Access Protocol (SOAP) and Web services. In the performance-critical setting of business computing, however, the flexibility of XML becomes a liability due to the potentially significant performance penalty. XML processing is conceptually a multitiered task, an attribute it inherits from the multiple layers of specifications that govern its use including: XML, XML namespaces, XML Information Set (Infoset), and XML Schema. Traditional XML processor implementations reflect these specification layers directly. Bytes, read off the "wire" or from disk, are converted to some known form. Attribute values and end-of-line sequences are normalized. Namespace declarations and prefixes are resolved, and the tokens are then transformed into some representation of the document Infoset. The Infoset is optionally checked against an XML Schema grammar (XML schema, schema) for validity and rendered to the user through some interface, such as Simple API for XML (SAX) or Document Object Model (DOM) (API stands for application programming interface). [0006]With the widespread adoption of SOAP and Web services, XML-based processing, and parsing of XML documents in particular, is becoming a performance-critical aspect of business computing. In such scenarios, XML is invariably constrained by XML parsing and validation by having the tokenizer drive the validation engine. In fact, most tokenizers parse the entire XML document by performing tokenizing with a DOM or SAX event stream and then run the validation engine over the stream of tokens or the DOM. However, technologies that treat validation as an integral part of parsing have not reached their full potential. Regardless of which manner of pushing the tokens is used, none of the current technologies allow the validation engine to be written in a recursive-descent code driven manner. As a result, this requires large tables, which increase the memory footprint, thus slowing processing efficiency. It also makes the validation code slower, and obscures the control flow of the whole parsing and validation processes. [0007]Thus, it is well known that there are no existing technologies that treat validation as an integral part of parsing. Therefore, it is desired to integrate validation and parsing, and enable the writing of the validation engine in a recursive-descent code-driven manner. SUMMARY OF THE INVENTION [0008]The shortcomings of the prior art are overcome and additional advantages are provided through the provision of a method for parsing a document, the document being in an Extensible Markup Language (XML) format, the method comprising: identifying data via the XML format; defining a tag set including a plurality of tags; defining a tokenizer that produces one token at a time; parsing the XML document via a parser; validating the XML document via a validation engine, the validation engine driving the tokenizer, and the validating being an integral part of the parsing; and permitting the validation engine to be written in a recursive-descent code-driven manner. [0009]The shortcomings of the prior art are overcome and additional advantages are provided through the provision of a system for parsing a document, the document being in an Extensible Markup Language (XML) format, the system comprising: a network; and a host system in communication with the network, the host system including XML software to implement a method comprising: identifying data via the XML format; defining a tag set including a plurality of tags; defining a tokenizer that produces one token at a time; parsing the XML document via a parser; validating the XML document via a validation engine, the validation engine driving the tokenizer, and the validating being an integral part of the parsing; and permitting the validation engine to be written in a recursive-descent code-driven manner. [0010]The shortcomings of the prior art are overcome and additional advantages are provided through the provision of a computer program for parsing a document, the document being in an Extensible Markup Language (XML) format, the computer program product comprising: a storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising: identifying data via the XML format; defining a tag set including a plurality of tags; defining a tokenizer that produces one token at a time; parsing the XML document via a parser; validating the XML document via a validation engine, the validation engine driving the tokenizer, and the validating being an integral part of the parsing; and permitting the validation engine to be written in a recursive-descent code-driven manner. [0011]Additional features and advantages are realized through the techniques of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. For a better understanding of the invention with advantages and features, refer to the description and the drawings. TECHNICAL EFFECTS [0012]As a result of the summarized invention, technically we have achieved a solution that integrates validation and parsing, thus resulting in a faster and more efficient validating parser, without large tables, and with a clear control flow through the entire parsing and validating processes. BRIEF DESCRIPTION OF THE DRAWINGS [0013]The subject matter, which is regarded as the invention, is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which: [0014]FIG. 1 illustrates one example of a diagram showing a validating engine communicating with a parser in order to receive a start tag; [0015]FIG. 2 illustrates one example of a diagram showing the parser communicating with the validating engine in order to send the start tag; [0016]FIG. 3 illustrates one example of a diagram showing the validation code calling a function GetNextTag( ); [0017]FIG. 4 illustrates one example of a diagram showing the parser transferring control back to the validating engine; [0018]FIG. 5 illustrates one example of a method for parsing and validating a document in a XML (Extensible Markup Language) format; and [0019]FIG. 6 illustrates one example of a communication between a validating engine and a parsing engine. Continue reading... Full patent description for Validator-driven architecture of an xml parsing and validating solution Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Validator-driven architecture of an xml parsing and validating solution patent application. ###  How KEYWORD MONITOR works... a FREE service from FreshPatents1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored. 3. Each week you receive an email with patent applications related to your keywords. Start now! - Receive info on patent apps like Validator-driven architecture of an xml parsing and validating solution or other areas of interest. ### Previous Patent Application: Method for validating ambiguous w3c schema grammars Next Patent Application: Simple one-pass w3c xml schema simple type parsing, validation, and deserialization system Industry Class: Data processing: software development, installation, and management ### FreshPatents.com Support Thank you for viewing the Validator-driven architecture of an xml parsing and validating solution patent info. IP-related news and info Results in 1.51547 seconds Other interesting Feshpatents.com categories: Software: Finance , AI , Databases , Development , Document , Navigation , Error |
||
