MétaCan
Menu
Back to cohort
Record W2136355198 · doi:10.1109/mcetech.2008.23

SecurityViews: A Dynamic Security for View-Oriented Programming

2008· article· en· W2136355198 on OpenAlex
Hamid Mcheick, Eric Dallaire

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

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsUniversité du Québec à Chicoutimi
Fundersnot available
KeywordsComputer scienceAdaptation (eye)Aspect-oriented programmingObject-oriented programmingSoftware engineeringJavaContext (archaeology)Distributed objectDomain (mathematical analysis)Software developmentObject (grammar)SoftwareDistributed computingProgramming languageCommon Object Request Broker ArchitectureArtificial intelligence

Abstract

fetched live from OpenAlex

In wide-enterprise information systems, the same objects play different functional roles during their lifecycle. The development and the distributtion of these functional roles can be realized using one of the aspect oriented software development techniques, in particular view oriented programming (VOP). Generally speaking, views are code fragments, which provide the implementation of different functionalities for the same object domain and theses views can be used as a units for distribution to improve performance issues. Therefore, using VOP encompasses a combination of views, which can be distributed, attached, detached dynamically throughout their object views lifecycle. In this context, an issue has to be addressed when a distributed object offers different views to different clients. A security access problem would be if a client somehow tries to perform an operation of a view, which is not attached by that client. Another issue has to be addressed is to manage views in a transparent way (implicitly) for clients. We propose a dynamic adaptation and security model based on Java security model to deal with theses issues.

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: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.636
Threshold uncertainty score0.629

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.034
GPT teacher head0.308
Teacher spread0.274 · 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