US2015205778A1PendingUtilityA1

Reducing programming complexity in applications interfacing with parsers for data elements represented according to a markup languages

Assignee: ORACLE INT CORPPriority: Oct 5, 2004Filed: Nov 17, 2014Published: Jul 23, 2015
Est. expiryOct 5, 2024(expired)· nominal 20-yr term from priority
G06F 16/83G06F 16/80G06F 16/245G06F 16/22G06F 17/30312G06F 17/30923G06F 17/30424G06F 17/272G06F 40/143G06F 40/221
55
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

According to an aspect of the present invention, a parser provides the portion identifiers (e.g., Xpath(s) in case of XML data files) of at least some of the data elements to the applications. As a result, the applications may be relieved from the task of computing the XPath(s) for various data elements. The implementation of applications may be simplified as a result. In one embodiment, prior API (application programming interface) is extended to provide the XPath(s). In an alternative embodiment, custom API is provided to enable the applications to obtain the XPath(s).

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method of processing data elements represented according to a markup language, said method comprising:
 receiving, in an object oriented parser, a file identifier of a data file with an instruction to parse said data file from an application implemented external to said object oriented parser, said data file containing a plurality of data elements;   retrieving, by said object oriented parser, each of said plurality of data elements from said data file;   for each of the retrieved data elements:
 determining, in said object oriented parser, a corresponding portion identifier of the retrieved data element, wherein said corresponding portion identifier indicates a relative path of the retrieved data element with respect to another data element in said data file according to said markup language, said relative path identifying one or more data elements between the retrieved data element and said another data element according to said markup language; and 
 providing, by said object oriented parser to said application, the retrieved data element and said corresponding portion identifier of the retrieved data element in association, 
 wherein said corresponding portion identifier is provided to said application, in the form of a string representing said relative path such that said application receives said string, 
   wherein said object oriented parser provides said plurality of data elements and respective portion identifiers, in association, as a response to said instruction.   
     
     
         2 . The method of  claim 1 , wherein said markup language comprises XML and said corresponding portion identifier of the retrieved data element comprises an XPath representing said relative path of the retrieved data element from said another data element. 
     
     
         3 . The method of  claim 1 , wherein said providing provides said corresponding portion identifier and the retrieved data element according to an application programming interface (API), wherein said application obtains said corresponding portion identifier and the retrieved data element by using one or more procedure calls according to said API. 
     
     
         4 . The method of  claim 3 , wherein said API is defined to provide said corresponding portion identifier and the retrieved data element as respective parameters of a single procedure call. 
     
     
         5 . The method of  claim 3 , wherein said API provides a procedure for said application to request that said XPath is to be provided either in abbreviated or non-abbreviated format. 
     
     
         6 . The method of  claim 3 , wherein said API provides a procedure for said application to request that attributes related to the retrieved data element are to be returned as XPaths. 
     
     
         7 . The method of  claim 3 , wherein said API provides a procedure for said application to request that attributes related to the retrieved data element are to be returned as values associated with the retrieved data element. 
     
     
         8 . The method of  claim 1 , wherein said retrieving retrieves successive data elements from said data file, wherein said determining determines the portion identifier for all of the data elements in said data file, wherein each portion identifier is determined based on a hierarchy in which the data element is present according to said markup language, and wherein the portion identifier is determined upon retrieval of the corresponding data element from said data file. 
     
     
         9 . The method of  claim 1 , wherein said relative path comprises a hierarchical path from a root data element contained in said plurality of data elements, wherein said root data element occurs at the beginning of said data file. 
     
     
         10 . A method implemented in an application, said method comprising:
 instructing an object oriented parser to parse a data file of interest, said data file containing a plurality of data elements represented according to a markup language, said object oriented parser being implemented external to said application;   obtaining said plurality of data elements from said object oriented parser in response to said instructing, wherein each of said plurality of data elements is obtained in association with a corresponding portion identifier of the obtained data element,   wherein said corresponding portion identifier indicates a relative path of the obtained data element with respect to another data element in said data file according to said markup language, said relative path identifying one or more data elements between the obtained data element and said another data element according to said markup language,   wherein said obtaining comprises receiving, by said application, said corresponding portion identifier in the form of a string representing said relative path; and   processing the obtained data elements and said corresponding portion identifiers.   
     
     
         11 . The method of  claim 10 , wherein said markup language comprises XML and said corresponding portion identifier of the retrieved data element comprises an XPath representing said relative path of the retrieved data element from said another data element. 
     
     
         12 . The method of  claim 10 , wherein said obtaining further comprises accessing each data element and said corresponding portion identifier in a data structure. 
     
     
         13 . The method of  claim 10 , wherein said obtaining obtains said corresponding portion identifier and associated one of said plurality of data elements according to an application programming interface (API). 
     
     
         14 . The method of  claim 13 , wherein said API is defined to provide said corresponding portion identifier and the associated data element as respective parameters of a single procedure call. 
     
     
         15 . The method of  claim 13 , wherein said API provides a procedure for said application to request that said XPath is to be provided either in abbreviated or non-abbreviated format. 
     
     
         16 . The method of  claim 13 , wherein said API provides a procedure for said application to request that attributes related to each of said plurality of data elements are to be returned as corresponding XPaths. 
     
     
         17 . The method of  claim 13 , wherein said API provides a procedure for said application to request that attributes related to each of said plurality of data elements are to be returned as values associated with the obtained data element. 
     
     
         18 . A computer readable medium carrying one or more sequences of instructions causing a digital processing system to process data elements represented according to a markup language, wherein execution of said one or more sequences of instructions by one or more processors contained in said digital processing system causes said digital processing system to perform the actions of:
 receiving, in an object oriented parser, a file identifier of a data file with an instruction to parse said data file from an application implemented external to said object oriented parser, said data file containing a plurality of data elements;   retrieving, by said object oriented parser, each of said plurality of data elements from said data file;   for each of the retrieved data elements:
 setting, in said object oriented parser, a corresponding portion identifier of the retrieved data element to equal a relative path of the retrieved data element with respect to another data element in said data file according to said markup language, said relative path identifying one or more data elements between the retrieved data element and said another data element according to said markup language; and 
 providing, by said object oriented parser to said application, said portion identifier and the retrieved data element in association, 
 wherein said corresponding portion identifier is provided to said application, in the form of a string representing said relative path such that said application receives said string, 
   wherein said object oriented parser provides said plurality of data elements and respective portion identifiers, in association, as a response to said instruction.   
     
     
         19 . The computer readable medium of  claim 18 , wherein said markup language comprises XML and said corresponding portion identifier of the retrieved data element comprises an XPath representing said relative path of the retrieved data element from said another data element. 
     
     
         20 . The computer readable medium of  claim 18 , wherein said providing further comprises:
 storing, by said object oriented parser, the retrieved data element and said corresponding portion identifier in a data structure, wherein said application obtains the retrieved data element and said corresponding portion identifier from said data structure.

Join the waitlist — get patent alerts

Track US2015205778A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.