Source: http://www.google.es/patents/US7802180?hl=es&dq=flatulence
Timestamp: 2017-08-22 11:25:24
Document Index: 202372672

Matched Legal Cases: ['Application No. 60', 'art 2', 'Application No. 2001290693', 'application No. 2007229359', 'application No. 2007229358', 'application No. 2001290693', 'Application No. 05', 'application No. 2007229358', 'application No. 2007229359', 'application No. 533163', 'application No. 200480011704', 'Application No. 05', 'application No. 533163', 'application No. 200480011704', 'art 1', 'art 1', 'art 2', 'art 2']

Patente US7802180 - Techniques for serialization of instances of the XQuery data model - Google Patentes
A method for representing XML information is provided. A serialized image of XML information is generated. The serialized image comprises a collection of one or more serialized data values, where each particular serialized data value in the collection includes data associated with a particular serialized...http://www.google.es/patents/US7802180?utm_source=gb-gplus-sharePatente US7802180 - Techniques for serialization of instances of the XQuery data model
Número de publicación US7802180 B2
Número de solicitud US 11/246,429
Fecha de prioridad 23 Jun 2004
También publicado como CA2572272A1, CA2572272C, CN1997995A, CN1997995B, DE602005022069D1, EP1759315A1, EP1759315B1, US20060036935, WO2006009768A1
Número de publicación 11246429, 246429, US 7802180 B2, US 7802180B2, US-B2-7802180, US7802180 B2, US7802180B2
Inventores James W. Warner, Zhen Hua Liu, Muralidhar Krishnaprasad
Citas de patentes (213), Otras citas (139), Citada por (11), Clasificaciones (6), Eventos legales (3)
Techniques for serialization of instances of the XQuery data model
US 7802180 B2
A method for representing XML information is provided. A serialized image of XML information is generated. The serialized image comprises a collection of one or more serialized data values, where each particular serialized data value in the collection includes data associated with a particular serialized data value type of a plurality of serialized data value types. The serialized image may also comprise a first field that includes a first value, which indicates that the serialized image includes the collection of one or more serialized data values. In some embodiments, the method is performed at a database system that supports a native XML data type, wherein the XML information is one or more instances of the native XML data type.
1. A method for representing eXtensible Markup Language (XML) information, comprising the computer-implemented steps of:
generating a serialized image of XML information, wherein the serialized image comprises:
a collection of two or more serialized data values, wherein each particular serialized data value in the collection includes data associated with a particular serialized data value type of a plurality of serialized data value types;
wherein the plurality of serialized data value types includes two or more of: an atomic type, a range type that describes a set of sequential items, an attribute type, a qualified name type, a dynamic function type, and a node type;
wherein the plurality of serialized data value types are defined in a data model specification that defines at least structures and data types for XML information;
wherein the collection of two or more serialized data values includes: a first serialized data value that is associated with a first serialized data value type of the plurality of serialized data value types, and a second serialized data value that is associated with a second serialized data value type of the plurality of serialized data value types, wherein the first serialized data value type is different than the second serialized data value type; and
a first field that includes a first value which indicates that the serialized image includes the collection of two or more serialized data values;
2. The method of claim 1, wherein each of the two or more serialized data values represents one or more XQuery items in the serialized image.
3. The method of claim 1, wherein the node type describes any one of an XML attribute, an XML element, an XML document, an XML schema-based element, an XML schema-based attribute, an XML comment, and an XML processing-instruction.
retrieving, from the serialized image, the data included in at least one serialized data value in the collection of two or more serialized data values; and
processing the data retrieved from the serialized image;
wherein the steps of the method are performed at a database system that supports a native XML data type, wherein the XML information is one or more instances of the native XML data type.
5. The method of claim 1, wherein each particular serialized data value in the collection of two or more serialized data values comprises:
a payload that comprises the data associated with the particular serialized data value type; and
a serialized data value type field that includes a field value which indicates the particular serialized data value type.
the field value indicates that the particular serialized data value type is associated with an atomic value;
the data associated with the particular serialized data value type includes the atomic value; and
the particular serialized data value further comprises:
a first data type field, wherein the first data type field includes a first information which indicates a first data type of the atomic value; and
a length field, wherein the length field includes a third information which indicates the length of the atomic value.
7. The method of claim 6, wherein the first data type of the atomic value is any one of an XML data type and a Structured Query Language (SQL) data type.
the field value indicates that the particular serialized data value type is associated with a range of values that includes a start value and an end value, wherein the start value and the end value are of a numeric data type;
the data associated with the particular serialized data value type includes the start value and the end value; and
the payload further comprises:
a start value field, wherein the start value field stores the start value; and
an end value field, wherein the end value field stores the end value.
the field value indicates that the particular serialized data value type is associated with a standalone attribute, wherein the standalone attribute includes an attribute name and an attribute value;
the data associated with the particular serialized data value type includes the attribute name and the attribute value, wherein the payload comprises a first portion that stores the attribute name, and a second portion that stores the attribute value; and
a first length field, wherein the first length field includes a first information which indicates the length of the attribute name; and
a second length field, wherein the second length field includes a second information which indicates the length of the attribute value.
the attribute name is a qualified XQuery name that comprises a prefix and a local name; and
the first portion of the payload further comprises:
a third length field, wherein the third length field includes a third information which indicates the length of the prefix;
a prefix field which stores the value of the prefix;
a fourth length field, wherein the fourth length field includes a fourth information which indicates the length of the local name; and
a local name field which stores the value of the local name.
the qualified XQuery name further comprises a namespace; and
a fifth length field, wherein the fifth length field includes a fifth information which indicates the length of the namespace; and
a namespace field which stores the value of the namespace.
the field value indicates that the particular serialized data value type is associated with a standalone qualified XQuery name, wherein the qualified XQuery name comprises a namespace, a prefix, and a local name;
the data associated with the particular serialized data value type includes values for at least one of the namespace, the prefix, and the local name; and
a first length field, wherein the first length field includes a first information which indicates the length of the namespace;
a namespace field which stores the value of the namespace;
a second length field, wherein the second length field includes a second information which indicates the length of the prefix;
a third length field, wherein the third length field includes a third information which indicates the length of the local name; and
the field value indicates that the particular serialized data value type is associated with an XQuery node;
the data associated with the particular serialized data value type is a series of bytes that represents the XQuery node; and
a node-type field, wherein the node-type field includes a first information that indicates the kind of the XQuery node;
a length field, wherein the length field includes a second information which indicates the length of the series of bytes; and
a format field, wherein the format field includes a third information which indicates a format of the series of bytes.
the XQuery node conforms to an XML schema; and
the first information indicates that the XQuery node is any one of an XML attribute, an XML element, an XML document, an XML schema-based element, an XML schema-based attribute, an XML comment, and an XML processing-instruction.
15. The method of claim 13, wherein the format of the series of bytes is a particular format of a plurality of XML serialization formats, wherein the plurality of XML serialization formats include at least one of:
a first format for a locator for a large object in storage that is shared by components of a database system;
a second format for a reference to an object in the database system, wherein the object can be accessed by components of the database system;
a third format used as a serialized format for objects in the database system;
a fourth format for a pointer to a memory location in memory shared by components of the database system;
a fifth format for compressed text; and
a sixth format for uncompressed text.
16. The method of claim 1, wherein the step of generating the serialized image comprises:
retrieving the data for each serialized data value in the collection of two or more serialized data values;
generating each serialized data value in the collection of two or more serialized data values; and
constructing the serialized image by concatenating each serialized data value in the collection of two or more serialized data values.
the first serialized data value includes first data that is associated with the first serialized data value type of the plurality of serialized data value types; and
the second serialized data value includes second data that is associated with the second serialized data value type of the plurality of serialized data value types.
18. A machine-readable volatile or non-volatile medium storing one or more sequences of instructions for representing eXtensible Markup Language (XML) information, which instructions, when executed by one or more processors, cause the one or more processors to perform steps comprising:
a first field that includes a first value which indicates that the serialized image includes the collection of two or more serialized data values.
19. The machine-readable volatile or non-volatile medium of claim 18, wherein each of the two or more serialized data values represents one or more XQuery items in the serialized image.
20. The machine-readable volatile or non-volatile medium of claim 18, wherein the node type describes any one of an XML attribute, an XML element, an XML document, an XML schema-based element, an XML schema-based attribute, an XML comment, and an XML processing-instruction.
21. The machine-readable volatile or non-volatile medium of claim 18, wherein the one or more sequences of instructions further comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform the steps of:
wherein the one or more sequences of instructions are performable at a database system that supports a native XML data type, wherein the XML information is one or more instances of the native XML data type.
22. The machine-readable volatile or non-volatile medium of claim 18, wherein each particular serialized data value in the collection of two or more serialized data values comprises:
23. The machine-readable volatile or non-volatile medium of claim 22, wherein:
24. The machine-readable volatile or non-volatile medium of claim 23, wherein the first data type of the atomic value is any one of an XML data type and a Structured Query Language (SQL) data type.
25. The machine-readable volatile or non-volatile medium of claim 22, wherein:
26. The machine-readable volatile or non-volatile medium of claim 22, wherein:
27. The machine-readable volatile or non-volatile medium of claim 26, wherein:
29. The machine-readable volatile or non-volatile medium of claim 22, wherein:
30. The machine-readable volatile or non-volatile medium of claim 22, wherein:
31. The machine-readable volatile or non-volatile medium of claim 30, wherein:
32. The machine-readable volatile or non-volatile medium of claim 30, wherein the format of the series of bytes is a particular format of a plurality of XML serialization formats, wherein the plurality of XML serialization formats include at least one of:
33. The machine-readable volatile or non-volatile medium of claim 18, wherein the instructions that cause generating the serialized image comprise instructions which, when executed by the one or more processors, cause the one or more processors to perform the steps of:
34. The machine-readable volatile or non-volatile medium of claim 18, wherein:
This application is a continuation-in-part of U.S. patent application Ser. No. 10/948,523, entitled “EFFICIENT EVALUATION OF QUERIES USING TRANSLATION”, filed by Zhen Hua Liu et al on Sep. 22, 2004 now U.S. Pat. No. 7,516,121, the entire contents of which are incorporated by reference for all purposes as if fully set forth herein, which claims the benefit of U.S. Provisional Application No. 60/582,706, filed Jun. 23, 2004, entitled “TECHNIQUES FOR PROCESSING XQUERY QUERIES IN A RELATIONAL DATABASE MANAGEMENT SYSTEM,” by Zhen Hua Liu et al, the entire contents of which are incorporated by reference for all purposes as if fully set forth herein. The present application claims priority to all previously filed applications mentioned in this paragraph.
This application is related to U.S. patent application Ser. No. 10/428,393, entitled “TECHNIQUES FOR TRANSFERRING A SERIALIZED IMAGE OF XML DATA”, filed by Muralidhar Krishnaprasad et al. on May 1, 2003, referred to hereafter as the “'393 application”, the entire contents of which are herein incorporated by reference as if fully set forth herein.
The present invention generally relates to extensible Markup Language (XML). The invention relates more specifically to a method for representing XML information.
The eXtensible Markup Language (XML) is a standard for data and documents that is finding wide acceptance in the computer industry. XML describes and provides structure to a body of data, such as a file, a data stream, or a data packet. The specification for XML was developed by the W3C consortium and is located on the Internet at “http://www.w3.org/XML”. As initially defined, the XML specification organizes information in XML nodes, where the XML nodes form a tree that consists of a root node and all the nodes that are hierarchically dependent on the root node. A tree of XML nodes whose root node is of a “Document Node” type is referred to as an XML document; a tree whose root node is not of a “Document Node” type is referred to as an XML fragment.
For example, the following Segment A
<publication publisher=“Doubleday”
year=“2003”></publication>
is an XML 1.0 document as indicated by the <?xml version=“1.0”> declaration. On the other hand, the following Segment B
is an XML fragment because its root node “<book>” is not a document node.
As initially defined, the XML specification provides for tags that delimit the sections of an XML entity, which sections are also referred to as XML elements. The data included between the tags is referred to as the XML element's content. Each XML element may contain one or more name-value pairs referred to as attributes. For example, in Segment B above, the start tag “<author>” and the end tag “</author>” delimit an XML element whose content is “Mark Berry”. The XML element delimited between the “<publication>” and “</publication>” tags includes two attributes: “publisher” which has a value of “Doubleday”, and “year” which has a value of “2003”.
The wide acceptance of XML as a standard for processing data led to the development of XML-enabled database systems. Some XML-enabled Relational Database Systems (RDBMS) and Object-Relational Database Systems (ORDBMS) provide a native built-in data type (referred to herein as XMLType) which allows users to store XML data natively via the use of XMLType tables or XMLType columns. Other XML-enabled database systems provide extensions and plug-ins that are capable of accessing and processing XML data stored as XML documents in XML repositories or other storage.
The ability to store XML data in database systems in turn led to the development of a new query language, the XML Query Language (referred to hereinafter as “XQuery”), for accessing and querying a broad spectrum of XML data and XML information resources. In order to support this new query language, a new data model, the XQuery Data Model, was developed. The XQuery Data Model defines precisely the information contained in the input to an XSLT or XQuery processing system and also defines all permissible values of expressions in the XQuery, XPath, and XSLT languages. A draft specification for XQuery is described in “XQuery 1.0: An XML Query Language”, W3C Working Draft 4 Apr. 2005, located at “http://www.w3.org/TR/xquery/”, the entire contents of which are incorporated by reference for all purposes as if fully set forth herein. A draft specification for XPath is described in “XML Path Language (XPath) 2.0”, W3C Working Draft 4 Apr. 2005, located at “http://www.w3.org/TR/xpath20/”, the entire contents of which are incorporated by reference for all purposes as if fully set forth herein. A draft specification for XSLT is described in “XSL Transformations (XSLT) Version 2.0”, W3C Working Draft 4 Apr. 2005, located at “http://www.w3.org/TR/xslt20/”, the entire contents of which are incorporated by reference for all purposes as if fully set forth herein. A draft specification for the XQuery Data Model is described in “XQuery 1.0 and XPath 2.0 Data Model”, W3C Working Draft 4 Apr. 2005, located at “http://www.w3.org/TR/xpath-datamodel/”, the entire contents of which are incorporated by reference for all purposes as if fully set forth herein.
The XQuery Data Model is generally based on the XML specification, but further requires support of at least the following new features:
Support for XML Schema types. The XML Schema recommendations define features, such as structures and simple data types, that extend the definitions in the XML specification with precise type information;
Representation of collections of documents and of complex values; and
In order to support processing of queries defined according to this new XQuery Data Model, an XML-enabled computer system or systems need to provide for efficient representation and processing of instances of this data model. As referred to herein, an instance of the XQuery Data Model is a block of data that conforms to the requirements set forth in the data model specification. For example, the processing of the following query written in the XQuery language,
for $b in doc (“http://bstore1.examp1e.com/bib.xml”) /bib/book
where $b/publisher = “Addison-Wesley” and $b/@year > 1991
<book year=“{ $b/@year }”>
requires at least parsing the query and identifying the instances of the XQuery Data Model, compiling the query and optimizing it if necessary, executing the query, and returning any result set to user.
Since the tasks related to processing an XQuery query may be performed by separate components of the same or a different computer system, the XQuery Data Model instances need to be represented in a uniform manner that is recognizable by the different components and/or computer systems. However, the currently existing mechanisms and techniques for representing XML information do not provide support for the new, strongly typed structural elements defined in the XQuery Data Model, such as, for example, atomic values and document nodes. For example, in an XML-enabled RDBMS that provides a native XMLType, the techniques described in the '393 application provide for representing and transferring a serialized image of XML data. However, since these techniques are developed to support XML data that conforms to the original XML specification, these techniques provide only for representing XML documents and XML fragments and do not address the issues raised by the introduction of the new, strongly typed structural elements in the XQuery Data Model.
Based on the foregoing, there is a clear need for techniques that provide for an efficient representation of instances of the XQuery Data Model that may be used in a variety of operational contexts.
FIG. 1 is a block diagram that illustrates an overview of the structure of a serialized image of XML information according to an embodiment;
FIG. 2 is a block diagram that illustrates an overview of the structure of a serialized data value that stores an atomic value according to an embodiment;
FIG. 3 is a block diagram that illustrates an overview of the structure of a serialized data value that stores a range of values according to an embodiment;
FIG. 4A is a block diagram that illustrates an overview of the structure of a serialized data value that stores a standalone attribute according to an embodiment;
FIG. 4B is a block diagram that illustrates an overview of the structure of an attribute name field that stores a qualified name according to an embodiment;
FIG. 5 is a block diagram that illustrates an overview of the structure of a serialized data value that stores an XQuery node according to an embodiment;
FIG. 6 is a block diagram that illustrates an overview of the structure of a serialized data value that stores a standalone qualified name according to an embodiment; and
Techniques for representing XML information are described herein. A serialized image of XML information is generated. The serialized image is a structured block of data representing a sequence. A sequence is a collection of one or more XQuery items, and is an instance of the XQuery data model. The serialized image is a collection of serialized data values, each representing one or more XQuery items. As used herein, an XML value refers to any value represented by the XQuery Data Model, and an instance of the XQuery Data Model may be an XML value. Each particular serialized data value in the serialized image includes an XML value or data that is associated with a particular serialized data value type. Serialized data value types are described hereinafter. In some embodiments, in addition to the collection of one or more serialized data values, a serialized image may also include a field for storing a value, which value indicates that the serialized image includes the collection of one or more serialized data values.
The techniques described herein provide for generating the serialized image by concatenating the serialized data values in a collection of one or more serialized data values. In one embodiment, after a request to generate a serialized image of XML information is received, the serialized image is created and opened for writing by making a call to the component of the computer system that is generating the image. The data for each serialized data value is retrieved based on the request. Each serialized data value is then generated, and a write call is made to add the serialized data value to the serialized image. After the series of write calls that add serialized data values to the serialized image are completed, a call is made to the component of the computer system to close the image. After the image is closed, it may be processed as indicated in the request.
The techniques described herein for serializing XML information may be used in a variety of contexts. For example, a serialized image of XML information generated according to the techniques described herein may be transferred from one component of a computer system to another component of the same system. Alternatively or in addition, a serialized image generated according to the techniques described herein may also be transferred from one computer system to another, or may be stored in a location in persistent or non-persistent storage that is shared by separate components of the same or a different computer system. Further, in some embodiments the serialized image may be structured as a stream that carries the collection of the one or more serialized data values. Thus, the techniques described herein are not limited to any particular context that may use serialized images.
After generating the serialized image, the data included in the serialized data values in the collection of one or more serialized data values may be retrieved and processed.
Operational Contexts
The techniques for serializing instances of the XQuery Data Model may be implemented in a wide variety of operational contexts. For example, serialized images of XML information as described herein may be transferred between separate components of the same computer system or between different computer systems.
For example, the techniques described herein may be implemented in a database system. The database system may receive an XQuery query from a client application, where the client application sends the elements of the query in a serialized image that is structured according to the techniques described herein. The database system receives the serialized image and extracts the elements of the XQuery query from it. The database system may then process the query, where the processing may involve creating serialized images according to the techniques described herein and transferring these images between components of the database system that participate in processing the query, such as, for example, between XQuery parsers, XQuery type checkers, XML compilers, etc. Depending on the particular implementation, serialized images generated according to the techniques described herein may be transferred between any entities, such as, for example, between processes in the same database system, between threads running in the same database system process, between two or more separate instances of the database system, between remote nodes of a distributed database system, and between separate processes that facilitate parallel processing of a query in a database system or systems.
Since the XQuery Data Model elements are strongly typed, the techniques described herein provide for lossless representation of XML information. The data types and other characteristics identified in any instances of the XQuery Data Model are preserved in the serialized images during any transfer or processing of the images in order to guarantee accurate and efficient processing of the underlying XQuery elements or documents represented by the instances.
Further, the serialized images of XML information described herein may be generated in response to a wide variety of requests.
For example, in one embodiment an object-relational database system supports a built-in XMLType data type for storing XML information natively in the database system. The XMLType data type is based on the SQL/XML standard defined in INCITS/ISO/IEC 9075-14:2003, the entire contents of which are incorporated herein by reference, and which is referred to hereinafter as the “SQL/XML 2003” standard. In this embodiment, the XMLType extends the SQL/XML 2003 standard by providing support for representing instances of the XQuery Data Model. To be compatible with the SQL/XML 2003 standard, this embodiment provides a type modifier to the XMLType, specified in parenthesis, which identifies the standard to which the XMLType conforms. For example, XML(CONTENT) stands for an XMLType that conforms to the SQL/XML 2003 standard; XML(SEQUENCE) stands for an XMLType that conforms to the XQuery Data Model and that is part of the new SQL/XML version. In this embodiment, an XMLType without the modifier (e.g. XML( )) is defaulted to XML(CONTENT). In addition, an XMLType with a DOCUMENT type modifier (e.g. XML(DOCUMENT)) may be used in this embodiment to represent XML(CONTENT) instances whose IS_DOCUMENT predicate is true (e.g. XMLType instances that are proper XML documents).
In this embodiment, querying of XML information is fully supported by using XQuery as the query language. The querying of XML information involves exchanging instances of the XQuery Data Model (as represented by the XMLType(SEQUENCE)) by using serialized images generated according to the techniques described herein. The serialized images may be generated by a variety of components and in response to a variety of circumstances. The serialized image may include instances of any supported XMLType, such as, for example, XML(SEQUENCE), XML(CONTENT), and XML(DOCUMENT). For example, an XMLType instance may be included in a serialized image for storing an XML document in an XMLType table or an XMLType column. In another example, XMLType instances may be generated from relational tables and views using SQL/XML 2003 publishing functions, such as XMLElement( ) and XMLAgg( ). The XMLType instances may then be included in a serialized image and the image may be further processed by the components in the database system that handle the publishing functions. In another example, XMLType instances may be generated from the result of an XQuery query embedded in an XMLQuery( ) function. In this example, after being generated, the XMLType instances may be included in a serialized image generated according to the techniques described herein and transferred to the client that called the XMLQuery( ) function. In another example, XMLType instances may be generated from the result of an XPath embedded in an Extracto function, and may be included in a serialized image for processing by the component that executed the Extract( ) function. In another example, an XMLType instance may be the return type of a user-defined or system-defined function, and may be included in a serialized image for processing by any component that calls the function. In another example, an XMLType instance can be converted from an object type, collection type or an arbitrary user-defined opaque type in the object-relational database system, or may be included in any SQL or functional operator in the database system. In this example, the XMLType instance may be included in a serialized image according to the techniques described herein and the image may be processed by any component of the database system that makes use of the object type, collection type, user-defined opaque type, or the operator supported by the database system.
Further, the techniques described herein for serialized representation of instances of the XQuery Data Model may be implemented in any computer system or systems that support processing or exchanging XML information. Examples of such systems include, but are not limited to, database systems, web systems, e-mail systems, OnLine Analytical Processing (OLAP) systems, and any systems capable of exchanging information over network data exchange protocols. Thus, the techniques described herein are not limited to any particular implementations, purpose, or use, and the examples provided herein are to be regarded in an illustrative rather than a restrictive sense.
Serialized Data Value Types
A serialized data value type describes a serialized data value, which corresponds to one or more XQuery items that are represented in a serialized image. An XQuery item is data which may be used in an XQuery expression and for which the XQuery Data Model provides at least a definition and a structure. As referred to herein, serialized data value types include any types that can describe now known or later defined XQuery items. The serialized data value types described herein include, but are not limited to, an atomic type, a range type that describes a set of sequential atomic values, and a node type that may be any one of an XQuery attribute type, an XML element type, an XQuery document type, an XML schema-based element type, an XML attribute type, an XML comment type, and an XML processing-instruction type. In addition, some embodiments may also support a dynamic function serialized data value type. A dynamic function serialized data value type describes a serialized data value, which may be generated on demand by a dynamic function or structure and which may represent an XQuery sequence or one or more XQuery items in a serialized image.
The XQuery items referred to herein are associated with XQuery item types that are described in the XQuery specification “XQuery 1.0: An XML Query Language”, W3C Working Draft 4 Apr. 2005, located at “http://www.w3.org/TR/xquery/”, the entire contents of which has been incorporated herein by reference, and in the XQuery Data Model specification “XQuery 1.0 and XPath 2.0 Data Model”, W3C Working Draft 4 Apr. 2005, located at http://www.w3.org/TR/xpath-datamodel/”, the entire contents of which has been incorporated herein by reference.
According to the XQuery specification and the XQuery Data Model specification, every XQuery item is either an atomic value or a node. An atomic value (e.g. the number “5” or the string “Hello world”) is data stored in the value space defined by an XQuery atomic type. A node (e.g. an XML element or an XML document) is an instance of one of the node kinds defined in the XQuery Data Model specification. Each node has a unique node identity, a typed value, and a string value. In addition, some nodes may have a name. The typed value of a node is a series of zero or more atomic values. The string value of a node is a value of type “xs:string”, which is a character data type defined for the XML Information Set. The name of a node is a value of type “xs:QName”, which is a data type that describes a qualified name as defined in the XQuery specification.
Some examples of XQuery item types that may be represented in serialized images by serialized data value types are provided below:
“xs:date” refers to the built-in atomic date data type named “xs:date”;
“attribute( )?” refers to an optional attribute node;
“element( )” refers to any element node;
“element(po:shipto, po:address)” refers to an element node that has the name “po:shipto” and has the type annotation “po:address” (which may be a schema type describing a post office address);
“element(*, po:address)” refers to an element node of any name that has the type annotation “po:address” (or a type derived from po:address);
“element(customer)” refers to an element node named “customer” with any type annotation;
“schema-element(customer)” refers to an element node whose name is “customer” and whose type annotation matches the schema type declared for a customer element in a schema declaration;
“node( )*” refers to a series of zero or more nodes of any kind.
Structure of a Serialized Image
A serialized image of XML information is a structured block of data that contains a collection of one or more serialized data values. A serialized data value is a structured block of data that corresponds to an instance of an XML value. In some embodiments, the XML value included in a serialized data value may be an instance of the XQuery Data Model. In other embodiments, for compatibility reasons, an XML value included in a serialized data value may also be an instance of a type aligned with the SQL/XML 2003 standard, or with any other XML-defined type that is now known or later developed.
FIG. 1 is a block diagram that illustrates an overview of the structure of a serialized image of XML information according to an embodiment. Serialized image 100 comprises image type field 104, and one or more serialized data values, such as serialized data values 106, 108, 110, and 112. In FIG. 1, ellipsis 111 indicates that serialized image 100 may include any number of serialized data values. Serialized image 100 may optionally comprise a version field 102.
The optional version field 102 stores a value that indicates a version of the image. In different embodiments, the version of the image may be associated with particular parameters, such as, for example, one or more parameters that indicate the version of the system generating and/or processing the image (e.g. an operating system version, a database system version, etc.)
In some embodiments, image type field 104 is used to identify the type of image 100 as an image that stores a collection of serialized data values and that is used in serialized representation of instances of the XQuery Data Model. For example, in a database system that supports the XMLType described above, image type field 104 may store a first value to indicate that the particular serialized image stores instances of XMLType(SEQUENCE), which type is used by the database system to represent instances of the XQuery Data Model. In the same database system, a different second value stored in image type field 104 may indicate that the particular serialized image stores instances of XMLType(CONTENT), which type is used by the database system to represent instances aligned with the SQL/XML 2003 standard.
A serialized data value included in serialized image 100, such as serialized data value 102, is a structured block of data that stores an instance of the XQuery Data Model. Each serialized data value in serialized image 100 includes data that is associated with a serialized data value type as described herein. The structure of each serialized data value corresponds to the structures defined for the particular serialized data value type that describes the serialized data value. In general, each serialized data value in serialized image 100 includes a serialized data value type field and a payload. The serialized data value type field stores a value that indicates the particular serialized data value type of the data that is stored in the serialized data value. The payload comprises the data that is stored in the particular serialized data value. The particular fields and other structural elements for supporting the different serialized data value types are described hereinafter.
In some embodiments, a serialized image may include only one serialized data value. In other embodiments, a serialized image may include a plurality of serialized data values. In these embodiments, each serialized data value in the plurality of serialized data values may store data that is associated with the same serialized data value type. In addition, each serialized data value in the plurality of serialized data values may store data that is associated with a first serialized data value type that is different from a second serialized data value type that is associated with data stored in one or more different serialized data values of the plurality of serialized data values.
To illustrate the structure of a serialized image generated according to the techniques described herein, consider the following request to serialize data that is associated with different serialized data value types:
R1 (2812, taxclass=“exempt”, <?xml version=10.0><a>A small XML document</a>) In request R1, “2812” is a numeric value, “taxclass=‘exempt”’ is a standalone attribute, and “<?xml version 1.0><a>A small XML document</a>” is a very small, albeit proper, XML document. Table 1 below depicts some of the fields and their corresponding values that may be included in a serialized image generated in response to request R1 according to the techniques described herein.
Example of Data Stored in a Serialized Image
Version 10gR2
Image Type SEQUENCE
Serialized data value Type ATOMIC
XML Type xsd:integer
Native Type dtynum
Value 2812
Serialized data value Type ATTRIBUTE
Attribute Name Length 8
Attribute Name taxclass
Attribute Value Length 6
Attribute Value exempt
Serialized data value Type NODE
Node Kind document
XML Serialization Format text
Node Content <?xml version=1.0><a>A small XML
As shown in the above Table 1, the serialized image stores each data in the request as a serialized data value of a particular serialized data value type. For example, the numeric value “2812” is stored in the image as a serialized data value of serialized data value type “ATOMIC”, the attribute “taxclass=‘exempt”’ is stored in the image as a serialized data value of serialized data value type “ATTRIBUTE”, and the small XML document is stored in the image as a serialized data value of serialized data value type “NODE”. Some of the fields in Table 1 (e.g. fields “XML Data Type”, “Native Data Type”, etc.) are specific for each particular serialized data value type and are discussed in detail hereinafter.
Structure of a Serialized Data Value of an Atomic Type
Atomic values, which may be represented herein by the atomic serialized data value type, are defined in the XQuery Data Model specification “XQuery 1.0 and XPath 2.0 Data Model”, W3C Working Draft 4 Apr. 2005, located at http://www.w3.org/TR/xpath-datamodel/”, the entire contents of which has been incorporated herein by reference. For example, the XQuery Data Model specification includes all the primitive data types that are defined in “XML Schema Part 2: Datatypes Second Edition”, W3C Working Draft 28 Oct. 2004, located at http://www.w3.org/TR/xmlschema-2/”, the entire contents of which is incorporated herein by reference as if fully set forth herein. Examples of these primitive types include the XML data types “xs:QName”, “xs:decimal”, “xs:boolean”, etc. In addition, the XQuery Data Model introduces and provides a schema for five new additional built-in data types, “xdt:untyped”, “xdt:untypedAtomic”, “xdt:anyAtomicType”, “xdt:dayTimeDuration”, and “xdt:yearMonthDuration”.
According to one embodiment, the structure of a serialized data value that includes data associated with an atomic serialized data value type is illustrated in FIG. 2. Serialized data value 200 comprises serialized data value type field 202, XML type field 204, native type field 206, length field 208, and value field 210.
Serialized data value type field 202 stores a value which indicates that the particular serialized data value includes data that is associated with an atomic serialized data value type.
XML type field 204 stores a value which indicates the XML data type of the data stored in the particular serialized data value. For example, if the particular serialized data value stores data for which the atomic XML data type is integer, then this field would store the value “xs:integer”.
Native type field 206 stores a value which indicates the native data type of the data stored in the particular serialized data value. The native data type is a data type supported by the computer system which generates the serialized image according to the techniques described herein; specifically, the native data type indicated by the value in native type field 206 is the data type used by the computer system to represent data that is associated with the XML type specified in field 204. For example, in a database system in which integers are represented by a Structured Query Language (SQL) data type, native type field 206 may store the value “SQL Number Type”.
In representing data of atomic serialized data value types, the techniques described herein provide for storing both the XML data type and the native data type for data that is included in serialized data values of the serialized image. Any specific information about the original data type of the data is preserved when the data is processed or transferred. For example, for numeric data, specific information about the data, such as, for example, arithmetic signs of integers, precision of real numbers, etc., is preserved in order to facilitate accurate processing of the data if the data is transferred. In this way, the techniques described herein provide for a lossless representation of instances of the XQuery Data Model.
Length field 208 stores a value which indicates the length of the data stored in value field 210. Depending on the particular implementation, the value stored in length field 208 may indicate a number of bytes, a number of bits, or any other data length indication that may be used by the computer system processing the value. Value field 210 stores the value of the instance of the XQuery Data Model, to which the particular serialized data value corresponds.
To illustrate the structure of a serialized data value storing data associated with an atomic serialized data value type, consider the following request R2:
R2 (2812)
In request R2, “2812” is a numeric value of the “xsd:integer” type. Suppose that the request is received by a database system in which numeric values of an integer data type are stored as SQL DTYNUM data type, where values of the DTYNUM data type are 4 bytes in length. In this case, a serialized data value generated in response to request R2 according to the techniques described herein comprises the fields and their corresponding values as shown in Table 2.
Example of Data Stored in a Serialized Data Value of Atomic Type
Structure of a Serialized Data Value of a Range Type
In one embodiment, the techniques described herein provide for a range serialized data value type. Logically, an instance of the range serialized data value type is an aggregation of instances that represents a plurality of serialized data values of a particular serialized data value type. In this embodiment, the range serialized data value type is defined as a separate serialized data value type in order to provide a scalable and efficient representation of a set of sequential XQuery values.
For example, suppose that a computer system needs to process an XQuery query that includes the range of values “1 to 1000”. Instead of generating and possibly transferring one thousand separate serialized data values, where each serialized data value stores an instance of an integer associated with an atomic serialized data value type, the techniques described herein provide for creating a single instance of the range serialized data value type, which instance indicates a set of sequential integer values from “1” to “1000”.
According to one embodiment, the structure of a serialized data value that includes data associated with a range serialized data value type is illustrated in FIG. 3. In this embodiment, serialized data value 300 comprises serialized data value type field 302, start value field 304, and end value field 306.
Serialized data value type field 302 stores a value which indicates that the particular serialized data value stores data that is associated with a range serialized data value type.
Start value field 304 stores the start value in the range represented by serialized data value 300. End value field 306 stores the end value in the range represented by serialized data value 300.
In this embodiment, the start value and the end value stored in start value field 304 and end value field 306, respectively, are represented in the serialized data value 300 in a data type that is native to the computer system that generates and processes the serialized image in which serialized data value 300 is included. Since according to the XQuery Data Model a range of values is always of “xs:integer” atomic type, in this embodiment the start and end values of a range are stored in a native data type in order to facilitate a more efficient transfer by providing for a smaller serialized image. For example, if the computer system is a database system that uses the SQL DTYNUM data type, then values stored in start value field 304 and end value field 306, respectively, are represented in the DTYNUM data type by default. In other embodiments, a serialized data value of the range serialized data value type may include one or more additional fields, the values of which may indicate the XML data type and/or the native data type of one or both of the start and end value of a value range represented in an instance of the range serialized data value type.
To illustrate the structure of a serialized data value storing data associated with a range serialized data value type, consider the following request R3:
R3 (1 to 1000)
In request R3, “1 to 1000” is a range of atomic values of the “xs:integer” XML data type. A serialized data value generated in response to request R3 according to the techniques described herein comprises the fields and their corresponding values as shown in Table 3.
Example of Data Stored in a Serialized Data Value of Range Type
Serialized data value Type RANGE
Start Value 1
End Value 1000
Structure of a Serialized Data Value of an Attribute Type
In one embodiment, a separate serialized data value type is provided to represent standalone XML attributes. A standalone attribute is an attribute that needs to be processed separately from the XML data or XQuery expression in which it is defined.
According to one embodiment, the structure of a serialized data value that includes data associated with an attribute serialized data value type is illustrated in FIG. 4A. In this embodiment, serialized data value 400 comprises serialized data value type field 402, attribute name length field 404, attribute name field 406, attribute value length field 408, and attribute value field 410.
Serialized data value type field 402 stores a value which indicates that the particular serialized data value stores data that is associated with an attribute serialized data value type.
Attribute name length field 404 stores a value which indicates the length of the attribute name in number of bytes. Attribute name field 406 stores the value of the name of the attribute. In some embodiments, the attribute name may be an XQuery qualified name. In these embodiments, attribute name field 406 stores the values which indicate the different portions that comprise an XQuery qualified name. The structures for representing the different portions of an XQuery qualified name are described hereinafter.
Attribute value length field 408 stores a value which indicates the length of the attribute value in bytes. Attribute value field 410 stores the value of the attribute.
To illustrate the structure of a serialized data value storing data associated with an attribute serialized data value type, consider the following XML element:
<a taxclass=“exempt”>Baby Food</a>
Suppose that, even though the attribute “taxclass=‘exempt”’ is defined in the above XML element, the computer system that processes the XML data needs to process this attribute separately from the XML element. Consider the following request R4:
R4 (taxclass=“exempt”)
In request R4, “taxclass=‘exempt”’ is considered a standalone attribute, and according to the techniques described herein it is represented by an instance of the attribute serialized data value type. A serialized data value generated in response to request R4 according to the techniques described herein comprises the fields and their corresponding values as shown in Table 4.
Example of Data Stored in a Serialized Data Value of Attribute Type
Structure of a Serialized Data Value which Includes a Qualified Name
According to the XQuery Data Model, qualified names may be used in XML data to identify different XML entities, such as, for example, attributes, variables, and functions. A qualified name, or a QName, is a set of three values representing: a possibly empty namespace, a possibly empty prefix, and a local name. The full definition of qualified names is provided in “Namespaces in XML”, W3C 14 Jan. 1999, located at “http://www.w3.org/TR/REC-xml-names/”, the entire contents of which are herein incorporated by reference as if fully set forth herein.
In one embodiment, an attribute name of a standalone attribute may be a qualified name. According to this embodiment, the structure of a qualified attribute name, such as the attribute name described in field 406 of FIG. 4A, is illustrated in FIG. 4B.
Referring to FIG. 4B, serialized data value 406 comprises namespace length field 420, namespace value field 422, prefix length field 424, prefix value field 426, local name length field 428, and local name value field 430.
Namespace length field 420 stores a value which indicates the length of the namespace in number of bytes. Namespace value field 422 stores the value of the namespace. Prefix length field 424 stores a value which indicates the length of the prefix in number of bytes. Prefix value field 426 stores the value of the prefix. Local name length field 428 stores a value which indicates the length of the local name in number of bytes. Local name value field 422 stores the value of the local name.
To illustrate the structure of a qualified attribute name, consider the following XML element:
<x xmlns:edi=“http://ecommerce.org/schema/”>
<a edi:taxclass=“exempt”>Baby Food</a>
The name of the “taxclass” attribute in the “<a>” XML element is a qualified name because it is qualified by the prefix “edi”. The prefix “edi” is specified as an attribute of the parent “<x>” XML element and is defined in the XML namespace schema located at “http://ecommerce.org/schema/”. Consider the following request R5:
R5 (edi:taxclass=“exempt”)
In request R5, “edi:taxclass=‘exempt”’ is considered a standalone attribute of attribute serialized data value type, which has a qualified attribute name. A serialized data value generated in response to request R5 according to the techniques described herein comprises the fields and their corresponding values as shown in Table 5.
Example of a Serialized Data Value of Attribute Type with a Qname
Attribute Name Length 39
Namespace Length 28
Namespace Value http://ecommerce.org/schema/
Prefix Length 3
Prefix Value edi
Local Name Length 8
Local Name Value taxclass
In other embodiments, any XML entity may be identified by an XQuery qualified name. These embodiments may use structures similar to the structures described herein for representing a qualified attribute name to represent any qualified name, such as, for example, a variable name, a function name, etc. Further, some embodiments may provide a separate serialized data value type to represent standalone qualified names as separate instances of the XQuery Data Model.
For example, in some embodiments a serialized data value may include data associated with a qualified name serialized data value type. One possible structure of such serialized data value is illustrated in FIG. 6. In FIG. 6, serialized data value 600 comprises serialized data value type field 602, namespace length field 420, namespace value field 422, prefix length field 424, prefix value field 426, local name length field 428, and local name value field 430.
Serialized data value type field 602 stores a value which indicates that the particular serialized data value includes data that is associated with a qualified name serialized data value type. The value stored in serialized data value type field 602 may be character data identifying the qualified name serialized data value type, such as, for example, the string “QNAME”. The rest of the fields in serialized data value 600, namely fields 420, 422, 424, 426, 428, and 430 may be the same as the fields described above with respect to FIG. 4B.
Structure of a Serialized Data Value of a Node Type
The XQuery item types that represent XQuery nodes are defined in the XQuery specification “XQuery 1.0: An XML Query Language”, W3C Working Draft 4 Apr. 2005, located at “http://www.w3.org/TR/xquery/”, the entire contents of which has been incorporated herein by reference. The XQuery specification defines the following node item types: XML attribute type, XML element type, XML document type, XML schema-based element type, XML schema-based attribute type, XML comment type, and XML processing-instruction type.
According to one embodiment, the structure of a serialized data value that includes data associated with a node serialized data value type is illustrated in FIG. 5. In this embodiment, serialized data value 500 comprises serialized data value type field 502, node kind field 504, length field 508, XML serialization format field 510, and node content field 512. In this embodiment, serialized data value 500 may optionally include a version field 506.
Serialized data value type field 502 stores a value which indicates that the particular serialized data value stores data that is associated with a node serialized data value type.
Node kind field 504 stores a value that indicates the particular kind of the XQuery node. For example, a first value stored in node kind field 504 may indicate that the content stored in node content field 512 is an XML element. A second value stored in node kind field 504 may indicate that the content stored in content field 512 is an XML document. Similarly, different values may be stored in node kind field 504 to indicate the different types of nodes that are supported by the node serialized data value type. In this way, the node instances of the XQuery Data Model included in a serialized image according to the techniques described herein may be properly processed by a computer system that generates and processes the serialized image. This feature is helpful when the node XQuery Data Model instances are included in XQuery queries, in the processing of which it makes a difference whether the node instance being passed is an entire XML document, or just an element of the document.
XML serialization format type field 510 includes a value which indicates the format of the content stored in node content field 512. Since the content of a node instance of the serialized data value type may be rather large, in some embodiments a serialization format is provided to facilitate a more efficient transfer of XML information. A set of possible XML serialization formats that may be used in these embodiments are described in the '393 application. For example, the XML serialization format may be an uncompressed text format, a compressed text format, a format for a locator of a large object in persistent storage that stores compressed XML data (e.g. a locator for a Large OBject (LOB)), a format for a reference to an object represented by an instance of a serialized data value type (e.g. XMLREF reference pointing to an object of XMLType in a object-relational database system), a format used as the format for images of serialized objects (e.g. OBJIMG format of images stored in persistent or non-persistent storage in a object-relational database system), and a format for a pointer to a shared location in memory where an instance of the node serialized data value type is stored (e.g. pointer to a shared location in the physical memory of a database system).
In some embodiments, serialized data value 500 may optionally include version field 506. Version field 506 stores a value which indicates a particular version of serialized data value 500. For example, in some embodiments, fields 506, 510, and 512 are included in images that were provided for storing instances of an XMLType that is aligned with the SQL/XML 2003 standard. In these embodiments, in order to provide a backward compatibility, such images may be stored directly in serialized data value 500. In these embodiments, the value stored in version field 506 of a particular serialized data value may be used to indicate whether the data of the instance stored in the serialized data value is of an SQL/XML type or of an XQuery Data Model type.
Length field 508 stores a value which indicates the length of the content stored in node content field 512. Node content field 512 stores the content of the node instance of the node serialized data value type that is included in serialized data value 500 in the format indicated by XML serialization format type field 510.
To illustrate the structure of a serialized data value storing data associated with a node serialized data value type, consider the following request R6:
R6 (<?xml version=1.0><a>A small XML document</a>)
In request R6, “<?xml version=1.0a>A small XML document</a>” is a proper XML document that is of a node serialized data value type, which node type is of the document kind. A serialized data value generated in response to request R6 according to the techniques described herein comprises the fields and their corresponding values as shown in Table 6.
Example of Data Stored in a Serialized Data Value of a Node Type
XML Serialization Format Type uncompressed text
Node Content <?xml version=1.0><a>A small
XML document</a>
In some embodiments, the techniques described herein provide for minimizing the size of serialized images that store serialized data values that include data associated with node serialized data value types. A call is made to open a serialized image, and the data of a particular serialized data value is initially being written in the image. Since instances of the node serialized data value type may get very large, a record is kept of how much information is written to the serialized image. When the size of the serialized image exceeds a predefined threshold, a pointer to a LOB in permanent storage is written in the node content field of the particular serialized data value, and the value in the XML serialized format type field is changed to indicate a “pointer-to-LOB” format. The data from the instance of the node serialized data value type is then transferred and written to a LOB in persistent storage. In this way, the size of the particular serialized data value, and respectively the size of the serialized image in which the particular serialized data value is included, is kept to a minimum while at the same time allowing relatively small instances of node types to be stored entirely in the image. This technique provides for efficient utilization of the computer system resources related to storing and transferring XML information, such as, for example, memory, persistent storage space, and CPU utilization.
Other Serialized Data Value Types
The techniques described herein allow for additional serialized data value types to be defined when there is a need to efficiently support serialization of specific instances of the XQuery Data Model that are related in some way. Instead of serializing related serialized data values of a particular serialized data value type or types, a new serialized data value type may be defined for representing these related serialized data values, where one serialized data value of this new serialized data value type will store enough information to uniquely identify the serialized data values and the relationships among them. In this way, the data stored in the related serialized data values can be efficiently transferred and processed without the need to serialize each separate serialized data value.
For example, a serialized data value type may be defined to support instances of values that are sequential but do not necessarily differ by equal increments. The dynamic function serialized data value type is an example of such serialized data value type. A serialized data value of a dynamic function serialized data value type may be used to store a set of values of a Fibonacci series that is generated by a function in an XQuery expression. In another example, a serialized data value type may be defined to support instances of serialized images that themselves include a collection of serialized data values storing XQuery values. A serialized data value of such serialized data value type may be used to represent two sets of serialized data values when one set is a superset of the other. Thus, the described techniques are not limited to the particular serialized data value types described in detail herein, and a wide variety of different serialized data value types may be defined in order to efficiently support a wide variety of situations in which transfer and processing of XML information is required.
The term “machine-readable medium” as used herein refers to any medium that participates in providing data that causes a machine to operation in a specific fashion. In an embodiment implemented using computer system 700, various machine-readable media are involved, for example, in providing instructions to processor 704 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as storage device 710. Volatile media includes dynamic memory, such as main memory 706. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise bus 702. Transmission media can also take the form of acoustic or light waves, such as those generated during radio-wave and infra-red data communications. All such media must be tangible to enable the instructions carried by the media to be detected by a physical mechanism that reads the instructions into a machine.
US4439837 16 Jun 1981 27 Mar 1984 Ncr Corporation Non-volatile memory system for intelligent terminals
US4536873 19 Mar 1984 20 Ago 1985 Honeywell Inc. Data transmission system
US5088032 29 Ene 1988 11 Feb 1992 Cisco Systems, Inc. Method and apparatus for routing communications among computer networks
US5295261 27 Jul 1990 15 Mar 1994 Pacific Bell Corporation Hybrid database structure linking navigational fields having a hierarchial database structure to informational fields having a relational database structure
US5404513 17 Jun 1993 4 Abr 1995 Dimensional Insight, Inc. Method for building a database with multi-dimensional search tree nodes
US5467471 10 Mar 1993 14 Nov 1995 Bader; David A. Maintaining databases by means of hierarchical genealogical table
US5590324 7 Feb 1995 31 Dic 1996 International Business Machines Corporation Optimization of SQL queries using universal quantifiers, set intersection, and max/min aggregation in the presence of nullable columns
US5625815 12 Abr 1996 29 Abr 1997 Tandem Computers, Incorporated Relational database system and method with high data availability during table data restructuring
US5680614 20 May 1993 21 Oct 1997 Nec Corporation Relational database management system
US5724577 7 Jun 1995 3 Mar 1998 Lockheed Martin Corporation Method for operating a computer which searches a relational database organizer using a hierarchical database outline
US5878415 20 Mar 1997 2 Mar 1999 Novell, Inc. Controlling access to objects in a hierarchical database
US5905982 4 Abr 1997 18 May 1999 International Business Machines Corporation Handling null values in SQL queries over object-oriented data
US5960194 17 Jul 1996 28 Sep 1999 International Business Machines Corporation Method for generating a multi-tiered index for partitioned data
US5983215 8 May 1997 9 Nov 1999 The Trustees Of Columbia University In The City Of New York System and method for performing joins and self-joins in a database system
US5999941 25 Nov 1997 7 Dic 1999 Micron Electronics, Inc. Database access using active server pages
US6012067 2 Mar 1998 4 Ene 2000 Sarkar; Shyam Sundar Method and apparatus for storing and manipulating objects in a plurality of relational data managers on the web
US6038563 25 Mar 1998 14 Mar 2000 Sun Microsystems, Inc. System and method for restricting database access to managed object information using a permissions table that specifies access rights corresponding to user access rights to the managed objects
US6055544 16 Mar 1999 25 Abr 2000 Inso Providence Corporation Generation of chunks of a long document for an electronic book system
US6061684 29 Ene 1999 9 May 2000 Microsoft Corporation Method and system for controlling user access to a resource in a networked computing environment
US6108698 29 Jul 1998 22 Ago 2000 Xerox Corporation Node-link data defining a graph and a tree within the graph
US6128610 25 Ago 1998 3 Oct 2000 Oracle Corporation Index with entries that store the key of a row and all non-key values of the row
US6141655 23 Sep 1997 31 Oct 2000 At&T Corp Method and apparatus for optimizing and structuring data by designing a cube forest data structure for hierarchically split cube forest template
US6154741 8 Abr 1999 28 Nov 2000 Feldman; Daniel J. Entitlement management and access control system
US6208993 22 Jul 1999 27 Mar 2001 Ori Software Development Ltd. Method for organizing directories
US6240407 17 Dic 1998 29 May 2001 International Business Machines Corp. Method and apparatus for creating an index in a database system
US6253195 20 Oct 1998 26 Jun 2001 Microsoft Corporation Optimized query tree
US6263332 14 Ago 1998 17 Jul 2001 Vignette Corporation System and method for query processing of structured documents
US6269380 31 Ago 1998 31 Jul 2001 Xerox Corporation Property based mechanism for flexibility supporting front-end and back-end components having different communication protocols
US6279006 14 Oct 1998 21 Ago 2001 Fujitsu Limited Structured data management system and computer-readable recording medium storing structured data management program
US6279007 30 Nov 1998 21 Ago 2001 Microsoft Corporation Architecture for managing query friendly hierarchical values
US6282537 6 Abr 1999 28 Ago 2001 Massachusetts Institute Of Technology Query and retrieving semi-structured data from heterogeneous sources by translating structured queries
US6298349 19 Ago 1998 2 Oct 2001 International Business Machines Corp. System resource display apparatus and method thereof
US6341289 6 May 1999 22 Ene 2002 International Business Machines Corporation Object identity and partitioning for user defined extents
US6343287 19 May 1999 29 Ene 2002 Sun Microsystems, Inc. External data store link for a profile service
US6356920 8 Mar 1999 12 Mar 2002 X-Aware, Inc Dynamic, hierarchical data exchange system
US6370537 30 Dic 1999 9 Abr 2002 Altoweb, Inc. System and method for the manipulation and display of structured data
US6418448 6 Dic 1999 9 Jul 2002 Shyam Sundar Sarkar Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web
US6438540 19 Jun 2001 20 Ago 2002 Vignette Corporation Automatic query and transformative process
US6438562 24 Ago 1999 20 Ago 2002 Oracle Corporation Parallel index maintenance
US6449620 2 Mar 2000 10 Sep 2002 Nimble Technology, Inc. Method and apparatus for generating information pages using semi-structured data stored in a structured manner
US6470344 27 Ago 1999 22 Oct 2002 Oracle Corporation Buffering a hierarchical index of multi-dimensional data
US6487546 27 Ago 1998 26 Nov 2002 Oracle Corporation Apparatus and method for aggregate indexes
US6496842 28 May 1999 17 Dic 2002 Survol Interactive Technologies Navigating heirarchically organized information
US6510434 29 Dic 1999 21 Ene 2003 Bellsouth Intellectual Property Corporation System and method for retrieving information from a database using an index of XML tags and metafiles
US6542911 1 Mar 2001 1 Abr 2003 Sun Microsystems, Inc. Method and apparatus for freeing memory from an extensible markup language document object model tree active in an application cache
US6574655 29 Jun 1999 3 Jun 2003 Thomson Licensing Sa Associative management of multimedia assets and associated resources using multi-domain agent-based communication between heterogeneous peers
US6584459 2 Jun 1999 24 Jun 2003 International Business Machines Corporation Database extender for storing, querying, and retrieving structured documents
US6604100 8 Feb 2001 5 Ago 2003 At&T Corp. Method for converting relational data into a structured document
US6654734 30 Ago 2000 25 Nov 2003 International Business Machines Corporation System and method for query processing and optimization for XML repositories
US6662342 13 Dic 1999 9 Dic 2003 International Business Machines Corporation Method, system, and program for providing access to objects in a document
US6675230 22 Ago 2000 6 Ene 2004 International Business Machines Corporation Method, system, and program for embedding a user interface object in another user interface object
US6684204 19 Jun 2000 27 Ene 2004 International Business Machines Corporation Method for conducting a search on a network which includes documents having a plurality of tags
US6708186 28 Sep 2000 16 Mar 2004 Oracle International Corporation Aggregating and manipulating dictionary metadata in a database system
US6718322 1 Oct 1999 6 Abr 2004 Ncr Corporation SQL-based analytic algorithm for rule induction
US6721723 23 Dic 1999 13 Abr 2004 1St Desk Systems, Inc. Streaming metatree data structure for indexing information in a data base
US6721727 29 Nov 2000 13 Abr 2004 International Business Machines Corporation XML documents stored as column data
US6721747 12 Ene 2001 13 Abr 2004 Saba Software, Inc. Method and apparatus for an information server
US6725212 31 Ago 2001 20 Abr 2004 International Business Machines Corporation Platform-independent method and system for graphically presenting the evaluation of a query in a database management system
US6732222 1 Feb 2002 4 May 2004 Silicon Motion, Inc. Method for performing flash memory file management
US6754661 22 Feb 2000 22 Jun 2004 Microsoft Corporation Hierarchical storage systems for holding evidentiary objects and methods of creating and operating upon hierarchical storage systems
US6772350 14 May 1999 3 Ago 2004 E.Piphany, Inc. System and method for controlling access to resources in a distributed environment
US6772412 16 Mar 2001 3 Ago 2004 Omron Corporation Data processing device equipped with a thread switching circuit
US6778977 19 Abr 2001 17 Ago 2004 Microsoft Corporation Method and system for creating a database table index using multiple processors
US6782380 14 Abr 2000 24 Ago 2004 David Victor Thede Method and system for indexing and searching contents of extensible mark-up language (XML) documents
US6785673 28 Dic 2001 31 Ago 2004 At&T Corp. Method for converting relational data into XML
US6795821 17 Jul 2001 21 Sep 2004 Trendium, Inc. Database systems, methods and computer program products including primary key and super key indexes for use with partitioned tables
US6801224 14 Sep 2000 5 Oct 2004 International Business Machines Corporation Method, system, and program for generating a graphical user interface window for an application program
US6804677 26 Feb 2001 12 Oct 2004 Ori Software Development Ltd. Encoding semi-structured data for efficient search and browsing
US6826568 20 Dic 2001 30 Nov 2004 Microsoft Corporation Methods and system for model matching
US6826727 24 Nov 1999 30 Nov 2004 Bitstream Inc. Apparatus, methods, programming for automatically laying out documents
US6836778 1 May 2003 28 Dic 2004 Oracle International Corporation Techniques for changing XML content in a relational database
US6836857 18 Oct 2001 28 Dic 2004 Sun Microsystems, Inc. Mechanism for debugging a computer process
US6871204 6 Sep 2001 22 Mar 2005 Oracle International Corporation Apparatus and method for mapping relational data and metadata to XML
US6889231 2 Dic 2002 3 May 2005 Oracle International Corporation Asynchronous information sharing system
US6915304 23 May 2001 5 Jul 2005 Kenneth A. Krupa System and method for converting an XML data structure into a relational database
US6918082 17 Dic 1998 12 Jul 2005 Jeffrey M. Gross Electronic document proofing system
US6964025 20 Mar 2001 8 Nov 2005 Microsoft Corporation Auto thumbnail gallery
US7028028 17 May 2001 11 Abr 2006 Enosys Markets,Inc. System for querying markup language data stored in a relational database according to markup language schema
US7031956 9 Oct 2001 18 Abr 2006 Verizon Laboratories Inc. System and method for synchronizing and/or updating an existing relational database with supplemental XML data
US7043716 13 Jun 2001 9 May 2006 Arius Software Corporation System and method for multiple level architecture by use of abstract application notation
US7051042 * 1 May 2003 23 May 2006 Oracle International Corporation Techniques for transferring a serialized image of XML data
US7062507 24 Feb 2003 13 Jun 2006 The Boeing Company Indexing profile for efficient and scalable XML based publish and subscribe system
US7072896 14 Feb 2001 4 Jul 2006 Verizon Laboratories Inc. System and method for automatic loading of an XML document defined by a document-type definition into a relational database including the generation of a relational schema therefor
US7124137 19 Dic 2002 17 Oct 2006 International Business Machines Corporation Method, system, and program for optimizing processing of nested functions
US7134072 13 Oct 1999 7 Nov 2006 Microsoft Corporation Methods and systems for processing XML documents
US7139746 5 May 2003 21 Nov 2006 Samsung Electronics Co., Ltd. Extended markup language (XML) indexing method for processing regular path expression queries in a relational database and a data structure thereof
US7171407 3 Oct 2002 30 Ene 2007 International Business Machines Corporation Method for streaming XPath processing with forward and backward axes
US20020029229 29 Jun 2001 7 Mar 2002 Jakopac David E. Systems and methods for data compression
US20020035606 18 May 2001 21 Mar 2002 Kenton Stephen J. Method and system for straight through processing
US20020038358 8 Ago 2001 28 Mar 2002 Sweatt Millard E. Method and system for remote television replay control
US20020054090 30 Ago 2001 9 May 2002 Silva Juliana Freire Method and apparatus for creating and providing personalized access to web content and services from terminals having diverse capabilities
US20020056025 1 Mar 2001 9 May 2002 Qiu Chaoxin C. Systems and methods for management of memory
US20020073019 22 Sep 1997 13 Jun 2002 David W. Deaton System, method, and database for processing transactions
US20020073236 12 Ene 2001 13 Jun 2002 Helgeson Christopher S. Method and apparatus for managing data exchange among systems in a network
US20020087596 29 Dic 2000 4 Jul 2002 Steve Lewontin Compact tree representation of markup languages
US20020116371 5 Dic 2000 22 Ago 2002 David Dodds System and method for the storage, indexing and retrieval of XML documents using relation databases
US20020116457 21 Feb 2002 22 Ago 2002 John Eshleman Systems and methods for managing distributed database resources
US20020120685 10 Abr 2002 29 Ago 2002 Alok Srivastava System for dynamically invoking remote network services using service descriptions stored in a service registry
US20020123993 29 Nov 2000 5 Sep 2002 Chau Hoang K. XML document processing
US20020124100 27 Abr 2000 5 Sep 2002 Jeffrey B Adams Method and apparatus for access to, and delivery of, multimedia information
US20020143512 28 Mar 2002 3 Oct 2002 Eiji Shamoto System simulator, simulation method and simulation program
US20020156811 23 May 2001 24 Oct 2002 Krupa Kenneth A. System and method for converting an XML data structure into a relational database
US20020169788 14 Feb 2001 14 Nov 2002 Wang-Chien Lee System and method for automatic loading of an XML document defined by a document-type definition into a relational database including the generation of a relational schema therefor
US20020184401 22 Oct 2001 5 Dic 2002 Kadel Richard William Extensible information system
US20020194157 27 Sep 1999 19 Dic 2002 Mohamed Zait Partition pruning with composite partitioning
US20020198874 26 Jul 2002 26 Dic 2002 Nasr Roger I. Automatic query and transformative process
US20030004937 13 Sep 2001 2 Ene 2003 Jukka-Pekka Salmenkaita Method and business process to maintain privacy in distributed recommendation systems
US20030009361 25 Ene 2001 9 Ene 2003 Hancock Brian D. Method and system for interfacing with a shipping service
US20030028563 26 Jun 2001 6 Feb 2003 William Stutz Methods and apparatus for extendible information aggregation and presentation
US20030033285 27 Sep 2002 13 Feb 2003 Neema Jalali Mechanism to efficiently index structured data that provides hierarchical access in a relational database system
US20030065659 27 Sep 2002 3 Abr 2003 Oracle Corporation Providing a consistent hierarchical abstraction of relational data
US20030078906 18 Oct 2001 24 Abr 2003 Ten-Hove Ronald A. Mechanism for facilitating backtracking
US20030093672 1 Jul 2002 15 May 2003 Bruce Cichowlas System for and methods of administration of access control to numerous resources and objects
US20030101194 1 Nov 2001 29 May 2003 Michael Rys System and method for loading hierarchical data into relational database systems
US20030105732 20 Feb 2001 5 Jun 2003 Kagalwala Raxit A. Database schema for structure query language (SQL) server
US20030154204 14 Ene 2003 14 Ago 2003 Kathy Chen-Wright System and method for a hierarchical database management system for educational training and competency testing simulations
US20030167456 13 Abr 2001 4 Sep 2003 Vinay Sabharwal Architecture for building scalable object oriented web database applications
US20030172135 4 Sep 2001 11 Sep 2003 Mark Bobick System, method, and data structure for packaging assets for processing and distribution on multi-tiered networks
US20030182624 19 Sep 2002 25 Sep 2003 Openwave Systems Inc. Method and apparatus for developing web services using standard logical interfaces to support multiple markup languages
US20030200214 14 Abr 2003 23 Oct 2003 Doole Douglas J. Detection and prevention of writing conflicts within nested query statements
US20030204787 30 Abr 2002 30 Oct 2003 International Business Machines Corporation Detecting network instability
US20030212662 5 May 2003 13 Nov 2003 Samsung Electronics Co., Ltd. Extended markup language (XML) indexing method for processing regular path expression queries in a relational database and a data structure thereof
US20030226111 3 Jun 2002 4 Dic 2003 Steve Wirts Application development acceleration employing declarative user interfaces
US20030229529 23 Feb 2001 11 Dic 2003 Yet Mui Method for enterprise workforce planning
US20030233618 16 Jun 2003 18 Dic 2003 Canon Kabushiki Kaisha Indexing and querying of structured documents
US20040006563 26 Jun 2002 8 Ene 2004 Arthur Zwiegincew Manipulating schematized data in a database
US20040064466 1 May 2003 1 Abr 2004 Oracle International Corporation Techniques for rewriting XML queries directed to relational database constructs
US20040088415 26 Nov 2002 6 May 2004 Oracle International Corporation Techniques for scalably accessing data in an arbitrarily large document by a device with limited resources
US20040143581 15 Ene 2003 22 Jul 2004 Bohannon Philip L. Cost-based storage of extensible markup language (XML) data
US20040148278 28 Mar 2003 29 Jul 2004 Amir Milo System and method for providing content warehouse
US20040167904 20 Feb 2003 26 Ago 2004 Ji-Rong Wen Semi-structured data storage schema selection
US20040176958 4 Feb 2002 9 Sep 2004 Jukka-Pekka Salmenkaita System and method for multimodal short-cuts to digital sevices
US20040193575 25 Mar 2003 30 Sep 2004 Chia-Hsun Chen Path expressions and SQL select statement in object oriented language
US20040199524 17 Jul 2003 7 Oct 2004 Michael Rys Systems and methods for transforming query results into hierarchical information
US20040205082 14 Abr 2003 14 Oct 2004 International Business Machines Corporation System and method for querying XML streams
US20040220912 1 May 2003 4 Nov 2004 Oracle International Corporation Techniques for changing xml content in a relational database
US20040220927 1 May 2003 4 Nov 2004 Oracle International Corporation Techniques for retaining hierarchical information in mapping between XML documents and relational data
US20040221226 30 Abr 2003 4 Nov 2004 Oracle International Corporation Method and mechanism for processing queries for XML documents using an index
US20040225680 8 May 2003 11 Nov 2004 Kim Cameron Declarative rules for metadirectory
US20040230667 22 Oct 2003 18 Nov 2004 Wookey Michael J. Loosely coupled intellectual capital processing engine
US20040255046 11 Jun 2003 16 Dic 2004 Microsoft Corporation Transformation of an asynchronous transactional messaging language into a web services compatible language
US20040260691 23 Jun 2003 23 Dic 2004 Desai Arpan A. Common query runtime system and application programming interface
US20040267719 27 Jun 2003 30 Dic 2004 Microsoft Corporation System and method for managed database query pre-optimization
US20040267760 23 Jun 2003 30 Dic 2004 Brundage Michael L. Query intermediate language method and system
US20050004892 23 Jun 2003 6 Ene 2005 Brundage Michael L. Query optimizer system and method
US20050010896 7 Jul 2003 13 Ene 2005 International Business Machines Corporation Universal format transformation between relational database management systems and extensible markup language using XML relational transformation
US20050044078 8 Sep 2004 24 Feb 2005 Overture Services, Inc. Technique for processing data in a network
US20050050058 25 Ago 2003 3 Mar 2005 Oracle International Corporation Direct loading of opaque types
US20050050059 25 Ago 2003 3 Mar 2005 Van Der Linden Robbert C. Method and system for storing structured documents in their native format in a database
US20050050092 25 Ago 2003 3 Mar 2005 Oracle International Corporation Direct loading of semistructured data
US20050091188 24 Oct 2003 28 Abr 2005 Microsoft Indexing XML datatype content system and method
US20050097084 31 Oct 2003 5 May 2005 Balmin Andrey L. XPath containment for index and materialized view matching
US20050102256 7 Nov 2003 12 May 2005 Ibm Corporation Single pass workload directed clustering of XML documents
US20050114314 26 Nov 2003 26 May 2005 International Business Machines Corporation Index structure for supporting structural XML queries
US20050138047 26 Mar 2004 23 Jun 2005 Oracle International Corporation Techniques for managing XML data associated with multiple execution units
US20050160076 25 Jun 2004 21 Jul 2005 Fujitsu Limited Method and apparatus for referring to database integration, and computer product
US20050160108 16 Ene 2004 21 Jul 2005 Charlet Kyle J. Apparatus, system, and method for passing data between an extensible markup language document and a hierarchical database
US20050210002 18 Mar 2004 22 Sep 2005 Microsoft Corporation System and method for compiling an extensible markup language based query
US20050228768 16 Sep 2004 13 Oct 2005 Ashish Thusoo Mechanism for efficiently evaluating operator trees
US20050228786 16 Sep 2004 13 Oct 2005 Ravi Murthy Index maintenance for operations involving indexed XML data
US20050228792 2 Jul 2004 13 Oct 2005 Oracle International Corporation Index for accessing XML data
US20050229158 16 Sep 2004 13 Oct 2005 Ashish Thusoo Efficient query processing of XML data using XML index
US20050289125 22 Sep 2004 29 Dic 2005 Oracle International Corporation Efficient evaluation of queries using translation
US20050289138 25 Jun 2004 29 Dic 2005 Cheng Alex T Aggregate indexing of structured and unstructured marked-up content
US20050289175 5 Abr 2005 29 Dic 2005 Oracle International Corporation Providing XML node identity based operations in a value based SQL system
US20060010124 3 Dic 2004 12 Ene 2006 Bea Systems, Inc. Systems and methods for implementing a computer language type system
US20060031204 22 Sep 2004 9 Feb 2006 Oracle International Corporation Processing queries against one or more markup language sources
US20060031233 26 Ene 2005 9 Feb 2006 Oracle International Corporation Technique of using XMLType tree as the type infrastructure for XML
US20060195476 30 Jun 2005 31 Ago 2006 Microsoft Corporation Platform for data services across disparate application frameworks
US20060212467 14 Jul 2005 21 Sep 2006 Ravi Murthy Encoding of hierarchically organized data for efficient storage and processing
US20060224576 4 Abr 2005 5 Oct 2006 Oracle International Corporation Effectively and efficiently supporting XML sequence type and XQuery sequence natively in a SQL system
EP1241589A2 1 Mar 2002 18 Sep 2002 Sun Microsystems, Inc. Method and apparatus for freeing memory from an extensible markup language document object model tree active in an application cache
GB2409078A Título no disponible
WO2000049533A2 17 Feb 2000 24 Ago 2000 Oracle Corporation Hierarchical indexing for accessing hierarchically organized information in a relational system
WO2001042881A2 6 Dic 2000 14 Jun 2001 B-Bop Associates, Inc. System and method for the storage, indexing and retrieval of xml documents using relational databases
WO2001059602A1 12 Feb 2001 16 Ago 2001 Acta Technologies, Inc. Nested relational data model
WO2001061566A1 16 Feb 2001 23 Ago 2001 Verizon Laboratories Inc. System and method for automatic loading of an xml document defined by a document-type definition into a relational database including the generation of a relational schema therefor
WO2003027908A Título no disponible
WO2003027908A2 27 Sep 2002 3 Abr 2003 Oracle International Corporation Providing a consistent hierarchical abstraction of relational data
1 "Notice of Allowance and Fee Due" received in 10/944, 170 dated Apr. 7, 2008, 8 pgs.
2 "Oracle 9i Project XDB"-The XML Database-Oracle-2001 (PPS 1-19).
3 "Oracle 9i Project XDB"—The XML Database—Oracle—2001 (PPS 1-19).
4 * "XQuery 1.0 and XPath 2.0 Functions and Operators," W3C, Nov. 12, 2003, available at: , pp. 1-193.
5 * "XQuery 1.0 and XPath 2.0 Functions and Operators," W3C, Nov. 12, 2003, available at: <http://www.w3c.org/TR/2003/WD-xpath-functions-20031112>, pp. 1-193.
6 Amended Claims, App. No. 01 970 715.7 13 pgs.
7 Australian Application No. 2001290693—current claims, 17 pgs.
8 Australian Governement, "Examiner's first report on patent application No. 2007229359", received Mar. 5, 2008, 2 pgs.
9 Australian Government, "Examiner's first report on patent application No. 2007229358", received Mar. 5, 2008, 2 pgs.
10 Australian Office Action; Examiner's first report on patent application No. 2001290693, dated Jun. 27, 2006, 4 pgs.
11 Banerjee, Sandeepan et al., "Oracle8i-The XML Enabled Data Management System" -Oracle Corporation, Mar. 2000, IEEE, pp. 561-568.
12 Banerjee, Sandeepan et al., "Oracle8i—The XML Enabled Data Management System" —Oracle Corporation, Mar. 2000, IEEE, pp. 561-568.
13 Bohannon, Philip, et al., "From XML Schema to Relations: A Cost-Based Approach to XML Storage" -Bell Laboratories, IEEE-2002-Proceedings of the 18th International Conference on Data Engineering (ICDE '02), pp. 1-28.
14 Bohannon, Philip, et al., "From XML Schema to Relations: A Cost-Based Approach to XML Storage" —Bell Laboratories, IEEE—2002—Proceedings of the 18th International Conference on Data Engineering (ICDE '02), pp. 1-28.
15 Bourret, R. et al.: A generic Load/Extract Utility for Data Transfer Between XML Documents and Relational Databases, Jun. 8-9, 2000, IEEE Computing SOC., pp. 134-143.
16 Braga, Daniele et al., "A Graphical Environment to Query XML Data with Query," Proceedings of the Fourth International Conference on Web Information Systems Engineering (WISE '03), 2003, IEEE, 10 pages.
17 Chae, MI-OK et al., "Design and Implementation of an Object-Oriented Multimedia DBMS Tightly Coupled with Information Retrieval Functions," Proc. 17th IASTED International Conference on Applied Informatics, Feb. 15-18, 1999, abstract.
18 Chen, Cindy Xinmin, et al., "XML Queries SQL," Proceedings of the First International Conference on Web-Age Information Management, ISBN: 3-540-67627-9, 9 pages.
19 Chen, Ruey-Shun et al., "Developing an XML framework for metadata system", Trinity College Dublin, Proc. of the 1st Inter. Sympo. on Information and Communication, pp. 267-272.
20 Cheng, Josephine et al., "IBM DB2 XML Extender, An end-to-end solution for storing and retrieving XML documents.," IEEE, ICDE '00 Conference, San Diego, Feb. 2000, 128 pages.
21 Cheng, Josephine, et al., "XML and DB2," 16th International Conference on Data Engineering, May 2000, 5 pages.
22 Choi, Byron et al., "The XQuey Formal Semantics: A Foundation for Implementation Optimization," May 31, 2002, IEEE XP-002353605, 15 pages.
23 Claims, Application No. 05 760 442.3-2201, 8 pages.
24 Claims, patent application No. 2007229358, 8 pgs.
25 Claims, patent application No. 2007229359, 8 pgs.
26 Claims, Patent application No. 533163/2003, 9 pages.
27 Claims, PCT/US2005/021259, dated Nov. 30, 2006, 8 pages (attached).
28 Cooper, Brian F. et al., " A Fast Index for Semistructured Data ," Proceeding of the International Conference on Very Large Databases, 2001, XP-002303292, pp. 341-350.
29 Current claims in China for foreign patent application No. 200480011704.3 (4 pgs).
30 Current claims in PCT/US02/30783, pp. 1-8.
31 Current claims in PCT/US03/35551, pp. 1-4.
32 Current Claims Patent App. 2001290693, 7 pages.
33 Current Claims PCT/US02/31168, EP App. No. 02799692.5, 8 pages.
34 Current Claims, PCT/US2005/011763, 4 pages.
35 Current Claims, PCT/US2005/020795, 5 pages.
36 Current Claims, PCT/US2005/021259, 10 pages.
37 Current Claims, PCT/US2005/021259, 15 pages.
38 Damiani, Ernesto et al., "Securing XML Documents", LNCS 1777, Mar. 2000, 15 pgs.
39 Damiani, Ernesto, et al., "Design and Implementation of an access control processor for XML documents", Computer Networks 33 (2000), Jun. 2000, 17 pgs.
40 Dayen, I., "Storing XML in Relational Databases", XML.com, XP-002275971(1998-2004), pp. 1-13.
41 Drake, Mark et al., "Understanding the Oracle9i XML Type," Oracle Corporation, 2004, http://otn.oracle.com/oramag/oracle/01-nov/o61xml.html?-template=/ocom/technology, data retrieved Jun. 29, 2004, pp. 1-5.
42 Drake, Mark et al., "Understanding the Oracle9i XML Type," Oracle Corporation, 2004, http://otn.oracle.com/oramag/oracle/01-nov/o61xml.html?—template=/ocom/technology, data retrieved Jun. 29, 2004, pp. 1-5.
43 European Patent Office, "Communication Pursuant to Article 94(3) EPC", Application No. 05 760 442.3-2201, dated Jun. 20, 2008, 2 pages.
44 European Patent Office, "Communication Pursuant to Article 96(2) EPC," App. No. 01 970 715.7, dated Jul. 19, 2006, 8 pgs.
45 European Patent Office, "Communication Pursuant to Article 96(2) EPC," EP App. No. 02799692.5, dated Jan. 18, 2006, 5 pages.
46 Florescu, Daniela et al., "A Performance Evaluation of Alternative Mapping Schemes for Storing XML Data in a Relational Database," INRIA Rocquencourt P Project Rodin-Rapport De Recherche, May 1999, pp. 1-32.
47 Florescu, Daniela et al., "A Performance Evaluation of Alternative Mapping Schemes for Storing XML Data in a Relational Database," INRIA Rocquencourt P Project Rodin—Rapport De Recherche, May 1999, pp. 1-32.
48 Funderbunk, J. et al., "XML programming with SQL/XML and XQuery", IBM Systems Journal, XP-002295973 (2002), pp. 642-665.
49 Gennick , Johnathan, "SQL in, XML out," Oracle Corporation, 2004, http://otn.oracle.com/oramag/oracle/03-may/o33xml.html?-template=/ocom/technology, data retrieved Jun. 29, 2004.
50 Gennick , Johnathan, "SQL in, XML out," Oracle Corporation, 2004, http://otn.oracle.com/oramag/oracle/03-may/o33xml.html?—template=/ocom/technology, data retrieved Jun. 29, 2004.
51 Gennick, Jonathan, "SQL in, XML out", May/Jun. 2003, Oracle Magazine, 5 pgs.
52 Hierarchical Queries, XP-002295972, pp. 8-3 to 8-7, 14 pages.
53 Higgens, Shelley, "Oracle9i, Case Studies-XML Applications," Oracle Corporation ,Release 1 (9.0.1), Jun. 2001, Part No. A88895-01, pp. 1-462 (On CD-Rom).
54 Higgens, Shelley, "Oracle9i, Case Studies—XML Applications," Oracle Corporation ,Release 1 (9.0.1), Jun. 2001, Part No. A88895-01, pp. 1-462 (On CD-Rom).
55 Higgins, Shelley, "Oracle9i, Application Developer's Guide-XML," Oracle Corporation, Release 1 (9.0.1), Jun. 2001, Part No. A88894-01, pp. 1-1,362. (On CD-Rom).
56 Higgins, Shelley, "Oracle9i, Application Developer's Guide—XML," Oracle Corporation, Release 1 (9.0.1), Jun. 2001, Part No. A88894-01, pp. 1-1,362. (On CD-Rom).
57 Hironobu, Koyaku, "What is brought to SQL Server 2000 by XML?", partial English translation, Enterprise Servers, IDG Japan, Dec. 1, 2000, vol. 3, No. 12, 1 page.
58 International Preli Minary Examining Authority, "Written Opinion," PCT/US2005/021259, dated Oct. 13, 2006, 7 pages.
59 International Preliminary Examination Report, Application No. PCT/US02/30783, Apr. 1, 2004, 15 pages.
60 International Preliminary Examination Report, Application No. PCT/US02/30783, Apr. 1, 2004, pp. 1-14.
61 International Preliminary Examination Report, Application No. PCT/US03/35551, Oct. 8, 2004, pp. 1-17.
62 International Preliminary Examining Authority, "Notification Concerning Informal Communications with the Applicant," PCT/US2005/021259, dated May 11, 2006, 4 pgs.
63 International Preliminary Examining Authority, "Notification of Transmittal of the International Preliminary Report on Patentability," PCT/US2005/011763, received May 15, 2006, 10 pages (including 3 pages of claims).
64 International Preliminary Examining Authority, "Notification of Transmittal of the International Preliminary Report on Patentability," PCT/US2005/021259, dated Feb. 2, 2007, 9 pages.
65 International Searching Authority, "Notification of the Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration," PCT/US2005/020795, Mailing Date Sep. 27, 2005, 13 pages.
66 International Searching Authority, "Notification of Transmittal of the International Search Report and the Written Opinion of the International Authority, or the Declaration," Nov. 2, 2004, PCT/US2004/010018, 14 pages.
67 International Searching Authority, "Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration," PCT/US2005/011763, dated Aug. 6, 2005, 12 pages.
68 International Searching Authority, "Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration," PCT/US2005/021259, dated Nov. 24, 2005, 13 pages.
69 International Searching Authority, International Search Report and Written Opinion, PCT/US2004/010018, dated Nov. 11, 2004, 14 pages.
70 IP Australia, "Examiner's Report No. 2, "Patent App. 2001290693, received Mar. 8, 2007, 2 pages.
71 Jajodia, Sushil, et al., "Toward a Multilevel Secure Relational Data Model," ACM, 1991, 8393 SIGMOD Record, 20 (1991) Jun., No. 2, New York, US, XP 000364619, pp. 50-59.
72 Japanese Patent Office, "Notice of Grounds of Rejection", Patent application No. 533163/2003, mailed Aug. 21, 2008 / received Aug. 21, 2008, 7 pages.
73 Kang, Ji-Hoon et al., "An XQuery Engine for Digital Library Systems that support XML data," Proceedings of the 2004 International Symposium on Application and the Internet Workshops, IEEE XP-0010684128, 5 pages.
74 Kang, Ji-Hoon et al., "An XQuery Engine for Digital Library Systems that support XML data," Proceedings of the 2004 International Symposium on Application and the Internet Workshops, IEEE XP010684128, 5 pages.
75 Katz, Howard et al., "Integrating XQuery and Relational Database Systems," Chapter 7-XQuery from the Expertrs: A Guide to the W3C XML Query Language, Addison Wesley Professional, Aug. 22, 2003, ISBM 978-0-321-18060-5, pp. 353-391.
76 Katz, Howard et al., "Integrating XQuery and Relational Database Systems," Chapter 7—XQuery from the Expertrs: A Guide to the W3C XML Query Language, Addison Wesley Professional, Aug. 22, 2003, ISBM 978-0-321-18060-5, pp. 353-391.
77 Khan, Latifur, "A Performance Evaluation of Storing XML Data in Relational Database Management Systems" -and Yan Rao-ACM-2001 (pp. 31-38).
78 Khan, Latifur, "A Performance Evaluation of Storing XML Data in Relational Database Management Systems" —and Yan Rao—ACM-2001 (pp. 31-38).
79 Lawrence et al. "Integrating Relational Database Schemas Using a Standardized Dictionary" -2001-ACM (pp. 225-230).
80 Lawrence et al. "Integrating Relational Database Schemas Using a Standardized Dictionary" —2001—ACM (pp. 225-230).
81 Lo et al., "XAS: A System for Accessing Componentized, Virtual XML Documents," IEEE, 2001, pp. 493-502.
82 Makoto, Onizuka, "XML and Database", partial English translation, XML Magazine, Shoeisha Co., Ltd., Jul. 1, 2000, vol. 10, No. 3, 1 page.
83 Manolescu, Dragos, Review of "Metadata solutions: using metamodels, repositories, XML, and enterprise portals to generate information on demand by Adrienne Tannenbaum", Mar. 2003, ACM Press, vol. 28, Issue 2, p. 38.
84 * McHugh et al., "Query Optimization for XML," 1999, 25th VLDB Conference, pp. 315-326.
85 McHugh, Jason et al., "Query Optimization for XML", XP-002333353, Proceedings of the 25th VLDB Conference (1999) pp. 315-326.
86 McHugh, Jason, et al. "Indexing Semistructured Data," Stanford Science Department, 1998, XP-002248313, pp. 1-21.
87 Melton, Jim, "ISO-ANSI Working Draft, XML-Related Specifications (SQL/XML)," WG3: DRS-020, H2-2002-365, Aug. 2002, 154 pages.
88 Murthy, Ravi et al., "XML Schemas in Oracle XML DB," Proceedings of the 29th VLDB Conference, 2003, IEEE XP-002353604, pp. 1009-1018.
89 Myllymaki, Jussi, "Effective Wed data Extraction with Standard XML Technologies," WWW10, May 1-5, 2001, pp. 689-696.
90 Noser, Hansrudi et al., "Dynamic 3D Visualization of Database-Defined Tree Structures on the WWW by Using Rewriting Systems," 2000, IEEE, XP-002262516, pp. 247-254.
91 Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration received from International application No. PCT/US2005/011762.
92 Office Action from China for foreign patent application No. 200480011704.3 dated Feb. 29, 2008 (6 pgs).
93 Oracle 9l-XML Database Developer's Guide-Oracle, XML DB, Release 2(9.2), Part No. A96620-02, Part IV Chapter 10, 10-1˜10-21, Shelley Higgins (24 pgs).
94 Oracle Corporation, "Oracle9i Application Server, Administrator's Guide," Release 2 (9.0.2), May 2002, Part No. A92171-02, Part No. A92171-02, pp. 1-392. (On CD-Rom).
95 Oracle Corporation, "Oracle9i XML Database Developer's Guide-Oracle XML DB," Release 2 (9.2), Mar. 2002, Part No. A96620-01, pp. 5-8-5-10, 5-21-5-24, 5-52-5-70, 10-5-10-20 and 11-1-11-20 (60 pgs).
96 Oracle Corporation, "Oracle9i XML Database Developer's Guide—Oracle XML DB," Release 2 (9.2), Mar. 2002, Part No. A96620-01, pp. 5-8-5-10, 5-21-5-24, 5-52-5-70, 10-5-10-20 and 11-1-11-20 (60 pgs).
97 Oracle Corporation, "Oracle9i XML Database Developer's Guide-Oracle XML DB," Release 2 (9.2), Mar. 2002, Part No. A96620-1, pp. 10-1-10-54.
98 Oracle Corporation, "Oracle9i XML Database Developer's Guide—Oracle XML DB," Release 2 (9.2), Mar. 2002, Part No. A96620-1, pp. 10-1-10-54.
99 Oracle Corporation, "Oracle9i XML Database Developer's Guide-Oracle XML DB," Release 2 (9.2), Mar. 2002, Part No. A96620-1, pp. 5-8-5-10, 5-21-5-24 and 5-32-5-52.
100 Oracle Corporation, "Oracle9i XML Database Developer's Guide—Oracle XML DB," Release 2 (9.2), Mar. 2002, Part No. A96620-1, pp. 5-8-5-10, 5-21-5-24 and 5-32-5-52.
101 Oracle, "Oracle 9i XML Developer's Kits Guide-XDK" Release 2 (9.2) Online retrieved at www.oracle.com/pls/db92/db92.docindex, Mar. 2002, 774 pages (Chapters 13-19 extracted, 88 pages).
102 Oracle, "Oracle 9i XML Developer's Kits Guide—XDK" Release 2 (9.2) Online retrieved at www.oracle.com/pls/db92/db92.docindex, Mar. 2002, 774 pages (Chapters 13-19 extracted, 88 pages).
103 PCT/US2004/010018-current claims.
104 PCT/US2004/010018—current claims.
105 Pending claims from International application No. PCT/US2005/011762.
106 Peng, Feng et al., "XPath queries on streaming data", 2003, ACM Press, pp. 431-442.
107 Ramakrishnan, Ragu et al., "SRQL: Sorted Relational Query Language" Jul. 1-3, 1998, IEEE, pp. 84-95.
108 Rollman , Rich, "SQL Server 2000 XML Enhancements", Microsoft Corp., Powerpoint Presentation at Mircrosoft TechEd, Jun. 2000, 42 pgs.
109 Rys, Michael et al., "Integrating XQuery and Relational Database Systems," Chapter 7-XQuery from the Experts: A Guide to the W3C XML Query Language, Addison Wesley Professional, Aug. 22, 2003, ISBN 978-0-321-18060-5, pp. 353-391.
110 Rys, Michael et al., "Integrating XQuery and Relational Database Systems," Chapter 7—XQuery from the Experts: A Guide to the W3C XML Query Language, Addison Wesley Professional, Aug. 22, 2003, ISBN 978-0-321-18060-5, pp. 353-391.
111 Schmidt et al.-"Efficient Relational Storage and Retrieval of XML Documents" CWI, The Netherlands (pp. 1-6).
112 Schmidt et al.—"Efficient Relational Storage and Retrieval of XML Documents" CWI, The Netherlands (pp. 1-6).
113 Schmidt et al., "Why and How to Benchmark XML Databases," SIGMOND Record, vol. 3, No. 3, Sep. 2001, pp. 27-32.
114 Shanmugasundaram J., et al. "Querying XML Views of Relational Data," Proceedings of the 27th Very Large Databases Conference, Rome, Italy, Sep. 2001, pp. 261-270.
115 Shanmugasundaram, Jayavel, et al., "Querying XML Views of Relational Data," Proceedings of the 27th Very Large Databases Conference, Rome, Italy, Sep. 2001, pp. 261-270.
116 Tomoharu, Asami, "Development of Database System by XML, Relaxer, and JDBC", partial English translation, XML Press, Gijutsu-Hyohron Co., Jul. 10, 2001, vol. 3, 2 pages.
117 Vion-Dury, Jean-Yves, "XPath on left and right sides of rules: toward compact XML tree rewriting through node patterns", 2003, ACM Press, pp. 19-25.
118 Vorthmann, Scott et al., "Beyond Schemas, Schema Adjuncts and the Outside World," Markup Languages, Online!, vol. 2, No. 3, Jun. 2000, pp. 1-8.
119 W3C, "Extensible Markup Language (XML) 1.0 (Third Edition)", W3C Recommendation, dated Feb. 4, 2004, 34 pages.
120 W3C, "XML Path Language (XPath) 2.0," W3C Working Draft Dated Apr. 4, 2005, 89 pages.
121 W3C, "XML Schema Part 1: Structures," W3C Recommendation, May 2, 2001, retrieved from the internet :, retrieved on Apr. 14, 2005, pp. 1-186.
122 W3C, "XML Schema Part 1: Structures," W3C Recommendation, May 2, 2001, retrieved from the internet :<http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/>, retrieved on Apr. 14, 2005, pp. 1-186.
123 W3C, "XML Schema Part 2: Datatypes," W3C Recommendation, May 2, 2001, retrieved from the internet:, retrieved on Apr. 14, 2005, pp. 1-138.
124 W3C, "XML Schema Part 2: Datatypes," W3C Recommendation, May 2, 2001, retrieved from the internet:<http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/>, retrieved on Apr. 14, 2005, pp. 1-138.
125 W3C, "XML Syntax for XQuery 1.0 (XQueryX)," W3C Recommendation, Working Draft, Dec. 19, 2003, retrieved from the internet, retrieved on Apr. 12, 2005, pp. 1-55.
126 W3C, "XML Syntax for XQuery 1.0 (XQueryX)," W3C Recommendation, Working Draft, Dec. 19, 2003, retrieved from the internet<http://www.w3.org/TR/2003/WD-xquery-20031219>, retrieved on Apr. 12, 2005, pp. 1-55.
127 W3C, "XQuery 1.0 and XPath 2.0 Data Model," W3C Working Draft dated Apr. 4, 2005, 91 pages.
128 W3C, "XQuery 1.0: An XML Query Language," W3C Recommendation, Working Draft, Oct. 29, 2004, retrieved from the internet, retrieved on Apr. 14, 2005, pp. 1-189.
129 W3C, "XQuery 1.0: An XML Query Language," W3C Recommendation, Working Draft, Oct. 29, 2004, retrieved from the internet<http://www.w3.org/TR/2004/WD-xquery-20041029>, retrieved on Apr. 14, 2005, pp. 1-189.
130 W3C, "XQuery 1.0: An XML Query Language," W3C Working Draft dated Apr. 4, 2005, 170 pages.
131 W3C, "XSL Transformations (XSLT) Version 2.0," W3C Working Draft dated Apr. 4, 2005, 346 pages.
132 Written Opinion, Application No. PCT/US03/35551, Nov. 10, 2004, 6 pages.
133 Yoshikawa, Masatoshi et al., "XRel: A Path-Based Approach to Storage and Retrieval of XML Documents Using Relational Databases", XP-001143686, ACM Transactions on Internet Technology (2001), pp. 110-141.
134 Zemke, Fred, "XML Query," Change Proposal, ISO/IEC JTC1/SC32 WG3:SIA-nnn ANSI NCITS H2-2004-02lrl, Mar. 14, 2004, 29 pages.
135 Zhang, Hui et al., "XQuery rewriting at the relational algebra level," Computer Systems Science and Engineering, vol. 18, No. 5, Sep. 2003, IEEE XP-009056809, pp. 241-262.
136 Zhang, Wansong, et al., "An Encoding Scheme for Indexing XML Data," E-Commerce and E-Service, 2004, XP-010697639, pp. 526-529.
137 Zhang, Xin et al., "Honey, I Shrunk the XQuery! -An XML Algebra Optimization Approach," Submission for WIDM'02, IEEE XP-002316448, 14 pages.
138 Zhang, Xin et al., "Honey, I Shrunk the XQuery! —An XML Algebra Optimization Approach," Submission for WIDM'02, IEEE XP-002316448, 14 pages.
139 Zisman et al., "Using XML to Build Consistency Rules for Distributed Specifications," Proceedings of the Tenth International Workshop on Software Specification and Design (IWSD'00), IEEE 2000, 8 pages.
US8209664 * 18 Mar 2009 26 Jun 2012 Microsoft Corporation High level programming extensions for distributed data parallel processing
US8255790 * 8 Sep 2006 28 Ago 2012 Microsoft Corporation XML based form modification with import/export capability
US8417714 * 22 Ene 2010 9 Abr 2013 Oracle International Corporation Techniques for fast and scalable XML generation and aggregation over binary XML
US8655894 * 26 Abr 2010 18 Feb 2014 Nokia Corporation Method and apparatus for index generation and use
US8924623 * 28 Jul 2010 30 Dic 2014 Oricane Ab Method for managing multi-layered data structures in a pipelined memory architecture
US9396284 * 18 May 2011 19 Jul 2016 Oracle International Corporation Method and system for implementing efficient updatable relational views over XML data
US20080065978 * 8 Sep 2006 13 Mar 2008 Microsoft Corporation XML Based Form Modification With Import/Export Capability
US20100241827 * 18 Mar 2009 23 Sep 2010 Microsoft Corporation High Level Programming Extensions For Distributed Data Parallel Processing
US20110184969 * 22 Ene 2010 28 Jul 2011 Sam Idicula Techniques for fast and scalable xml generation and aggregation over binary xml
US20110264666 * 26 Abr 2010 27 Oct 2011 Nokia Corporation Method and apparatus for index generation and use
US20120191919 * 28 Jul 2010 26 Jul 2012 SUNDSTROEM Mikael Method for managing multi-layered data structures in a pipelined memory architecture
Clasificación de EE.UU. 715/234
Clasificación internacional G06N3/00
Clasificación cooperativa G06F17/30932, G06F17/30917
Clasificación europea G06F17/30X7P2, G06F17/30X3D
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:WARNER, JAMES W.;LIU, ZHEN HUA;KRISHNAPRASAD, MURALIDHAR;REEL/FRAME:017086/0852
16 Ago 2011 CC Certificate of correction