MétaCan
Menu
Back to cohort
Record W2029752352 · doi:10.1142/s0218843007001676

SUPPORTING DISTRIBUTED EVENT-CONDITION-ACTION RULES IN A MULTIDATABASE ENVIRONMENT

2007· article· en· W2029752352 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueInternational Journal of Cooperative Information Systems · 2007
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Database Systems and Queries
Canadian institutionsUniversity of TorontoWilfrid Laurier UniversityUniversity of Ottawa
Fundersnot available
KeywordsComputer scienceOperandEvent (particle physics)Programming languageSemantics (computer science)Active databaseExecution modelSet (abstract data type)Specification languageDatabaseTheoretical computer scienceDistributed computingOperating system

Abstract

fetched live from OpenAlex

We describe a mechanism based on distributed Event-Condition-Action (ECA) rules that supports data coordination in a multidatabase setting. The proposed mechanism includes an ECA rule language and a rule execution engine that transforms rules when they are first posted, and then coordinates their execution. Like traditional ECA rules, our ECA rule language has three parts: an event language, a condition language, and an action language. The event language provides a set of operators with a formal semantics for a multidatabase environment, and which allows a wide variety of composite events. The condition language provides Boolean algebra operators that take as operands either composite or simple conditions. The action language provides a conjunction of simple or composite actions. The execution model partitions rules to more easily manageable forms, distributes them to relevant databases, monitors their execution and composes their evaluations. The mechanism has been designed in a manner that minimizes the number of messages that need to be exchanged over the network. We have also conducted an experimental evaluation to compare the implementation with a naïve centralized execution model. The paper also presents a prototype implementation as well as experimental results on its performance. This work is part of an on-going project intended to develop data coordination techniques for data sharing settings.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.945
Threshold uncertainty score0.529

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.007
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.016
GPT teacher head0.320
Teacher spread0.305 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it