MétaCan
Menu
Back to cohort
Record W7095226569

b y r

2016· article· en· W7095226569 on OpenAlexaboutno aff

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldSocial Sciences
TopicPrivacy, Security, and Data Protection
Canadian institutionsnot available
Fundersnot available
KeywordsInformation privacyPrivacy by DesignPrivacy policyInformation privacy lawDirectivePrivacy softwareFTC Fair Information PracticeData Protection Act 1998Commission
DOInot available

Abstract

fetched live from OpenAlex

control is a social value deeply embedded in our societies. A global survey found that 88 % of people are worried about who has access to their data; over 80 % expect governments to regulate privacy and impose penalties on companies that do not use data re-sponsibly. But privacy regulation is not easy. The Internet’s current economics as well as national security manage-ment benefit from the collection and use of rich user profiles. Technology constantly changes. And data is like water: it flows and ripples in ways that are difficult to predict. As a result, even a well-conceived, general, and sustain-able privacy regulation, such as the European Data Protection Directive 95/46/EC, struggles to ensure its ef-fectiveness. Companies regularly test legal boundaries and many risk sanc-tions for privacy breaches to avoid con-straining their business. Against this background, the Eu-ropean Commission and other regu-latory bodies are looking for a more effective, system- and context-specific balance between citizens ’ privacy rights and the data needs of compa-nies and governments. The apparent solution proposed by regulators now, but barely specified, is Privacy by De-sign (PbD). At first sight, the power-ful term seems to suggest we simply need to take a few Privacy-Enhancing Technologies (PETs) and add a good dose of security, thereby creating a fault-proof systems ’ landscape for the future. But the reality is much more challenging. According to Ann Cavoukian, the Ontario information and privacy commissioner who first coined the term, PbD stands for a pro-active integration of technical privacy principles in a system’s design (such as privacy default settings or end-to-end security of personal data) and the recognition of privacy in a company’s risk management processes.1 PbD can thus be defined as “an engineering and strategic management approach that commits to selectively and sus-tainably minimize information sys-tems ’ privacy risks through technical and governance controls.”

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 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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
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.958
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.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.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.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.034
GPT teacher head0.313
Teacher spread0.278 · 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 teacher head, not a consensus.

Study designNot applicable
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

Citations0
Published2016
Admission routes1
Has abstractyes

Explore more

Same topicPrivacy, Security, and Data ProtectionFrench-language works237,207