MétaCan
Menu
Back to cohort
Record W2291652304 · doi:10.1109/repa.2015.7407733

Reusing knowledge on delivering privacy and transparency together

2015· article· en· W2291652304 on OpenAlexaffabout
Olena Zinovatna, Luiz Marcio Cysneiros

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Software Engineering Methodologies
Canadian institutionsYork University
Fundersnot available
KeywordsTransparency (behavior)Computer sciencePersonally identifiable informationInterdependenceInternet privacyComputer securityPasswordInformation privacySoftwarePrivacy softwarePrivacy by DesignReuseWorld Wide WebEngineering

Abstract

fetched live from OpenAlex

Heavy reliance on modern technologies causes the concepts of transparency and privacy to become more and more intertwined. Some recent privacy incidents illustrates that, such as: sharing of personal health information between United States and Canadian border services agencies; enabling voice recognition software by default in Samsung's smart TVs; accidentally collecting personal information such as emails, addresses, user IDs and passwords by Google Street View car. However, all of these incidents lack transparency in disclosing features that could trigger privacy violation; leaving the general public unaware of what, how and when their personal information or information about their behaviour is being collected and used. Developing software that addresses both qualities is a challenge. Capturing patterns of knowledge that represent alternatives to achieve Privacy requirements together with Transparency properties can help software engineers to model more comprehensive solutions. We use Softgoal Interdependencies Graphs (SIG) to capture such patterns. This paper demonstrates a set of softgoal interdependency graphs (SIG) illustrating how transparency and privacy impact each other.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.015
metaresearch head score (Gemma)0.043
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.015
Threshold uncertainty score0.080

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0150.043
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0010.003
Bibliometrics0.0050.003
Science and technology studies0.0030.012
Scholarly communication0.0070.024
Open science0.0030.013
Research integrity0.0030.005
Insufficient payload (model declined to judge)0.0040.001

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.135
GPT teacher head0.331
Teacher spread0.196 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations19
Published2015
Admission routes2
Has abstractyes

Explore more

Same topicAdvanced Software Engineering MethodologiesFrench-language works237,207