MétaCan
Menu
Back to cohort
Record W2019412575 · doi:10.1108/14636690710816426

When standards become business models: reinterpreting “failure” in the standardization paradigm

2007· article· en· W2019412575 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.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueInfo · 2007
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicDigital Platforms and Economics
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsStandardizationInteroperabilityBusiness modelComputer scienceProcess (computing)Process managementKnowledge managementBusinessMarketingWorld Wide Web

Abstract

fetched live from OpenAlex

Purpose This paper aims to explore the question: “What is the relationship between standards and business models?” and illustrate the conceptual linkage with reference to developments in the mobile communications industry. Design/methodology/approach A succinct overview of literature on standardization, business models and platform markets in the paper leads to a hypothesis on the relationship between present‐day standardization processes and business model design. This is then explored by means of three short case studies. Findings The case studies of Mobile‐ICT illustrate that regardless of institutional orientation or process, the most important standardization strategy for equipment and service providers is to create platforms that are open to the development of complementary products and services while at the same time preserving the proprietary edge necessary to ensure lock‐in effects. All three cases yielded strong reasons to doubt whether many of the traditional advantages of standardization (interoperability, economies of scale, positive externalities, etc.) will be achieved equitably for all of the stakeholders. Originality/value This is an exploratory paper that aims to shed light on present‐day concerns about “failure” in the standardisation paradigm.

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.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.497
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0010.006
Open science0.0000.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.017
GPT teacher head0.225
Teacher spread0.208 · 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