MétaCan
Menu
Back to cohort
Record W2962376450

Beyond the Clouds, Part 2: What Happens to the Files You Store in the Clouds When You Die?

2019· article· en· W2962376450 on OpenAlexaboutno aff
Johan David Michels, Dimitra Kamarinou, Christopher Millard

Bibliographic record

VenueSSRN Electronic Journal · 2019
Typearticle
Languageen
FieldComputer Science
TopicBlockchain Technology Applications and Security
Canadian institutionsnot available
Fundersnot available
KeywordsCloud computingReal estatePrivacy rightsRelation (database)Point (geometry)LawDigital rights managementInternet privacyLaw and economicsPolitical scienceBusinessComputer securityComputer scienceInformation privacySociologyDatabase
DOInot available

Abstract

fetched live from OpenAlex

This paper considers what happens to users’ rights in relation to the digital files they have stored in the cloud when they die. It is based in part on a survey of the terms and conditions of popular consumer-facing cloud services. A minority of cloud terms of service explicitly exclude heirs inheriting rights to access files stored in the cloud. Most terms do not address the point directly, but instead exclude the assignment of users’ contractual rights and copyright licenses. As a result, these rights and licenses do not constitute things in action. We argue that such rights will therefore not form part of the user’s estate and so not be transmitted to his or her heirs when the user dies. Unlike for physical assets, heirs therefore lack a clear legal claim to recover a deceased’s digital files from the cloud, many of which may instead be lost or deleted. This paper considers the extent to which this outcome could be challenged under consumer protection law and whether the law should be amended so as to grant heirs rights of access to digital assets. The paper focuses on English law, while drawing on examples from Canada, the United States, Germany, France, and the Netherlands.

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.003
metaresearch head score (Gemma)0.010
Version: metacan-v3-hybrid-931329e0061cValidation 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.037
Threshold uncertainty score0.074

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0030.010
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
Science and technology studies0.0050.012
Scholarly communication0.0090.023
Open science0.0010.004
Research integrity0.0050.004
Insufficient payload (model declined to judge)0.0160.002

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.007
GPT teacher head0.223
Teacher spread0.216 · 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 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

Citations2
Published2019
Admission routes1
Has abstractyes

Explore more

Same venueSSRN Electronic JournalSame topicBlockchain Technology Applications and SecurityFrench-language works237,207