| Data reporting application programming interfaces in an xml parser generator for xml validation and deserialization -> Monitor Keywords |
|
|
  Data reporting application programming interfaces in an xml parser generator for xml validation and deserializationThe Patent Description & Claims data below is from USPTO Patent Application 20080046874. 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]The present invention relates to the field of data reporting when parsing XML documents, and more particularly to how to directly deserialize the data in an application-specific format, without costly intermediate processing and representations. [0004]2. Description of Background [0005]Extensible Markup Language, or XML, parsers are deployed in varying applications, each requiring different application interfaces to report the data with. Sometimes this is achieved by writing an entire application specific parser or by writing the parser against a sufficiently general and low level Application Programming Interface, or API, and supplying transducers for application-specific data structures. Other times, parsers are written to support several APIs, or are written as a collection of multiple generalized components only some of which are used each time. For example, Xerces, an open source XML parser, supports several versions of the Simple API for XML, or SAX, and the Document Object Model API, or DOM, as well as Xerces Native Interface, or XNI, making it slower. Other XML parsers have been written as a collection of generalized components, which the end user has to assemble by hand. In all these cases, adding a new API requires a lot of new code that is low-level, high-complexity, hard-to-debug, and hard-to-maintain. The user ends up modifying the validation code to add support for a new data reporting API. [0006]Therefore, a method for generating the appropriate API code relevant to the particular usage of an XML parser would be highly desirable. SUMMARY OF THE INVENTION [0007]Exemplary embodiments include a method for interfacing with an XML (Extensible Markup Language) parser generator to generate deserialization information interleaved with XML parsing and validation, including: configuring a parser generator with information about the schema which the instance data conforms to, in order to generate an XML parser that parses and validates the instance data efficiently; providing a data reporting application programming interface (API) and a generator module; providing one or more implementations of the data reporting API; providing the XML parser generator with a data reporting API implementation module; generating an XML parser to parse and validate instance documents conforming to the specified input schema and deserializing the instance documents into the desired deserialization format during the parse. [0008]System and computer program products corresponding to the above-summarized methods are also described and claimed herein. [0009]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 to the drawings. TECHNICAL EFFECTS [0010]As a result of the summarized invention, technically we have achieved a solution, which provides a means of interfacing with a standalone data reporting API generator module that is interfaced with by the parser generator, to designate the desired deserialization code into the generated parsing and validation code. BRIEF DESCRIPTION OF THE DRAWINGS [0011]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: [0012]FIG. 1 illustrates the interaction between the parser generator and an event stream data reporting API generator module that uses SAX events to notify the application of the instance document data, and shows the code generated in the resulting parser, in accordance with exemplary embodiments; and [0013]FIG. 2 illustrates the interaction between the parser generator and a business object data reporting API generator module for the case when deserialization into application specific objects is needed by the application, in accordance with exemplary embodiments. [0014]The detailed description explains the preferred embodiments of the invention, together with advantages and features, by way of example with reference to the drawings. DETAILED DESCRIPTION OF THE INVENTION [0015]The present invention and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. It should be noted that the features illustrated in the drawings are not necessarily drawn in all detail possible. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the present invention in detail. The examples used herein are intended merely to facilitate an understanding of ways in which the invention may be practiced and to further enable those of skill in the art to practice the invention. Accordingly, the examples should not be construed as limiting the scope of the invention. [0016]In exemplary embodiments, a data reporting API module may be implemented as an independent piece of the parser generator. The data reporting API module is invoked during code generation, and given context information of where the parser is at the time of invocation. At that point, the data reporting API module determines what code needs to be generated into the runtime instruction stream. The XML Parser generated in this way contains the exact code needed to generate the targeted event stream, business object, or other structure, resulting in very efficient notifications or deserialization into objects, during the parsing phase. [0017]Different implementations of the data reporting API object are loaded during the code generation phase, based on information provided by the user regarding the desired deserialization format of the XML instance data. FIG. 1 shows an example of an event stream API generator object that uses SAX events to notify the application of the instance document data. FIG. 2 shows sample API Generator code as well as the corresponding generated code for the case where deserialization into application specific objects is needed by the application. The specific deserialization API shown in the figure is Java API for XML-Based Remote Procedure Call, or JAX-RPC. [0018]In one embodiment, application specific operations are inserted directly into the generated executable code, in a context sensitive way. This is achieved by associating actions with their context, in a way that disengages them from the operational details of parsing and validation. Arbitrary code can be inserted for specific contextual aspects, through the use of a generalized data reporting API generator module, which removes indirection layers at runtime and allows for optimal performance. The compile-time separation of application-specific code into separate modules results in parser generator code that is simpler and easier to maintain. For example, adding or removing support for a different data reporting interface would no longer require any modification of the parsing or validation code. Continue reading... Full patent description for Data reporting application programming interfaces in an xml parser generator for xml validation and deserialization Brief Patent Description - Full Patent Description - Patent Application Claims Click on the above for other options relating to this Data reporting application programming interfaces in an xml parser generator for xml validation and deserialization patent application. Patent Applications in related categories: 20080295083 - Explicit delimitation of semantic scope - Systems and methods are provided with respect to computer programming. Program behavior can be tuned to provide a seamless mixture of semantic behavior across a single program language syntax. Semantic behavior can be explicitly specified at arbitrary levels of syntactic granularity (e.g. expressions, members, types, compilation units . . . ... ###  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 Data reporting application programming interfaces in an xml parser generator for xml validation and deserialization or other areas of interest. ### Previous Patent Application: Compiler using interactive design markup language Next Patent Application: Method and system for providing dynamically configurable and extensible control of electronic devices Industry Class: Data processing: software development, installation, and management ### FreshPatents.com Support Thank you for viewing the Data reporting application programming interfaces in an xml parser generator for xml validation and deserialization patent info. IP-related news and info Results in 0.13681 seconds Other interesting Feshpatents.com categories: Electronics: Semiconductor , Audio , Illumination , Connectors , Crypto , |
||
