S. Spaccapietra and C. Parent: View Integration: A Step forward in Solving Structural Conflicts. IEEE Trans. on Knowledge and Data Engineering 6 (2), 1994, pp. 258-274. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Situation and Perspective of Knowledge Engineering - Studer, Decker, Fensel, Staab (2000) (1 citation) (Correct)
....the information about which stem partially from the first and partially from the second source. This fusion task, however, requires the alignment of different knowledge models, or to put it crisp it requires ontology alignment. Alignment of schemata has been a hot topic in the database community [62] and like in ontology engineering proper (cf. Hovy [45] linguistic cues may help considerably in determining appropriate candidates for concept alignment [49] 18] Ontology alignment, however, needs support way beyond concept alignment. For instance, ontologies often evolve independently from ....
S. Spaccapietra and C. Parent: View Integration: A Step forward in Solving Structural Conflicts. IEEE Trans. on Knowledge and Data Engineering 6 (2), 1994, pp. 258-274.
ERC+: an object based entity relationship approach - Spaccapietra, Parent (1992) (2 citations) Self-citation (Spaccapietra) (Correct)
....independently of other users views. For federated environment, it should support reuse of existing databases and existing application programs, without contradicting the launching of new federated database services. 18 An integration methodology has been designed to meet the above objectives [Spaccapietra 90, 91] Its major features are: automatic resolution of structural conflicts (arising because of different representations of the same real world objects) conflict resolution performed without modification of initial views, use of a formal declarative approach for user (or DBA) definition ....
S. Spaccapietra, C. Parent: View Integration: a Step Forward in Solving Structural Conflicts, EPFL-DI-LBD Research Report, Lausanne, August 1990 (to appear in IEEE Transactions on Knowledge and Data Engineering)
Model Independent Assertions for Integration of.. - Spaccapietra, Parent.. (1992) (80 citations) Self-citation (Spaccapietra) (Correct)
....principle is that the integrated schema has to support queries and updates on all underlying databases. If different constraints hold on related data in different databases, the integrated constraint has to be the weakest one, so that 9 An algorithm for integration of ER views is proposed in [43]. 31 no access request is unduly rejected at the integrated level. For instance, if age of persons is limited to the 20 50 range in database DB1 and database DB2 has more persons than DB1, with age ranging from 20 to 65, the integrated schema will hold a 20 65 age range constraint. The 20 50 ....
S. Spaccapietra, C. Parent: View integration: a step forward in solving structural conflicts, IEEE Transactions on Data and Knowledge Engineering, due to appear October 1992
User-oriented Databases - Spaccapietra Self-citation (Spaccapietra) (Correct)
....independently of other users views. For federated environment, it should support reuse of existing databases and existing application programs, without contradicting the launching of new federated database services. An integration methodology has been designed to meet the above objectives [Spaccapietra 90, 91] Its major features are: automatic resolution of structural conflicts (arising because of different representations of the same real world objects) conflict resolution performed without modification of initial views, use of a formal declarative approach for user (or DBA) definition of ....
S. Spaccapietra, C. Parent: View Integration: a Step Forward in Solving Structural Conflicts, EPFL-DI-LBD Research Report, Lausanne, August 1990 (to appear in IEEE Transactions on Knowledge and Data Engineering)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC