PNR: Passenger Name Record, Problems Not Resolved? The EU PNR Conundrum After Opinion 1/15 of the CJEU
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.
Bibliographic record
Abstract
The long-standing debate concerning the transfer, processing and retention by national law enforcement authorities of Passenger Name Record (PNR) data has regained momentum with the adoption of Directive 2016/681/EU, which lays down a PNR regime operating within the EU, and, above all, with the delivery, on 26 July 2017, of the CJEU’s negative Opinion on the new envisaged EU-Canada PNR agreement. The Court’s finding that several provisions of the draft agreement do not comply with Articles 7 and 8 of the EU Charter of Fundamental Rights, on the protection of private life and personal data, inevitably raises doubts concerning the fate of the EU PNR bilateral agreements already in force (namely, with Australia and the United States) and of the PNR Directive. At the same time, this evolving scenario has immediate and very practical implications for air-carriers operating between the EU and third States, which may find themselves trapped by conflicting obligations due to the complex interplay between EU data protection laws, the EU PNR regime, and third States’ PNR legislation. Far from being limited to the EU legal order, the recent developments may exert an effect on foreign airlines’ operations to and from the EU and condition future negotiations between the EU and third countries.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it