MétaCan
Menu
Back to cohort
Record W4400090684 · doi:10.9785/cri-2024-250304

Yes, This Is A Puff Piece? A Comparative Analysis of the Vendor Defences of Puffery, Statements of Future Intent and Disclaimers — How far does the divergence between promised and actual capabilities of an ERP implementation stretch until the ERP vendor is liable … and then stretch further until the ERP vendor is no longer liable?

2024· article· en· W4400090684 on OpenAlexaboutno aff
John Beardwood

Bibliographic record

VenueComputer Law Review International · 2024
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicERP Systems Implementation and Impact
Canadian institutionsnot available
Fundersnot available
KeywordsVendorDivergence (linguistics)BusinessAdvertisingMarketingPhilosophyLinguistics

Abstract

fetched live from OpenAlex

Abstract In past articles we have reviewed critical lessons learned from various failed ERP implementations and outsourcing transactions. One of the common themes is the divergence between the representations made by technology vendor sales teams as to promised skills, expertise and delivery, and the actually provided skills, expertise and delivery. In turn, the analysis of the resulting lawsuits has emerged, in response to customer allegations of negligent misrepresentation and fraudulent misrepresentation, the vendor defences of puffery and opinion, statements of future intent, and contractual disclaimer. The article begins in this Part 1 by providing an overview of the law of misrepresentation, and then the common vendor defences of puffery and opinion, statements of future intent, and contractual disclaimers, in Canada (I) and in the United States (II). Part 2 will then complete the overview with a look at the European Union (III) and an assessment how these defences were raised by vendors in two recent ERP failure lawsuits (IV), before concluding with lessons learned for vendors and customers (V).

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.035
metaresearch head score (Gemma)0.103
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.035
Threshold uncertainty score0.184

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0350.103
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0040.005
Science and technology studies0.0050.013
Scholarly communication0.0100.013
Open science0.0010.003
Research integrity0.0030.004
Insufficient payload (model declined to judge)0.0050.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.031
GPT teacher head0.332
Teacher spread0.301 · 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 designQualitative
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
Published2024
Admission routes1
Has abstractyes

Explore more

Same venueComputer Law Review InternationalSame topicERP Systems Implementation and ImpactFrench-language works237,207