Dealing with composite data through data model entities
First Claim
1. A method of providing a logical framework for defining abstract operations for accessing physical data comprising a plurality of physical entities each comprising a plurality of physical fields, the method comprising:
- providing an abstract model for defining abstract operation specifications logically descnbing operations to access the data, the abstract model comprising;
(a) a plurality of logical fields;
(b) a mapping rule for each of the plurality of logical fields, which map each of the plurality of logical fields to at least one of the physical entities of the data; and
(c) a plurality of model entity definitions, each comprising at least one logical field corresponding to a physical entity;
providing an interface from which each of the plurality of model entity definitions is selectable in generating an abstract operation specification to access the data of the physical entity corresponding to a selected model entity definition; and
providing a run-time component to transform, according to the abstract model, the abstract operation specifications into physical operation specifications consistent with the physical data.
2 Assignments
0 Petitions
Accused Products
Abstract
The present invention is generally directed to a system, method and article of manufacture for accessing data represented abstractly through an abstraction model. In one embodiment, a data repository abstraction layer provides a logical view of an underlying data repository that is independent of the particular manner of data representation. A query abstraction layer is also provided and is based on the data repository abstraction layer. A runtime component performs conversion of an abstract query (i.e., a request for results or a request to modify data) into a form that can be used against a particular physical data representation. Abstract and/or physical queries are transformed according to model entities which define a relationship between logical fields of the data repository abstraction layer.
-
Citations
28 Claims
-
1. A method of providing a logical framework for defining abstract operations for accessing physical data comprising a plurality of physical entities each comprising a plurality of physical fields, the method comprising:
-
providing an abstract model for defining abstract operation specifications logically descnbing operations to access the data, the abstract model comprising; (a) a plurality of logical fields; (b) a mapping rule for each of the plurality of logical fields, which map each of the plurality of logical fields to at least one of the physical entities of the data; and (c) a plurality of model entity definitions, each comprising at least one logical field corresponding to a physical entity; providing an interface from which each of the plurality of model entity definitions is selectable in generating an abstract operation specification to access the data of the physical entity corresponding to a selected model entity definition; and providing a run-time component to transform, according to the abstract model, the abstract operation specifications into physical operation specifications consistent with the physical data. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23)
-
-
24. A computer-readable medium containing a program which, when executed by a processor provides a logical framework for defining abstract modification operations for modifying physical data, the program comprising:
-
an abstract model for defining an abstract modification specification logically describing operations to access the data the abstract model comprising; (i) a plurality of logical fields; (ii) a mapping rule for each of the plurality of logical fields, which map the plurality of logical fields to physical entities of the data; (iii) a plurality of model entity definitions, each comprising at least two logical fields each corresponding to a separate physical entity; and (iv) a physical entity relationships specification defining interrelationships between the physical entities of the data, and a run-time component configured with; (i) transformation instructions to transform an abstract modification specification, comprising logical fields selected according to a selected model entity definition, into at least two physical modification statements consistent with the physical data, wherein each of the at least two physical modification statements modifies a different physical entity of the data; and (ii) ordering instructions to order the at least two physical modification statements according to the physical entity relationships specification. - View Dependent Claims (25, 26, 27, 28)
-
Specification