P. Mogilevski. Integration and Translation of Heterogeneous Data. M.Sc Thesis, Tel-Aviv University. 1997. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Correspondence and Translation for Heterogeneous Data - Abiteboul, Cluet, Milo (2000) (47 citations) (Correct)
....mapping is fairly easy. We have experimented with various types of data sources (e.g. HTML, SGML, relational, OODB) and with defining correspondences translations between them. A detailed description of the system and of the experiments conducted is beyond the scope of this paper. For details see [24]. As assistance to the user, both the source and the target data (in their middleware format) can be displayed on a graphic window in a tree like representation that is hiding details unnecessary to the restructuring (e.g. tags or parsing information) and starting from that representation, the ....
P. Mogilevski. Integration and translation of heterogeneous data. Technical report, M.Sc Thesis, Tel-Aviv University, 1997.
WebSuite - A Tool Suite for Harnessing Web Data - Beeri, Elber, Milo, Sagiv.. (1998) (16 citations) Self-citation (Mogilevski) (Correct)
....middleware data model. Then, the data is translated from one representation to another. Finally, the data is exported from its second representation to the target. The heart of W3TRANS is its handling of the second phase, namely translations inside the middleware. For that, the TreeLog language [3, 17] is used. It is a rule based declarative language, with a fixpoint semantics. It differs from other rule based languages in its strong 3 tree awareness: it provides syntactic constructs to search and build complex trees that represent data. A significant advantage of the language is that in most ....
P. Mogilevski. Integration and Translation of Heterogeneous Data. M.Sc Thesis, Tel-Aviv University. 1997.
WebSuite-A Tool Suite For Harnessing Web Data - Beeri (1998) (16 citations) Self-citation (Mogilevski) (Correct)
....information) ii) Then, the data is translated from one abstract representation to the other. iii) Finally, the data is exported to the target. Fig. 1 displays our translation scheme. For part (ii) of the translation scheme (translations inside the middleware) we use the TreeLog language [3, 29]. It is a rule based language, with a fixpoint semantics, in the flavor of Datalog. It differs from other rule based languages in its strong tree awareness: it provides syntactic constructs to search and build complex trees that represent data. For lack of space we cannot give here a formal ....
....build complex trees that represent data. For lack of space we cannot give here a formal definition of the middleware model and the TreeLog language, nor can we demonstrate how the language is used for defining useful translations. More details and examples of translation programs can be found in [3, 29]. Nevertheless, we would like to point out one significant advantage of the language with respect to updates. Assume some data has been extracted and translated from one format to the other, and then was updated in the target system. To propagate the update back to the source, one needs to know ....
P. Mogilevski. Integration and Translation of Heterogeneous Data. M.Sc Thesis, Tel-Aviv University. 1997.
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