MétaCan
Menu
Back to cohort

Modeling the mashup ecosystem: structure and growth

2009· article· en· W1763236706 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

VenueR and D Management · 2009
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicService and Product Innovation
Canadian institutionsCarleton University
FundersScuola Superiore Sant'Anna
KeywordsMashupComputer scienceWorld Wide WebEcosystemWeb serviceEcologyBiologyWeb 2.0

Abstract

fetched live from OpenAlex

Mashups combine data and services provided by third parties through open APIs (such as Google Maps and Flickr), as well as internal data sources owned by users. The creation of mashups is supported by a complex ecosystem of interconnected data providers, mashup platforms, and users. In this paper, we examine the structure of the mashup ecosystem and its growth over time. Several observations follow from our analysis. First, we can conclude that while the number of new APIs and mashups over time follows a linear growth pattern, the distribution of mashups over APIs is not uniform but follows a power law. This implies that a small number of APIs provides the basis for the majority of mashups, and the other APIs are only used in certain application niches. Second, our analysis suggests that mashup platforms were introduced in response to the increasing complexity of mashups, as mashups evolved from one-feature mashups (widgets). Third, we observe that complementary relationships between open APIs are formed based on the position of the APIs in the ecosystem. The propensity of two APIs to be used together in the same mashup depends on the existing number of mashups to which they both contribute. The growth of the mashup ecosystem follows a pattern where keystone data providers or ‘powerful hubs’ attract niche data providers as complementors, and the positions of keystones in the ecosystem are mutually reinforcing.

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.000
Version: codex-gemma-dda1882f352aValidation 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: Empirical
Teacher disagreement score0.377
Threshold uncertainty score0.269

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.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.012
GPT teacher head0.200
Teacher spread0.188 · 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