Abstract: An object-oriented interface for providing access to stored data comprises a data enumeration module that provides an object-oriented view to at least one stored first datum that is not an object created by the interface. The interface also includes a scanning module that cooperates with the data enumeration module to change the view from the stored first datum to another datum. Methods for using the interface are also provided.

Abstract: The claimed subject matter relates to an architecture that can facilitate an incremental approach to an Object-Relational mapping solution. The architecture can provide a rich data model that is defined at the value layer. The rich data model can expose an interface that conforms with the interfaces exposed by common storage-specific data providers. The architecture can extend common storage-specific data provider to support common command representations, and provide entity services that work in terms of the rich data model as well as object services such as identity management, updating and change tracking.

Abstract: The claimed subject matter provides a system and/or a method that facilitates constructing and initializing an object within a single expression. An interface component can receive data related to an object that has at least one property associated therewith. A syntax component can combine a construction of the object and an initialization of the at least one property into a single expression.

Abstract: Dynamically generated interfaces can be applied on existing classes independently of underlying class definitions. This allows developers to work with values from different data models using a single paradigm and without the need to explicitly move data into actual objects. In one aspect, an automated interface generation system is provided. The system includes a mapping component that generates an object structure for one or more data structures residing in local or remote databases. A viewer displays the object structure to facilitate data interactions with the database. Generally, the mapping component is associated with a compiler and automatically defines views of the object structure via one or more interfaces.

Abstract: A data mapping architecture for mapping between two or more data sources without modifying the metadata or structure of the data sources themselves. Data mapping also supports updates. The architecture also supports at least the case where data sources that are being mapped, are given, their schemas predefined, and cannot be changed. The architecture includes a mapping component that receives respective metadata from at least two arbitrary data models, and maps expressions between the data models.

Abstract: A computer system and method generate a semantic representation of one or more XML language inquiries across relational and non-relational data sources. A semantic intermediate language representation explicitly describes the meaning of the one or more XML language inquiries. The semantic intermediate language may be a graph structure with nodes which describe the operations of the original query. Operators assigned to the nodes in the semantic graph allow an unambiguous definition of the original XML query. The semantic intermediate language may be used to perform XML queries over single or multiple data sources. A method includes receiving at least one inquiry, defining at least one node object for every operation within the received inquiry, translating each node object using operators, and generating a semantic representation from the operators.

Abstract: Users and programmers view relational database tables using an schema such as an SQL-annotated XML schema. The schema describes how XML data maps into base tables and fields, including complex one-to-many and many-to-many relationships.

Abstract: Users and programmers can load semi-structured hierarchical data, such as XML data, of arbitrary size and structure into relational database tables using an schema such as an SQL-annotated XML schema. The schema describes how XML data maps into base tables and fields, including complex one-to-many and many-to-many relationships. The hierarchical data is streamed into the relational database tables in a single operation.