MétaCan
Menu
Back to cohort
Record W7100081872

THE UNIVERSITY OF CALGARY Improving the Modularity of Context-Sensitive Concerns through the Use of Declarative Event Patterns

2005· article· en· W7100081872 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsnot available
Fundersnot available
KeywordsEvent (particle physics)Modularity (biology)Protocol (science)MaintainabilitySoftwareCommunications protocolProtocol analysisAbstraction
DOInot available

Abstract

fetched live from OpenAlex

Software modules communicate with one another to form coherent software systems. In order to facilitate this interaction, knowledge of the communication protocol is split up and embedded in each participating module, making local reasoning about the protocol difficult. Modules themselves become collectively responsible for seeing that the appropriate sequence of messages transpires. With protocols scattered in this way, and tangled amongst the details that intrinsically belong inside modules, the traceability, comprehensibility, and maintainability of the concern they represent, and of the system as a whole, tend to suffer. Declarative event patterns (DEPs) are a means to implement communication pro-tocols between modules in a localized manner. DEPs describe sequences of events in the execution of a system and include the ability to recognize properly nested structures. They allow a developer to describe a protocol at a high level, without the need to express extraneous details. A developer can indicate that specific actions be taken when a given pattern occurs. Protocol patterns are automatically translated

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.000
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.757
Threshold uncertainty score0.225

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.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.081
GPT teacher head0.282
Teacher spread0.201 · 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