TALE — A temporal active language and execution model

Avigdor Gal, Opher Etzion, Arie Segev

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Complex applications in domains such as decision support systems and real time systems require a functionality that is achieved by combining the active and temporal database technologies. In this paper we present TALE, a Temporal Active Language and Execution model. TALE is a temporal active database programming language, combined with an execution model that enables a correct and efficient processing of operations. As such, TALE is a step in accommodating software engineering challenges in modern information systems. TALE primitives are presented using examples and an EBNF. The run-time control mechanism of the model is introduced and TALE properties, namely active and temporal capabilities, and reflective programming capabilities are discussed.

Original languageEnglish
Title of host publicationAdvanced Information Systems Engineering - 8th International Conference, CAiSE 1996, Proceedings
EditorsPanos Constantopoulos, John Mylopoulos, John Mylopoulos, Yannis Vassiliou
Pages60-81
Number of pages22
DOIs
StatePublished - 1996
Event8th International Conference on Advanced Information Systems Engineering, CAiSE 1996 - Heraklion, Greece
Duration: 20 May 199624 May 1996

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume1080
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference8th International Conference on Advanced Information Systems Engineering, CAiSE 1996
Country/TerritoryGreece
CityHeraklion
Period20/05/9624/05/96

Keywords

  • Active databases
  • Database programming languages
  • Information modeling
  • Temporal databases

ASJC Scopus subject areas

  • Theoretical Computer Science
  • General Computer Science

Fingerprint

Dive into the research topics of 'TALE — A temporal active language and execution model'. Together they form a unique fingerprint.

Cite this