MétaCan
Menu
Back to cohort
Record W2116082280 · doi:10.4000/vertigo.9671

La directive IPPC : où en est-on et où va-t-on ?

2010· article· fr· W2116082280 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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueVertigO · 2010
Typearticle
Languagefr
FieldEnvironmental Science
TopicEnvironmental Policies and Emissions
Canadian institutionsnot available
Fundersnot available
KeywordsHumanitiesPolitical sciencePhilosophy

Abstract

fetched live from OpenAlex

Depuis 1996, la mise en œuvre de la directive IPPC (Integrated Pollution Prevention and Control) est au cœur des débats publics et politiques. Des non-conformités subsistent encore actuellement ; les points bloquants ne sont pas encore totalement levés que déjà une nouvelle directive sur les émissions industrielles se profile à l’horizon.Cette directive IPPC impose notamment aux industriels concernés par cette réglementation d’utiliser des « meilleures techniques disponibles » (MTD). Or, au niveau local, les exploitants n’ont pas les moyens suffisants de justifier qu’ils utilisent des MTD ou des techniques ayant des performances équivalentes. Cet article traite de l’évolution du cadre réglementaire lié à la mise en œuvre de la directive IPPC depuis 1996, en Europe et plus particulièrement en France. Il propose un bilan synthétique des principaux points bloquants à sa mise en œuvre. En conclusion, l’article montre, que grâce à l’analyse approfondie du contexte réglementaire d’application de l’IPPC en Europe, il est important de développer une méthodologie d’évaluation des performances environnementales au sens de l’IPPC.

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 categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.493
Threshold uncertainty score1.000

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.001
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0100.010

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.246
Teacher spread0.239 · 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