MétaCan
Menu
Back to cohort
Record W3194777318 · doi:10.1093/indlaw/dwab019

International Employment Cases Post-Brexit: Choice of Law, Territorial Scope, Jurisdiction and Enforcement

2021· article· en· W3194777318 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

VenueIndustrial Law Journal · 2021
Typearticle
Languageen
FieldSocial Sciences
TopicDiscrimination and Equality Law
Canadian institutionsTrinity College
Fundersnot available
KeywordsChoice of lawJurisdictionBrexitScope (computer science)Conflict of lawsLawInternational lawPolitical scienceEnforcementMunicipal lawExclusive jurisdictionInterpretation (philosophy)Common lawLaw and economicsEconomicsBusinessInternational tradeEuropean union

Abstract

fetched live from OpenAlex

Abstract The globalisation of employment relationships means that the international aspects of employment law are important in an ever growing number of cases. In particular, international employment cases may raise issues relating to international jurisdiction, choice of law and territorial scope. Before the UK left the EU, directly effective EU Regulations regulating jurisdiction and choice of law provided the rules which are applied in a large number of cases. This article outlines the changes post-Brexit and the resulting overlapping regimes which now govern international employment cases. The choice of law rules in the Rome I Regulation and Rome II Regulation remain as part of retained EU law. International jurisdiction will now be governed entirely by national law rules. However, for cases in the High Court, the common law rules are amended to mirror the provisions which are previously applied under the Brussels I Regulation recast. Although in many cases the rules look the same, different principles of interpretation will apply, and, longer term, now that the rules are not binding as matter of EU there will be scope to amend and reform the rules.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.987
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.123
GPT teacher head0.384
Teacher spread0.261 · 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